https://steveblank.com/2022/10/25/a-simple-map-for-innovation-at-scale/ * Home * About Steve * Startup Books * Slides/Videos * Fund Raising * Tools! * Secret History [cropped-10] [bg_header_] Steve Blank Entries RSS | Comments RSS [ ] [Search] * Email Subscription Enter your email address to subscribe to this blog and receive notifications of new posts by email. Email Address [ ] Sign me up! Join 55,021 other subscribers * Entrepreneurship is a Calling See more how to Startup videos here * Categories + 2 Minute Lessons (15) + Air Force (18) + Ardent (9) + Business Model versus Business Plan (64) + California Coastal Commission (9) + China (8) + Commencement Speeches (9) + Conservation (4) + Convergent Technologies (4) + Corporate/Gov't Innovation (114) + Covid-19/Recovery (9) + Customer Development (316) + Customer Development Manifesto (34) + E.piphany (12) + Educators Summit (7) + ESL (8) + Family/Career/Culture (79) + Gordian Knot Center for National Security Innovation (7) + Hacking For Defense (38) + Hacking for Diplomacy (10) + Hacking for Recovery (5) + Harvard Business Review (11) + Innovation Doctrine (2) + Innovation Outposts (4) + Investment Readiness Level (6) + Lean LaunchPad (114) + Life Sciences (NIH) (26) + Market Types (15) + Marketing (27) + MIPS Computers (2) + National Security (29) + Navy (4) + NIH (National Institutes of Health) (17) + NSF (National Science Foundation) (18) + Rocket Science Games (10) + Science and Industrial Policy (26) + Secret History of Silicon Valley (23) + SiriusXM Radio Show (50) + SuperMac (12) + Teaching (176) + Technology (82) + Technology Innovation and Great Power Competition (13) + Technology Innovation and Modern War (20) + Tesla (5) + Uncategorized (8) + Venture Capital (80) + Vertical Markets (5) + Zilog (5) * Get Steve Blank via your RSS Feed + RSS - Posts + RSS - Comments * Recent Posts + A Simple Map for Innovation at Scale + Mapping the Unknown - The Ten Steps to Map Any Industry + National Industrial Policy - Private Capital and The America's Frontier Fund Steps Up + Finding and Growing the Islands of Innovation inside a large company - Action Plan for A New CTO + Artificial Intelligence and Machine Learning- Explained + Lessons for the DoD - From Ukraine and China + Cram Down - A Test of Character for VCs and Founders + Here's What Happened When Deputy Secretary of Defense Dr. Kathleen Hicks visited Stanford's Gordian Knot Center for National Security Innovation + The Quantum Technology Ecosystem - Explained + The Semiconductor Ecosystem - Explained * [ ] [Search] * Archives + October 2022 + September 2022 + June 2022 + May 2022 + April 2022 + March 2022 + January 2022 + December 2021 + November 2021 + October 2021 + September 2021 + August 2021 + July 2021 + June 2021 + May 2021 + April 2021 + March 2021 + February 2021 + January 2021 + December 2020 + November 2020 + October 2020 + September 2020 + August 2020 + July 2020 + June 2020 + May 2020 + April 2020 + March 2020 + February 2020 + January 2020 + December 2019 + November 2019 + October 2019 + September 2019 + June 2019 + May 2019 + April 2019 + March 2019 + January 2019 + December 2018 + November 2018 + October 2018 + September 2018 + August 2018 + July 2018 + June 2018 + April 2018 + March 2018 + February 2018 + January 2018 + November 2017 + October 2017 + September 2017 + August 2017 + July 2017 + June 2017 + May 2017 + April 2017 + March 2017 + February 2017 + January 2017 + December 2016 + November 2016 + October 2016 + September 2016 + August 2016 + July 2016 + June 2016 + May 2016 + April 2016 + March 2016 + February 2016 + January 2016 + December 2015 + November 2015 + October 2015 + September 2015 + August 2015 + July 2015 + June 2015 + May 2015 + March 2015 + February 2015 + January 2015 + December 2014 + November 2014 + October 2014 + September 2014 + August 2014 + July 2014 + June 2014 + May 2014 + April 2014 + March 2014 + February 2014 + January 2014 + December 2013 + November 2013 + October 2013 + September 2013 + August 2013 + July 2013 + June 2013 + May 2013 + April 2013 + March 2013 + February 2013 + January 2013 + December 2012 + November 2012 + October 2012 + September 2012 + August 2012 + July 2012 + June 2012 + May 2012 + April 2012 + March 2012 + February 2012 + January 2012 + December 2011 + November 2011 + October 2011 + September 2011 + August 2011 + July 2011 + June 2011 + May 2011 + April 2011 + March 2011 + February 2011 + January 2011 + December 2010 + November 2010 + October 2010 + September 2010 + August 2010 + July 2010 + June 2010 + May 2010 + April 2010 + March 2010 + February 2010 + January 2010 + December 2009 + November 2009 + October 2009 + September 2009 + August 2009 + July 2009 + June 2009 + May 2009 + April 2009 + March 2009 + February 2009 * Other Stuff + About Steve + Startup Tools + Secret History + Books for Startups + Slides/Videos + Raising Money A Simple Map for Innovation at Scale Posted on October 25, 2022 by steve blank [BCG][BCG]An edited version of this article previously appeared in the Boston Consulting Group's strategy think tank website. I spent last week at a global Fortune 50 company offsite watching them grapple with disruption. This 100+-year-old company has seven major product divisions, each with hundreds of products. Currently a market leader, they're watching a new and relentless competitor with more money, more people and more advanced technology appear seemingly out of nowhere, attempting to grab customers and gain market share. [Hokusai-tidal-wave-small][Hokusai-tidal-wave-small] This company was so serious about dealing with this threat (they described it as "existential to their survival") that they had mobilized the entire corporation to come up with new solutions. This wasn't a small undertaking, because the threats were coming from multiple areas in multiple dimensions; How do they embrace new technologies? How do they convert existing manufacturing plants (and their workforce) for a completely new set of technologies? How do they bring on new supply chains? How do they become present on new social media and communications channels? How do they connect with a new generation of customers who had no brand loyalty? How to they use the new distribution channels competitors have adopted? How do they make these transitions without alienating and losing their existing customers, distribution channels and partners? And how do they motivate their most important asset - their people - to operate with speed, urgency, and passion? The company believed they had a handful of years to solve these problems before their decline would become irreversible. This meeting was a biannual gathering of all the leadership involved in the corporate-wide initiatives to out-innovate their new disruptors. They called it the "Tsunami Initiative" to emphasize they were fighting the tidal wave of creative destruction engulfing their industry. To succeed they realized this isn't simply coming up with one new product. It meant pivoting an entire company - and its culture. The scale of solutions needed dwarf anything a single startup would be working on. The company had hired a leading management consulting firm that helped them select 15 critical areas of change the Tsunami Initiative was tasked to work on. My hosts, John and Avika, at the offsite were the co-leads overseeing the 15 topic areas. The consulting firm suggested that they organize these 15 topic areas as a matrix organization, and the ballroom was filled with several hundred people from across their company - action groups and subgroups with people from across the company: engineering, manufacturing, market analysis and collection, distribution channels, and sales. Some of the teams even included some of their close partners. Over a thousand more were working on the projects in offices scattered across the globe. John and Avika had invited me to look at their innovation process and offer some suggestions. Are these the real problems? This was one of the best organized innovation initiatives I have seen. All 15 topic had team leads presenting poster sessions, there were presenters from the field sales and partners emphasizing the urgency and specificity of the problems, and there were breakout sessions where the topic area teams brainstormed with each other. After the end of the day people gathered around the firepit for informal conversations. It was a testament to John and Avika's leadership that even off duty people were passionately debating how to solve these problems. It was an amazing display of organizational esprit de corps. While the subject of each of the 15 topic areas had been suggested by the consulting firm, it was in conjunction with the company's corporate strategy group, and the people who generated these topic area requirements were part of the offsite. Not only were the requirements people in attendance but so was a transition team to facilitate the delivery of the products from these topic teams into production and sales. However, I noticed that several of the requirements from corporate strategy seemed to be priorities given to them from others (e.g. here are the problems the CFO or CEO or board thinks we ought to work on) or likely here are the topics the consulting firm thought they should focus on) and/or were from subject matter experts (e.g. I'm the expert in this field. No need to talk to anyone else; here's what we need). It appeared the corporate strategy group was delivering problems as fixed requirements, e.g. deliver these specific features and functions the solution ought to provide. Here was a major effort involving lots of people but missing the chance to get the root cause of the problems. I told John and Avika that I understood some requirements were known and immutable. However, when all of the requirements are handed to the action teams this way the assumption is that the problems have been validated, and the teams do not need to do any further exploration of the problem space themselves. Those tight bounds on requirements constrain the ability of the topic area action teams to: * Deeply understand the problems - who are the customers, internal stakeholders (sales, other departments) and beneficiaries (shareholders, etc.)? How to adjudicate between them, priority of the solution, timing of the solutions, minimum feature set, dependencies, etc. * Figure out whether the problem is a symptom of something more important * Understand whether the problem is immediately solvable, requires multiple minimum viable products to test several solutions, or needs more R&D I noticed that with all of the requirements fixed upfront, instead of having a freedom to innovate, the topic area action teams had become extensions of existing product development groups. They were getting trapped into existing mindsets and were likely producing far less than they were capable of. This is a common mistake corporate innovation teams tend to make. I reminded them that when team members get out of their buildings and comfort zones, and directly talk to, observe, and interact with the customers, stakeholders and beneficiaries, it allows them to be agile, and the solutions they deliver will be needed, timely, relevant and take less time and resources to develop. It's the difference between admiring a problem and solving one. As I mentioned this, I realized having all fixed requirements is a symptom of something else more interesting - how the topic leads and team members were organized. From where I sat, it seemed there was a lack of a common framework and process. Give the Topic Areas a Common Framework I asked John and Avika if they had considered offering the topic action team leaders and their team members a simple conceptual framework (one picture) and common language. I suggested this would allow the teams to know when and how to "ideate" and incorporate innovative ideas that accelerate better outcomes. The framework would use the initial corporate strategy requirements as a starting point rather than a fixed destination. See the diagram. I drew them a simple chart and explained that most problems start in the bottom right box. [Validating-problems][Validating-problems]These are "unvalidated" problems. Teams would use a customer discovery process to validate them. (At times some problems might require more R&D before they can be solved.) Once the problems are validated, teams move to the box on the bottom left and explore multiple solutions. Both boxes on the bottom are where ideation and innovation-type of problem/solution brainstorming are critical. At times this can be accelerated by bringing in the horizon 3, out-of-the-box thinkers that every company has, and let them lend their critical eye to the problem/solution. If a solution is found and solves the problem, the team heads up to the box on the top left. But I explained that very often the solution is unknown. In that case think about having the teams do a "technical terrain walk." This is the process of describing the problem to multiple sources (vendors, internal developers, other internal programs) debriefing on the sum of what was found. A terrain walk often discovers that the problem is actually a symptom of another problem or that the sources see it as a different version of the problem. Or that an existing solution already exists or can be modified to fit. But often, no existing solution exists. In this case, teams could head to the box on the top right and build Minimal Viable Products - the smallest feature set to test with customers and partners. This MVP testing often results in new learnings from the customers, beneficiaries, and stakeholders - for example, they may tell the topic developer that the first 20% of the deliverable is "good enough" or the problem has changed, or the timing has changed, or it needs to be compatible with something else, etc. Finally, when a solution is wanted by customers/beneficiaries/stakeholders and is technically feasible, then the teams move to the box on the top left. The result of this would be teams rapidly iterating to deliver solutions wanted and needed by customers within the limited time the company had left. Creative destruction Those companies that make it do so with an integrated effort of inspired and visionary leadership, motivated people, innovative products, and relentless execution and passion. Watching and listening to hundreds of people fighting the tsunami in a legendary company was humbling. I hope they make it. Lessons Learned + Creative destruction and disruption will happen to every company. How will you respond? + Topic action teams need to deeply understand the problems as the customer understands them, not just what the corporate strategy requirements dictate o This can't be done without talking directly to the customers, internal stakeholders, and partners + Consider if the corporate strategy team should be more facilitators than gatekeepers + A light-weight way to keep topic teams in sync with corporate strategy is to offer a common innovation language and problem and solution framework Share this: * Print * Email * * Tweet * * * WhatsApp * [pinit_fg_e][pinit_fg_e] * Telegram * Share on Tumblr * Pocket * Like this: Like Loading... Filed under: Corporate/Gov't Innovation, Customer Development | << Mapping the Unknown - The Ten Steps to Map Any Industry Leave a Reply Cancel reply * contact: info@kandsranch.com [twitter-lo][twitter-lo] @sgblank [linkedin1][linkedin1] [new-som-bl][new-som-bl] [hbr-reprin][hbr-reprin] [four-steps][four-steps] [sbpodcastb][sbpodcastb]Get the Podcasts for Free * My Tweets Powered by WordPress.com. WP Designer. Loading Comments... Write a Comment... [ ] Email [ ] Name [ ] Website [ ] [Post Comment] %d bloggers like this: