TEI 286: Get the 5-step process that is changing how innovation works in organizations across the world – with Pete Newell
Summary: How product managers can lead innovation and help transform their organization<br> My guest is changing how companies innovate and he is doing it with a 5-step process. You’ll hear the details in the discussion, but the five steps are called:<br> <br> * sourcing,<br> * curation,<br> * discovery,<br> * incubation, and<br> * transition.<br> <br> He created this process as an Army Colonel and former director of the Army’s Rapid Equipping Force, where he deployed a record 170 new products. He was leading innovation in the challenging environments of Iraq and Afghanistan battlefields. Now he is improving innovation effectiveness in companies. He is also working with Steve Blank on a book to capture and share the innovation process. But, you can get the key insights now, long before the book is published.<br> Summary of some concepts discussed for product managers<br> [2:59] How do you define innovation?<br> Innovation is the delivery of something that either changes people’s lives or significantly changes business. Nothing is an innovation until it delivers something to somebody that changes behavior or solves a problem. And innovation must be scalable.<br> [4:35] Can you walk us through your 5-stage innovation process outlined in the Harvard Business Review article you wrote with Steve Blank (see link below)?<br> The innovation process has five stages and an operating system that allows all the different methodologies, decision points, and data to connect to ensure an adequate throughput.<br> [5:40] Sourcing<br> This stage is about sourcing people, ideas, problems, and technologies—finding what’s out there. Hackathons are useful for sourcing people. My company created a problem-sourcing seminar where we trained teams to go into the organization and vigilantly discover problems. Tech scouting—visiting conventions and talking to people working on problems— is another great way to source problems.<br> [15:55] Curation<br> Dis-aggregate complex problems into smaller issues, then prioritize the issues and build teams around them. Begin to prioritize based on risk and impact and determine which team would be best for each problem. Prioritization tells you why you’re working on what. Look at the quality of the team and the problem, and the pathways that you have to follow to the next step. In order to ensure throughput in your innovation pipeline, make sure you have the best, most ready things moving to the next step. Those things might not necessarily be the highest priorities in the long-run, but they are what create the most value that you can accomplish right now.<br> [23:45] Discovery<br> Answer the questions, “Do we have the right problem? Can we define what success in solving it looks like? Do we know whom we’re solving it for?” Next prove that you have a viable solution and a way of deploying that solution to the customer. Finally, consider whether the cost ratio is feasible. We run multiple ideas at once in Discovery, but only about 1/4 of curated ideas make it to Discovery.<br> [9:10] Incubation<br> We determine readiness in three levels: Technology readiness—do we understand the technology involved in solving this problem? Investment readiness—do I have the right team or do I need to add someone to the team? Adoption readiness—have I identified the first customers, am I ready to scale, and do I have the team to get the innovation to users?<br> [10:30] Transition<br> Transition the innovation back into the business. It must scale appropriately with the right people. It must be sustainable, meaning that we can train people to work on it and can keep updating it. You don’t have an innovation until you’ve transitioned it into the real environment. Everything prior to that is learning about the problem.<br> Bonus Question<br> [35:35] How does the innovation process work in times of crisis?<br>
