I had a coffee chat last week with the Chief Information Officer (CIO) of an ASX100 manufacturing company. In a very traditional and process-driven organization she wants her team to lead cross-functional innovation initiatives and has introduced hack days to initiate a spark. She was concerned about how to keep momentum after a hack day. So she approached me to draw on my experience of helping Global 500 companies create innovation ecosystems.
Wikipedia: a hackathon (also known as a hack day hack fest or code fest) is a design sprint-like event in which computer programmers and others involved in software development, including graphic designers, interface designers, project managers, and others, often including domain experts, collaborate intensively on software projects.
In this company, she wants to use hack days as a way for her technology team to contribute to resolve problems experienced by employees or customers. Just the week before, she had organized and facilitated the first hack day.
It was a big success and three self-organized teams had formed on three different ideas that had picked up momentum throughout the day. Those three ideas were all efficiency innovation. They were about improving existing business processes, rather than exploring new products, services or businesses.
But even though they were still relatively close to current business they were also different enough for the team to be hesitant about the way to progress them further after the hack day. And as days passed by, she was growing worried that momentum and energy would be lost and that the hack day would lead to no tangible outcome.
She had a deep sense of opportunity for real change but felt she had to act quickly. I asked her what her real purpose was with these hack days. If she looked beyond her immediate need to support those three teams, what was the long-term objective? She acknowledged that delivering on those three ideas was not the end game.
“This is just the first step in a much longer journey to develop the ability to adapt and change as an organization”, she said.
2. Innovation Readiness
With more clarity on the long-term objective we zoomed back on the immediate need.
“How ready is the organization to support those three teams today? What can they piggy back on? What is missing?”
To help her with this I showed her the innovation readiness assessment tool we developed at Strategyzer. It helps leaders identify strengths and weaknesses in their innovation ecosystem, and also acknowledge their current blind spots (i.e. the things they should be doing to nurture a thriving innovation ecosystem that they are not even aware of).
As my colleague Tendayi Viki writes:
“At the moment, companies are jumping in feet first, looking to innovate before they’ve done the work to assess their level of readiness to nurture innovation and build the right internal structures and environment.”
Score your organization for the 3 following categories:
- Leadership Support
- Organization Design
- Innovation Practice
The tool focuses on the three critical areas of leadership support, organizational design and innovation practice. I also explained how powerful the tool is as a workshop exercise to align key stakeholders on:
She jumped on this idea and said that the two most urgent improvement areas would be innovation tools and process management. Teams out of hack days needed to be urgently equipped with a toolkit and a process they could follow to progress their innovation idea from a hack day experience to a delivered outcome.
3. Mapping The Innovation Ecosystem
Executives develop a strong capability for quick decision-making, but I wanted to make sure she was not settling on those improvement areas too quickly. So I walked her through the other “usual suspects” in my experience, the typical weaknesses and blind spots I see in organizations that prevent innovation initiatives to come to fruition (e.g. wrong incentive system, inadequate portfolio governance model, experience gap, fragile leadership support). And I told her about the scaffolding elements we usually have to put in place to make sure innovation initiatives have the best chance of success. I did a quick drawing using the visual framework I developed for business transformation or innovation ecosystem design.
The framework shows:
With what she had shared so far the visual representation looked like this:
And I told her she should keep updating the framework as her understanding of the innovation ecosystem in her company developed. As it happens so often when we get in flow, time flies and our coffee catchup came to quite an abrupt stop as we ran out of time.
As we were leaving, she told me she realized that building a strong change capability would be a marathon and not a sprint. She was absolutely fine with a phased approach, and with an initial model that would be small and not perfect.
It just had to be fit for purpose. She asked me if we could meet again soon to flesh out the setup of a minimal toolkit and process to support teams out of hack days.
“With pleasure,” I said. “But for now, sorry, got to run to my next meeting...”
Recap on how to keep momentum after a hack day: