Listen to the Interview

Subscribe: Google Podcasts | Stitcher | TuneIn | RSS

How can product managers help their organizations become more innovative? That is the topic of this discussion with the author of Innovation Wars: Driving Successful Corporate Innovation Programs.

The author is Scott Bale, a technology & innovation evangelist. Scott has been a serial entrepreneur, speaker at TEDx, and now runs Innovation Labs Asia, based in Singapore. In the interview, Scott shares a model for helping organizations be more innovative that consists of 4 C’s:

• Context
• Culture development
• Capability, and
• Collaboration

 

Practices and Ideas for Product Managers and Innovators

Summary of questions discussed:

• Your book Innovation Wars is a guide book for product managers to help their organizations become more innovative. It addresses several tools for taking the guess work out of creating and launching successful products. Let’s start by talking about how you get your customers to innovate for you. Can you tell us about that? Innovation is a very creative process. The reason to co-create with customers is to ensure you are building products that customers need and want. There are many examples of companies that have done this but that are not well-known for it, including Apple, Tesla, and Facebook. Also, look at the related problems or jobs customers need to solve. For example, when someone gets a mortgage, they likely will be moving and moving is painful. A bank that provided a mortgage that also helped you move would create a competitive advantage.

• How can we start with co-creating? I use a framework inspired from the world of Design Thinking that I call the 4 C model: Context, Culture development, Capability, and Collaboration. Co-creating is part of Capability. Start with what facts you know about your customer. Then identify their aspirations and goals – the job they need done. Knowing that, identify the obstacle or challenge in achieving the goal. Uncover what they have already tried to solve the problem and what their existing behaviors are. These are the early adopters who want to solve the problem but have not found a satisfactory solution yet and represents a persona to find early adopters.

• Can you take us through rest of the 4 C model? The first C is context – how do you structure yourself and create an environment for innovation. Next is Culture development, which is developing a culture of curiosity, experimentation, and the role of failure. Capability is the third C. This involves quantifying the value of an idea and the elements we discussed previously. Lean Startup practices can be used here. The final C is Collaboration – look for partners and others in the supply chain of a product to add value.

• What else do we need to know? We need to apply Assumption Exploration. This is where hypotheses are created and tested to better understand the customer problem. You need to examine what you are assuming about the customer problem and solution. Focus first on the assumptions with the deepest impact and risk and design an experiment to test these assumptions. Steve Blank’s work to test hypotheses is the basis of this exploration. Interviews with people representing the persona you created can be used to test hypotheses. If an assumption is wrong, refocus the persona or the problem to solve and test again. When conducting the assumption tests, look for patterns that invalidate or validate an assumption.

 

Useful links:

• Innovation Wars, Scott’s newest book
• Scott’s website
• Scott’s LinkedIn Profile

 

Innovation Quote

“How will you know how to speak to your customers if you never speak to your customers.” –Will Evans

 

Thanks!

Thank you for being an Everyday Innovator and learning with me from the successes and failures of product innovators, managers, and developers. If you enjoyed the discussion, help out a fellow product manager by sharing it using the social media buttons you see below.