• 618: Building an innovation capability that lasts – with Bruce Vojak, PhD
    2026/11/16
    Three causes of inconsistency in product innovation Watch on YouTube TLDR Bruce Vojak returns to the show to explain why companies struggle to consistently innovate. He sees three causes of a lack of repeatability in innovation: lack of alignment, discipline, and the right people. To build a lasting innovation capability, start with the people. Then add a simple process and a clear strategy. In the end, it’s always about the people. Introduction Many companies don’t have an innovation problem. They have a repeatability problem. They get one breakthrough, maybe two, and then the organization settles back into protecting what works. The fundamentals of innovation aren’t a mystery. So why aren’t companies consistently innovating, and how do you change that? Bruce Vojak is back to answer that. Bruce has been an innovator at MIT Lincoln Laboratory, Amoco, and Motorola, and an innovation researcher at the University of Illinois. He co-authored Serial Innovators and No-Excuses Innovation, and today he helps mature companies build, renew, and sustain their innovation capability through Breakthrough Innovation Advisors. In this episode you’ll learn what it takes for an organization to create an innovation system. Summary of Concepts Discussed for Product Managers How Do Serial Innovators Work? Bruce learned innovation by working beside masters. As a graduate student at the University of Illinois, he worked in the lab of Nick Holonyak, inventor of the visible LED. The lab produced the first demonstration of the quantum well laser. By observing Nick and others, Bruce saw that innovation needs the act of belief. Each state comes with uncertainty, so moving on requires faith or belief. Bruce watched Nick and Nick’s advisor John Bardeen spot patterns in data that most people would have missed. It was life-changing for Bruce to watch these remarkable innovators at work, and this experience led Bruce to ask how serial innovators know which problems to work on. Why Companies Fail to Innovate Repeatably Although the fundamentals of innovation are well known, companies still struggle to apply them. Bruce identifies three causes: lack of alignment (strategic and tactical), lack of discipline, and lack of the right people. Lack of Strategic and Tactical Alignment Strategic alignment answers the question, are we going to invest in innovation at all? One or two people at the top can block innovation. Tactical alignment applies to each project. Even in a company committed to innovation, an innovator has to make the case for a specific idea and bring the organization along. Innovation as an Insurance Policy or an Option for Growth Often, CEOs who champion innovation do so either because they have no other choice or because they have seen innovation work before. Bruce frames an innovation investment as either an insurance policy or an option for future growth. Discipline Starts with Executives Bruce sees lack of discipline most often from senior executives. Executives should decide when an investment decision is made and what the criteria are. They shouldn’t fund things that wouldn’t work in the marketplace, and they shouldn’t stop projects that meet the criteria. To maintain discipline, Bruce prefers a small number of simple, customized processes. At Motorola, quarterly roadmapping sessions started with an hour of re-learning what portfolio categories green, yellow, and red meant. Bruce says that the best processes are there to instruct the neophyte, remind the expert, and discipline the executive to make decisions. A process doesn’t replace the innovator, but it’s a tool to keep everybody in lockstep. Serial Innovators Serial innovators are exemplars of innovation who repeatedly make renewal happen in an organization. They see patterns in the market before others do. They take ownership and serve not only the customers but also shareholders, executives, and colleagues. Putting the Pieces Together for Repeatable Innovation Bruce starts with people. Find or hire people who fit the description of serial innovators. Bruce suggests letting a serial innovator use half of their time to explore innovative projects while continuing to solve customer problems with the other half. Next, add a simple phase gate. Make small bets based on what you learn. For strategic alignment, have a simple strategy that is easy to explain and measure against. Balancing Discovery and Development Bruce is a fan of both incremental and breakthrough innovation. Incremental innovation is typically customer-driven. Renewal requires both an understanding of market needs and technical insight. Useful Links Check out No-Excuses InnovationListen to 524: Why Moneyball is the best breakthrough innovation movie – with Bruce Vojak, PhDConnect with Bruce on LinkedInLearn more about Breakthrough Innovation Advisors Innovation Quote “It’s always about the people.” – Bruce Vojak Application Questions Of the three causes of failed ...
    続きを読む 一部表示
    41 分
  • 617: Test your gut, don’t trust it –the scientific mindset for product teams – with Stefan Thomke, PhD
    2026/11/09
    Experiments to inform product decisions Watch on YouTube TLDR Stefan Thomke, professor at Harvard Business School, and author of The Scientific Mindset: How Thinking Scientifically Drives Better Business Decisions, shares five elements of a scientific mindset, four types of uncertainty in innovation, and three tests of a good hypothesis. Learn why good product decisions are rooted in testing more and assuming less. Introduction When Stefan Thomke studied almost 22,000 online experiments (mostly A/B tests) run by more than 1,300 companies, only about one in five changes made a measurable difference. Half of the changes made things worse. If experienced teams can’t predict the effect of a small change, how confident should any of us be about a creating a new product? Stefan is the William Barclay Harding Professor of Business Administration at Harvard Business School, where he has studied experimentation and innovation for more than three decades. He started as an engineer, learning experimental design to solve a production problem in a semiconductor plant. He is the author of Experimentation Matters and Experimentation Works. His new book, The Scientific Mindset: How Thinking Scientifically Drives Better Business Decisions, completes the trilogy. Stefan was on the show in 2020 to explain how to run product experiments. This time we look at the thinking that decides which experiments are worth running and what you do with the answers. You’ll learn how to find the assumptions hiding in a new product idea using four kinds of uncertainty, how to turn an assumption into a strong hypothesis, and why “customers want this feature” isn’t yet a hypothesis. Summary of Concepts Discussed for Product Managers Five Elements of a Scientific MindsetStefan opens with a question: What did you do the last time you didn’t know what to do? He quotes Richard Feynman: “The first principle is that you must not fool yourself, and you’re the easiest person to fool.” The human brain is a belief engine. We see connections between unrelated things and confuse correlation with causation. To overcome this, we need to think scientifically about decisions. Stefan identifies five elements of a scientific mindset that apply to business decisions: Be a knowledgeable skeptic.Articulate testable hypotheses.Produce hard evidence.Probe cause and effect.Create an experimentation culture, a shared scientific mindset. Skeptics vs DenialistsA skeptic is not a denialist. A skeptic is neutral. They look at the evidence with an open mind and want the truth. A denialist starts with a conclusion, picks evidence that supports it, and dismisses evidence that contradicts it. Stefan calls this running the scientific method in reverse. It’s easy to fall in love with a conclusion and only question the evidence that disagrees with us. Product managers do this when they run customer research to validate a solution instead of finding unmet needs. Instead, fall in love with the customer’s problem, not your solution. Test More and Assume LessThe greatest danger zone is when you are most confident in your assumptions and under pressure to act. That is the time to test your assumptions. Stefan explains that information is most valuable when it is most surprising. Effective leaders don’t trust their gut. They test their gut. Four Types of Uncertainty in InnovationStefan sees four types of uncertainty in innovation: R&D uncertainty: Does the product, service, technology, or process work as intended?Scale-up uncertainty: Can we produce it at high volume, high quality, and reasonable cost?Market or customer uncertainty: Are customers interested, will they pay, and how should we price it?Investment uncertainty: How much money and how many resources should we commit? Why Experience and Data Aren’t EnoughStefan explains that while experience and data are both valuable, they have limits. Relying on experience and data too heavily can prevent you from testing your assumptions. It is easy to mistake correlation for causality. Use experiments in addition to experience and data, because experiments can prove you wrong. Three Tests of a Good HypothesisStefan describes three tests for a hypothesis: It has measurable variables.It is simple.It can be proven wrong. Wolfgang Pauli would reply to a bad hypothesis with “This is not only not right. It’s not even wrong.” A hypothesis that cannot be falsified is worse than one that is simply incorrect. Stefan gives an example of a good hypothesis, which Kohl’s tested: “Opening our stores one hour later will have an insignificant impact on store revenue.” This is a measurable hypothesis they could test in a subset of stores. On the other hand, “We can take our brand upmarket,” is a bad hypothesis since it is not measurable. Designing Fast, Frugal ExperimentsExperiments should be: reversibleinexpensive, at least until they lead to large commitmentsat an appropriate level of rigor for how much ...
    続きを読む 一部表示
    1分未満
  • 616: TRIZ for product managers, without years of training – with Jay Nakagawa and Bill Reid
    2026/11/02
    AI tools for accelerating TRIZ and JTBD Watch on YouTube TLDR Jay Nakagawa and Bill Reid recap their workshop from the 2026 PDMA Ignite Innovation Summit on combining Jobs-to-be-Done and TRIZ and using AI tools to accelerate their analyses. These tools help product managers eliminate contradictions between competing customer demands instead of settling for trade-offs. Introduction Your customers want it faster, better, and cheaper, all at once. Most product teams pick two and call it a trade-off. What if the trade-off is a contradiction you can solve, resulting in much greater value? I recorded this episode at the 2026 PDMA Ignite Innovation Summit, where that question was answered. Two returning guests join me. Jay Nakagawa is Co-Executive Director of the Society for Artificial Intelligence and Competitive Intelligence (SAICI) and is also the Director of Competitive Intelligence at Dell Technologies. Bill Reid is Vice President at Boulder Imaging and has spent more than 30 years developing products at companies including Ford, GE Aircraft Engines, and GM. He is named on more than 20 US patents. At the PDMA Ignite Innovation Summit, they led a workshop that combines Jobs-to-be-Done (JTBD), TRIZ (Theory of Inventive Problem Solving), and generative AI to turn hard constraints into product breakthroughs. Let’s learn a practical, 80/20 way to apply TRIZ principles and how generative AI can speed up inventive problem-solving so you don’t have to be a TRIZ expert. Summary of Concepts Discussed for Product Managers TRIZ: A Framework for Solving ContradictionsGenrich Altshuller developed TRIZ while working in a patent office. He believed anyone could be an inventor. He looked at patents to study how people solve problems and found patterns that held across fields. His tools include separation principles, technical contradictions, substance-field analysis with 76 standard solutions, and 12 trends of technical evolution. Bill describes TRIZ as a how-to book for solving known contradictions among constraints. Bill and Jay have combined TRIZ with Jobs-to-be-Done and competitive intelligence to identify and prioritize customer needs. AI Tools for Faster TRIZ AnalysisUsing AI tools can accelerate TRIZ analysis from weeks to minutes. At the PDMA conference, Jay and Bill led a workshop on using TRIZ and Jobs-to-be-Done with AI tools. Jobs-to-be-Done and TRIZThe workshop started with guiding product managers to understand their customers’ Jobs-to-be-Done statements. Bill used the example of a quarter-inch hole. The JTBD statements are to minimize the time to make the hole, minimize damage to the wood, and maximize accuracy. Improving speed leads to increased damage to the wood. That is a contradiction among customer needs. Workshop participants used a contradiction matrix from TRIZ to plot technical parameters corresponding to customer needs. Teams then used the contradiction matrix to brainstorm solutions. Know Fundamental Principles to Evaluate AI OutputAnalysis can be accelerated using AI tools, but as Bill and Jay explain, in order to know if the output of an AI tool is reasonable, you still need to understand the basic principles behind JTBD and TRIZ. It is still critical to have humans in the loop. Training AI on Jobs-to-be-Done and TRIZIn the workshop, Jay and Bill provided some files to train AI models to use JTBD and the 40×40 TRIZ matrix. Each participant loaded these files onto their own AI tools. The models were then ready to answer questions using these principles such as how a company can make its product more valuable or how difficult each contradiction would be to resolve. Participants described customer objectives, and the AI models used their training to give ideas on how to meet those objectives, using JTBD and TRIZ. Combining JTBD and TRIZ to Identify and Solve ContradictionsSolving one contradiction often reveals a new one, which is why a manual TRIZ analysis can take weeks or months. Jobs-to-be-Done identifies customer needs and prioritizes desired outcomes. The TRIZ framework points product managers to possible solutions by eliminating contradictions. Useful Links Watch Jay and Bill’s pre-conference webinar on TRIZ and JTBD, “From Contradictions to Breakthroughs”Download files on TRIZ and JTBD for training an AI model: TRIZ Contradictions MatrixKnow Your Customers’ “Jobs to Be Done”, Clayton ChristensenJobs to Be DoneLLM-based Extraction of Contradictions from Patents40 TRIZ Principles Connect with Jay and Bill on LinkedInLearn more about Jay’s Society for Artificial Intelligence and Competitive IntelligenceCheck out Jay’s book, The UnConventional Strategist603: Survive the AI revolution of product management – with Bob Cooper, PhD Innovation Quotes “And suddenly the inventor appeared.” – Genrich Altshuller, creator of TRIZ “Get rid of the box.” – Jay Nakagawa Application Questions What are some contradicting outcome statements for your product?What do you ...
    続きを読む 一部表示
    36 分
  • 615: How to separate signal from noise in customer feedback – with Kristyn Corrigan
    2026/10/26
    Make the most of AI tools for voice-of-the-customer research Watch on YouTube TLDR Kristyn Corrigan, Principal at Applied Marketing Science, joins me to discuss how product teams can move from drowning in customer feedback to identifying the core needs that drive product decisions. We explore shifting the Voice of the Customer (VOC) from a formal research method to an organizational mindset, the risks and opportunities of using AI in analyzing feedback, and actionable tools like the VOC focus brief to enhance cross-functional alignment and innovation. Introduction Your customers are telling you what they need every day, through usage data, support tickets, sales calls, online communities, and more. AI can summarize all of it in seconds — that’s no longer the hard part. Instead, it’s knowing which needs are worthwhile — what’s the signal to act on and what’s the noise to avoid. To help us answer that, Kristyn Corrigan joins us again. She is a Principal at Applied Marketing Science, where she leads the Insights for Innovation practice. She has more than 20 years of experience helping companies uncover customer needs and turn them into products, and she trains teams to run their own VOC programs. At the PDMA conference, she led a workshop on moving from a pile of customer feedback to the few needs that should drive product decisions. She’s here so we can learn to do that too. Summary of Concepts Discussed for Product Managers Reframing Voice of the Customer (VOC)Kristyn explains that VOC has shifted from being just a set of research interviews to a comprehensive mindset that leverages the wealth of customer insights found throughout an organization. This includes feedback from CRM data, recorded sales conversations, social media, forums, and support tickets. Product teams need to intentionally curate these sources to ensure the insights inform key product decisions. Kristyn has had success helping salespeople learn to ask voice-of-the-customer questions to help sales interviews provide more valuable insights. Separating the Signal from the Noise in Customer ResearchWith the explosion of data from internal and external sources, product teams risk getting lost in noise. Kristyn discusses the importance of aligning the entire organization on research and business questions and identifying which data sources are relevant. Not all feedback holds equal value so strategic focus is essential. Responsible and Effective Use of AI for VOC ResearchAI tools like Copilot and Claude can rapidly synthesize and summarize large volumes of feedback, but Kristyn warns they often miss meaningful innovation details and tend to smooth out themes, potentially losing valuable nuance. These tools can’t be used without trained humans guiding the process and critically evaluating the customer needs that AI identifies. Kristyn notes that AI tools are built to affirm the user. AI is good at summarizing and smoothing themes, but innovation lives in the details, so effective VOC can be lost when using AI summaries alone. A customized AI tool built for customer research and trained human analysts can avoid this problem. What is Voice-of-the-Customer?In order to evaluate AI-generated customer needs, it’s important to understand what VOC is. Kristyn defines VOC as a systematic understanding of customers needs or benefits they seek from using your product. That’s very different from the solution that meets those needs. Real-World Example of Finding the Signal in VOC ResearchKristyn shares a case study from a time her team worked with an HVAC company. They embarked on an effort to understand feedback related to a specific component of the HVAC system. They explored existing customer feedback on contractor forums, review sites, YouTube, and social media, and used both AI tools and humans to analyze the data. By outlining their research questions and having a clear picture of existing feedback, they were able to zero in on a few important insights: First, in addition to contractors, homeowners were talking online about this product, which provided additional insights about customer needs. Second, the research pointed the team to a specific area of the installation process they needed to explore more. To separate the signal from the noise, the team recognized these needs in the existing data and validated their findings further with traditional techniques like ethnography and interviews. This combination allowed the team to move faster and have more resources for traditional research. VOC Focus BriefFor teams that don’t have access to AI tools designed specifically for VOC research, Kristyn recommends using a VOC focus brief, a shared document where teams state research questions, hypotheses, and possible data sources. Next, create an analysis plan and ensure the entire team is well-aligned. Kristyn also recommends developing the VOC brief with others from cross-functional teams and sharing it widely across the ...
    続きを読む 一部表示
    36 分
  • 614: Stop starting projects you cannot finish – with Mike Dalton
    2026/10/19
    Prioritize the right product projects – for product managers Watch on YouTube TLDR I’m siting down with innovation expert Mike Dalton to discuss why capable companies overcommit to too many projects and struggle to move any of them forward. He reveals practical frameworks and tools to help product leaders focus on the right projects, avoid resource overload, and deliver more value to both customers and organizations. Introduction Picture a customer calling and asking, “Where’s my new product?” And you don’t have a good answer. That’s the situation a plant leader at Danfoss described being in, before today’s guest showed up. Three months later, on-time delivery was over 90%. Our guest, Mike Dalton, spent 23 years inside SC Johnson, running the P&L for its most profitable business unit, before he set out to answer a key question: Why do capable companies keep moving fifty projects an inch forward instead of five projects a mile? He answered that question at my favorite innovation conference — PDMA’s Ignite Innovation Summit. His books, Simplifying Innovation and Unlocking Innovation Productivity, also provide valuable insights for product innovators and managers. I wanted to have this conversation because every product leader I talk to is being asked to do more with less. Mike’s answer isn’t “work harder.” It’s “stop starting so much.” And to get there, you just need a few tools, including a simple pipeline control mechanism that can meaningfully increase how many projects finish. We’ll learn about that and more. Summary of Concepts Discussed for Product Managers Problem of Too Many ProjectsOrganizations routinely take on more projects than they have resources for. This leads to spreading teams thin, multitasking inefficiencies, and slower overall product delivery. Mike emphasizes that throwing more resources at the problem is never the answer. Instead, the key is focusing existing resources on a few prioritized projects. Choosing the Right ProjectsSelecting the right projects to focus on is central to increasing innovation productivity. Mike describes a customer value lens for vetting opportunities, ensuring products are both valuable to customers and profitable for the organization. He warns against ideas driven solely by internal executives, advocating for direct customer engagement to identify high-value unmet needs. Portfolio and Resource ManagementMike explores how to balance a portfolio of projects based on strategic importance, risk, and expected ROI. He suggests using resource bandwidth as a limiting factor—most organizations can only run about a third of the projects they attempt efficiently. He recommends zero-based project budgeting and prioritizing projects by return per unit of effort, with less promising projects placed in the backlog or dropped. Improving Project ExecutionExecution challenges are often rooted in resource overload rather than a lack of project management skills. Mike describes the need for mechanisms like early warning dashboards to track project risks and make sure shared resources are allocated to the most critical initiatives, not just those championed by the loudest internal voices. This fosters focus and better organizational outcomes. Practical Starting PointsFor leaders looking to address project overload, Mike recommends tools such as a virtual drum for resource planning (with a downloadable resource shared in the episode). Categorize projects as small, medium, and large and determine how many of each size your organization can run at full speed at one time. Monitor total work-in-progress (WIP) to help visualize limits, identify focus areas, and create a foundation for real portfolio discussion and prioritization. Useful Links Clear Winner Accelerator – A cross functional assessment to ensure a clear understanding of your right to win for any opportunityPipeline Bandwidth Accelerator – A visualization of your portfolio vs your pipeline bandwidth so you know when you can start the next project without derailing those already underwayCheck out Mike’s books, Unlocking Innovation Productivity and Simplifying InnovationVisit Mike’s website, GuidedInnovation.com Innovation Quote “Most hack away at the branches while few strike at the roots.” – paraphrase of Henry David Thoreau Application Questions How does your organization currently decide which projects to prioritize or pause?In what ways does multitasking or project overload impact your team’s productivity and morale?What tools or frameworks do you use to assess the value of potential projects through the “customer value lens”?How might you introduce more objective resource management or portfolio controls in your product practice?What strategies can you adopt to ensure the most valuable projects receive the needed attention and resources, rather than just the ones advocated by the most influential stakeholders? Bio Michael A. Dalton Managing ...
    続きを読む 一部表示
    18 分
  • 613: Overcoming the 7 most common weaknesses in product innovation – with Chad McAllister, PhD
    2026/10/12
    Seven mistakes that hold back product teams Watch on YouTube TLDR I’m sharing insights from my presentation at the PDMA’s Ignite Innovation Conference, focusing on how organizations can overcome the seven most common weaknesses in product innovation. Drawing from decades of hands-on experience and the PDMA Body of Knowledge, I detail actionable steps for product professionals to boost their effectiveness and drive better outcomes for their teams and organizations. Introduction Last week, at the PDMA’s Ignite Innovation Conference, I gave a short presentation on overcoming the seven most common weaknesses in product innovation. Today, I want to bring that presentation to you as well. The Product Development and Management Association’s (PDMA) has been researching product innovation and product management for 50 years. They provides resources for product managers about how the most innovative companies innovate, including the book Product Development and Management Body of Knowledge, which I have contributed to each edition of, including as a co-author on the current edition. PDMA organizes the body of knowledge of product management into seven knowledge areas. In this presentation, I’m talking about what I’ve learned teaching these seven knowledge areas over the past two decades. I train product teams through the Rapid Product Mastery (RPM) Experience. At the end of each RPM Experience, I create a next steps report, including my observations of the team’s weaknesses and how to address them. The teams also list the processes, tools, and concepts they believe would most help them deliver products customers love. In this presentation, I’ll share the most common weakness identified in these reports from each of the seven knowledge areas. Use the personal scorecard I created to follow along and identify your own weaknesses: Summary of Concepts Discussed for Product Managers 1. Product Innovation ManagementMost frequent weakness: Product managers are acting as project managers. They say, “I used to have interactions with customers, but not anymore.”Recommendation: Re-establish direct customer contact. 2. StrategyMost frequent weakness: Product managers don’t know the strategic objectives or priorities.Recommendation: Make the strategy visible and share the strategic objectives frequently. 3. Portfolio ManagementMost frequent weakness: Lack of clarity around how projects are selected.Recommendation:  Have an explicit and visible method for understanding the criteria for selecting a project. Select against strategic buckets. (Breakthrough, Platform, Derivative, Support) 4. ProcessMost frequent weakness: A process for building exists, but the front end is missing or undisciplined, and the process gets dropped under pressure.Recommendation: Put a more disciplined front end in front of delivery, focused on discovery and scoping. Validate the solution. 5. Design & DevelopmentMost frequent weakness: A thin ideation, prototyping, and validation toolkit is used, with little agreement on which tools are helpful.Recommendation: Build a shared toolkit that spans all three stages — ideation, prototyping, validation — and get team agreement on which tool to use when. 6. Market ResearchMost frequent weakness: Sales is used as a substitute for customer research, and there is no synthesized voice of the customer.Recommendation: Separate customer discovery from sales and give product managers direct customer contact. Synthesize the voice of the customer for each segment and share it with the whole product team. Keep the language the customer shares. 7. Culture, Teams, & LeadershipMost frequent weakness: The culture is siloed and top-down, while the product managers want cross-functional collaboration.Recommendation: Break the silos and build cross-functional teams. 4 Repeated Themes1. Clear strategy2. Customer research3. Supportive culture4. Discovery process Application Questions Which of the seven knowledge areas does your team struggle with most, and what small step could you take to address it this week?How frequently do you have direct contact with customers, and what could you do to strengthen that connection?In your team, how visible and actionable are your organization’s strategic objectives?What tools or processes does your team currently use for ideation and customer validation, and where do you see opportunities for improvement?How would you describe your organization’s approach to cross-functional teamwork, and what changes could foster greater collaboration and innovation? Thanks! Thank you for taking the journey to product mastery 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. Source
    続きを読む 一部表示
    42 分
  • 612: Why 70% of innovation efforts fail (and it’s not your process) – with Anita Friis Sommer, PhD
    2026/10/05
    The seven missing pieces for successful product innovation Watch on YouTube TLDR Dr. Anita Friis Sommer joins me to discuss why most corporate innovation initiatives fail despite decades of process frameworks like Agile, Stage-Gate, and Lean Startup. Drawing on her experience co-developing the Agile Stage-Gate model and leading innovation at LEGO and the Novo Nordisk Foundation CO2 Research Center, Anita Friis Sommer shares practical insights from her new book, Mission-Driven Innovation. She emphasizes that true innovation success comes not from a single methodology but from aligning seven critical organizational dimensions. The conversation covers mission-driven leadership, creating empowering systems for innovation, and how budgeting, governance, and digital enablement play a key role. Introduction Here’s an uncomfortable number: Somewhere between 70 and 90 percent of corporate innovation initiatives never deliver the impact they promised — and that’s after decades of Agile, Stage-Gate, Lean Startup, and other frameworks we’ve thrown at the problem. Our guest today helped create one of those frameworks. And her argument is that the method was never the thing holding your success back. Our guest is Dr. Anita Friis Sommer. She co-developed the Agile–Stage-Gate model with Dr. Bob Cooper, work that earned her the Maurice Holland Award twice. She spent over a decade at the LEGO Group leading sustainable operations at global scale, and today she’s the chief operating officer of the Novo Nordisk Foundation CO₂ Research Center, where she’s helping turn carbon-capture science into technology the world can actually use. She’s brought all of that together in a new book called Mission-Driven Innovation: How to Lead Technology in a Complex World. She will help you understand what actually determines innovation success and how to add the missing pieces to your organization. Summary of Concepts Discussed for Product Managers Why Innovation Frameworks Aren’t EnoughAnita explains that processes like Agile Stage-Gate introduce helpful structure and flexibility, but simply installing a new methodology does not guarantee repeatable innovation success. The underlying organizational system often inhibits these frameworks from realizing their full potential. Seven Dimensions of Mission-Driven InnovationAnita outlines the seven dimensions that drive innovation success: Mission, Purpose, and Values: A motivating mission rooted in something beyond profit inspires intrinsic motivation and creativity, shifting teams from a fear mindset to one driven by passion.Leadership and People: Moving from command-and-control to servant leadership creates psychological safety and strength-based teams.Strategy and Roadmapping: Complex innovation needs co-created strategies and clear roadmapping, involving more than just top executives in future-oriented planning.Structure and Governance: Modern organizations benefit from empowered decision-making at tactical and operational levels, moving away from classic bureaucratic bottlenecks towards “team of teams” models.Innovation Processes: Effective innovation combines linear strategic oversight with iterative, agile experimentation at the operational level, allowing for frequent learning and pivots.Planning and Budgeting: Dynamic, KPI-driven portfolios outperform static, project-locked annual budgets, enabling real-time reallocation of resources toward emerging opportunities.Digital Enablers: Success requires integrating digital experimentation and AI directly into product teams, ensuring that capabilities, not just technology, are distributed throughout the organization. Useful Links Visit Anita’s website, MissionDrivenInnovation.comCheck out Anita’s book, Mission-Driven Innovation: How to Lead Technology in a Complex WorldConnect with Anita on LinkedIn Innovation Quote “You cannot think your way into a new way of acting. You have to act your way into a new way of thinking.” – Jørgen Vig Knudstorp, CEO of LEGO Group Application Questions Which of the seven mission-driven innovation dimensions feels most challenging for your organization to align, and why?How does your current budgeting process support or hinder real-time innovation pivots and learning?In what ways could your team’s leadership style become more like a “gardener” and less like a “chess master”?What practices might you introduce to make your organizational values more actionable and intrinsically motivating?How can digital enablers (AI, simulations, transparent dashboards) become integrated parts of your product teams, rather than siloed functions? Bio Anita Friis Sommer is an innovation leader, researcher, and author focused on helping organizations turn promising ideas and technologies into successful products and business outcomes. An Associate Professor at Aarhus University and former innovation leader at LEGO, she co-developed the Agile–Stage-Gate approach with Dr. Robert G. ...
    続きを読む 一部表示
    46 分
  • 611: The #1 career decision product leaders get wrong – with Ben Lamorte
    2026/09/28
    Make the career decision aligned with who you are Watch on YouTube TLDR I’m welcoming back Ben Lamorte, veteran OKR coach, to discuss his new book Start With You: Go Beyond Prototyping. Get Clarity Before You Commit. Our conversation centers on how product professionals can use decision analysis and introspection to shift from endlessly prototyping their lives to making bolder, more authentic career decisions reflective of their true selves. Ben shares his personal journey, lessons learned from working in OKRs, and his Identity Blueprint tool for individual career clarity. Introduction My guest today was on the show about two years ago, and he gave us one of the best conversations we’ve had on getting an organization clear on what actually matters. Ben Lamorte, the most experienced OKR coach and founder of OKRs.com, is back, and this time the subject isn’t your company’s goals. It’s yours. Ben has a new book called Start With You: Go Beyond Prototyping. Get Clarity Before You Commit and it makes a contrarian argument for product professionals. We’ve built our careers on prototyping and iteration — test, learn, adjust, repeat. Ben says that’s the right way to develop a product, and the right way to run the first half of your career. But by mid-career, he argues, you’ve already gathered the data about yourself. More experiments won’t help. What you need now is the language to name what you already know, and the courage to commit to it. He’s taken the decision-analysis framework, information, values, alternatives, that he learned from his Stanford professor Ron Howard, and applied it to the question of what you do next with your professional life. And given the pace of change hitting product people, this is a very important discussion to hear. Summary of Concepts Discussed for Product Managers Personal Reflection on CareerAfter years coaching over 200 organizations on OKRs, Ben experienced a professional slowdown, leading him to apply rigorous decision frameworks inward. When his daughter asked him, “Would you do your work tomorrow if you didn’t get paid?” he began to reflect on personal fulfillment and career direction. This catalyzed his transition from organizational OKRs to helping individuals, especially mid-career professionals, define what truly matters for themselves and make value-aligned commitments. Ben’s New Book, Start with YouBen’s book helps professionals identify their identity capital, which includes experiences, credentials, relationships, reputation, and skills. Using a gardens metaphor, Ben describes how we accumulate different types of identity capital: thriving gardens (energizing skills), spent gardens (skills we’ve outgrown), dormant gardens (skills/experiences shelved away), overharvested gardens (skills depleted by overuse), and undervalued gardens (assets we overlook). He challenges readers to think about their dormant identity capital — a skill or experience from their past that isn’t currently being put to use but could rise up at the right moment. Decision Analysis: Information, Values, AlternativesBen leverages the decision analysis framework taught by Ron Howard at Stanford — information, values, and alternatives — to empower career decisions. Like a three-legged stool, making a decision requires three legs: strengths (identity capital), values (what you need and want), and career direction (on or off the “menu” of existing jobs). This approach helps product professionals move beyond defaulting to what’s available and design new possibilities tailored to themselves. Get Clarity Before You CommitWhile prototyping and iteration are essential for product development (and early careers), Ben challenges the dogma of always “prototyping your life.” Making big life decisions is not prototyping; it’s committing. Ben’s book helps people get clarity before committing to a big decision. The Identity BlueprintBen’s Identity Blueprint is an AI-powered self-reflection tool that synthesizes personal stories into a report illuminating your strengths, values, and undervalued possibilities. It’s designed to help individuals gain visceral clarity before making major commitments, whether shifting careers or reigniting their passion for current work. Don’t Follow Your Passion; Find ItMany young people are told to find their passion, but it’s nearly impossible to know your passion before you get good at doing something. Ben’s book helps readers find the things that are meaningful to them and fit with their identity capital. It gives you a framework for bringing your true self into the world. This can lead to finding your passion. Surround Yourself with the Right People Ben says that the most important overlooked part of loving your work is finding the direction that allows you to surround yourself with the people that you want to be surrounded with. The people around you will change you. In Ben’s opinion, it is better...
    続きを読む 一部表示
    27 分