Product Mastery Now for Product Managers, Leaders, and Innovators

How product managers use AI to boost productivity and innovation success Watch on YouTube TLDR In this episode of Product Mastery Now, Katie Trauth Taylor, PhD, CEO and co-founder of Narratize AI, joins me to discuss how AI is transforming product innovation processes. She shares insights from working with Fortune 500 companies like NASA, Boeing, and Comcast, and dives into research showing that product and R&D teams spend up to 70% of their time on documentation and communication rather than true innovation. Katie outlines four best practices for leveraging AI, including the use of knowledge hubs, AI agents, and robust documentation processes, to unlock productivity, capture tribal knowledge, and speed up time to market by as much as 46%. The conversation also highlights the importance of storytelling in gaining buy-in for new ideas and the potential for AI to revolutionize knowledge management and portfolio intelligence. Introduction Product teams waste a lot of their time doing things that don’t help get to the heart of product innovation. We need to flip the script on that so that we can be more productive with our innovation efforts. In this discussion, you’re going to learn how companies like Boeing, Comcast, and others are accomplishing this. We’re going to talk about four specific approaches for unleashing AI for product innovation. To help us with that is our guest, Dr. Katie Trauth Taylor. She is the CEO and co-founder of Narratize AI, and she helps R&D transform their scattered knowledge into a competitive advantage. She has worked with NASA, Boeing, and other Fortune 500 companies to cut documentation time and speed products to market. Katie discovered that innovators are spending too much of their time just trying to communicate their ideas, and she built an AI platform to improve this. She holds a PhD from Purdue University and has published peer-reviewed research on innovation storytelling that’s reshaping how teams work. Find out more about the Product Development and Management Association (PDMA) and next year’s innovation conference. Summary of Concepts Discussed for Product Managers The Problem with Documentation:Product teams spend roughly 70% of their time on documentation, reporting, and knowledge lookup instead of direct innovation. This significantly slows time to market. AI as a Knowledge Capture Tool:Katie turned to large language models to transform how product teams do documentation. AI can systematically prompt and capture insights, store tribal knowledge, and automate documentation customized to roles and project phases. The Power of Storytelling:Successful innovation relies on crafting compelling narratives, not just data. Five drivers for effective storytelling are empathy, engagement, alignment, evidence, and impact. Best Practices for Leveraging AI in Product Teams: Think Outside the Chatbot: AI tools are a knowledge-capture capability, not just a question-and-answer capability. Use AI to prompt and store deep organizational insights, not just answer questions. Narratize AI provides workflows for product innovation processes like Agile and Jobs-To-Be-Done. Embrace AI Agents: Agents can provide proactive, role-specific updates (like regulatory changes or market intelligence) and work in the background. Documentation or It Didn’t Happen: Accurate, human-reviewed documentation is crucial for knowledge management and competitive advantage. Toward Product Portfolio Intelligence: With AI-enabled product knowledge hubs, organizations can now have real-time insights across portfolios, breaking silos and aiding strategic decisions. Knowledge Management Revolution:Capturing lessons learned and even past failures allows organizations to prevent repeating mistakes and leverage prior discoveries, especially as a significant portion of the workforce retires. Actionable Insights for Product Managers: Building cross-functional relationships is vital. Don’t innovate in a silo. Portfolio intelligence can transform decision-making beyond traditional management by surfacing insights on demand. AI enables better onboarding, reduces redundant efforts, and future-proofs organizations as knowledge is no longer lost with employee turnover. Useful Links Learn more about Narratize Check out the Narratize YouTube channel Connect with Katie on LinkedIn Innovation Quote “If it’s a truly disruptive innovation from a company, you can almost guarantee it wasn’t a straight A-to-B path that delivered the results. So as you recognize the success, recognize also the journey that got you there.” – Joel Schall Application Questions How much time does your team currently spend on documentation and communication versus actual product innovation? In what ways could AI help you capture and surface tribal knowledge within your organization? Which of the five storytelling drivers—empathy, engagement, alignment, evidence, impact—do you find hardest to implem

What product managers should know about patents, trade secrets, and copyright Watch on YouTube TLDR In this episode, I’m joined by David Carstens, a seasoned IP attorney and founding partner at Carstens, Allen & Gourley, who brings over 30 years of legal and technical experience in intellectual property (IP) strategy. Our conversation dives into the importance of IP management for product managers, how to build an IP strategy, when to consider patents versus trade secrets, the complexities of software and AI-generated content, and the rapid pace of change in the IP landscape. The episode is a must-listen for any product manager navigating decisions around invention protection, copyright, and the evolving influence of artificial intelligence. Introduction If you’ve ever wondered whether to patent that new feature, worried about AI training data copyright issues, or struggled to justify IP investment to leadership, you’re not alone. We’re exploring intellectual property strategy for product managers—and what it means to get it right and how expensive it can be when you get it wrong. Most product managers don’t receive training on IP strategy, yet the decisions you make daily have massive IP implications. Our guest is David Carstens, who has a unique combination of technical depth and legal expertise. He’s a founding partner at Carstens, Allen & Gourley. He has dual engineering degrees, an MBA, and over 30 years experience protecting IP for companies building software, medical devices, and telecommunications products. He’s also an entrepreneur who founded multiple companies including a nationally chartered bank and an innovation platform, plus he’s been teaching IP law at SMU for three decades. David is currently investing in and speaking about the Fifth Industrial Revolution, making him well positioned to help us also understand how AI is reshaping IP strategy. Summary of Concepts Discussed for Product Managers IP Strategy Framework:David mentions that there isn’t a “one-size-fits-all” framework for IP strategy; it starts with assessing a company’s current position, identifying valuable innovations, evaluating what can realistically be protected, and aligning actions with budget constraints. Key steps include identifying strong value propositions, checking for existing patents or IP conflicts, and sometimes considering licensing or redesign if a competitor already owns relevant patents. Timing and Collaboration:Product managers should start thinking about IP early—preferably well before product launch or tooling investment. Collaborating with an IP attorney and creating a culture that values teamwork and knowledge sharing can help spot and protect innovations more effectively. Patents, Trade Secrets, and Value:Patents offer competitive advantages by providing pricing freedom, can act as bargaining assets, and are vital for companies seeking investment. Trade secrets, by contrast, are about keeping valuable information confidential (e.g., formulas or processes not disclosed publicly), but are only effective if the information can’t be easily reverse-engineered from the product. Software & AI Challenges:The fast pace of software development often complicates patent decisions. Patentability is more likely when software enables a genuinely novel technical process rather than automating routine tasks. For AI-generated content, copyright ownership is still unsettled; it usually depends on the degree of human contribution to the creative process. Legal systems are racing to catch up as AI shakes up traditional definitions of authorship and originality. The Fifth Industrial Revolution and Legal Evolution:David argues we’re entering a new industrial age defined by AI, blockchain, quantum computing, and advanced materials. The IP legal framework, largely unchanged for centuries, is struggling to keep pace with these rapid innovations, making adaptability and ongoing awareness essential for product managers. Useful Link Learn more about Carstens, Allen & Gourley Intellectual Property Law Firm Innovation Quote “Pressure is a privilege.” – Billie Jean King Application Questions At what point in your product development process do you typically involve IP considerations, and how might earlier engagement affect outcomes? How do you differentiate between an innovation worth patenting versus keeping as a trade secret in your product or technology stack? What internal processes or culture shifts could help your team better identify and protect intellectual property? How does the uncertainty around AI-generated content and copyright influence your use of AI tools in product development? What steps can you take to ensure your IP strategy remains effective as emerging tech (AI, blockchain, etc.) rapidly changes the innovation landscape? Bio David Carstens distinguishes himself not only through his comprehensive knowledge of legal protection of Intellectual Prop

A leadership framework that gives product managers influence Watch on YouTube TLDR In this episode, Uma Subramanian shares her insights and proven framework for transitioning from individual contributor to effective leader in tech and product management roles. Drawing from her extensive experience at Microsoft and Turing, Uma explains the identity shift required for leadership, introduces her SOAR framework (Strategic Impact, Outstanding Communication, Authority/Personal Brand, Relationship Mastery), and provides actionable tips for developing each pillar. Listeners will learn how to think beyond their immediate role, communicate their impact, build a compelling personal brand, and master the art of building relationships—all key to becoming sought-after leaders. Introduction Today we’re exploring a challenging transition in product management —the shift from individual contributor to someone who multiplies the success of others. I know the first time I became responsible for a team, I was a fish out of water. I knew what made me successful in my previous role, but I didn’t know how to be successful leading others. I had not learned that yet. How do you lead when no one actually taught you how to lead? In this discussion, we’re going to give you a proven framework and helpful tools for successfully making this transition. Our guest is Uma Subramanian, and she understands this transformation very well. She spent 20 years at Microsoft evolving from programmer to leading global teams. Then she became Head of Developer Success at Turing, where she built a developer community from zero to 37,000 members in just five months while driving NPS scores to world-class levels of 92. She’s a certified executive coach with Maxwell Leadership, trained in positive psychology, and now helps tech professionals worldwide make this same leadership leap through her company, Limitless Leaders. Uma understands both the technical and human sides of this challenge. Summary of Concepts Discussed for Product Managers The Leadership Identity Shift:Uma and host Chad discuss how moving into leadership isn’t just a role change but an identity change. Success as an individual often doesn’t translate directly; leaders must learn to orchestrate success with others. Uma’s SOAR Framework for Leadership: S – Strategic Impact: Thinking beyond your job description to create greater value for your organization, being proactive, and bringing others along. O – Outstanding Communication: Communicating your value effectively, using storytelling to persuade, and making sure your impact is recognized. A – Authority & Personal Brand: Defining what you want to be known for, aligning others’ perceptions with your authentic self, and standing out in your niche. R – Relationship Mastery: Building genuine relationships at all levels, creating an ecosystem of support, and focusing on people as much as tasks. Encouraging Teams to Rally Around Strategic Goals:Product leaders elevate impact company-wide, often going beyond their assigned responsibilities. This approach can lead to friction, such as when Uma developed engineering tools without first looping in the appropriate teams. Through these experiences, Uma learned that encouraging teams to align with strategic goals requires proactive communication and collaboration. She highlights the value of involving the appropriate teams early on as well as partnering across teams to solve problems together. Communicating Your Impact Effectively:Many professionals often hesitate to communicate their value, fearing it might come across as self-promotion or bragging, or believing others already know what they’ve accomplished. Uma encourages a shift from simply discussing tasks and experiences to focusing on the results and business value those efforts create. Impactful communication also involves storytelling—not just presenting data or logic, but tapping into the emotional side to persuade stakeholders and gain buy-in. She has seen how developing storytelling skills can “change the game” for her clients and help their contributions gain recognition and support from upper management. Building Your Personal Brand:Uma highlights the power of clear, intentional branding—including “I am” statements—which can help leaders articulate what they’re uniquely great at and shape how they’re perceived across their careers. Uma shares her own experience: When interviewing for a leadership position at Turing after her time at Microsoft, she created a pitch deck that included several “I am” statements. These reflected recurring themes throughout her career: “I love to build things from the ground up.” “I love to bring people together and help them grow.” “I love to take on new challenges.” Your brand and “I am” statements are not tailored to a single job or company—they should be innately true and consistently evident across your career. Relationship Mastery:Building great relationships goes beyond pr

Practical strategies for building influence and confidence from a Product VP coach Watch on YouTube TLDR In this episode, I talk with Rebecca Arora, founder of Access Alignment, executive coach, and author of Somatic Intelligence, about making the transition from successful product manager or director to VP of Product and beyond. Rebecca shares practical strategies for this professional transition, including the need to shift from domain expertise to people leadership, the importance of relationship mapping, communication skills, and strategic thinking. She offers advice on handling stress, leveraging self-awareness, and using coaching techniques to empower teams. We also explore how to set yourself up for success in the first 90 days of a new leadership role. Introduction Let’s say you’re a product manager, you have done outstanding work, and you’re getting promoted to Product VP. Congratulations! The excitement lasts about 24 hours before reality hits. Suddenly you’re responsible for product strategy, team leadership, board presentations, and influencing executives. The skills that made you successful as an individual contributor won’t be enough to make you successful as a Product VP. How do you make this transition? Many of the Product VPs I have talked with use a professional coach to help them move from doing product management work to leading the people who do the work. Our guest today is one of those coaches who has helped several Product VPs. From this episode, you’ll learn practical steps to take for making a similar transition from individual contributor to leader, setting yourself up for long-term success.  Our guest is Rebecca Arora, founder of Access Alignment and author of Somatic Intelligence. Rebecca has a unique background – she was a Co-Founder and the first Product Leader at Mode Media, which scaled to become the #1 lifestyle digital media company. She also contributed to product strategy at Oracle. For the past 16 years, she’s been coaching C-suite leaders and top execs in all functions (including Product). Rebecca’s clients work at exceptional companies such as Google, Salesforce, IDEO, Pinterest, Blue Shield of California, Accenture, and many more. Her book, Somatic Intelligence, helps leaders align head, heart, and body to lead with awareness, confidence, and clarity.  Summary of Concepts Discussed for Product Managers Transitioning from Individual Contributor to Leader:Rebecca describes the challenges facing newly promoted Product VPs, noting the skills that made you a great product manager may not be sufficient as a senior leader. The key leap is shifting your mindset from being an expert to becoming more of a coach and empowering others. The Company as Your Product:As you move up, your sphere of influence expands. Rebecca encourages leaders to think of the company and entire industry as their “product,” applying product management skills to relationships, organizations, and strategy, not just the features you build. Overcoming the Expert Trap:Product leaders can struggle with letting go of being the domain expert and instead fostering empowerment and growth in others. Rebecca advises asking open-ended coaching questions and making space for your team to experiment—even if they do things differently from how you would. Relationship Mapping and Communication:Building new relationships is a priority. Rebecca suggests creating a relationship map to identify stakeholders and potential influencers, addressing conflicts, and strengthening weak connections. Top product leaders may leverage communication coaching to refine their tone and message delivery. Self-Awareness and Blind Spots:While developing your own self-awareness, simultaneously encourage self-awareness from your team. Rebecca advocates for collecting feedback, self-assessment, and being aware of personality differences within a team. She highlights the value of recognizing your blind spots and understanding that not everyone is motivated or learns the same way you do. You cannot always guide people the way you want to be guided. 360-degree Feedback:Product leaders can get 360-degree feedback by interviewing their boss, direct reports, peers, and other stakeholders and ask them, “What are my strengths?” and “What could I improve upon?” First 90 Days in a Product Leadership Role:Rebecca’s advice is to go on a listening tour—ask lots of questions and be curious. Apply user research principles to understanding the organization. Prioritize relationship-building at all levels. Hone your strategic, long-range industry viewpoint. Managing Stress and Personal Growth:The transition to senior leadership is stressful and can feel isolating. Rebecca shares practical tips: slow down (“Slow is smooth. Smooth is fast.”), lean back to get perspective on challenges, smile more, and use humor to reset your mindset. Rebecca recommends that during a stressful time, p

How product managers can build emotional connections that drive retention, revenue, and referrals Watch on YouTube TLDR Product delight goes beyond functionality to create emotional connections with users. Dr. Nesrine Changuel, former product leader at Google, Spotify, and Microsoft, presents a four-step framework for systematically building delight into products. The approach involves identifying both functional and emotional motivators, turning them into product opportunities, categorizing solutions using a Delight Grid, and validating through a Delight Excellence Checklist. Research shows emotionally connected users have 2x higher retention and revenue, plus 60% more referrals. The optimal product portfolio balances 50% functional features, 40% deep delight (both functional and emotional), and 10% surface delight (purely emotional). Introduction Why do customers choose your product? Is it faster, does it have the best features, or is it priced better than your competitors? Don’t kid yourself, these are areas where your competitors can easily reach parity. So, what makes a product stand out? What makes it become the product customers genuinely love and can’t imagine living without? Not only will you find out in this episode, but you’ll also learn about the framework to make it happen. Our guest expert is Dr. Nesrine Changuel. She has spent over a decade building products used by millions at Google, Spotify, and Microsoft. She’s the creator of the Delight Framework that helped teams at these companies systematically build emotional connection into products. She now teaches this methodology at business schools, including INSEAD and ESSEC, and her recent book, Product Delight, describes these proven methods. Summary of Concepts Discussed for Product Managers What is Product Delight?Product delight means creating products that connect with users on an emotional level while solving functional problems. It addresses both what users need to accomplish and how they want to feel while using the product. The Four-Step Delight Framework: Identify Motivators: List both functional motivators (what users want to accomplish) and emotional motivators (how they want to feel – productive, secure, connected, etc.). Create Product Opportunities: Transform emotional motivators into concrete product possibilities that can be implemented. Generate Solutions Using the Delight Grid: Categorize features into three types: Low Delight: Purely functional features Surface Delight: Purely emotional features Deep Delight: Features addressing both functional and emotional needs Validate with the Delight Excellence Checklist: Ensure features bring impact, avoid distraction, remain inclusive, and provide continuous rather than one-time delight The 50-40-10 Rule:Nesrine recommends that the optimal product roadmaps should contain: 50% low delight (functional features) 40% deep delight (functional + emotional) 10% surface delight (purely emotional) Examples and Case Studies: Spotify Examples: Low Delight: Search by lyrics functionality Surface Delight: Spotify Wrapped (contributed to 20% app downloads in 2020) Deep Delight: Discover Weekly, collaborative playlists, Spotify Jam Uber Security Features:Uber transformed the emotional motivator of feeling secure into features like location tracking for partners and proactive safety notifications when rides deviate from expected routes. Motivational Segmentation:Users can be segmented by why they use products, not just who they are or what they do. Spotify users might be goal-oriented (knowing exactly what to listen to) or inspiration-seeking (wanting discovery and recommendations). Business Impact:Research from multiple studies (including McKinsey and Harvard Business Review) shows emotionally connected users demonstrate: 2x higher retention compared to merely satisfied users 2x higher revenue through increased purchases 60% higher referral rates through word-of-mouth recommendations Implementation in Organizations: Integration Approaches: Dedicate specific PM roles to delight (rare but effective) Make space for both delight features and functional features in regular backlogs Establish product culture and principles that prioritize emotional connection Allocate a specific cadence (e.g., one deep delight feature per quarter) Jobs-to-be-Done Connection:Nesrine’s Delight Framework builds on Jobs-to-be-Done theory by making the emotional and social job aspects more actionable through specific tools like the Delight Grid and Delight Excellence Checklist. Useful Links Connect with Nesrine on LinkedIn Check out Nesrine’s new book Product Delight Visit Nesrine’s website Check out Nesrine’s Substack Innovation Quotes “Whether B2B or B2C, delight is essential in every B2H (business-to-human) industry.” – Nesrine Changuel “We don’t want to work only on things that will change over the next 10 years. We want to also

Top challenges product leaders face and how to overcome them Watch on YouTube TLDR Product leadership expert Rich Mironov discusses three core challenges CPOs and product VPs face: effectively communicating value in business terms rather than process terminology, building trust through merchandising wins before gaining decision-making authority, and reducing product waste by making better decisions about what to build. Executives don’t care how product gets made; they care about revenue impact. Success requires translating product outcomes into financial language and proving value through small wins before requesting broader organizational changes. Introduction We’re talking about the top challenges CPOs and Product VPs face. Navigating them well can cause your career to excel and result in valuable products. Navigating them poorly has career-limiting consequences. This discussion will help you avoid the latter by giving you approaches to address common product leadership challenges. Our guest has mentored more product leaders and executives than anyone else I know over his 40-year career in product roles. He has served as interim CPO for 15 companies, founded the first Product Camp, consulted to hundreds of tech companies, and wrote the book The Art of Product Management. His blog, “Product Bytes,” is widely read by product leaders. From that description, you likely already know who our guest is—Rich Mironov. Rich has seen every product leadership disaster imaginable and knows how to fix them. Let’s learn how to address and even avoid such challenges. Summary of Concepts Discussed for Product Managers First Principles for Product Leaders:Rich outlines three areas product leaders must champion: Real end users Extended teams (product managers, designers, engineers, DevOps, technical writers) Overall business health (long-term value) Speaking the Executive Language: Executives are not interested in hearing you talk about product processes and methodologies They want to know when money will arrive and how much Product leaders must translate improvements into financial impact Example: “Reducing churn by 2% equals $45-50 million more revenue and IPO one year earlier” Reducing Product Waste:Rich distinguishes between two types of waste: Engineering waste (late delivery, quality issues) – the minority Product waste (building the wrong things) – the majority of failures Focus on reducing products that “land like a dead thud in the market” The Trust-Building Problem: Moving to product-led decision making requires taking authority away from sales and marketing This creates resistance unless product teams prove they make better decisions Solution: Build trust through showing value before requesting organizational changes The Merchandising Strategy:Weekly practices for building influence by recording and communicating added value: Document and communicate product team wins in financial terms Ask your team members for names of people outside product management who did something good in the last week and thank those people through their managers Translate OKRs and metrics into monetary value Block 15 minutes every Friday for “merchandising meeting” with yourself How Product Leaders Can Make Better Use of Product Managers: Delegate product work to focus on organizational leadership Critique work as a mentor, not just a boss Help struggling product managers find roles elsewhere in the company where they’ll succeed Team Structure Preferences:Rich’s preferred team composition: 1 product manager (not writing code) 1 designer (essential for user-facing products) 4-6 developers/engineers/DevOps professionals Warning signs: 1 PM across 2 teams, 1 PM with only 3 engineers Useful Links Connect with Rich on LinkedIn Check out Rich’s blog Innovation Quote “Other people are not an imperfect version of you. They are a perfect version of themselves.”  – Pam Fox Rollin Application Questions How can you better translate your current product initiatives into financial terms that would resonate with executives? What specific metrics could you connect to revenue impact? What small, measurable wins could your product team achieve in the next quarter to demonstrate value to skeptical stakeholders? How would you merchandise these wins effectively? In your current role, what decision-making authority currently belongs to sales, marketing, or other departments that might benefit from product team input? How could you build trust before suggesting changes? Looking at your recent product releases, which ones might qualify as product waste? What could have been done differently in the decision-making process? Based on Rich’s team structure recommendations, how does your current team composition compare? Are there changes you could advocate for to improve the product manager to engineer ratio or ensure adequate design sup

Lessons from Saturday Night Live for improving product team culture Watch on YouTube TLDR John Krewson, who began his career in sketch comedy before moving to software product development, explains what product teams can learn from sketch comedy. Like comedy writers, product teams must be able to be vulnerable, throw away unsuccessful ideas, and prioritize delivering valuable products over perfect products. John shares principles and practices adapted from sketch comedy that product managers can use to balance autonomy and accountability, make meetings more engaging, and understand customer problems. Introduction What if the secret to building breakthrough products is less about an innovation framework and more about the chaotic, creative energy of a Saturday Night Live writers’ room? Specifically, can sketch comedy principles revolutionize the way your software teams collaborate, create, and deliver products that customers love? We are about to find out, and I won’t keep you in suspense—lessons from sketch comedy can make you a better product manager and developer. In this episode, you’ll hear specific techniques to transform boring meetings into energizing collaborative sessions, practical methods to help your team improve ideas fast, and a new approach to product ownership that distributes creative control without losing focus. Our guest is John Krewson, who brings a unique perspective as a 25-year software industry veteran and professional sketch comedy performer, including a brush with SNL. He’s the founder of Sketch Development Services, has coached everyone from startups to Fortune 50 companies on agile transformation, and wrote the book on applying sketch comedy principles to product development, titled Pitch, Sketch, Launch. Summary of Concepts Discussed for Product Managers John Krewson’s Journey: John began his career as a professional actor and performed as a background player on Saturday Night Live. He then switched careers to software development and worked his way up to management, leadership, and consulting roles. As a product leader, John found himself relying on his training as an actor and director. How Sketch Comedy Principles Inform Product Development:A software development team builds features without knowing whether they will satisfy the customer, in much the same way as a sketch comedy team has no idea if their sketch will be funny. The sketch comedy team mitigates risk by making their sketch only three and a half minutes long. Similar to software features, the sketch is a tight, independent unit of value, where the risk is mitigated by its independentness. John studied the process of moving from an idea to a product in sketch comedy, particularly at SNL, and, along with a comedy sketch writer, wrote about how that process could be applied to product development in Pitch, Sketch, Launch. Efficiency and Iteration:In sketch comedy, 90% of sketches don’t go on the air. Comedy teams practice their ideas on small audiences to figure out which sketches are funny before bringing them to a big show. In product development, ideas should be iterated upon using customer feedback. Vulnerability and Transparency:Sketch comedy teams have thick skins because they’ve been told they’re not funny 90% of the time. Organization culture can allow teams to be vulnerable enough to put ideas forward that may have a 90% chance of being unsuccessful. Always Be Ready:Lorne Michaels said, “We don’t go on because it’s ready. We go on because it’s 11:30.” Saturday Night Live has never missed a deadline in 50 years, not by aiming to be perfect, but by presenting the best version they can get done by Saturday. Rather than trying to figure out the most efficient way of landing the plane, they figure out the most valuable way of landing the plane. Opportunities to Play:At John’s company, Sketch, the product development teams take dedicated “play days” to play with and react to each others’ ideas, whether good or bad. Autonomy and Accountability:At SNL, sketch writers have 100% autonomy over writing their sketches during the week, but the director has accountability over the final show by choosing which sketches are performed. Similarly, product teams can balance autonomy and accountability by allowing independent units to build features, while having overarching accountability to select which features make it into the final product. Agile and Scrum:In an analogy to Scrum, on SNL, the director Lorne Michaels is the product owner, who articulates the vision for the product. The sketch writers and cast members are the development team, which executes on the vision. State managers and directors facilitate the execution and support the development team. The Role of the Product Owner:The product owner knows more about the customer than anyone else on the team. John suggests that the product owner should spend a third of their t

Winning product portfolios in physical product development Watch on YouTube TLDR In this episode, Matt Carr, VP of Design at Umbra, joins us to discuss the intersection of design leadership, product strategy, and innovation in physical product development. Matt shares practical frameworks Umbra uses to balance creative vision and business reality, offers insights into managing a global product portfolio, discusses approaches to cross-functional collaboration, and highlights how direct customer interaction (especially via e-commerce and social media) drives rapid product iteration. Product managers will find actionable tactics for portfolio balancing, design decision-making, and fostering a design-led culture. Introduction What does it take to design products that delight consumers while hitting profit targets? We are examining design leadership and product strategy with someone who has mastered both. If you’ve ever struggled to balance creative vision with commercial reality, or wondered how to scale design across global teams, this episode will give you frameworks you can use immediately. Matt Carr is VP of Design at Umbra, the Canadian-based company that designs products for every room of the home. He’s spent 25 years at Umbra, from junior designer to leading their global design operations. He’s created products that have been featured in The New York Times, Surface Magazine, and Met Home. More importantly, he’s built systems for “balancing business and imagination” that keep Umbra at the front of innovation. Summary of Concepts Discussed for Product Managers Umbra’s Global Design DNA:Matt explains how Umbra crafts products “for every room in your home.” Their five core values guide design: modern aesthetic, originality, casual sensibility, accessibility (price), and functionality. Product Portfolio Management:Umbra maintains long-standing lines (the maintenance bucket), continually innovates with blue sky ideas, and expands on successes through thoughtful derivatives, all while staying globally relevant. Case Study: Bellwood Photo Frame:As part of Umbra’s long-standing commitment to picture frames—a core “maintenance” product category—Matt Carr and his team recognized the need to innovate in a saturated market. Unlike traditional frames, the Bellwood features a single, continuous curve around the corners, giving it a modern, sculptural feel. It’s designed to look attractive from all angles, not just the front—a key differentiator from standard frames with plain or unsightly backs. The price-point allows Umbra to deliver premium feel at a price accessible to their global customer base. Practical Design Process:Matt outlines the design journey from early sketch and cardboard prototypes to iterative 3D models and tooling, emphasizing early, low-cost experimentation and the importance of cross-functional team input. The process involves: Identifying the Need or Opportunity Cross-Functional Brainstorming Early Concept Development Iterative Refinement and Prototyping Continuous Cross-Departmental Input Alignment with Brand DNA Customer Feedback and Iteration Final Development and Launch Consumer-Driven Innovation:Umbra’s internal team members often represent the target customer, but rapid feedback loops with end users—especially via e-commerce and social media—now accelerate product refinement, color choices, and new category opportunities. Ensuring Design Consistency at Scale:Matt explains how Umbra collaborates with external designers worldwide while maintaining brand DNA. Matt shares how great ideas are adapted through internal “design massage” to align with company ethos. Useful Links Learn more about Umbra Connect with Umbra on Instagram Connect with Matt on LinkedIn Innovation Quote “Your last impression is your lasting impression.” – Matt Carr Application Questions How can you adopt Umbra’s approach of balancing “blue sky” innovation and “maintenance” portfolio projects in your own product line? What are ways to involve cross-functional teams (manufacturing, sales, marketing) early and meaningfully in your design and development process? In what ways are you soliciting and incorporating direct customer feedback into product iteration, and how might you leverage newer channels like social media more effectively? How do you ensure that new product ideas—whether internal or external—consistently align with and reinforce your brand’s design principles? What prototyping strategies could you use to rapidly test and improve product concepts before significant investment in tooling or development? Bio Matt’s passion for design was first sparked when he interned at Douglas Cardinal Architects. He went on to study at Humber School of Industrial Design, where he received an ‘All-Canadian Academic’ award for scholastic and varsity achievements. An integral part of the Umbra design team since 2001, Matt has contributed countless designs to

Focused product strategy and teams Watch on YouTube TLDR In this episode, Blair LaCorte—seasoned leader, investor, former CEO of AEye, and coach to 50+ CEOs— breaks down the keys to building product teams that win. Blair shares insights on aligning product strategy with company goals, the importance of saying no and making trade-offs, and why team culture and people patterns matter more than anything. He draws on experiences across tech, aviation, private equity, and defense, offering memorable lessons on scaling organizations, product leadership, and the human side of performance (including when and how to part ways with team members). The episode closes with advice for product managers seeking purpose, growth, and ways to elevate themselves and their teams. Introduction Whether you’re a product manager trying to get your team aligned, or a product leader striving to translate executive vision into actionable roadmaps, this episode addresses the real challenges you face every day. You’ll hear from a leader who has built high-performing product teams and grown organizations across different industries, from taking autonomous vehicle tech company AEye through a $1.8 billion IPO while launching products across automotive and defense markets, to scaling XOJET into one of the fastest-growing companies in aviation history. He’s worked with over 40 companies as a private equity Operating Partner at TPG and now coaches 50+ CEOs through his Pinnacle Performance Elite mastermind. His career started in tech at Sun Microsystems and Autodesk and has spanned hardware, software, and services. If anyone knows what separates high-performing product teams from the rest, it’s our guest, Blair LaCorte. Summary of Concepts Discussed for Product Managers Focused Product Strategy & Team Alignment:Success starts with product managers who grasp both internal operations and external market realities, aligning product decisions tightly to company strategy. Focus is critical—great leaders say no more than yes. Scaling & Market Fit:Blair details how autonomous vehicle tech company AEye shifted from pure autonomous vehicles to ADAS (Advanced Driver-Assistance Systems), aligning their tech roadmap with realistic market cycles and cash flow needs. Team Dynamics & Culture: For a product team, the type of culture is less important than the consistency of the culture and the consistency of the team. Teams with alignment and clear expectations outperform more talented but chaotic groups. Winning builds healthy cultures; the feeling of progress is essential. Hard Choices & Leadership:Removing the wrong team members is tough but essential. Blair emphasizes the importance of honest feedback, quick decision-making, and quickly firing weaker performers to allow the rest of the team to move forward. Personal Growth & Knowing Yourself:Blair dives into psychology, personality frameworks, and patterns—urging product leaders to understand themselves, seek feedback, show vulnerability, and continually develop their Johari Window (the intersection of self-perception and how others see you). Technology vs. Humanity:As technology advances rapidly, keeping humanity at the center becomes more important than ever. Product managers must weigh the impact of their products, striving for both business value and societal good. Useful Links Connect with Blair on LinkedIn Learn more about PPE Mastermind Innovation Quote “The biggest threat to mankind is when our technology outstrips our humanity.” – Albert Einstein Application Questions How do you decide which product opportunities or features to say no to, and what’s your process for making those tough calls? In your experience, what factors contribute most to a consistent and winning team culture? How do you maintain this as the team grows or changes direction? What practices have you found effective (or ineffective) when giving feedback or offboarding team members who aren’t the right fit? How do you identify your own blind spots as a product leader? Which personality or feedback frameworks have helped you most? How could you practice being more vulnerable as well as accepting criticism? Bio Blair LaCorte is a groundbreaking and battle-scarred business executive and transformational leader who has leveraged his curiosity, collaborative nature and his competitive spirit into an unconventional and remarkable career journey. His experiences are also very unique from a functional perspective having taken on full time executive roles across a wide spectrum of business stages, ranging from startup to growth and from restructuring to liquidity events including sales, mergers and several IPO’s. 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

Product management lessons from Amazon’s $4 billion acquisition of One Medical Watch on YouTube TLDR Dr. Joseph Michelli—speaker, consultant, and bestselling author—joins me to explore how product innovation and exceptional customer experiences can transform industries, with a deep dive into One Medical, the patient-centered healthcare startup recently acquired by Amazon for $4 billion. The conversation sheds light on designing human-centric experiences, the strategic use of technology and AI, and the importance of empowering both employees and customers in service delivery. Practical takeaways for product managers include blending automation with empathy, continuous improvement through design thinking, and fostering workplace environments where innovation thrives. Introduction If you’ve ever struggled with whether to automate a customer touchpoint or keep it human, if you’ve wondered how to measure the “personal” side of your product experience, or if your team debates where AI helps versus where it hurts customer relationships—this discussion is for you. We’ll examine how companies dominate their markets through product innovation and customer experience that creates loyal fans, with a focus on One Medical, a start-up that Amazon acquired for $4 billion. Our guest is Dr. Joseph Michelli, an internationally sought-after speaker and organizational consultant. He is a New York Times #1 bestselling author who has spent his career inside the world’s most customer-obsessed companies—from Starbucks and Ritz-Carlton to Mercedes-Benz and Zappos. His latest book, All Business Is Personal, examines the human-centered approach that made One Medical stand out in healthcare. Summary of Concepts Discussed for Product Managers The One Medical Story:Founded by innovator Tom Lee, One Medical reimagined primary healthcare by leveraging technology for convenience, accessibility, and eliminating pain points (like waiting in both the waiting room and exam room). Their membership model allows customers to view providers’ schedules directly and schedule appointments online. Ninety-seven percent of their patients wait for less than three minutes to be seen by their provider. One Medical’s model integrates with existing health insurance, while streamlining scheduling, communication, and clinical experiences. Designing for People:One Medical designs not only for customers but also for employees. Especially in healthcare, where burn-out and lack of talent are serious challenges, a humane experience for employees is essential. One Medical leverages user experience (UX) research, streamlines workflows, and uses AI to handle administrative burdens and enhance face-to-face interactions. Practical Innovation:With influences from design thinking and Lean methodologies, One Medical empowers all team members as “spotters and solvers.” Practices like job rounding, customer walks, huddle boards, and cross-functional problem-solving are part of their DNA. Amazon’s Influence:Joseph discusses Amazon’s acquisition, culture clashes (and blends), and the unique challenge of integrating a highly human service business into Amazon’s tech-forward ecosystem. Healthcare of the Future:The integrated experience—app-based triage, same-day appointments, telehealth, and even Amazon Pharmacy delivery—showcases the potential of digital-centric, consumer-driven healthcare. Useful Links Check out All Business is Personal Connect with Joseph on LinkedIn Visit Joseph’s website Innovation Quote “Anyone can invent. Very few can innovate.” – unknown Application Questions Where do you see opportunities in your organization to redesign both customer and employee experiences using human-centered design thinking? How can your product team balance the use of automation and AI with the need for genuine human connection? What barriers currently prevent your team from regular customer empathy activities, such as shadowing or role rotation? How can frontline employees become more confident and able to solve problems in real-time? What processes or traditions does your organization repeat “because they always have”—and how could they be challenged or reimagined? Bio Joseph A. Michelli, Ph.D., C.S.P., is an internationally sought-after speaker, author, and organizational consultant who transfers his knowledge of exceptional business practices in ways that develop joyful and productive workplaces with a focus on customer experience. His insights encourage leaders and frontline workers to grow and invest passionately in all aspects of their lives. Dr. Michelli is a Wall Street Journal, USA Today, Publishers Weekly, Nielson BookScan, and New York Times #1 bestselling author. His books include: Stronger Through Adversity: World-Class Leaders Share Pandemic-Tested Lessons on Thriving During the Toughest Challenges The Airbnb Way: 5 Leadership Lessons for Igniting Growth through Loya

The biggest challenges when moving from individual contributor to product VP Watch on YouTube TLDR In this episode, I welcome Piers Fallowfield Cooper—executive coach and author of Are You Still the Future?—to explore one of the most critical career transitions in product management: moving from individual contributor to product leader. We discuss why success as a product manager doesn’t guarantee success in leadership, the mindset and skills required to thrive as a product VP, the importance of personal strengths and adaptability, and practical advice for building a successful, energized team. Introduction Let me paint a picture of a common occurrence. Product VPs and leaders start out as individual contributors, i.e., product managers. Because of their outstanding work, delivering value for the organization and delighting customers, the product manager’s responsibilities and influence quickly increases, resulting in a promotion to Product VP. Sounds great, right? Maybe not—a couple months after the promotion they are struggling and their teams are frustrated. If you were that newly promoted VP, you would be wondering if you made a terrible mistake. Let’s turn that around. This discussion will help to equip you for the most critical transition in product management careers—the leap from individual contributor to product leader. This isn’t just about getting promoted; it’s about fundamentally shifting how you think, act, and add value. And, if you are already a product leader, this discussion will also help you improve and how you mentor your ICs. Our guest is Piers Fallowfield-Cooper, who has coached over 130 C-suite executives through major leadership transitions. He’s spent 30 years in senior executive roles himself scaling companies across finance, technology, and e-publishing. His book Are You Still The Future? was a Business Book of the Year finalist in 2024. He knows how to effectively navigate the journey from individual contributor to executive leader. Summary of Concepts Discussed for Product Managers The Challenge of the Transition:Many product VPs begin as outstanding product managers, but leadership requires a shift from “I” to “we.” The skills and knowledge that led to promotion often don’t translate to success at the next level—leadership is less about specific expertise and more about asking the right questions, fostering a broader perspective, and leading through others. T-Shaped Leadership:Piers explains the necessity of moving from being a deep specialist to developing broad horizontal skills—an essential shift in most careers, including product management. Find Your Sweet Spot:Ambition doesn’t always mean you want or would be happier in a leadership role. Ask yourself why you want to get promoted and consider what trade-offs come with increased responsibility. Key Shifts for Aspiring Leaders: The move from “doing” to “thinking and leading.” Creating regular thinking time with diverse stimuli. Observing and reflecting on effective leadership styles, then building a personal leadership approach authentic to you. Focusing on helping the team succeed, rather than being everyone’s friend. Strengths, Energy & Environment: Use tools like Strengths Finder to identify what energizes you, not just what you’re competent at. Play to your energizing strengths, focus on what the business needs, and work where you add the most value. Provide an environment that fosters high performance: ensure adequate sleep, a positive environment, and fair, slightly challenging deadlines. Adaptability is key; those who are flexible can thrive in changing environments. Leadership Pitfalls & Practical Advice: Avoid “day one stupid”—don’t rush to fix things before understanding what works. Ask, “What do we do really well here?” and “Are there dumb things we should stop?” Don’t overthink or second-guess; often learning comes from experience, not theory. As a leader, work to not trigger the fight/flight/freeze response in your team by ensuring fairness, and predictability. Foster trust by showing vulnerability. Create a coaching and learning environment for your team, helping others to succeed rather than micromanaging. Useful Links Connect with Piers on LinkedIn Check out Are You Still The Future? Visit Piers’s website Innovation Quotes “The robots will adapt, will you?” – Piers Fallowfield-Cooper “Today’s certainties are tomorrow’s absurdities.” – Peter Drucker “Prediction is very difficult, especially about the future.” – Yogi Berra Application Questions What was the most surprising challenge you faced (or anticipate facing) in moving from an individual contributor role to a leadership role? How can product leaders create an environment that maximizes team performance and individual energy? Why is it important to reflect on your own motives for pursuing leadership, and what tools or approaches help with th

How product managers can make their own futures Watch on YouTube TLDR In this episode of Product Mastery Now, we’re joined by Robin Champ, VP of Strategic Foresight at LBL Strategies and Harvard Extension School instructor. Robin shares practical approaches for product managers and leaders to anticipate, rather than merely react to, disruptions in the market and competitive landscape. Through the Strategic Foresight Framework, scenario planning, and trend scanning, Robin explains how to create agile strategies that help organizations deliver value in uncertain futures. Introduction Any product manager with some experience knows the frustration of being blindsided—competitor launches that catch you off-guard, market shifts that kill your roadmap, or customer behaviors that seemingly emerge overnight. Many product teams are in a cycle of reacting to change and putting out fires. Instead, what if you could anticipate change? By the end of this episode, you’ll have the strategic foresight framework that is taught at Harvard and applied in organizations. Our guest is Robin Champ, Vice President of Strategic Foresight at LBL Strategies and Harvard Extension School instructor. Robin spent 33 years applying foresight in the highest-stakes environments—the U.S. Secret Service and Department of Defense. She trains executives on the strategic planning methodologies that equips them to stay ahead of competitive threats and create opportunities. Also, Robin is speaking on Tuesday, September 16th, 2025, at my favorite product innovation conference, the Product Development and Management Association’s Ignite Innovation Conference. Learn more about the conference at www.PDMAsummit.com. Summary of Concepts Discussed for Product Managers What is Strategic Foresight? Foresight vs. Forecasting: Foresight embraces uncertainty and explores multiple possible futures rather than making a single prediction. Scenario Planning: Organizations develop strategies by considering different directions the future could take, enabling agility and preparedness for disruption. Why Product Managers Need Foresight Competitive Advantage: With foresight, product managers are better equipped to stay ahead of market changes, competitor launches, and evolving customer behavior. Case Example: Robin describes applying scenario planning with a senior living community to anticipate shifting senior preferences and invent innovative solutions. Foresight Methodologies Environmental Scanning: Deliberately monitoring signals and trends in the market and society via tools like LinkedIn, futurist publications, and AI-powered analytics. Futures Wheel: Mapping out potential first-, second-, and third-order impacts of proposed changes or emerging trends. Bringing in Creativity: Leveraging both human creativity (e.g., involving science fiction writers) and AI tools to generate diverse and imaginative future scenarios. Practical Application Use scenario planning and futures wheels to consider the implications of market shifts, like changing education delivery models with AI and shorter attention spans. Scanning can be both manual and AI-assisted; following futurists can keep PMs ahead of upcoming trends. Strategic foresight enhances not just resilience, but also innovation and relevance. Useful Links Connect with Robin on LinkedIn Check out the Harvard course Robin teaches, Mastering Foresight: Scenario-Based Planning Register for the PDMA Ignite Innovation Conference and use code PDMAChad20 for 20% off your registration for the All-Access Pass or the Summit Pass Learn more about LBL Strategies  Innovation Quote “Organizations have to make their futures or risk being overtaken by the future.” – Clark Murdock, Future Making Application Questions How could scenario planning or the futures wheel help your product team be more agile in the face of uncertainty? In what ways are you currently scanning for trends or signals in your market? What could you do to improve this process? Where could your organization benefit from shifting from forecasting to strategic foresight in its strategy or product planning? What are the most disruptive “unknowns” facing your product category—how well prepared are you? How might you use AI or creative exercises (like science fiction narratives) to inspire future-focused thinking within your product team? Bio Robin L. Champ is Vice President of Strategic Foresight at LBL Strategies;  a Certified Strategy Management Professional (SMP);  and an instructor at Harvard Extension School. She helps organizations anticipate change, navigate uncertainty, and design strategies that drive real impact. With a background that includes leading foresight and strategy efforts at the U.S. Secret Service and the Department of Defense, Robin brings a practical, future-focused approach grounded in decades of experience. Today, she works with leaders across sectors to turn insight into action.  Thanks! Thank you for t

How product managers can build customer-centric AI products Watch on YouTube TLDR Juanjo Duran, Chief Product Officer & Chief Marketing Officer at Exoticca, joins Product Mastery Now to share how to create AI-powered product features customers actually love, not just features that sound impressive. Drawing on 25+ years in diverse leadership roles, Juanjo discusses leveraging customer obsession, data-driven decisions, and practical frameworks to balance innovation with execution. Learn how to embed AI across teams, structure innovation projects, and use the customer journey—from inspiration through to objection handling—as your roadmap for building differentiated products that deliver real value. Introduction Picture this: You’re a product leader trying to build AI features that customers actually use, not just technology that sounds impressive in board meetings. You’re scaling your product organization while maintaining innovation momentum. And you’re doing all this in an industry where the stakes for getting it wrong are high. We are discussing building smarter products that integrate AI that customers actually want. We’ll also explore practical frameworks for balancing innovation with execution in rapidly scaling organizations.  Our guest is Juanjo Duran, Chief Product Officer and Chief Marketing Officer at Exoticca, a leading travel tech platform that provides multi-day travel packages. Juanjo brings a unique perspective—25+ years in consumer goods at P&G and Mars, operations leadership at easyJet, marketing at eDreams, and now product leadership at Exoticca.   Summary of Concepts Discussed for Product Managers Key Topics & Takeaways From FMCG to Travel Tech: The Leadership Thread Juanjo describes his journey from Procter & Gamble and Mars, to travel and product leadership at Exoticca. The unifying principle? Putting the customer at the center, leveraging data-driven decisions, and focusing on how brands create value. The Travel Customer Journey Redefined In travel, the journey starts the moment a customer begins browsing for trips, not just when booking or traveling. Product pages are transformed to make users fall in love with destinations, describe the experience simply, and address objections upfront. Structuring Innovation: Purpose-Driven Evaluation Initiatives at Exoticca are filtered by their fit with company purpose: making dream trips accessible, creating extraordinary experiences, and serving customers end-to-end. Innovation efforts are prioritized by value to customers, strategic fit, feasibility, and business impact. The AI Journey: From Efficiency to Customer Value Early AI efforts focused on automating repetitive tasks for efficiency. The real shift came from asking: “How can AI deliver better value for customers?” AI is embedded across every team, used in personalizing customer experiences, managing dynamic trip pricing, addressing customer queries (pre/post booking), and predicting pricing far in advance. Innovation Project Structure Cross-functional discovery and alignment at the outset saves time later. Prototyping, rapid iteration, and A/B testing form the foundation of execution. Not every tool or solution needs to be built in-house—focus in-house efforts on core differentiators, and look outward for other solutions. Useful Links Connect with Juanjo on LinkedIn Learn more about Exoticca Innovation Quotes “The best way to predict the future is to create it.” – attributed to Peter Drucker “Inspiration? Of course it exists but it has to find you working.” – Pablo Picasso Application Questions How can your organization better map and influence the customer journey to enhance product experiences? When thinking about adopting AI, how do you balance efficiency gains versus solving genuine customer problems? What criteria should guide your decision to build versus buy AI or tech solutions? How can cross-functional collaboration be improved during the innovation process in your organization? Which part of your product experience could be transformed by focusing on customer emotions rather than solely on features or benefits? Bio Juanjo Duran is a Global Travel and FMCG Executive (CEO/CMO/CPO) passionate about how Technological transformation can improve consumers’ lives. Currently CPO and CMO of a game changing travel tech disruptor where he is exploring AI as a Value Accelerator for consumers. Juanjo was previously CEO of Deliberry, a game changing grocery business disruptor and also Venture Capital Investor and Consumer & Brand Tech Advisor. Juanjo is passionate about change and leadership. He was lucky to learn from the best leaders and the best companies: 20 years in P&G learning from the best about proactively and methodically driving brand’s constant growth, 7 years in Mars Inc learning from the best about leading people through values and principles and learning fro

The 2025 PDMA Ignite Innovation Summit Watch on YouTube TLDR Today I’m sitting down with Bill Reed and Spike Ross-Corbett, PDMA board members and co-chairs of the 2025 Ignite Innovation Conference planning committee. We reflect on top takeaways from past PDMA conferences, including invaluable lessons on customer research, adaptive product development, building cultures of innovation, and leveraging networking opportunities. Spike and Bill also offer a sneak peek into this year’s conference in Chicago, highlighting fresh formats, hands-on workshops, and powerful networking. Get practical insights to elevate your product management game and learn how to unlock a special discount for the upcoming summit. Introduction As a product professional, what is your favorite conference to attend? We have a lot of good options, but mine has been Ignite Innovation, which the Product Development and Management Association (PDMA) runs annually. I attended the first one in 2006 after hearing about it in a local group of product professionals. Since then, I have attended most years when I could, and I will be there again this year. It is being held at the Marriott Marquis in Chicago from September 13th-16th. This episode will discuss examples of what we have learned at past conferences and what we expect to learn this year. Joining me are two board members of PDMA who are also the co-chairs for the committee planning the conference—Bill Reid and Spike Ross-Corbett. Summary of Concepts Discussed for Product Managers PDMA Ignite Innovation Conference:My favorite product development and management conference, hosted in Chicago, September 13th-16th, 2025. Meet the Guests: Bill Reed: Leads product and innovation teams at Boulder Imaging, with a rich history in innovation, patents, and engineering. Spike Ross Corbett: Heads product development at Portland Marketing Analytics, focusing on making marketing ROI analysis accessible. Past Conference Takeaways: Geoff Thatcher’s Experience Design Model: Apply theme park design (attract, trust, inform, internalize, act) to product management. (423: Transforming products into experiences – with Geoff Thatcher) Andrea Ruttenberg on Voice of Customer: Needs-based interviews are the foundation for innovation success. You don’t need hundreds—just strong qualitative insights. (477: Three-step VOC system – with Andrea Ruttenberg, PhD) Marissa Mayer’s 20% Time Story: Google’s AdSense was born from a culture that allows even “bad ideas” to be pursued, powering breakthrough innovation. Networking Impact: Random dinner groups at past conferences fostered lasting professional connections. Peter Monkhouse on Embracing Uncertainty: Adaptive, iterative development and embracing uncertainty helps PMs tackle ambiguity with confidence. (439: Differences and similarities between product and project management – with Peter Monkhouse) Sarah Robb O’Hagan on Qualitative Interviews: One-on-one interviews with 12 high school athletes gave Gatorade the insights they needed to turn around a struggling company. DFW Innovation Culture (Outstanding Corporate Innovator Award Winner): Everyone can be an innovator. Cross-org training fosters every-employee innovation, even in public sector contexts. (508: The practices of the most innovative companies – with 2024 Outstanding Corporate Innovator winner) Stop the Stupid: Doug Hall’s catchphrase to remind everyone on your team to innovate. (522: Stop the stupid using proactive problem solving – with Doug Hall) AI-Accelerated Design Sprints: Hands-on workshops integrating AI with design sprints showcased in St. Louis. (517: How to conduct an AI Design Sprint – with Mike Hyzy) 2025 Conference Preview: Tangible, Practical Tools: Sessions will give attendees actionable frameworks and tools. Themed Tracks: Innovation execution Product and innovation strategy Deming Institute track on applying systems thinking to innovation Outstanding Corporate Innovator (OCI) Winners: Insights from a century-old company that’s reinventing itself and a fast-growing new entrant. Research to Reality: Engaging academics and practitioners in high-energy, collaborative sessions. Workshops Featuring Industry Experts: Competitive analysis with Dell’s Jay Nakagawa and AI applications in product with MIT’s Dave Robertson. Mastermind Sessions: Guided problem-solving sessions and deep discussions about real problems that product managers face Networking Opportunities: City tours and excursion to innovation hub (MHUB). Innovation Cafe: I’ll be conducting podcast interviews in the Innovation Cafe—come find me! Useful Links Register for the PDMA Ignite Innovation Conference and use code PDMAChad20 for 20% off your registration for the All-Access Pass or the Summit Pass Listen to interviews with Ignite keynote speakers Listen to 546: Strategic foresight gives product managers a competitive edge – with Jod Kaftan Listen to 548: Building a culture of fearless product innovation

Why product managers need a systematic framework to de-risk innovation Watch on YouTube TLDR This episode dives deep into the new ISO 56001 standard for innovation management with Dr. Magnus Karlsson, a global leader in the field and a key contributor to the standard. Learn why systematic innovation matters, how ISO 56001 can help organizations move beyond ad hoc creativity to reliable business results, and what practical steps product managers and leaders can take to build innovation capabilities—plus resources for making the standard actionable in your organization. Introduction Are your innovation efforts consistently delivering results, or do they feel more like a series of random experiments? We’re diving into systematic innovation management with one of the foremost experts in the field. This isn’t just about being more creative – it’s about transforming how your organization turns ideas into market success, reliably and repeatedly. Every product leader faces the challenge of delivering value that drives business growth while managing risk. Without a systematic approach, you’re essentially gambling with your innovation resources.  In this episode, you’ll discover exactly how to implement a systematic innovation management approach based on the recently published ISO 56001 framework. Our guest is Dr. Magnus Karlsson, Adjunct Professor in Innovation Management at KTH Royal Institute of Technology in Stockholm. Magnus has over a decade of experience as Director of New Business Development and Innovation at Ericsson, where he developed approaches to collaborative innovation. He built on that experience and for nearly 20 years has been instrumental in developing international innovation management standards with the Swedish Institute for Standards, a key contributor to ISO standards. Magnus is also a partner at Amplify, a Sweden company that helps organizations across the world to innovate. While your competitors might still be relying on inspiration and luck, you could be implementing a proven system that delivers consistent innovation results. Summary of Concepts Discussed for Product Managers Systematic vs. Random Innovation:Most organizations still treat innovation as a series of random experiments. ISO 56001 offers a holistic management system, making consistent innovation possible. The Need for Standards:Despite abundant research on what drives innovation, companies struggle to apply best practices at scale, and some organizations risk losing their innovative capability. The ISO 56001 standard codifies proven methods for innovation into a plug-and-play framework. Origins & Purpose of ISO 56001:Developed out of real-world challenges at companies like Ericsson, the standard helps organizations measure, sustain, and grow their innovation capability with clear, certifiable requirements. Framework Overview:Core elements include: Context Analysis: Understand new technologies and opportunities. Innovation Intent: Consider why you need to innovate and what you must achieve. Leadership Involvement: Engage top management in innovation, including defining innovation strategy and promoting innovation culture. Five Building Blocks of the Innovation Process: Identifying opportunities Generating ideas Validating concepts (hypothesis-driven, low-cost experiments) Development Deployment Continuous Improvement:The standard emphasizes ongoing assessment, maturity modeling, and the PDCA (Plan-Do-Check-Act) cycle to adapt and grow innovation practices. Roles in Innovation:While no fixed roles are prescribed, clear assignment and development of competencies (with a forthcoming competency framework) are critical for success. Senior leadership engagement is vital, with product managers well-positioned to drive bottom-up and top-down adoption. How Product Managers Can Use ISO 56001:Product managers can consider how their current practices may already be aligned to the ISO 56001 framework and how they could improve their practices, then fill any gaps. Certification & Practical Adoption:Adoption of ISO 56001 not only improves internal capability but also bolsters branding, customer trust, and talent attraction. While certification is new, interest is growing, especially among organizations wanting to benchmark or externally validate their innovation maturity. Useful Links Connect with Magnus on LinkedIn Check out Amplify for more resources about ISO 56001 Innovation Quote “Spend a little to learn a lot.” – Vijay Govindarajan Application Questions How would your organization’s approach to innovation change if you adopted a systematic, standard-based framework like ISO 56001? What are the biggest cultural and leadership barriers to consistent innovation in your workplace, and how could a formal management system help address them? In your product management practice, which of the five process building blocks (identify, generate, validate, develop, deploy) tends to be weakest

How product managers can master go-to-market strategies Watch on YouTube TLDR Most product launches fail not because the product is flawed, but because the launch strategy misses the mark. In this episode, product marketing expert Rebecca Shaddix shares a blueprint for go-to-market strategies that drive real impact. Discover why product and marketing must build launch plans together, how to create alignment through ongoing collaboration, and the pillars of an effective go-to-market framework, even in large or siloed organizations. Plus, learn why defining acceptable mistakes can spur faster, safer innovation, and how internal enablement and the Rolling Thunder launch approach create momentum that lasts. Introduction Let’s say you’ve built an incredible product. Your engineering team delivered exactly what you envisioned. The stakeholders are excited and you are feeling good. But guess what, 95% of product launches fail not because the product isn’t good enough, but because it wasn’t brought to market effectively. Let’s help with that by discussing the steps for creating go-to-market strategies that actually work. If you’ve ever watched a brilliant product struggle to find its audience, or felt that sinking feeling when marketing says they need “just a few more weeks” to figure out positioning, or witnessed the chaos that happens when product and marketing teams aren’t aligned, then this episode is for you.  Our guest, Rebecca Shaddix, knows a lot about creating go-to-market plans. She has built go-to-market strategies for some of the fastest-growing tech companies in the US. As Senior Director of Product Marketing at 15Five and founder of the award-winning consulting firm Strategica Partners, she’s helped launch complex products that went on to drive millions in revenue. She’s the former marketing director at GoGuardian—the fastest-growing education company in US history—and she’s been a contributor to Forbes for more than a decade.   Summary of Concepts Discussed for Product Managers The Real Reason Most Launches Fail:95% of launches stumble due to poorly executed market communication, not underlying product issues. Collaborative Go-To-Market Planning:The handoff between product and marketing is a recipe for confusion and missed opportunity. Instead, Rebecca recommends an ongoing, bidirectional process where insights are shared, teams are co-creators, and monthly (or more frequent) joint meetings ensure mutual investment and understanding. Customer Advisory Boards:Minimize silos and increase trust and credibility across teams by creating cross-functional customer advisory boards. These boards amplify customer insights and bring users closer to product leaders—and to each other. Acceptable Mistakes:Frame launches as controlled experiments. By agreeing upfront on specific, acceptable mistakes, teams can move faster, reduce anxiety, and tailor their efforts to the business’s top priorities. Rebecca’s Four Pillars of Go-To-Market: Market Insights & Research: Validate you’re building the right thing for the right people. Positioning: Clarify theme and messaging before creative work or marketing begins. Internal Enablement: Ensure every team has the right info (and only what they need) to do their job, and establish clear communication channels for post-launch feedback and problem-solving. Product Launch – Rolling Thunder Approach: Continue to respond to customer feedback and iterate after launch. Pre-Mortem and Post-Mortem Reviews:Use pre-launch (pre-mortem) meetings to predict risks and tripwires, and post-launch (post-mortem) retrospectives to reflect and continuously improve. Useful Links Connect with Rebecca on LinkedIn Learn more about Strategica Read Rebecca’s Forbes article, “Why Every Strategy Needs An ‘Acceptable Mistake” Read Rebecca’s Forbes article, “How To Create Great Go-To-Market Strategy” Innovation Quote “Know your miss” – from playing disc golf Application Questions What communication or collaboration barriers exist between your product and marketing teams, and how could you break them down? How do you currently gather and share customer insights? Could a customer advisory board improve your internal alignment or product decisions? Have you ever explicitly discussed acceptable mistakes ahead of a launch, and how might that change your team’s willingness to experiment? Of the four go-to-market pillars Rebecca describes, which is your organization strongest in, and which is most overlooked? How could you apply the “Rolling Thunder” approach to an upcoming product or feature launch in your organization? Bio Rebecca Shaddix is a seasoned marketing executive and go-to-market strategist with a proven track record of driving significant revenue growth across various industries. With a unique background that combines deep technical expertise, data-driven

A product management methodology that guarantees market success Watch on YouTube TLDR This episode is a deep dive into practical product innovation with Walter and Scott Herbst—a legendary father-son duo boasting over 230 patents and decades of product success. They share their proven, data-driven methodology, pivot stories, and the importance of truly understanding customer problems. Listeners learn how to avoid common innovation pitfalls, leverage multiple solution paths, and set themselves up for product success, whether they’re in a Fortune 100 or a startup. Introduction How does product innovation really work? This episode is a master class in the art and science of product innovation with two masters of the craft – a father and son duo who together hold over 230 patents and have shaped products you likely use every day. Innovation isn’t a buzzword for our guests – it’s the family business spanning three generations. For product managers feeling the constant pressure to create the next big thing while managing stakeholders, resources, and market realities, you’ll learn how creative ideas become commercial successes.  Our guests are Walter and Scot Herbst of the Herbst Produkt design firm. They bring an extraordinary perspective to product innovation. Dr. Walter Herbst, recognized by Business Week as one of the ‘Fathers of Product Design,’ founded his first design consultancy in 1962 and later created Northwestern University’s prestigious Master of Product Design and Development Management program. His son Scot now leads their Silicon Valley design firm, partnering with Fortune 100 companies and breakthrough startups alike on award-winning products across healthcare, consumer tech, and more.  We are about to learn practical wisdom earned through sixty years of successful product development – insights that could make the difference between your next product’s success or failure.  Summary of Concepts Discussed for Product Managers Iconic Product Stories: Smith & Nephew: A company that makes tools for medical procedures. Tasked with “how do you sell more knees?” The answer wasn’t a new product, but a redesign of the surgical tools—leading to increased sales through better ergonomics and usability. Slice: Pivoted from crowded home goods to the overlooked commercial cutting space, ultimately building a 70+ product portfolio and a successful acquisition. The Proven Herbst Innovation Methodology: Phased approach: Discovery & definition Concept development Refinement Final design Commitment to a proven, repeatable process—so much so they’ve guaranteed client success. Heavy emphasis on understanding the real problem before jumping to solutions. Tools & Tactics: Deep user research: Ethnography and direct observation to catch customer pain points and behaviors not revealed in surveys. Collaborative, iterative solution generation: Encourages bringing multiple ideas to the table, and rigorous filtering before converging on the best one. Documenting “what it is and what it is not” early, then posting for persistent team alignment. Organizational Wisdom: Methodology is the backbone—style isn’t enough. Success comes from open-mindedness and the discipline to revisit assumptions. Teams should be comfortable discarding ideas and avoiding low-hanging fruit to pursue truly valuable innovations. Useful Links Learn more about Herbst Produkt Check out the Master of Product Design and Development Management at Northwestern Check out Mastering Product Innovation Connect with Herbst Produkt on LinkedIn or Instagram Innovation Quote “There is no prize for solving correctly what proves to be the wrong problem.”  – Emeritus Dean Julio Ottino from Northwestern University “Lasting products are built on a solid foundation. A strategic approach is your bedrock.”  – Scot Herbst Application Questions How do you ensure your team truly understands the real problem before moving to solutions? What methods or rituals help your organization resist the temptation to chase the first or most obvious solution? How do you incorporate ethnographic research or direct observation into your product development process? In what ways could your innovation process benefit from more rigorous segmentation or user criteria early on? What practices do you have in place to keep teams open to pivoting—like Slice’s shift from consumer to commercial markets? Bio Walter is a partner in Herbst Produkt, Santa Cruz, CA, which has won more design awards in the US, per employee, and has been honored by the Edison Foundation every year for the last 13 years. He holds 124 US patents in housewares, hardware, medical, and commercial products. He is a Fellow of the National Academy of Inventors and the recipient of the “Distinguished Professor” award from Northwestern University where he founded the Master of Product Design and Development Management program. Additionally

How Snap-On puts customers at the center of product management Watch on YouTube TLDR In this episode, Ben Brenton, Chief Innovation Officer at Snap-on, joins me to share practical strategies for fostering a sustainable, fearless culture of innovation. Ben reveals how Snap-on transformed a traditional manufacturing mindset into one deeply centered on real customer insight. He details actionable systems that drive continual breakthrough products—not through motivational rhetoric, but through persistent field engagement, cross-functional collaboration, and relentless focus on customer needs. Whether you work in tools, software, or services, this conversation is packed with lessons on making innovation succeed in any industry. Introduction We have all been in a meeting where someone says “we need to be more innovative” but nobody can explain how to actually make that happen. These are organizations where innovation gets relegated to a buzzword in a value statement instead of becoming the driving force behind breakthrough products. This discussion will change that, providing practical insights into how to build and sustain a culture of innovation – not through motivational speeches or innovation theater, but through practical systems, processes, and frameworks that actually work.  My guest is Ben Brenton, Chief Innovation Officer at Snap-on, who for the last 18 years has built what he calls a “culture of fearless innovation” at a company known for making the tools that fix the world. Ben took a traditional manufacturing company and transformed how they approach product development by putting customer insights at the center of everything and creating systems that encourage calculated risk-taking. He’s done this across industries – from consumer goods at Kraft and PepsiCo to industrial tools at Snap-on – supporting that these principles work regardless of your market. You’ll hear practical guidance that separates companies that consistently deliver breakthrough products from those that just hope innovation will somehow happen.  Summary of Concepts Discussed for Product Managers Customer-Centric Innovation:Ben attributes Snap-on’s innovation success to putting the end user at the center of everything. Product managers, engineers, and even software developers regularly get out into the field to truly understand customer needs and pain points. Field Research Over Innovation Theater:The company invests in real-world ethnographic research—visiting customers in their environments rather than relying on surveys or remote interviews, which can result in curated or less honest feedback. Prototyping and Iteration with Customers:Snap-on involves customers throughout the development process, from early concepts to full prototypes, ensuring the team doesn’t drift from the original customer needs as ideas become reality. Cross-Functional Collaboration:Great innovation requires breaking down silos. Ben encourages engineers, marketers, product managers, and even finance and legal to participate in customer visits and debriefs, supporting a diversity of insights and buy-in. Customer Interviews:At Snap-on, product managers, engineers, and employees from all functions interview customers in the field, practicing active listening to catch deep insights. They then must bring those insights together into a business recommendation. Scaling the Culture:Ben discusses the importance of top-level support and slow organizational growth—hiring based on need and early wins, rather than building large teams up front. Storytelling Over Pure Data:To drive decisions, Ben emphasizes crafting compelling stories from real customer interactions, rather than just presenting data. Useful Links Learn more about Snap-on Check out Snap-on’s Makers and Fixers initiative Connect with Ben on LinkedIn Register for the PDMA Ignite Innovation Conference and use code PDMAChad20 for 20% off your registration for the All-Access Pass or the Summit Pass Listen to episode 120: Product development and management at Snap-on – with Ben Brenton, PhD Innovation Quote “The biggest mistakes in innovation are the products you don’t launch, not the ones you launch and fail.” – Ben Brenton “No one ever makes a decision based on data. People only make decisions based on great stories.” – paraphrase of Daniel Kahneman Application Questions What practical steps can your organization take to ensure product teams have regular, direct exposure to real customers? Have you observed innovation theater in your company, and how did it affect results? What would real fieldwork change? How can cross-functional teams be more effectively included in your product discovery and prototyping processes? What are some stories you’ve encountered where listening to customers fundamentally changed your product direction or messaging? How would a “Makers and Fixers” style camp

Vertical and horizontal alignment in product management Watch on YouTube TLDR In this episode of Product Mastery Now, I’m interviewing Mark Reich, senior coach at Lean Enterprise Institute and former Toyota executive, to demystify hoshin kanri—a Japanese strategic framework that transformed organizations like Toyota and powered major innovations such as the Lexus launch. Mark outlines how hoshin kanri enables both top-down and bottom-up alignment, creating a culture where strategy and innovation are owned at every level of the organization. Introduction Product managers know they need to align their work with their organization’s strategy. Often, it’s not clear how to actually accomplish this. We need a strategic framework that can transform how your organization innovates to support strategic objectives. Hoshin kanri is such a framework and has worked for other organizations, including helping Toyota launch Lexus, one of the most successful automotive innovations in history. By the end of this conversation, you’ll understand specific frameworks and tools, like catchball, for connecting your work to the organization’s strategy. Our guest is Mark Reich, Senior Coach at the Lean Enterprise Institute and author of the new book Managing on Purpose. Mark spent 23 years at Toyota, including six years in Japan working directly with Chief Engineers during the Lexus launch. He then managed Toyota’s North American strategic planning process during a period when the company nearly doubled in size. For over a decade, he’s coached executives at companies like GE Appliances, Turner Construction, and Nucleus Software on implementing hoshin kanri for breakthrough results. If anyone can show you how to turn strategic planning into an innovation engine, it’s Mark Reich. Summary of Concepts Discussed for Product Managers What is Hoshin Kanri?Hoshin kanri is a management methodology that defines organizational strategy and engages people at all levels to execute on core objectives. It facilitates both vertical (top-down and bottom-up) and horizontal (cross-functional) alignment. Hoshin refers to the direction of an organization and can also refer to a document of strategic objectives and actions. Kanri refers to the management necessary to execute those actions and achieve those objectives. The Power of AlignmentMark shares how Toyota’s breakthrough with the Lexus brand was achieved by aligning the whole organization—product development, marketing, sales, and manufacturing—around a clear, bold objective using hoshin kanri. It’s Not Just Top-DownSuccessful strategic execution requires both leadership direction and frontline insight. Innovation often emerges from understanding real customer problems at the ground level. Vertical & Horizontal AlignmentVertical alignment connects executive strategy with actions at every management and frontline level. Horizontal alignment ensures departments and functions work together toward shared objectives, rather than working at cross-purposes. Catchball: The Engagement MechanismThe Catchball process is a key component of hoshin kanri. It facilitates structured dialogue up and down the organization (vertical) and across teams (horizontal), fostering ownership, learning, and consensus on strategic objectives and how to execute them. Practical First Steps for Product LeadersMark explains how product leaders can start using hoshin kanri by focusing on a handful of clear objectives, breaking them down into actionable departmental and individual goals, and engaging the necessary cross-functional support. Useful Links Connect with Mark on LinkedIn Check out Managing on Purpose Learn more about Lean Enterprise Institute Innovation Quote “Innovation is a bottom-up phenomenon.” – Matt Ridley Application Questions Where does your organization currently struggle most with alignment—vertically between strategy and frontline execution, or horizontally across teams and functions? How could adopting a framework like hoshin kanri help your team connect day-to-day tasks to high-level strategic objectives? What processes (if any) does your organization have in place to capture the raw voice of the customer from those on the frontlines, and how could this be improved? In the context of your current or most recent product launch, what would catchball look like as a structured approach to achieving cross-functional buy-in and action? What three to five strategic priorities would make the biggest impact in your organization if everyone was genuinely aligned and accountable for them? Bio Mark Reich spent 23 years working for Toyota, starting in 1988 with six years in Japan in the Overseas Planning Division, where he was responsible for Product Planning and collaborated with Chief Engineers to define vehicle specifications for overseas markets. This pivotal time was when Toyota introduced the Lexus to the world.  In 1994, Mark returned to the

How product managers can see around corners Watch on YouTube TLDR In this episode of Product Mastery Now, I’m interviewing Jod Kaftan, service design leader at Launch by NTT Data and former head of product design and research at Oracle, to explore strategic foresight—a methodology that moves product managers beyond traditional road mapping to anticipate and shape the future their products will compete in. Jod explains how evidence-based imagination creates competitive advantage and shares practical tools for applying futuristic methodologies to product development, helping teams escape short-term thinking and position themselves for the futures they can see coming. Introduction Too many product managers are building tomorrow’s products with yesterday’s planning methods. While your competition is reacting to trends after they’ve already taken hold, what if you could be the one who sees the trends coming? In this episode, we are exploring a methodology to give you that advantage—strategic foresight for product managers. This allows you to move beyond traditional road mapping to anticipate and shape the future your products will compete in. This is evidence-based imagination that gives you a real competitive edge. Our guest is Jod Kaftan, previously the Head of Product Design and Research at Oracle and now the service design leader at Launch by NTT Data. With over 20 years of experience helping organizations from Sony, Google, Wells Fargo, and others navigate uncertain futures, Jod is known for moving teams beyond traditional 3-horizon planning to apply real futurist methodologies. He’s pioneered approaches that turn “evidence-based imagination” into competitive advantage. Also, Jod is keynoting at my favorite product innovation conference, the Product Development and Management Association’s Ignite Innovation Conference. It is Sept 13th-16th in Chicago. Go to PDMAsummit.com for details about the conference. Miss this conversation and your roadmaps will stay trapped in short-term thinking while more strategic competitors position themselves for the futures they can see coming. That’s a risk you can’t afford, and this episode will equip you to avoid it. Summary of Concepts Discussed for Product Managers Human-Centered Approach to InnovationJod emphasizes expanding human-centered design beyond end users to include all stakeholders—frontline employees, partners, and anyone involved in delivering customer value. This front-stage/backstage perspective recognizes that improving employee experience inevitably improves customer experience. What is Strategic Foresight?Strategic foresight is an evidence-based imagination approach that moves beyond prediction to explore what’s probable, possible, and preferable. It’s about getting out of the prediction business and into building more agile, adaptive organizations by using personal agency to curate preferred futures anchored in values. The Triangle Framework: Probable, Possible, PreferrableJod outlines a framework starting with probable futures (what’s likely), expanding to possible futures (what could be), and culminating in preferred futures (what we want based on our values). This creates guiding images that point back to actions we should take today. Evidence-Based ImaginationStrategic foresight uses detailed, systematic imagination that activates multiple brain regions. By imagining futures with painstaking detail, teams can create more robust strategic responses. Scanning SignalsPractical foresight begins with collecting signals—evidence of the future in the present—organized in some way, such as by industry or by Social, Technological, Environmental, Economic, and Political (STEEP) categories. Signals from outside your industry can be particularly valuable. These signals become themes that inform scenario planning and strategic action. The Future of Product ManagementJod envisions product managers becoming orchestrators of the product development cycle, working with AI tools while maintaining the uniquely human capabilities of collaboration, novelty, and innovation that prevent commoditization. Useful Links Connect with Jod on LinkedIn Learn more about Jod’s executive coaching, Design-Led Futures Register for the PDMA Ignite Innovation Conference and use code PDMAChad20 for 20% off your registration for the All-Access Pass or the Summit Pass Innovation Quote “The skill of the 21st century will be unlearning and learning.” – Alvin Toffler Application Questions What signals are you currently seeing in your industry that could indicate major shifts in the next 10 years, and how might these impact your product strategy? If you applied the probable-possible-preferrable framework to your product roadmap, what preferrable future would you want to work toward, and what values would anchor that vision? How could you start building the muscle memory of signal colle

How PDMA used VOC research to drive innovation Watch on YouTube TLDR In this episode, Kristyn Corrigan shares insights from a recent Voice of the Customer (VOC) research project for the Product Development and Management Association (PDMA). We explore how product professionals can move beyond assumptions to capture meaningful customer insights, the methodologies behind robust VOC research, and actionable findings that can transform both products and organizations. Key takeaways include practical steps for conducting qualitative and quantitative VOC and understanding how to identify the most valuable unmet customer needs. Introduction Here’s the brutal truth about customer research: Most product managers and innovators think they know their customers, but they’re building products for assumptions, not real people. In this discussion, we are detailing a recently completed Voice of the Customer project that’s helping the longest existing professional association for—guess who—product managers and innovators! That’s right—the VOC project was to better understand who the ideal customers of the professional association are and what their needs are. The association is one I’ve talked about before—PDMA, the Product Development and Management Association. If you’ve ever struggled to get meaningful customer insights, felt overwhelmed by diverse customer segments, or wondered how to turn research findings into actual product changes, this episode is for you. Our guest is Kristyn Corrigan, Principal at Applied Marketing Science and PDMA Board of Directors member. With 17 years of consulting experience, she’s helped companies transform customer insights into successful products. She leads the Insights for Innovation practice, has published work in Fast Company, and guest lectured at MIT Sloan. Summary of Concepts Discussed for Product Managers Genesis of the PDMA VOC Project:Motivation behind conducting formal VOC research for PDMA after a 20-year gap—driven by the need to understand current and prospective members’ needs, retention, and engagement strategies. Segmentation Strategy:PDMA membership includes academics, practitioners, and service providers. The research intentionally sampled a mix across these segments and various career stages (early, mid, late). Methodological Approach: Qualitative, in-depth interviews kicked off at the 2024 PDMA conference (21 interviews with diverse participants). Ensured unbiased sampling, including non-members and attendees at other industry events. Use of open-ended discussion guides and a focus on eliciting stories and real experiences to minimize bias and dig deeper into needs. Transcription and Analysis: All interviews were transcribed verbatim. Introduction of a fine-tuned AI model specifically developed for qualitative VOC analysis, trained on numerous past studies. Side-by-side analysis showed high overlap between AI and human analysts, but each also uncovered unique needs. Quantitative Follow-Up: Validated qualitative insights with a broader online survey. Built an opportunity matrix based on need importance and market performance, highlighting areas for innovation. Insights PDMA Learned from VOC Research: Certification is important, but well met in the market—opportunities for innovation exist in building meaningful community, providing personalized and actionable knowledge, and enabling networking. The dangers of jargon and acronyms for newcomers—need to create an inclusive onboarding experience. Emphasis on listening, story-based interviewing, and detaching from bias or defensiveness during research. Tips for Conducting VOC Interviews: Start with easy, open-ended questions. Move from broad to specific, anchoring discussions in the customer’s actual experiences. Build trust, clarify you’re there to listen (not sell), and focus on what genuinely matters to the customer. Useful Links Learn more about Applied Marketing Science Connect with Kristyn on LinkedIn Listen to episode 071: How product managers can conduct Voice of the Customer research Listen to episode 529: Is this the best AI-powered market research approach? – with Carmel Dibner Innovation Quote “It takes as much time to solve a bad problem as it does a good problem. And if you’re not working on good problems, you’re really wasting your time.” – Abbie Griffin Application Questions What assumptions about your customers guide your current product decisions, and how might VOC research challenge or refine them? How does your team currently segment customer research participants, and are you capturing the full spectrum of user experiences and needs? What practices could you adopt to ensure interviews produce genuine, story-driven insights rather than surface-level feedback or solution requests? Where could incorporating AI tools into your VOC process save time or reveal new types of customer needs not easily visible through manual analysis? How can findings from VOC resear

A product manager’s journey to Product VP Watch on YouTube TLDR In this episode, I talk with Adam Feinstein, Vice President of Product at AppFolio, about what makes a great product leader in technology organizations. Adam shares his journey from electrical engineering in semiconductors to leading product teams in software, discussing the transitions, challenges, and valuable lessons he’s learned along the way. We explore topics like transitioning between industries, moving from individual contributor to leader, the importance of people problems over technical ones, business acumen, collaborating across functions, the value of mentors and coaching, and Adam’s strategies for staying organized and effective as a VP of Product. Introduction What distinguishes great product leaders in complex technology companies, and how do you become a great product leader? Is it technical knowledge, business acumen, or something else entirely? In this discussion, we’ll examine product leadership in tech organizations.  Our guest is Adam Feinstein. We met at a product leadership group Rich Mironov organized to help product leaders excel. Adam is Vice President of Product at AppFolio. He has navigated the challenging journey from individual contributor to executive leadership, including switching from the hardware industry to software. AppFolio is transforming property management through innovative cloud-based solutions. Whether you’re an aspiring product manager wondering about your career trajectory or a seasoned leader facing complex challenges, Adam’s candid insights on successes and trials will be helpful.  Summary of Concepts Discussed for Product Managers Adam Feinstein’s Career Path: Transitioned from semiconductor physics to software product management. Valued curiosity and willingness to learn over static domain knowledge. Took a step back in job title to move into software, which paid off in the long run. Key Product Leadership Transitions: Moving from individual contributor to group product manager was a significant growth point, emphasizing hiring, networking, and giving away ideas. Director and VP roles require more focus on people and cross-organizational collaboration. Learned the mantra: “Every problem is a people problem.” Importance of Business Acumen: Early exposure to business fundamentals (P&L, costing, pricing) was important. Understanding the business “money story” and being able to speak the language of business helped in senior roles. Collaboration and Communication: “Slow is smooth, smooth is fast” – taking time to align stakeholders leads to better and faster outcomes. Effective communication and ensuring others truly understand intentions and strategy is vital. Coaching, Mentorship, and Growth: Adam benefited from a variety of mentors, each teaching a different skill (business, marketing, strategy). Personal coaches were instrumental, especially in creating frameworks and honing people skills. Role of a VP of Product: A typical month is focused on clear priorities, impactful writing, coaching, product reviews, and cross-functional advocacy. Leverages AI tools like ChatGPT and Claude for clarity and efficiency in writing. Notes the reality of long hours and the need to balance family commitments. Challenges in Product Leadership: VP roles require balancing multiple priorities, not just optimizing for one goal. Clarity, focus in communication, and creative problem-solving are critical. Training and Continuous Learning: Foundational product management courses and ongoing coaching have been vital. Most recent coaching is focused more on human psychology and interpersonal dynamics rather than just product methods. Useful Links Connect with Adam on LinkedIn Learn more about AppFolio Innovation Quote  “Slow is smooth. Smooth is fast.” – Adam Feinstein Application Questions How does the perspective that “every problem is a people problem” shift the way you think about solving organizational or product challenges? When communicating with your team or cross-functional teams, what are some practical tactics to ensure your message is both clear and empathetic? What role have mentors or coaches played in your growth as a product professional, and how did you find or select them? If you don’t have a mentor, how could you find one? Or how could you be a mentor to someone else? How do you balance personal life with demanding leadership roles, and what boundaries or strategies have worked for you? Bio Adam Feinstein is the Vice President of Product Management at AppFolio, where he leads the Resident Industry Segment, a business dedicated to creating a modern, connected experience for renters—from application through move-out—and helping property managers deliver exceptional service throughout the resident journey.  Since March 2025, Adam has embraced this new strategic focus, after previously leading product management for AppFolio’s

UX research practices to maximize product team resources Watch on YouTube TLDR During my conversation with Nick Cawthon, a UX research expert who drives innovation at Gauge and teaches at the California College of Arts, we explored how product teams can strengthen their customer research capabilities without slowing down development. Nick emphasized that while technology is accelerating design and development at unprecedented speeds, successful product managers must balance this velocity with strategic research methods like ethnographic studies and observational research. The key insight: Investing time upfront in understanding what customers actually need—not just what they say they want—prevents building dead-on-arrival products and saves significant development resources. Nick shared practical approaches for resource-constrained teams, including guerrilla research techniques at conferences and mixed methods combining qualitative insights with quantitative data. Key Topics De-risking product development through upfront customer research investment Ethnographic research methods Rapid research strategies AI integration in research Guerrilla research techniques Building research capabilities within existing product teams without dedicated researchers Service design perspective for understanding complete customer journey experiences Introduction We’re talking about research methods and tools that drive smarter product decisions. This is research that helps you uncover what customers really need, not just what they say they want. If you’ve ever wondered how to get better insights without slowing down development, this episode is for you. You’ll walk away with practical advice on how to strengthen your team’s research muscle, even if you don’t have a dedicated researcher. To help us, our guest is Nick Cawthon. Nick has been shaping the UX and research space in San Francisco for decades. He’s spoken at Google’s Tech Talks, Stanford, and PARC. He is an adjunct professor at the California College of the Arts and a Data Science Program Mentor at the University of California. He now drives innovation at Gauge, which helps companies solve complex design challenges. They integrate mixed methods research approaches into product design process to create products customers want, need, and love. The Evolution of UX Research in Product Development The landscape of product development fundamentally shifted when Apple introduced the iPhone, and with it, a new understanding of what makes technology truly user-friendly. During my recent conversation with Nick Cawthon, a seasoned UX research expert who has been shaping the research space in San Francisco for decades, he reflected on this pivotal moment that transformed how we approach customer research methods. Before 2010, Nick explained, anyone claiming to be a UX practitioner would raise eyebrows because the field simply wasn’t mainstream. The concept of user experience research was largely unknown outside specialized circles. However, the iPhone’s success sparked a question across the tech industry: Why do Apple’s products “just work” while others require extensive user manuals and troubleshooting? The iPhone marked a fundamental shift from subjective design approaches to objective, research-driven product development. Nick described how designers previously operated from a place of personal expression, creating products based on individual aesthetic preferences rather than user needs. The iPhone era forced a dramatic change in methodology—designers could no longer rely on personal taste alone. The transformation introduced behavioral sciences into mainstream product development. Research methods that were once confined to academic settings suddenly became essential tools for product teams. This evolution moved design from being an expression of self to a systematic approach focused on guiding users through experiences as intuitively as possible. Nick noted that early attempts at understanding user behavior included primitive methods like heat maps and click tracking during the Web 1.0 era. These tools attempted to decode where users focused their attention, though the insights were often scattered and difficult to interpret. This historical context matters for product managers because it highlights how recently customer research became integral to successful product development. Understanding this evolution helps explain why many organizations still struggle to implement effective research practices—they’re building capabilities that only became industry standard within the last fifteen years. The shift from subjective to objective design thinking represents more than just a methodological change. It established the foundation for modern product management research strategies that prioritize user needs over internal assumptions, setting the stage for the sophisticated research approaches that drive successful products today. The Ne

Product portfolio management skills that transform product managers into strategic leaders Watch on YouTube TLDR Innovation portfolio management is the bridge between strategy and execution that many product managers overlook, yet mastering it becomes essential for both successful idea championing and career advancement into senior leadership roles. Colin Nelson, Chief Innovation Consultant at Hype Innovation, explains how effective portfolio management requires strategic alignment through foresighting and core competency analysis, agile design with regular review cycles, and the implementation of an “innovation shelf” to store viable concepts for future development. Organizations must balance resources across incremental improvements, adjacent innovations, and disruptive projects while leveraging both internal teams and external partnerships to accelerate development and reduce risk. The key lies in creating transparency across all innovation efforts, establishing common data collection methods, and building flexibility into the portfolio to pivot when market conditions change. Key Topics Portfolio Management Fundamentals Strategic Innovation Alignment The Innovation Shelf Strategy Agile Portfolio Design Resource Optimization Three-Tier Portfolio Structure Collective Intelligence Portfolio Review Processes Introduction Have you ever pitched a brilliant product idea only to watch it disappear into the corporate abyss? When I teach product managers about the seven elements of product mastery, their eyes often glaze over when we reach portfolio management. “That’s someone else’s job,” they say, usually referring to senior leadership. But here’s the wake-up call that changes their perspective: First, you’ll never successfully champion your ideas if you don’t understand how they fit into the larger portfolio puzzle. And second—for the career-minded among you—you won’t ascend to senior leadership positions without understanding how portfolios are constructed and managed. Those are two good reasons to learn more about portfolio management, which is why Colin Nelson is joining us. Colin is the Chief Innovation Consultant at HYPE Innovation, a leading provider of innovation management software and consulting services. He is an expert in the field of Collective Intelligence, supporting global organizations and communities on how to achieve efficient, effective, and sustainable innovation and business change using online tools and processes. Colin is a respected thought leader on several innovation subjects, including Innovation Management, Enterprise Collaboration, and Innovation Portfolio Management, publishing numerous articles on these topics. So whether you’re trying to get your product ideas noticed or plotting your path to senior leadership, today’s conversation will equip you with the portfolio management knowledge you need to succeed. The Four Pillars of Innovation Performance In Colin’s work helping companies improve their innovation performance, he noticed four main themes that create the foundation for effective innovation portfolio management and provide a roadmap for systematic improvement. Absorbing External Signals Employee Involvement in Innovation Value Chain Innovation Effective Portfolio Management Today, we’ll focus on portfolio management. Why Product Managers Must Master Portfolio Management Colin described portfolio management as the journey that determines whether innovations move from ideas to market reality. Without mastering these skills, product managers remain stuck at the tactical level, unable to influence strategic decisions or demonstrate the business acumen that senior roles require. Understanding innovation portfolio management transforms how product managers approach their work. Instead of focusing solely on individual projects, they begin thinking about how their initiatives contribute to the organization’s overall innovation strategy. This shift in perspective not only increases the likelihood of project approval but also positions product managers as strategic contributors who can see the bigger picture and make decisions that benefit the entire organization. Objectives of Portfolio Management The primary objective of innovation portfolio management is protecting the organization’s future relevance in world of regular disruption. Innovation represents tomorrow’s sales, making portfolio decisions critical for long-term survival and growth. Organizations that fail to manage their innovation portfolios effectively often find themselves unprepared for market disruptions or changing customer needs. Portfolio management also creates efficiency in the development process by establishing clear frameworks for resource allocation and project prioritization. This efficiency becomes especially important when organizations face capacity constraints and must choose between multiple promising

How to be a future-proofed product manager Watch on YouTube TLDR In my recent conversation with Steve Johnson, former lead instructor at Pragmatic Marketing and product management coach with 30 years of experience, we explored how AI is reshaping product management. Steve emphasized that while AI will automate many tactical aspects of product management, the strategic role becomes even more critical. Product managers must focus on understanding customer problems rather than jumping to solutions, avoid disconnection from customers, and break down organizational silos. As AI transforms our work, product managers who embrace their strategic role will thrive, while those who don’t risk becoming obsolete. Key Topics AI’s impact on product management roles and responsibilities Using AI as a companion rather than a replacement The importance of a problem-centered approach How organizational structures often hinder effective product innovation The evolving role of Product Ops and its proper implementation Breaking down organizational barriers to information flow Introduction Today’s episode is a free-form discussion. In this series, I’m reaching out to past colleagues and experts whom I’ve talked with before to catch up and discuss the state of innovation and product management. My guest doesn’t know what I’m going to ask him, and I don’t know what he’s going to ask me. With me is Steve Johnson. I have known Steve Johnson for a few years. I knew him by reputation when he was the lead instructor at Pragmatic Marketing, where he led instructional efforts and created training for 15 years you. We met at a conference a few years ago and have kept up since then. Today, Steve coaches product teams with a focus on the strategic role of product management, which will come into our discussion today. AI’s Impact on Product Management Steve began our discussion by mentioning his concern about the impact of AI on product management. He told a personal story that illustrates AI’s current capabilities. After experiencing heart-related concerns, he wanted to analyze his medical history to identify any patterns. Faced with ten years of text-based medical records, he uploaded the PDFs to ChatGPT and asked it to create a chart tracking his blood pressure, pulse, and weight over time. Within seconds, he had the visualization he needed. However, later someone asked him if he was concerned about training the model with his personal health data. Like many people, Steve had never considered this concern before. Many professionals are uploading sensitive information to AI systems without fully understanding the implications. Sales teams upload call sheets, product managers share product ideas, and countless others input proprietary data into these systems without considering who might access this information. For product managers specifically, Steve described AI as a “watershed” moment comparable to the introduction of the internet and World Wide Web—a truly business and life-changing technology. His perspective balanced optimism with caution: Opportunities Challenges Elimination of tedious product management tasks Long-term employment concerns as AI replaces roles Ability to build more products, faster Economic concerns if AI displaces too many jobs Greater need for strategic product decision-making Privacy and security risks with sensitive data Steve articulated a perspective that should reshape how we think about our roles: As AI makes it easier to build more products, it becomes increasingly critical to ensure we’re building the right products. As AI automates the tactical aspects of product management, the strategic role becomes more important than ever. This theme—that product managers must embrace their strategic function or risk being replaced by AI—emerged as a central concern throughout our conversation. In an era where AI can quickly generate requirements documents, mockups, and even code, the unique human ability to understand customer problems and make strategic decisions becomes the key differentiator for product managers who want to remain relevant. The first phase of AI integration into product management is already happening, with tools like ProdPad incorporating AI capabilities directly into their platforms. These integrations streamline workflows by allowing product managers to leverage AI without switching contexts. For example, a product manager might use an AI assistant within their product management tool to analyze customer research data and identify potential gaps in understanding. However, the fundamental question remains: As AI transforms how we work, what aspects of product management will remain uniquely human, and how can product professionals position themselves to thrive in this new landscape? AI as a Product Manager’s Companion We discussed the possibility of using AI as a workplace companion rather than a replacement

How product managers can build an environment for breakthrough innovation Watch on YouTube TLDR In my conversation with Catherine Connelly, a 20-year tech entrepreneur who co-founded MyYearbook at 15 and grew it into The Meet Group (a $500 million exit), we explored how to build environments where breakthrough product innovation happens consistently. Catherine emphasized that innovation culture starts with founders but can be cultivated by anyone willing to embrace failure, iterate quickly, and keep customers at the center of all decisions. The key is creating psychological safety, celebrating learning from failures, and making risk-free experimentation possible. Key Topics Building psychological safety that enables risk-taking Structuring product results meetings that celebrate learning from failures Creating systems that make experimentation truly risk-free Implementing a “kill fast” mindset for unsuccessful products and features Using customer stories to drive meaningful innovation Balancing operational execution with innovation initiatives Leveraging storytelling to gain support for innovation efforts Introduction Ever wondered why some teams consistently create breakthrough products while others are barely keeping up on maintenance work?   Today, we’re tackling how to build environments where product innovation actually happens! Every product leader has watched promising ideas die because of organizational roadblocks, excessive caution, or flawed decision processes. You know firsthand that brilliant concepts mean nothing without the right conditions to develop them. From this episode, you’ll walk away with methods to immediately transform how your team innovates.  Our guest, Catherine Connelly, is a 20-year female tech entrepreneur. She co-founded MyYearbook at 15 years of age and grew it into The Meet Group, a social dating company, later achieving exits totaling $600 million. Her recent book Designing Success: Lessons from 20 Years as a Female Tech Entrepreneur captures two decades of creating environments where breakthrough innovations thrive despite constant market shifts. Building a Foundation for Innovation Culture Catherine explained that innovation culture starts with the founding team and how they approach work from the very beginning. At MyYearbook, the foundation for innovation began with a sibling dynamic between Catherine and her brothers that created natural psychological safety. Working with her brothers meant they were used to bouncing ideas off each other without fear of judgment. This family dynamic established an environment where team members could pitch ideas without worrying about negative consequences if those ideas didn’t succeed. The understanding that a person’s worth isn’t tied to the success of their last idea became a cornerstone of their innovation approach. For product managers looking to foster innovation, the culture supporting innovation typically comes from the founders or founding team. How things work from the very beginning shapes the organization’s approach to experimentation and risk-taking. Catherine described how this initial foundation allowed her team to maintain a culture of innovation throughout the company’s growth: Open Communication: Regular team meetings where discussing failures was normalized Psychological Safety: Creating an environment where people could share “dumb ideas” without repercussions Focus on Learning: Treating unsuccessful experiments as valuable learning opportunities Collective Ownership: Recognizing that innovation can come from anyone, not just the product team This foundation of psychological safety made it possible for the organization to take the calculated risks necessary for breakthrough innovation. When team members don’t fear judgment or career consequences for failed attempts, they’re more willing to propose novel solutions and challenge established thinking. The key takeaway for product leaders is that building an innovative environment starts with establishing these foundational elements of safety, open communication, and a learning mindset. Without this foundation, other innovation practices and processes are unlikely to yield significant results, regardless of how well they’re implemented. Structuring for Innovation: Product Results Meetings Catherine shared how her team built systems that reinforced their innovation culture, with product results meetings being a crucial component. These weren’t typical status meetings focused on celebrating wins—they were structured learning sessions where teams reported experiment results regardless of outcome. What made these meetings unique was their deliberate emphasis on failed experiments. Catherine explained that at The Meet Group, they dedicated more attention and discussion time to experiments that didn’t succeed than to those that did. This counterintuitive approach re

How product leaders can stay as focused as a bee Watch on YouTube TLDR In today’s distraction-filled world, product managers and leaders struggle to maintain focus. In my recent podcast interview with Jones Loflin, author of Focused as a Bee, we explored how the honeybee’s remarkable focus and intentionality can teach us valuable productivity lessons. Jones shared six “permissions” that form a framework for improving focus, along with practical strategies for managing distractions and creating environments conducive to deep work. This article unpacks these concepts specifically for product leaders looking to enhance their productivity and effectiveness. Key Topics Lessons from honeybees for product managers The difference between being “busy” versus being “focused” The six permissions to focus: Prioritize, Plan, Be Unavailable, Recharge, Change, and Be Consistent Practical strategies for managing both internal and external distractions Creating triggers and environments that support focused work Applying focus techniques with limited schedule control Using focus to drive product innovation and change management Introduction Have you ever reached the end of your workday and wondered, “What did I even accomplish today?” With endless emails, notifications, and distractions pulling us in every direction, staying focused feels harder than ever. But what if we could take a lesson from one of nature’s most efficient workers—the honeybee—to regain control of our attention and productivity? That’s exactly what today’s guest, Jones Loflin, will share with us—practical tips and mindset hacks for improving our focus. Jones is a successful speaker and the author of several books including his latest, Focused As A Bee, as well as Always Growing, Juggling Elephants, and Getting To It. He also worked as a senior trainer on the best-selling book, Who Moved My Cheese? Jones has 30 years of experience, growing confident leadership, implementing change and improving productivity with simple, no-fluff solutions. Focused as a Bee The statistics are sobering: 79% of professionals find it impossible to focus for more than an hour, with 59% unable to maintain focus for even 30 minutes. Our thoughts typically shift to something else after just three minutes. Most of us have heard the phrase “busy as a bee,” but Jones challenged this common expression. Being busy implies activity but not necessarily accomplishment. Through his experience as a beekeeper, Jones observed that bees are actually “focused as a bee” — intentionally directing their time and energy toward what’s most important at every moment. This distinction is critical for product leaders. In our world of constant demands and shifting priorities, we can easily fall into the trap of being perpetually busy without achieving meaningful outcomes. The honeybee, however, demonstrates an unwavering commitment to what matters most for the colony’s survival and success. Jones’s journey into beekeeping began when he and his daughter received a hive as a gift. Their first colony died after a year because they weren’t good beekeepers yet. This experience taught them an important lesson: Bees have a mind of their own and remain laser-focused on what they want to accomplish. While humans can assist them, we can’t change their fundamental nature. For product leaders, this serves as a reminder that success requires more than just activity. It demands intentional focus on outcomes that drive value for customers and the organization. Just as a bee’s focus is often a matter of colony life and death, our ability to focus on what truly matters can determine the success or failure of our products and teams. The book Focused as a Bee takes the form of a business parable about two individuals: one struggling with focus and another who has learned focus principles through beekeeping. Through their story, Jones introduces six key permissions that can help anyone, especially busy product leaders, improve their focus and productivity. Permission to Focus The first step of Jones’s framework is giving yourself permission to focus. This might sound obvious, but Jones’s pointed out that most of us naturally give ourselves permission to be distracted without realizing it. We respond to every notification, allow frequent interruptions, and rarely create conditions that support deep concentration. For product leaders, intentional focus requires acknowledging that it doesn’t come naturally in our distraction-filled environments. It demands conscious effort and deliberate actions. Without this fundamental permission, we end up with those days where we ask ourselves, “Where did the time go?” or “What did I actually accomplish?” Under the overarching permission to focus, there are six other permissions that we can must give ourselves in order to stay f

How LEGO built a passionate community that drives product growth Watch on YouTube TLDR Community-driven product development transformed LEGO from near-bankruptcy to industry leadership by engaging adult fans and positioning LEGO as a creative medium. This approach creates authentic relationships with customers who become collaborators, advocates, and co-creators for your products, ultimately driving innovation and business results. Key Topics Relational not transactional: Build genuine relationships where “everybody goes home happy” rather than viewing community as free marketing or support Four-part framework to build a community: Find the right people, identify the right timing, define clear outcomes, and design engaging activities The “Octopus Theory”: Community engagement delivers multiple simultaneous benefits including better product decisions, advocacy, team motivation, and competitive differentiation Ecosystem thinking: Communities influence broader audiences beyond direct participants Executive champions: Senior-level support is crucial for sustainable community initiatives Power of direct interaction: Engineers and product teams respond to feedback when hearing directly from customers Shared purpose: Rally around something bigger than either individual benefits or company goals Introduction Today we are talking about building passionate communities that drive product growth. How can you create authentic, engaged communities that transform your product’s trajectory? We’re talking about turning fans into collaborators, advocates, and even co-creators. As a product manager, you need to know how to build something customers don’t just use—but love. This discussion will explore the steps to tap into the power of community, learning from successful examples at LEGO and Apple.  Our guide to make all this happen is Jake McKee—the original LEGO Community Guy. He didn’t just grow a community—he helped change the culture of one of the world’s most iconic brands, reviving a rapidly declining company. Today, he advises organizations on how to build loyal communities that fuel innovation and drive business results.  This discussion will help you avoid disaster and instead deliver sustained growth. The LEGO Turnaround Story: A Community-Driven Renaissance When Jake McKee joined LEGO in the early 2000s, the iconic brand was heading toward a financial cliff. By 2003, the company was nearing bankruptcy – a fact that many people today don’t fully appreciate. The problem stemmed from a fundamental misunderstanding of what made LEGO special. In an attempt to stay relevant in a world where children had less free time for play, LEGO had simplified their products – replacing multiple bricks with larger, single-piece components that reduced building time. As Jake explained, this strategy backfired spectacularly. The simplified products lost the core appeal of LEGO– the ability to build and rebuild with flexible components. The result was “the world’s worst toy” – not good as a traditional toy and not good as a LEGO product. Jake joined LEGO Direct, a division tasked with centralizing all direct-to-consumer efforts, including: Catalog sales Early online presence Exclusive kits development Adult fan engagement What’s particularly interesting is that Jake took on a dual role – performing his official job as a senior web producer while simultaneously building relationships with adult LEGO fans, a group the company had completely ignored for decades. Initially, this community work gained little traction within LEGO. But when the financial crisis hit and marketing budgets were slashed, Jake’s “free marketing” approach through community engagement suddenly became attractive to colleagues who had previously dismissed it. Key Phases of LEGO’s Community-Driven Turnaround Phase Challenge Community Solution Result Pre-crisis Declining sales Identifying adult fans as untapped market Early exclusive kits for adults Financial crisis (2003) Near bankruptcy Leveraging fan enthusiasm for marketing Opening company to external collaboration Recovery Rebuilding brand relevance Co-creating with adult fans (Mindstorms 2.0) Featured on Wired magazine cover Long-term growth Sustaining innovation Establishing LEGO as a creative medium Adult fans now represent 45% of business This transformation didn’t happen overnight. Jake spent years building relationships and gradually shifting the company’s perspective. The breakthrough moment came with the Mindstorms 2.0 (NXT) project, where LEGO brought in adult fans to help design the product – a radical departure from their previous closed development approach. Beyond Demographics: The Ecosystem Approach to Community Building One of the most valuable insights from my conversation with Jake was his emphasis on thinking beyond demographic segments. Rather than simply targeting adult LEGO fans as a market, he p

Sustainable product management drives business success Watch on YouTube TLDR Sustainable product management integrates environmental considerations into the entire product lifecycle, creating value for businesses, customers, and the planet. Kaila Byrzgalski’s experience at Steelcase demonstrates how a dedicated sustainability role can bridge the gap between corporate environmental goals and product innovation. By approaching sustainability as a core business strategy rather than a separate initiative, product managers can discover opportunities to reduce costs, attract environmentally conscious customers, and build more resilient products. Key Topics Cross-functional integration is essential – sustainability connects portfolio management, marketing, design, and operations Three layers of sustainability exist in organizations: corporate reporting, product stories, and detailed product data Lifecycle assessments help identify environmental hotspots and improvement opportunities in products Sustainable materials innovation can simultaneously reduce costs and environmental impact Business benefits include cost optimization, market expansion, and strengthened customer relationships Getting started requires overcoming analysis paralysis by taking small, meaningful steps Every role can be a sustainability role, with product managers uniquely positioned to drive meaningful change Introduction We’re diving deep into a topic that scarcely existed a decade ago: sustainable product management. Sustainability is no longer a buzzword—it’s a core strategy for product leaders like Kaila Bryzgalski at Steelcase. If you’ve ever wondered how sustainability improves product innovation and business success, this discussion is for you. You’ll gain insights into real-world practices from Kaila, a leader who’s created her role from scratch, making a tangible impact at Steelcase. Together, we’ll learn why sustainability is not only vital but also how to integrate it into product strategy.   Creating a Sustainable Product Management Role Steelcase has approached sustainability as part of its corporate DNA for over 100 years. The company has long valued “people and planet” alongside profit. This foundation made it possible for Kaila to create a specialized role focused on product sustainability marketing. The company employs what Kaila called a hub-and-spoke sustainability model: The Hub: A central sustainability team of subject matter experts The Spokes: Specialized sustainability roles in different departments: Marketing Operations Supply management Design Understanding a Portfolio Manager for Product Sustainability Role The portfolio manager for product sustainability position at Steelcase sits at the intersection of multiple departments. This cross-functional role connects brand communications, marketing, portfolio management, and product development with the sustainability hub and corporate ESG impact team. Kaila described managing what she called “the layers of sustainability”: Sustainability Layer Description Example Highest Level Corporate impact reporting and stakeholder communications Annual sustainability reports, investor communications Middle Level Product-specific sustainability stories Marketing materials highlighting sustainable features Foundational Level Detailed product data and metrics Lifecycle assessments, environmental product declarations As a portfolio manager for product sustainability, Kaila manages both: The green product portfolio (products with differentiated sustainability features like the carbon neutral product line) Sustainability attributes for Steelcase’s broader catalog of 500+ global products For product managers looking to enhance their sustainability skills, understanding this layered approach helps create a comprehensive strategy rather than isolated initiatives. How to Create a Similar Role in Your Organization If you’re interested in creating a similar sustainable product management position in your company, Kaila identified three key factors that enabled the role at Steelcase: Company values aligned with sustainability (research and insight-focused culture) Leadership support for the position Customer demand creating market pull for sustainable products Practical Steps for Creating a Sustainability Role For product managers looking to establish a similar role, Kaila recommended these actionable steps: 1. Research your company’s impact report and materiality assessment Consider using AI tools to help summarize lengthy reports Look for mentions of product design or sustainability in the materiality spectrum 2. Gather evidence of customer demand Collect data points from sales teams about customer requests Research market trends in sustainability for your product category 3. Make a business case to leadership Present findings on company values and customer demand Show how a dedicated sustainability role could address bo

The most important takeaways from past episodes of Product Mastery Now TLDR Product innovation requires deliberate approaches to teamwork, problem-solving, and customer understanding. John Spero, former senior R&D manager and current innovation professor, highlighted frameworks and methodologies that help product teams work effectively together. These include using tools like DISC assessments to build stronger teams, applying Design Thinking approaches to understand customer needs, and using creative problem-solving techniques to tackle innovation challenges systematically. Key Topics Building innovation cultures and effective product teams Using DISC assessments to improve team dynamics and productivity Applying Design Thinking frameworks to solve complex problems Voice of the Customer methodologies for deeper customer insights Divergent and convergent thinking techniques for innovation Tackling the “fuzzy front end” of product development Facilitation tools like Six Thinking Hats and Phoenix Checklist Best practices for prototype development and testing Professional development paths for product managers Introduction In this episode, our guest is highlighting some takeaways from previous episodes of Product Mastery Now and sharing how they connect with his work today, teaching innovation. With us is John Spero. John has had a long and successful career in product development and management and related roles, including being a senior R&D Manager at Praxair and then Lean Specialist as well as an Agile Coach for the same organization, including after the acquisition by Linde, the global industrial gases company based in Ireland. Now he teaches at Daemen University in their Leadership & Innovation program, focusing on critical thinking, decision making, and problem-solving skills for complex innovation situations. John and I met through the Product Development and Management Association (PDMA), and he invited me to help onboard product managers at Praxair. John assigns podcast episodes, including Product Mastery Now, to his students, and recently he suggested that we discuss key takeaways from these episodes. Let’s see what he has found that is essential for innovators to know. Building Culture and Teams for Innovation Success Creating successful products starts with having the right innovation culture and effective teams. John explained that before students can create valuable products, they need to understand how to foster an innovation culture within their organizations. This means creating an environment where creative thinking is encouraged, risk-taking is supported, and learning from failure is valued. He referenced 493: Perfecting Product Culture and Teams, noting that many students come into his program with academic research experience but struggle to transfer that knowledge into actual product development. The bridge between research and product creation requires a supportive team culture. What Makes an Effective Innovation Team? John has found that the most successful innovation teams share several key characteristics: Complementary skills that cover different aspects of product development Understanding of behavioral styles and work preferences Clear communication about how team members prefer to work Mutual respect for different approaches to problem-solving John shared how he uses DISC assessments in his teaching and previous corporate work to help team members understand each other’s work styles. This behavioral assessment tool identifies four primary work styles, each with different strengths in the innovation process. DISC Style Common Traits Innovation Strengths Dominance (D) Direct, action-oriented Driving projects forward, making decisions Influence (I) Outgoing, enthusiastic Generating ideas, building connections Steadiness (S) Supportive, team-oriented Maintaining harmony, following through Conscientiousness (C) Analytical, detail-focused Ensuring quality, attention to details Tension often emerges between team members with different styles. For example, sales professionals (typically high in D and I traits) might grow frustrated with engineers (often high in C traits) for what they perceive as moving too slowly. By understanding these different work preferences, teams can appreciate that engineers’ thoroughness is actually ensuring quality rather than causing unnecessary delays. This understanding of team dynamics creates a foundation for effective innovation. When team members recognize and value their different approaches, they can collaborate more effectively to solve customer problems. Design Thinking Approaches for Effective Innovation John highlighted the importance of Design Thinking as a structured framework for product innovation. Tom Granzow has a four-phase Design Thinking approach (480: Putting Design Thinking into practical action – with Tom Granzow). When John teaches Design Thinking, he extends the framework into a six-step proces

Use the Press Release FAQ Framework to make better product management decisions Watch on YouTube TLDR The Amazon PRFAQ framework is a powerful product strategy tool that helps teams “work backwards” from customer needs to create successful products. Unlike traditional approaches that start with solutions, this method begins by envisioning the finished product as if it already exists, forcing teams to clarify their vision, validate assumptions, and make better decisions before investing significant resources. Key Topics: The PRFAQ is a strategic document with three parts: press release (1 page), customer FAQs (1 page), and internal FAQs (4 pages) The framework’s value comes from the discovery, debate, and decision process it creates Review sessions involve multiple stakeholders reading and critiquing the document Common mistakes include treating it as a marketing tool or including too many implementation details Benefits include stronger stakeholder alignment, better execution, and clearer distinction between facts and assumptions The approach is suitable for innovators beyond Amazon, including product managers, founders, and executives Introduction How can you transform your product innovation with Amazon’s revolutionary PRFAQ Framework – a proven approach not just at Amazon, but adopted by many organizations, resulting in successful product development and launches. That is what we’ll discover together in this episode. You’ll learn how to implement this “work backwards” approach in your organization, how to craft compelling press releases that define customer value from day one, and practical techniques to anticipate and address the tough questions that can make or break your product.  Our guest today is Marcelo Calbucci, author of The PRFAQ Framework and an experienced product and technology leader. With over 25 years of experience, Marcelo has founded multiple startups, after getting the entrepreneurs itch, building on the experience he gained while working as a development manager at Microsoft. He has served as CTO at various companies, and developed the PRFAQ Framework based on his firsthand experience at Amazon. His deep expertise in product development and innovation makes him the perfect guide to help you apply and adapt Amazon’s innovation approach for your work. Use what Marcelo shares today to improve how you conceptualize, develop, and launch products that customers want and love.  Amazon’s PRFAQ Framework: Transforming Product Innovation Through Working Backwards The “working backwards” methodology, centered around the PRFAQ framework, offers a structured way to conceptualize, develop, and launch products that customers genuinely love. This approach isn’t just limited to Amazon – many organizations have adopted it with impressive results. Marcelo developed this framework based on his firsthand experience at Amazon, building on knowledge gained as a development manager at Microsoft and through founding multiple startups. His deep expertise in product development makes him the perfect guide to help product managers adapt Amazon’s innovation approach to their own work. Understanding the PRFAQ Framework PRFAQ stands for Press Release and Frequently Asked Questions. It’s a strategic document consisting of three main components: Section Length Purpose Press Release 1 page Paints a vision of the future as if your product already exists Customer FAQs 1 page Addresses questions customers would ask about the product Internal FAQs 4 pages Explores feasibility, viability, customer problems, solutions, and go-to-market strategy The press release portion helps you create an aspirational vision of your product’s future. You write it as if your product has already launched, describing what it does and the value it provides to customers. This forces you to think from the customer’s perspective from day one. The customer FAQ section anticipates questions that potential users might have. These typically include practical considerations like pricing, data migration, and getting started with the product. The internal FAQ section, which is the most substantial part, addresses deeper questions about feasibility, market opportunity, and business strategy. This is where you explore whether your product idea is viable and worth pursuing. What the PRFAQ Is Not The PRFAQ framework should not include: Tactical execution details Feature specifications Wireframes Branding elements Technical architecture These elements come later in the product development process, after you’ve decided the opportunity is worth pursuing. The PRFAQ is focused exclusively on vision and strategy, helping you determine if the product idea deserves your team’s time and resources. By keeping the framework focused on strategic elements rather than implementation details, you can make better decisions about which opportunit

How product managers can create irresistible products Watch on YouTube TLDR Product psychology goes far beyond traditional product-market fit. When customers feel compelled to buy products, they move from rational comparison to emotional connection. Successful products trigger what Laurier Mandin calls “the flip” – transforming wants into psychological needs, making purchasing non-negotiable. Key topics: The psychology of “I need that” responses vs. traditional product-market fit How the “dog brain” makes purchase decisions 250x faster than rational thinking The “coveted condition” framework for emotional product connections Why products need to be 10x better to overcome status quo bias The CLIMB framework for identifying functional, emotional, transformative, and transcendent needs Integrating product development and marketing from the concept stage How craftsmanship and attention to detail create emotional value Introduction What makes a product not just desirable, but absolutely necessary in the minds of customers? In this discussion, we’re investigating the psychology of product development and marketing with Laurier Mandin. He is a product marketing strategist who has spent over three decades guiding hundreds of innovative products to market success. As founder of Graphos Product, he’s helped numerous startups and established brands through need-centric product development and compelling marketing strategies. With a deep understanding of consumer psychology and behavioral economics, he brings a unique perspective to product creation and marketing. He is also the author of I Need That and creator of the Product: Knowledge podcast. You’ll come away from this conversation with fresh insights and practical frameworks for creating products that customers don’t just want – but feel they absolutely need.  Beyond Product-Market Fit: Creating Products Customers Are Compelled to Buy Product managers often focus on achieving product-market fit – that sweet spot where a product satisfies a specific market need well enough to sustain itself and grow. I asked Laurier what the different is between a product that achieves product-market fit and a product that a customer is “compelled to buy.” While product-market fit focuses primarily on rational factors like features, pricing, and market size, being “compelled to buy” taps into something deeper – the psychological transformation that happens when a want becomes a need. The “Flip” From Want to Need Laurier described this transformation as “the flip” – the moment when our mind converts a desire into a psychological need. Beyond basic physiological needs, our perceived needs are mental constructs. When a product triggers this flip, owning it becomes entirely non-negotiable. Customers will overcome any friction or barrier to get it. Traditional Product-Market Fit Products Customers Are Compelled to Buy Focuses on rational factors (features, pricing) Focuses on emotional triggers Aims for customer satisfaction Aims for “I need that” reactions Faces constant price pressure and competition Breaks through resistance and friction Customers compare features Customers imagine life with the product Products that merely satisfy a need constantly battle price pressure and competition. In contrast, products that trigger an “I need that” response bypass these challenges because customers are no longer rationally comparing features – they’re emotionally invested in owning the product. This shift from satisfaction to compulsion represents a powerful strategic advantage for product teams who understand how to engineer it. The Psychology Behind Purchase Decisions Understanding how customers make buying decisions is crucial for creating products they feel compelled to purchase. Laurier explained that our brains have two primary decision-making systems: the “dog brain” (limbic system) and the rational brain (neocortex). The Dog Brain vs. The Rational Brain The dog brain is our emotional center, where intense responses and impulsive behaviors originate. It operates about 250 times faster than our rational brain. This explains why buying decisions often happen in milliseconds, driven by emotion rather than logic. Here’s what makes this understanding so powerful for product development: Purchase decisions start in the emotional center of the brain The rational brain only rationalizes decisions after they’re made emotionally Creating emotional connections happens before rational feature comparison Why Our Brains Prefer Emotional Decisions Our brain’s preference for emotional decision-making isn’t random – it’s about energy conservation. While the brain represents only about 2% of our body weight, it consumes approximately 20% of our energy. This creates a natural tendency to avoid energy-intensive r

Transform product team collaboration with Workshop Culture Watch on YouTube TLDR In my recent conversation with Alison Coward, author of Workshop Culture, we explored how product managers can transform collaboration and problem-solving through effective workshop facilitation. Alison shared that workshop culture isn’t about running constant workshops but about applying workshop principles to everyday collaboration. The key is a three-part approach: thorough preparation before, skilled facilitation during, and consistent follow-through after. By starting with the end in mind and focusing on creating the right environment for both introverted and extroverted team members, product managers can break down silos and foster innovation as a collective outcome. Key Topics Defining workshop culture and its importance for cross-functional collaboration The three-part workshop process (before, during, after) Starting with the end in mind when planning workshops Effective facilitation techniques that balance different communication styles The power of being the “ignorant” facilitator without domain expertise Creating the right physical environment for productive workshops Ensuring post-workshop implementation and follow-through Real-world example of transforming organizational collaboration Innovation as a collective outcome requiring effective team dynamics Introduction Today we’re exploring how product managers can improve their work with stakeholders, promote collaboration and trust, and apply a problem-solving approach. Our guest is Alison Coward, author of Workshop Culture: A Guide to Building Teams That Thrive. With over 20 years of experience leading creative teams, Alison has helped organizations worldwide boost team creativity, productivity, and collaboration. We’ll unpack what workshop culture means, learn practical steps for product managers to design impactful workshops, and hear real examples of how these techniques have helped teams overcome challenges. Understanding Workshop Culture Alison defined workshop culture as “ a team culture that uses the principles and practices of workshops and facilitations to achieve creativity and productivity and to build a more effective environment for team collaboration.” It doesn’t mean a team is running workshops all the time. Instead, it’s about applying the principles and practices of workshops and facilitation to create a more effective environment for team collaboration. Think about the last great workshop you attended. Remember that feeling at the end of the day – ideas flowing freely, people engaging meaningfully, and clear outcomes achieved. Often, this feeling disappears when you go back to work the next day. Workshop culture aims to capture this energy and extend it into everyday work. Despite recognizing the importance of collaboration in theory, many product teams struggle to make it work in practice. Meetings become status updates rather than problem-solving sessions. Stakeholders protect their territory rather than exploring possibilities. The implementation gap between idea and execution grows wider. Workshop culture bridges this gap by focusing on three key elements: Element Description Principles The mindsets that drive effective collaboration (curiosity, active listening, synthesis) Practices The specific techniques that facilitate shared understanding and decision-making Environment The physical and psychological conditions that enable creative thinking For product managers, implementing workshop culture means transforming how your team approaches problems. Rather than defaulting to the highest-paid person’s opinion or the loudest voice in the room, you create structured opportunities for all perspectives to contribute to solutions. The result? Teams that not only collaborate more effectively during dedicated sessions but carry that collaborative mindset into all aspects of product development. The Three-Part Workshop Process Effective workshops involve much more than just the session itself. Alison described a three-part process that many product managers overlook when planning collaborative activities: 1. Before: Preparation and Planning Preparation represents nearly 60% of what makes a workshop successful. This phase involves researching context, understanding team dynamics, clarifying objectives, and designing activities that will achieve your desired outcomes. 2. During: Facilitation and Activities This is what most people think of as “the workshop” – the actual time when participants gather to collaborate. While important, Alison noted that even the best-planned activities can go sideways if you’re not prepared to adapt to what emerges in the room. 3. After: Implementation and Follow-Up Perhaps the most neglected aspect of workshops is what happens afterward. Without deliberate follow-through, even the most energizing session can fail to create lasting impact. This pha

AI in product management – perspectives from the legal industry, education, and entrepreneurship Watch on YouTube TLDR In my recent conversation with product executive and former colleague Matt Coatney, we explored how artificial intelligence is transforming product management and innovation. The technology has evolved dramatically in the past decade, from fragile, expensive systems to powerful tools that integrate seamlessly into workflows. Product managers can leverage AI for everything from customer research and brainstorming to prototyping and workflow automation. While organizations must balance specialized versus general AI tools and address concerns like hallucinations and data privacy, the benefits for productivity and innovation are substantial. The most successful implementations focus on solving real customer problems and seamlessly integrate into existing workflows. Key Topics Using AI as a brainstorming partner to overcome creativity blocks Accelerating product development with AI-powered prototyping tools Integrating AI into product management platforms and workflows Balancing specialized AI products versus general-purpose models Managing AI hallucinations and verification challenges Learning from AI adoption in risk-averse industries like legal Impact on mentorship and professional development Future trends: local AI models and data privacy Introduction In this episode, we had a free-form discussion. My guest doesn’t know what I’m going to ask him and I don’t know what he is going to ask me. Our goal is to make the discussion valuable for product managers, leaders, and innovators. Joining me is a former colleague, Matt Coatney. We worked together on an important product for LexisNexis. I went on to teach graduate courses in innovation and coach product managers and leaders in organizations, while Matt got more involved in Information Technology, leading professional services and consulting operations for a few organizations as well as serving as CIO for one of the large law firms in the US. His career started in AI systems some 25 years ago and today he continues learning about and applying AI and is also is a product executive. The Current State of AI in Product Management Matt asked about my observations of the effects of AI, from the perspective of a product manager, entrepreneur, and educator. Last year at the Product Development and Management Association (PDMA) conference, three separate sessions featured AI tools specifically designed for customer research. This wasn’t just theoretical discussion. These were practical applications already being implemented by forward-thinking product teams. At the PDMA conference, I participated in a workshop led by Mike Hyzy, where we completed what would normally be a 3-5 day Design Sprint in just three hours. Our team consisted of four humans and one AI companion, which functioned as a fifth team member. The AI was operated by someone skilled in prompt writing who understood the product space. What impressed me most was how the AI accelerated our work. When we brainstormed customer problems, the AI helped us explore details we hadn’t considered. It suggested unmet needs, offered additional perspectives, and helped us develop a comprehensive view in a fraction of the time it would have taken traditionally. By the end of those three hours, we had developed a solid marketing description for solving a customer problem and created a decent prototype—impressive results for such a compressed timeframe. Practical AI Applications for Product Professionals On a personal level, I’ve found AI tools like Claude to be valuable as brainstorming partners. Rather than trying to craft lengthy prompts with all my requirements upfront, I’ve shifted to a more conversational approach. Kicking ideas around with AI helps me overcome the inertia of starting a task. Matt shared similar experiences, noting that this brainstorming use case is often underappreciated. While many focus on productivity enhancements like email responses and content generation, the creative thinking support is particularly valuable for entrepreneurs and product innovators. Many professionals today lack the “water cooler culture” opportunities to casually discuss ideas with colleagues, especially with remote work becoming more common. AI tools help fill this gap, providing an always-available thinking partner. We also discussed the prototyping capabilities of AI. Matt mentioned tools like GitHub Copilot for assisting developers, and V0, which can build functional web applications directly from human prompts. These tools allow people with little or no coding knowledge to write code. For entrepreneurs and product managers, these prototyping tools address a common challenge: developing clear user workflows before engaging software developers. Taking time to create detailed prototypes helps clarify thinking and identify assumptions that might co

Product management is the best path to senior leadership Watch on YouTube TLDR In my recent interview with Elizabeth Samara-Rubio, Chief Business Officer at SiMa.ai, we explored the journey from product management to senior leadership. Elizabeth shared how her product management experience at HP and other companies shaped her approach to business leadership. She emphasized the importance of setting a clear North Star for teams, challenging assumptions with data, and creating a culture that embraces calculated risk-taking. Her insights on Edge AI applications revealed how companies are gaining competitive advantages through both product-focused and process-focused AI integration strategies. Key Topics How product management experience provides a foundation for executive leadership Setting direction as a senior leader through clear vision and metrics Edge AI applications and benefits: privacy, security, and cost advantages Creating customer value through innovation and “getting your own truth” Building a data-driven leadership culture Two approaches to AI integration: product-focused and process-focused Advice for product managers aspiring to senior leadership roles Introduction When you meet an exceptional product manager – a product master – you’re often seeing a future business leader in the making. They have a spark – an obsession with customer needs, a knack for strategy, an ability to unite teams around a vision – it’s the same DNA that builds great companies. Our guest today embodies this evolution, taking her product management foundation to pioneer AI innovation and lead high-growth companies.  From launching products at HP in the late 90s to driving AI innovation today, Elizabeth Samara-Rubio’s journey offers unique insights into how product management shapes business leadership. As Chief Business Officer at SiMa.ai, she’s now at the forefront of Edge AI technology, bringing artificial intelligence directly to devices where decisions need to be made. In this discussion, we’ll explore how Elizabeth’s early product management experience influences her approach to building high-growth, customer-focused companies. We’ll also dive into her perspective on AI’s transformative impact on industries, drawn from her work at the intersection of strategy, product, and artificial intelligence.  Whether you’re a product manager looking to expand your influence or a business leader interested in the impact of AI on your industry, Elizabeth’s insights bridge the gap between product thinking and company building.  From Product Manager to Business Leader Product managers are prepared to be leaders, as the challenges of balancing multiple stakeholders, making data-driven decisions, and keeping customers at the center of everything you do are experiences that translate directly to executive roles. The transition from managing products to leading businesses isn’t automatic, however. It requires developing new skills while leveraging the product mindset that made you successful in the first place. As Elizabeth’s journey shows, product managers who successfully make this leap often maintain their customer focus and data-driven approach while expanding their vision to encompass the entire business. Throughout our discussion, Elizabeth shared insights on setting direction as a senior leader, applying product management tools to business leadership, and leveraging AI to create competitive advantages. Her experiences provide a roadmap for product managers looking to grow their careers beyond traditional product roles and influence entire organizations. What makes this journey from product manager to business leader particularly relevant today is how technology – especially AI – is transforming products, services, and entire industries. Leaders with product backgrounds are uniquely positioned to guide this transformation. Setting Direction as a Senior Leader One of the differences between product management and executive leadership is the scope of direction-setting. While product managers focus on product vision and roadmaps, senior leaders must establish a North Star for entire organizations. Elizabeth emphasized that setting direction as a Chief Business Officer involves providing sufficient clarity for each function to understand its role. At SiMa.ai, this direction centered on customers who are both anxious and excited about AI possibilities. By establishing customers as the North Star, Elizabeth ensured every team—from product managers to field application engineers and sales—could align their work toward becoming trusted advisors in this space. But direction-setting isn’t just about vision. Elizabeth highlighted three essential components: North Star orientation – Creating a clear, compelling direction that guides decision-making Measurable objectives – Establishing metrics to track

How AI captures customer needs that human product managers miss Watch on YouTube TLDR In my recent conversation with Carmel Dibner from Applied Marketing Science, we explored how artificial intelligence is transforming Voice of the Customer (VOC) research for product teams. The collaboration between AMS and MIT researchers has yielded impressive results, with AI tools not only matching human analysts in identifying customer needs but often exceeding them—especially for emotional needs that humans might overlook. Rather than replacing human researchers, AI serves as a copilot, helping product teams uncover twice as many unique needs while reducing analysis time and eliminating bias. This hybrid approach offers tremendous potential for innovation, particularly in the early stages of product development. Key Topics AI can now match or exceed human analysts in identifying customer needs from research data Large Language Models (LLMs) are surprisingly effective at capturing emotional needs that humans often miss AI finds twice as many unique customer needs compared to human analysts alone The most effective approach is using AI as a “copilot” alongside human researchers AI tools significantly speed up data analysis and can process multiple data sources simultaneously These tools can find niche needs that create innovation opportunities AI still has limitations in prioritizing needs and assessing the validity of different data sources Introduction Voice of the Customer research has been a cornerstone of product management for decades. But it is changing, with AI tools that are transforming how we uncover and analyze customer needs. While some fear AI might miss the human element of customer research, recent advancements show it can actually help us capture more nuanced emotional needs while eliminating human bias. Joining us is returning guest, Carmel Dibner, who is a principal and co-owner at Applied Marketing Science (AMS), where she has helped companies uncover critical customer insights to improve products, services, and customer experiences. Before moving to consulting she was in brand management at Unilever. More recently, she has collaborated with AI researchers at MIT to improve VOC outcomes. I regard Applied Marketing Science, Carmel’s company, as the thought leaders in VOC research, and it was the first organization to formalize the VOC interview process. In this discussion, we’ll explore how LLMs are revolutionizing Voice of the Customer analysis. Carmel will share results of experiments where AI not only matched human analysts in extracting customer insights but excelled at finding hidden needs – unmet needs that could unlock your next innovation opportunity and create competitive advantage. Whether you’re skeptical about AI in customer research or eager to embrace it, this discussion will challenge your assumptions about the future of Voice of the Customer analysis. The AI Revolution in Voice of the Customer Research Early AI Experiments (2017-2018) AMS began experimenting with artificial intelligence for customer research around 2017-2018. Their initial focus was on developing algorithms that could effectively analyze textual data and extract meaningful customer insights. However, these early efforts faced significant limitations. The AI could identify potentially useful information, but human analysts still needed to invest considerable time sifting through and making sense of what the AI had found. The process wasn’t yet efficient enough to deliver the time-saving benefits they hoped for. Recent Breakthroughs (2023) In 2023, AMS and MIT researchers tackled a more ambitious question: Could AI now effectively craft unmet customer needs statements that would be just as good as those created by experienced human analysts? To answer this question, they employed a technology called supervised fine-tuning. This approach involved “teaching” large language models how to craft clear, actionable customer needs statements based on transcript data, social media comments, and other text sources. Time PeriodResearch FocusAI ApproachLimitations2017-2018Extracting customer insights from textBasic AI algorithmsRequired significant manual effort to interpret results2023Crafting complete customer needs statementsSupervised fine-tuning of LLMsMuch improved but still best used alongside human analysis The supervised fine-tuning approach represented a significant advancement. Rather than simply flagging potentially relevant text, these newer AI models could produce fully formed needs statements that captured what customers truly wanted and why. This breakthrough laid the groundwork for the impressive results they observed in their comparative experiments between AI and human analysts. Validating AI Effectiveness in VOC Research The claim that AI could match or even exceed human performance in VOC research required solid evidence. During our conversation, Carmel descr

How an AI-powered fashion startup achieved product-market fit Watch on YouTube TLDR In this episode, we’re joined by Anya Cheng, former product leader at Meta, eBay, McDonald’s, and Target, and current founder of the AI-powered fashion startup Taelor. Her journey from corporate product management to successful startup founder offers valuable lessons for product managers and innovators. The key message: Focus on solving one problem exceptionally rather than competing on multiple features. Key Topics Why successful products often start with a single powerful feature How to discover and validate product-market fit through deep customer research The importance of balancing customer feedback with your own product vision Ways to create value on both customer and supplier sides of your business Lessons from Target’s iPad app success through radical feature minimization The value of breaking out of your industry bubble for innovation insights Introduction We all face numerous challenges creating products customers love—understanding the customer and their unmet needs, achieving product-market fit, working with stakeholders, scaling the product in the marketplace, and more. Today we’ll learn how to overcome some of those challenges from a product leader with experience at Target, McDonalds, eBay, and Meta, and now as Founder and CEO of Taelor. Our guest, Anya Cheng, founded Taelor, combining her leadership experience at B2Cs and her knowledge of tech product management, to make it easy for men to wear stylish clothes for any occasion. Anya also is mentor at 500 Startups and a teacher of product management for Northwestern University. A Fresh Perspective on Product Development Anya challenged common assumptions about product development strategy. Instead of advocating for feature-rich products or complex innovation frameworks, she emphasized the power of solving one problem exceptionally. This approach has informed her success across different industries and roles, from retail to technology. Core Product Development Challenges: The Power of Single-Feature Focus Anya highlighted a mistake many startups and product teams make: trying to compete with established companies by matching or exceeding their feature lists. The Feature Competition Trap During her work mentoring product managers and startups, Anya noticed a recurring pattern. Teams often pitch their products by comparing them to industry giants: “It’s like Uber, but with these extra features” or “It’s Amazon, plus these additional capabilities.” The problem? This approach fundamentally misunderstands how successful products actually emerge and grow. Large companies can quickly replicate individual features, making it nearly impossible for smaller players to compete on feature quantity. Instead, a startup should focus on solving one problem better than anyone else. Historical Examples of Successful Single-Feature Products To illustrate the power of focused problem-solving, Anya shared three examples: Company Initial Core Feature Outcome Google Simple search bar Outperformed Yahoo’s comprehensive portal YouTube Video upload and sharing Acquired by Google Instagram Photo filters Acquired by Meta The Key to Standing Out The lesson Anya learned from both her corporate experience and startup journey is clear: Success comes from doing one thing exceptionally rather than doing many things adequately. She shared wisdom from her mentors, including founders of Rotten Tomatoes and YouTube, who emphasized that startups should focus on having “one giant check mark” instead of many small ones. This approach requires: Identifying a specific, valuable problem to solve Developing a focused solution that addresses that problem better than any alternative Resisting the temptation to add features just because competitors have them Maintaining focus on core value proposition during growth Finding Product-Market Fit: The Taelor Case Study The journey to product-market fit often begins with a personal pain point, but successful products emerge when founders look beyond their own experiences. Anya’s development of Taelor offers valuable lessons in how to validate and expand upon initial product insights. From Personal Problem to Market Opportunity Anya found herself wanting to look more professional but discovered existing clothing services weren’t designed for busy professionals who prioritized efficiency over fashion. This led her to explore whether others faced similar challenges. Through market research, she discovered her ideal customers weren’t whom she initially expected. While her original problem centered on professional women’s clothing needs, her research revealed a more acute pain point among busy professional men who: Need to look good for various occasions Don’t enjoy shopping Want to save time on clothing decisions Prefer efficiency over fashion exploration Develop

The product manager’s path to influence Watch on YouTube TLDR In my recent conversation with Francesca Cortesi, CPO, we explored why the popular phrase “CEO of the product” can be misleading for product managers. Francesca explained that while this concept aims to emphasize ownership and decision-making authority, successful product management actually requires a different approach. Instead of acting as a sole decision-maker, today’s product managers need to excel at facilitation, stakeholder collaboration, and building trust across teams. She shared insights from her experience leading product teams at various organizational scales and helping companies transform their product vision into measurable business growth. Key Topics The evolution from the traditional “decision-maker” model to a modern “facilitator” approach in product management How product management roles and responsibilities vary across different organization sizes and contexts Essential skills for product management success: trust building, stakeholder management, and collaborative leadership Setting clear role boundaries and expectations in product management positions Practical strategies for navigating product management challenges while maintaining customer focus Career development considerations for product managers, including different growth paths and role transitions Introduction Ever heard someone call product managers “CEO of the product”? It’s a catchy phrase that has attracted some people to product management, but it certainly doesn’t tell the whole story. In today’s discussion we’ll break down where the CEO comparison holds up, where it falls short, and most importantly what makes product management a uniquely challenging and rewarding role in its own right. Along the way we’ll explore how the role varies across different organizations and discuss the critical skill of defining and managing the boundaries of that product management role. If you’re considering how to grow your product management career and your influence, this episode will give you some clarity about what success really looks like in this field. Our guest is Francesca Cortesi, CPO and consultant for some of Europe’s multi-billion dollar brands and fastest growing businesses. Recently, at Hemnet, Sweden’s beloved property platform, she led product development that drove a 130% increase in top line revenues, making it the growth engine of the business. She now runs her own consultancy, helping CEOs scale their companies by transforming product vision into measurable business growth. The Reality Behind “CEO of the Product”: Redefining the Product Manager’s Role The “CEO of the product” concept emerged when product management literature was scarce, and professionals often had to figure out their roles with limited guidance. Early in her career, Francesca encountered this phrase alongside the common description of product management as sitting at the intersection of business, user experience, and technology. While this description aimed to emphasize ownership and agency in decision-making, it created some misconceptions about the role. Traditional View Modern Reality Product manager as primary decision maker Product manager as skilled facilitator Information flows through PM as central point PM enables direct cross-functional collaboration Focus on authority and control Focus on influence and alignment Today’s product management landscape has evolved significantly. While the role still requires strong leadership skills, the most successful product managers approach their work differently than what the “CEO of the product” phrase might suggest. Instead of focusing on authority and control, they excel at facilitation, stakeholder collaboration, and building trust across teams. This shift reflects a deeper understanding of how successful products are built in modern organizations. As we’ll explore in this article, effective product management requires a unique blend of skills that goes beyond traditional leadership models. Whether you’re an aspiring product manager, a seasoned professional, or a leader developing your product team, understanding these nuances is necessary for success in today’s product landscape. The Evolution of Product Management Understanding Francesca shared how her understanding of product management transformed over her career, moving from a traditional decision-maker model to a more nuanced facilitator approach. This evolution offers valuable insights for product managers at all career stages. The Traditional Decision-Maker Model: A Limited View Early in her career, Francesca interpreted the “CEO of the product” concept literally, believing her primary role was to make decisions. She positioned herself at the intersection of different functions, collecting input f

Serial innovators see dead people Watch on YouTube TLDR The transformation of Olay from a declining “Oil of Old Lady” brand into a market-leading skincare innovator offers valuable lessons for product managers and innovation leaders. Through deep consumer research, strategic pricing, and holistic product development, P&G’s Nancy Dawes led a team that created an entirely new market category of “mass-prestige” skincare products. The success of this transformation hinged on understanding consumer psychology, developing innovative technology, and carefully positioning the product between mass market and luxury price points. Key Topics Characteristics and strategies of successful serial innovators in product development Comprehensive approach to consumer research and insight gathering Strategic product positioning and pricing in the mass-prestige market Integration of technical innovation with consumer psychology Organizational navigation techniques for innovative product managers Holistic approach to product development and brand transformation Market validation and testing strategies for premium products Cross-functional expertise development for product innovation Introduction Remember when Pringles was just another potato chip, or when Olay was losing its shine in the cosmetics aisle? If you’ve ever wondered how struggling brands transform into market leaders, you’re about to get a masterclass in product innovation and consumer insight. Today, we’re joined by Nancy Dawes, a legendary force in product transformation who tripled Pringles sales and breathed life into the Olay brand by creating new product lines. She was Proctor & Gamble’s first female engineer to be honored as a Victor Mills Society Research Fellow. Nancy has also been recognized as a Serial Innovator—featured in the book Serial Innovators: How Individuals Create and Deliver Breakthrough Innovations in Mature Firms. She spent 38 years at P&G mastering the art of understanding what customers want before they know they want it. After retiring from P&G, Nancy continues to guide founders and entrepreneurs in creating products customers love and also volunteers with Ohio State College of Engineering and Girl Scouts of Western Ohio. Whether you’re leading a product team at a Fortune 500 or founding a startup, Nancy’s proven approach for uncovering consumer insights and driving breakthrough innovation could be the difference between your product’s decline and its dramatic comeback. Serial Innovation in Product Development Nancy characterized serial innovators as those who: conceive new ideas for products that solve problems develop those ideas into breakthrough new products and services invent technologies as needed along the way guide those products into the market for commercial success Serial innovators solve important consumer problems, and often figuring out the right problem is just as important as fixing it. They invent new technologies to support their solutions and follow their products into the marketplace rather than handing them to someone else. The Olay Transformation: A Product Innovation Case Study Nancy told the story of how Olay transformed from a struggling brand, called “Oil of Old Lady” by some customers, to a market leader through strategic product innovation. The story begins in 1985 when P&G acquired Olay, which was then known as Oil of Olay. By 1995, when Nancy joined the project, the brand had declined by approximately 50% in value. Market Analysis and Opportunity Recognition Nancy identified four factors that created the perfect environment for transformation: Demographic Opportunity: 75 million Baby Boomer women were entering their prime skincare years, ready to reinvent aging Technology Evolution: The emergence of alpha hydroxy acids moving from professional to consumer products Corporate Support: Strong leadership commitment to winning in the skincare category Expertise Alignment: Right combination of technical knowledge and consumer understanding Initial Assignment vs. Strategic Vision Nancy’s original assignment was simply to create a superior facial moisturizer, but Nancy recognized that just having a better product wasn’t enough for success and it wasn’t really what the women who were buying skincare and starting to age really wanted. She came to this conclusion by using what she calls “kitchen logic”—understanding both what women wanted and how women believed anti-aging skin care products worked. Customers believed products need to penetrate the skin to work. They wanted to develop a product that is efficacious and that women intuitively feel is working. Connecting the Dots To create a product that delights customers, Nancy and her team had to “collect and connect” many dots—considering many areas that were important to customers. Their innovations included: Design Element S

How product managers use Jobs-To-Be-Done to create products customers love Watch on YouTube TLDR In this episode, I explain the Jobs-To-Be-Done (JTBD) framework, a powerful approach to understanding customer needs and developing successful products. Real-world examples like McDonald’s morning milkshakes, Snickers vs. Milky Way marketing strategy, and Bosch’s entry into the circular saw market demonstrate how understanding what customers are trying to accomplish (their “job-to-be-done”) leads to better product decisions and innovation. The episode contrasts Clayton Christensen’s consumer demand approach with Tony Ulwick’s job analysis perspective, while providing practical guidance for conducting customer interviews and prioritizing product improvements. Key Topics: The classic McDonald’s milkshake study and what it reveals about customer behavior How Mars used Jobs-To-Be-Done to differentiate Snickers and Milky Way Bosch’s successful entry into the North American circular saw market through customer observation Two main approaches to Jobs-To-Be-Done: consumer demand vs. job analysis Four key areas to explore in Jobs-To-Be-Done interviews How to prioritize unmet needs through customer surveys The importance of ethnographic research in understanding customer needs Tony Ulwick’s IBM PCjr experience and its influence on Jobs-To-Be-Done Different jobs-to-be-done for various podcast listener segments The fundamental role of curiosity in effective product management Introduction Last week, I met with my podcast production team to discuss the job-to-be-done that our listeners have. I got a few blank looks and one person said, “Yeah, the milkshake story.” Since we don’t all know the milkshake story, I want to share this Jobs-To-Be-Done (JTBD) story with you too. Jobs-To-Be-Done is a great tool, concept, and language that helps us understand the customer’s problem, what they need solved, and what might prevent them from buying our product. I’ve found the JTBD language very helpful, and through examples and applications, I hope you’ll learn how to make better use of it yourself. The Classic Milkshake Story McDonald’s wanted to sell more milkshakes. They had tried reformulating them, making them thicker, and offering flavor-of-the-month options, but sales hadn’t improved significantly. What caught their attention was that they were selling many milkshakes around 9-10 o’clock in the morning through the drive-thru. They hired Clayton Christensen and his colleagues to examine this phenomenon. As Clayton tells the story on YouTube, they stationed themselves at the end of the drive-thru lane. When customers ordered a morning milkshake, they would ask, “What did you hire that milkshake to do for you?” The responses were revealing. Many customers had a long, boring commute ahead and wanted: Something that would take time to consume Was easy to drink while driving Would fill them up Help with the monotony of the drive When asked what else they had tried for breakfast, customers mentioned alternatives like donuts, which are messy and distracting while driving. The milkshake worked well because it satisfied multiple needs: It was filling, took time to consume, and was neat and easy to manage while driving. Analyzing the Milkshake Case Study The milkshake story illustrates how JTBD helps us understand existing products. We’re examining what consumers are doing, their demand for the product, and any friction in the process. This understanding provides insights into how we can improve the product to better meet customer needs and make our marketing more effective to attract the right customers – in this case, those looking for a breakfast solution during their morning commute. Interestingly, I’ve never heard Clayton Christensen or others discuss what McDonald’s actually did with these insights. As an occasional McDonald’s customer, I’m not sure if they made any changes. It seems they could have developed a morning smoothie – a breakfast-appropriate option that might appeal to health-conscious customers with the same need. A smoothie might sound healthier than a milkshake, which can feel like an indulgence or too sweet for breakfast. The Snickers vs. Milky Way Case Study Another interesting JTBD example comes from Chris Spiek, who shared it in episode 057 of this podcast. The story involves two candy bars: Snickers and Milky Way. Chris’s boss, Bob Moesta at the Rewire Group, was hired by the candy company to help them decide which product to remove from the market. The company believed focusing their energy on one brand would help them compete more effectively. Bob began his research at an airport when he noticed someone selecting a Snickers bar. This led to a broader study where researchers would observe customers making purchases and ask why they chose one candy bar

How serial innovators transform product management Watch on YouTube TLDR Navigating innovation in mature organizations requires a unique approach that goes beyond traditional business strategies. During my conversation with Bruce Vojak, PhD, a leading expert in breakthrough innovation, we explored the challenges and opportunities for product managers and business leaders seeking to drive meaningful organizational change. The key is understanding how serial innovators can transform business potential and overcome deeply entrenched operational mindsets. Understand the concept of serial innovators and their unique value to organizations Learn strategies for overcoming innovation barriers in mature businesses Discover practical tools for fostering a culture of continuous innovation Explore real-world examples of successful innovation in different industries Develop a mindset that embraces creative problem-solving and organizational renewal Introduction Innovating is tough for businesses. Companies find something that works and gives them a competitive advantage and then tend to stick with it, limiting meaningful innovation over time. Since you are an innovator, you already know where your organization struggles with innovation. I have had the pleasure of coaching some of the best organizations in their industry and I can tell you every company can improve how it innovates. Let’s get some help and learn how to talk about the importance of innovation with senior leaders and the tools that can help organizations be better at innovation. Joining us is Dr. Bruce Vojak, founder of Breakthrough Innovation Advisors. He helps companies survive and thrive in a volatile, complex, and increasingly ambiguous world. Bruce has a unique and powerful mix of expertise in product innovation, including as a Director at Motorola, and in academia and research, serving at the Grainger College of Engineering at the University of Illinois at Urbana-Champaign and previously as a researcher at MIT Lincoln Laboratory. His research in innovation has been published in several places, including his recent book No-Excuses Innovation and his practice-changing book Serial Innovators. The Challenge of Innovation in Today’s Business Landscape Mature businesses typically have three strategic options when facing innovation challenges: Strategy Description Extend Current Model Optimize existing processes and incrementally improve current offerings Lean Optimization Focus on reducing costs and improving operational efficiency Pursue Innovation Develop breakthrough solutions and explore new market opportunities The most successful organizations recognize that innovation is not a one-time event but a continuous process. It requires a unique approach that goes beyond traditional management techniques. Product managers and business leaders must create an environment that nurtures creative thinking, supports risk-taking, and values the unique perspectives of serial innovators within their organizations. By understanding these challenges and adopting a proactive approach to innovation, businesses can transform potential obstacles into opportunities for growth and renewal. Understanding Serial Innovators: The Breakthrough Difference Serial innovators are a unique breed of professionals who consistently drive breakthrough innovations within organizations. These individuals possess a remarkable ability to see opportunities where others see roadblocks. Bruce’s research, highlighted in the groundbreaking book Serial Innovators revealed fascinating insights into these exceptional team members. Unlike traditional employees who often work within established frameworks, serial innovators approach challenges with a fundamentally different mindset. They’re not just thinking outside the box – they’re reimagining the box entirely. Characteristics of Serial Innovators What sets these individuals apart? Bruce’s research identified several key traits: Exceptional ability to understand unarticulated customer needs Willingness to challenge existing organizational assumptions Capability to reframe complex problems in unique ways Intrinsic motivation to drive meaningful change The Value They Bring to Organizations Serial innovators are not just creative thinkers – they’re strategic assets. Many of the most significant breakthroughs in business come from these individuals who: Innovation Capability Organizational Impact See Patterns Others Miss Identify new market opportunities before competitors Navigate Organizational Challenges Build bridges between departments and break down silos Drive Continuous Improvement Create sustainable paths for business renewal One insight from Bruce’s research was the diverse backgrounds of these innovators. Interestingly, most serial innovators he studied did not have traditional business degrees. Instead, they learned business “on the street” – through direct experience, observation,

How product managers can make OKRs drive real results Watch on YouTube TLDR In my recent conversation with Ben Lamorte, the world’s most experienced OKR coach and founder of OKRs.com, we explored how product managers and leaders can transform their approach to Objectives and Key Results (OKRs). Ben shared insights about why many OKR implementations fail and how to avoid common pitfalls. The key to success lies in focusing on measurable outcomes, maintaining transparency, and avoiding the temptation to create too many OKRs. Whether you’re just starting with OKRs or looking to improve your existing implementation, this comprehensive guide will help you create an effective OKR framework that drives real results. Key Topics: Understanding OKRs: Their evolution from Intel’s early days to modern implementation Common pitfalls: The top reasons why OKR programs fail and how to avoid them Implementation strategies: Key factors for successful OKR deployment Practical guidelines: Choosing the right cycle length and organizational levels Success factors: The importance of transparency and outcome-focused metrics Change management: How to transition your team to effective OKR usage Introduction Does the mention of OKRs make you break into a cold sweat, or does it energize you with a sense of purpose? Whether you’re nodding in recognition or scratching your head wondering what OKRs even are, you’re about to discover how this powerful framework can transform your work life. In this episode, we’ll cut through the confusion and show you exactly how to turn Objectives and Key Results from a dreaded management mandate into your secret weapon for driving success. Miss this episode, and you risk continuing to struggle with misaligned priorities, unclear metrics, and the frustration of not seeing how your work impacts the bigger picture. With us is a true OKR expert, Ben Lamorte. Ben has more OKR coaching experience than anyone. Consequently, he has become the coach to OKR coaches. He has also helped business leaders and organizations to define and make measurable progress on their most important goals, guiding more than a hundred organizations in deploying OKRs. He is the founder of OKRs.com, which provides resources and coaching services. He co-authored Objectives and Key Results: Driving Focus, Alignment, and Engagement and authored The OKRs Field Book. Understanding OKRs: From Intel to Modern Product Teams The evolution of Objectives and Key Results (OKRs) began at Intel during the 1970s and 1980s, where Andy Grove transformed the traditional Management by Objectives (MBO) system into something more dynamic and outcome-focused. He decoupled objectives, which are broad qualitative statements, from their specific measurable results, creating a framework that would eventually reshape how organizations set and achieve goals. While MBOs were typically tied directly to bonuses, OKRs intentionally separate performance measurement from goal setting. This separation encourages teams to think bigger and take calculated risks without fear of compensation impacts. Here’s how the two approaches differ: Aspect Traditional MBOs OKRs Compensation Link Directly tied to bonuses Deliberately separated from compensation Goal Structure Combined goals and metrics Separated objectives from measurable results Review Cycle Usually annual More frequent (e.g., two- or four-month cycles) Transparency Often private between manager and employee Highly transparent across organization Core Components of Effective OKRs Ben emphasized that OKRs serve as a critical thinking framework rather than just a goal-setting tool. The objective answers the question “What is the most important area to focus on?” while key results address “How will we know we’ve achieved it?” This structure creates clarity and alignment across teams by: Establishing clear, measurable targets that indicate progress toward objectives Creating a common language for discussing goals across the organization Enabling teams to understand how their work contributes to larger organizational goals Promoting regular check-ins and adjustments based on measurable progress As organizations like Oracle and Google adopted and refined the OKR framework, they demonstrated its effectiveness in driving alignment and results. These companies used OKRs as a communication tool, ensuring everyone spoke the same language about priorities and progress. This common understanding became particularly valuable for product teams, who often need to coordinate efforts across multiple departments and stakeholders. The beauty of this system lies in its flexibility and focus on outcomes rather than activities. For product managers, this means shifting conversations from feature lists and deadlines to measurable impacts and customer value. This outcome-focused approach helps teams stay aligned on what truly matters while maintaining the agility to adjus

A product manager’s guide to breaking free from reactive problem solving Watch on YouTube TLDR In my recent conversation with Doug Hall, master of turning chaos into clarity, we explored how product managers and innovation leaders can break free from reactive problem-solving and create more value through proactive innovation. Doug shared that the average manager wastes 3.5 hours daily fixing problems, with 75% of issues stemming from broken systems rather than employee mistakes. Even more concerning, products typically lose 50% of their innovative value during development as unique ideas get compromised to fit existing systems. Doug offered practical solutions through three powerful frameworks that can transform how teams approach innovation and problem-solving. Key Topics: How to define problems effectively using the Yellow Card method, inspired by military Commander’s Intent principle Creating solutions through structured “Create Sessions” that leverage stimulus, diversity of thought, and fear reduction Six types of innovation stimulus, including patent mining and wisdom mining from academic sources Using the Deming Cycle (Plan-Do-Study-Act) to systematically reduce risks in product development Transforming organizational culture by focusing on system improvement rather than individual blame Introduction Ever feel like your organization is stuck in an endless cycle of putting out fires instead of truly innovating? You’re not alone in that frustration. Today, we’re diving into a well-practiced approach that will transform how you and your team solve problems and drive innovation. Our returning guest, Doug Hall, is a master of turning chaos into clarity – he’s not just the founder of Eureka! Ranch and co-founder of the Dexter Bourbon Distillery, but has spent decades helping companies break free from innovation roadblocks. Doug also has a new book hot off the press titled Proactive Problem Solving: How Everyone Can Fix Problems & Find Ideas for Working Smarter! Doug joined us in episode 518 and is back to share battle-tested strategies that will help you fix problems faster and smarter. Proactive Problem Solving Doug was motivated to write Proactive Problem Solving by two pieces of data showing the impact of reactive problem solving: The average manager wastes 3.5 hours every day dealing with problems. Seventy-five percent of these issues stem from broken systems, bureaucracy, and inefficient processes, while only 25% come from employee mistakes. Products typically lose 50% of their innovative value during the development process. This happens because unique ideas get repeatedly compromised to fit existing systems, rather than adapting our systems to support innovation. We discussed the book’s three main sections: Defining Problems Creating Solutions Driving out Risks Defining Problems Doug shared an approach for defining problems borrowed from military strategy – the Commander’s Intent framework. This methodology emerged from lessons learned during World War II and the Korean War, where military leaders discovered that simply telling teams what to do wasn’t enough. Instead, they needed to explain why it matters. The Three Components of Commander’s Intent What needs to be done – The clear direction that points the organization toward a specific goal Why it matters – The deeper purpose that provides motivation and context for the work Boundaries and scope – Clear guidelines for what’s in and out of scope for the solution The Yellow Card The Yellow Card tool helps teams capture and communicate both problems and potential solutions effectively. Its first section focuses on problem definition, clearly stating what the problem is and why solving it matters. This why component is particularly important as it serves as the motivational energy source when teams face challenges or setbacks. The second section of the Yellow Card focuses on communicating solutions, including how the solution works, its key benefits, and an easy next step for learning more. This last component – the easy next step – helps reduce resistance to change. When presenting new ideas, especially those that challenge existing systems, people naturally feel stress. By providing a simple, low-risk way to learn more about the solution, teams can build confidence gradually and increase buy-in for larger changes. Structure of the Yellow Card Tool Section Components Purpose Problem Definition What + Why Creates focus and motivation Solution Elements How it works + Key benefits Outlines approach and value Next Steps Easy actions for learning more Reduces resistance to change The Yellow Card serves a dual purpose: it helps teams think through problems more clearly and provides a structured way to communicate solutions to stakeholders. Doug shared that this approach has proven so effective that when used in a Canadian TV show called &#82

The product manager’s journey from Individual Contributor to Chief Product Officer Watch on YouTube TLDR Kimberly Bloomston’s journey from individual contributor to Chief Product Officer at LiveRamp demonstrates the key transitions and skills needed at each level of product management leadership. Her path highlights how responsibilities evolve from hands-on product development to strategic business leadership, emphasizing the importance of continuous learning, vulnerability, and strong relationship-building skills. Key Topics: Career progression stages in product management, from IC to CPO Transition from tactical to strategic responsibilities at each level Evolution of stakeholder management and leadership requirements Importance of vulnerability and continuous learning in product leadership Role of business acumen in product management success Critical skills needed at different career stages Value of cross-functional understanding and relationships Impact of organizational structure on product leadership Balance between product expertise and business leadership Strategies for successful career transitions in product management Introduction In this episode, I interviewed Kimberly Bloomston, Chief Product Officer at LiveRamp, to explore her journey from individual contributor (IC) to executive leadership in product management. Kim’s unique perspective comes from climbing every rung of the product management career ladder, experiencing firsthand the evolving responsibilities and challenges at each level. The path from IC to Chief Product Officer isn’t just about gaining more responsibility – it’s about transforming how you think about product development, team leadership, and business strategy. Whether you’re aiming for your first product management role or setting your sights on the C-suite, understanding these career dynamics can help you navigate your own path to product leadership success. Early Career Foundation: Building a Base for Product Leadership Kim’s journey into product management began with an unconventional blend of philosophy and computer science studies in college. This unique combination developed both her analytical thinking skills and her ability to question assumptions – capabilities that would later prove valuable in her product career. Growing up in a tech-friendly household with an entrepreneurial father who owned retail businesses gave her early exposure to both technology and business operations. Her first professional role was with a retail industry consulting company, where she started as a part-time employee during college. Over ten years, she rose through the ranks until everyone in the company reported to her. The company operated a software platform for their call center, managing customer communications while ensuring compliance with state regulations. As VP of Operations, Kim worked with third-party engineering consultants to improve the platform’s ROI and customer outcomes. It was during this time that Kim discovered her passion for product management. She shared a story about finding a way to save a hundred dollars per week through code automation. When discussing this achievement with her brother, an engineer, he pointed out that what she was doing – finding ways to improve processes and outcomes through technology – was essentially product management. This revelation led her to refocus her career from general business operations to technology product management. Key Learnings from Early Career Experience Cross-functional understanding: Her operational role provided valuable insights into how different business functions work together, from support and services to sales and customer success Business metrics expertise: Managing operations gave her deep understanding of business KPIs and how they impact different teams Leadership experience: Early management responsibilities helped develop crucial people skills before entering product management Technical foundation: Growing up with technology and working with engineering teams built technical credibility This foundation proved instrumental in Kim’s later product management roles. Her experience managing people, understanding business operations, and working with technology teams gave her a unique perspective that many product managers develop only later in their careers. Most importantly, it sparked her passion for using technology to solve real business problems – the core essence of product management. These early experiences highlight an important lesson for aspiring product leaders: there’s no single “right” path into product management. Whether you’re coming from engineering, business operations, or another field entirely, your unique background can provide valuable perspective and skills for a successful product management career. Transitioning to Individual Contributor (IC) Product Manager Kim’s entry into pr

How product managers are transforming innovation with AI tools Watch on YouTube TLDR In this deep dive into AI’s impact on product innovation and management, former PayPal Senior Director of Innovation Mike Todasco shares insights on how AI tools are revolutionizing product development. From enhancing team brainstorming and prototype development to product iteration, AI is becoming an essential tool for product managers. However, Mike emphasizes the importance of balancing AI capabilities with human oversight, warning against over-reliance on AI. The discussion explores practical applications of AI tools like ChatGPT and Claude in product development, including MVP refinement, customer testing, and marketing content creation. Drawing from his experience building PayPal’s Innovation Labs, Mike also shares valuable insights on creating an innovation culture that empowers all employees to contribute to product innovation, regardless of their role. Key Topics: Building Innovation Culture (PayPal Case Study) AI as a Brainstorming Partner AI Tools in Product Development Product Development Acceleration AI Implementation Cautions Future of AI in Product Development Customer Testing and Validation AI’s Impact on Product Innovation and Management: A New Era for Product Teams In this episode of Product Mastery Now, I’m interviewing Mike Todasco, former Senior Director of Innovation at PayPal and current visiting fellow at the James Silberrad Brown Center for Artificial Intelligence. Mike brings valuable insights about the revolutionary transformation of product development through artificial intelligence. Through our discussion, Mike shares how this dramatic acceleration in product development processes signals a fundamental shift for product teams. Drawing from his experience leading innovation at PayPal and holding over 100 patents, Mike explains how AI tools are creating new opportunities for innovation, faster iteration cycles, and more comprehensive market understanding while maintaining a balance between artificial intelligence and human insight. Building Innovation Culture: Lessons from PayPal’s Innovation Lab In our discussion, Mike shares insights from his experience building PayPal’s Innovation Lab following the company’s separation from eBay in 2015. He explains that their approach to innovation deliberately avoided the common pitfall of creating a two-tiered system where only designated “innovators” were responsible for new ideas. Creating an Inclusive Innovation Environment The foundation of PayPal’s innovation success rested on a culture of trust and autonomy. Mike points to their unlimited vacation policy as a symbol of this trust-based culture, where employees were treated as responsible adults capable of managing their time and contributions. This philosophy extended to how employees could engage with the Innovation Lab, allowing them to pursue innovative projects alongside their regular responsibilities. Traditional Innovation Model PayPal’s Inclusive Approach Designated innovation teams Open to all employees Structured innovation times Flexible engagement Rigid definition of innovation Adaptable interpretation Top-down innovation goals Self-directed innovation Implementation Strategy PayPal deliberately kept the definition of innovation flexible. Rather than imposing a strict interpretation, they allowed different roles to define innovation in ways that made sense for their work. Mike encouraged employees to include innovation in their annual goals but never forced this approach. Innovation goals were customized to individual roles and responsibilities The Innovation Lab served as a gathering space for collaborative work Employees had freedom to explore projects in their spare time Leadership encouraged but didn’t mandate innovation participation This approach helped create a culture where innovation wasn’t seen as an additional burden but as an organic part of the workplace. While some areas of the company found this adjustment challenging, PayPal’s long-standing history of innovation made the cultural shift more natural. The success of this approach demonstrates how creating the right environment for innovation can be more effective than mandating it through formal structures. Leveraging AI in Product Development: A Practical Approach Mike shares examples of how AI is transforming product development, starting with his own daily interactions with tools like Claude and ChatGPT. His examples demonstrate the versatility of AI in both personal and professional contexts. AI as Your Development Partner Through our discussion, Mike explains how AI can serve as a brainstorming partner for product managers. He illustrates this with a recent experience helping an entrepreneur develop a video analysis product. What stands out is their approach to rapid iteration – continuously challenging themselves to simplify their c

How product managers can adapt core responsibilities across different organizations and contexts Watch on YouTube TLDR Through his research and practical experience at MasterCard, Nishant Parikh identified 19 key activities that define the role of software product managers. He emphasizes that these activities vary based on context (large vs. small organizations, B2B vs. B2C, Agile vs. Waterfall). The discussion reveals how product management has evolved since 1931 and highlights the importance of clear role definition to prevent job frustration. The core focus of these activities is on thorough market research, continuous customer engagement, and strategic product development. Key Topics: Market research as the foundation of product success Evolution from problem space to solution identification Product positioning and vision development Differences between product manager and product owner roles Flexible vs. fixed roadmapping approaches Continuous customer engagement throughout product lifecycle Financial analysis and business case development Impact of organizational size on PM responsibilities Role of AI tools in modernizing product management Importance of cross-functional collaboration Introduction In this episode, I’m interviewing Nishant Parikh, Director of Product Management at MasterCard. We explored the 19 essential activities that define successful software product management today. Drawing from his 20+ years of technology experience and extensive research, Nishant shared insights about how these activities vary across different organizational contexts – from startups to enterprises, B2B to B2C, and Agile to Waterfall environments. He emphasized the importance of role clarity and how the lack of it often leads to frustrated product managers leaving their positions. In this article, I’ll share the key takeaways from our discussion, including why market research should be your foundation, how customer engagement has evolved to become a continuous process, and the ways AI is reshaping traditional product management activities. Why study the 19 key activities of software product managers? Nishant’s motivation came from his personal experience navigating different product management roles over six years. Each position required vastly different responsibilities: In his first PM role, he focused on high-level solution development and feature writing His next position emphasized go-to-market activities At a small MasterCard acquisition company, he had to handle everything from product development to writing stories and epics Currently at MasterCard’s foundry team, his focus is on innovation and ideation This variety of experiences left him confused about the core responsibilities of a product manager. This confusion motivated him to pursue research to better understand: What a product manager’s key responsibilities should be How the discipline has evolved since its inception in 1931 Why many PMs leave their jobs due to lack of role clarity How to address the overlapping responsibilities between product managers, product leaders, and innovators He noted that while large organizations might have 100 defined activities for product managers, it’s impossible for one person to handle them all. This led him to research and identify 19 core activities specific to product management, with clear separation from product marketing, sales, and go-to-market functions. Consolidating insights from different bodies of knowledge Nishant identified three main bodies of knowledge in product management, each with distinct limitations: PDMA (Product Development and Management Association) ISPMA (International Software Product Management Association) – focused specifically on software industry Product Marketing Body of Knowledge – combines product management and product marketing The key problem he identified is that none of these bodies of knowledge clearly distinguish between different product management roles or account for various contextual factors that affect how product managers should work, such as: Organization size (large vs. small companies) Development methodology (Agile vs. Waterfall) Product type (AI vs. non-AI products) Market focus (B2B vs. B2C) He emphasized that these contextual factors significantly impact a product manager’s role. For example: In large companies, different departments handle specialized functions In small companies, one product manager might handle all responsibilities The same role can look very different between B2B and B2C products Nishant’s research aimed to consolidate insights from these different bodies of knowledge and account for various contextual factors to provide a clearer, more comprehensive perspective for product managers and leaders. His goal was to help product managers understand how their role should adapt based on their specific organizational context and product type. 1. Market Research As software produ

Why product managers need to stop the stupid Watch on YouTube TLDR Innovation expert Doug Hall reveals why most organizations struggle with innovation despite recognizing its importance. Through his experience running Eureka! Ranch and Dexter Bourbon Distillery, Hall discovered that successful innovation requires a bottom-up transformation focusing first on empowering frontline employees to fix inefficiencies (“stop the stupid”), then enabling middle managers to improve systems, and finally allowing leadership to pursue bigger strategic innovations. This three-level approach has shown to increase innovation value by 28% versus the typical 50% decline seen in traditional top-down approaches. Key Topics: The Innovation Paradox: While 80% of CEOs say innovation is critical, only 20% believe their organizations are good at it Employee Innovation Barriers: 37% don’t see innovation as their job, 29% don’t know what to do about it Middle Management Challenge: Managers waste 3.5 hours daily dealing with mistakes and system flaws System vs. People Problems: 78% of issues come from flawed company systems, only 22% from employee mistakes The “Stop the Stupid” Approach: Start with empowering employees to fix immediate inefficiencies before pursuing larger innovations Three-Step Framework: 1) Teach innovation fundamentals, 2) Build confidence through early wins, 3) Develop systems thinking Measurable Impact: Organizations can achieve 4 improvement actions per employee per month Cultural Transformation: Focus on intrinsic motivation rather than external incentives The Innovation Paradox in Organizations: Why Companies Struggle to Innovate Doug shared that when you look at any survey of CEOs, more than 80% will say that innovation is crucial for their organization’s future success. However, when asked about their organization’s current innovation capabilities, the numbers flip dramatically – only about 20% believe their organizations are effectively innovating. Doug illustrated this disconnect with a story from his consulting work. His team had just presented breakthrough solutions to a problem that a CEO had previously deemed impossible. Rather than excitement, the CEO’s response was, “Huh, wow. I guess you did figure it out. Now what do I do? I guess I gotta do it.” The disappointment in the executive’s voice revealed a deeper truth about organizational resistance to innovation. This resistance manifests in various ways: Departments operating in silos resist changes that affect their established processes Middle managers hesitate to support innovations that might impact their performance metrics Frontline employees don’t see innovation as part of their role Existing systems and procedures inadvertently suppress new ideas Doug explained why simply having good ideas isn’t enough. Successful innovation requires addressing deeper organizational dynamics and systems that either enable or inhibit change. As we explored in our conversation, resolving this paradox requires a fundamental shift in how organizations approach innovation, starting not with grand strategies but with empowering employees to make small, meaningful improvements in their daily work. Breaking through this paradox requires recognizing that innovation isn’t just about generating new ideas – it’s about transforming how organizations think about and implement change at every level. This understanding forms the foundation for a more effective approach to organizational innovation. The Problem with Traditional Innovation Approaches: Why Good Ideas Often Fail Doug shared a startling insight from three separate studies that crystallizes why traditional innovation approaches often fall short. When organizations take an innovative idea into development, its forecasted value typically declines by 50% before launch. The Innovation Value Loss Problem A truly disruptive idea will challenge multiple departments in an organization. A genuinely innovative product might require: Changes to the supply chain Different manufacturing equipment New customer service processes Alternative sales channels Modified operational procedures When these departmental challenges arise, organizations typically respond by compromising the original idea. As Doug put it, “It’s like you’re managing the death of ideas.” Each department makes small compromises to fit within existing systems until the final product barely resembles the original innovative concept. The Hidden Organizational Barriers Through our discussion, Doug revealed how organizational silos create powerful resistance to innovation: Performance Metrics Conflict Manufacturing departments hesitate to support innovations that might lower their productivity metrics. Departmental Isolation In many corporations, departments operate as separate units where promotion and income depend on making their indivi

A custom ChatGPT model that helps accelerate product innovation Watch on YouTube TLDR In this episode, I interview Mike Hyzy, Senior Principal Consultant at Daugherty Business Solutions. He explains how to conduct an AI-powered design sprint that transforms product concepts into clickable prototypes in just hours instead of weeks. Using a custom ChatGPT model combined with collaborative team workshops, product teams can rapidly move from initial customer insights to validated prototypes while incorporating strategic foresight and market analysis. Key Topics: Strategic foresight approach to product development, focusing on customer needs 2-5 years ahead Triple diamond decision framework for analyzing problems, customers, and markets Integration of team collaboration, AI assistance, and external validation Rapid wireframe and UI design generation using ChatGPT and DALL-E Creation of interactive prototypes using CodePen for immediate testing Custom AI model prompts and best practices for design sprint facilitation Early go-to-market strategy integration in the product development process Practical implementation of AI tools to accelerate product innovation Introduction Imagine taking a product concept from initial customer insight to clickable prototype in just a few hours. That’s exactly what I witnessed at PDMA’s recent Inspire Innovation Conference, where Mike Hyzy demonstrated a groundbreaking approach to AI Design Sprints that’s revolutionizing product development acceleration. By combining strategic foresight, a custom ChatGPT model, and collaborative workshop techniques, Mike led how six teams to achieve what typically takes weeks of work in just under three hours. As a product management professor and practitioner, I’ve seen many methodologies for speeding up innovation, but this approach was different – transforming ChatGPT into a virtual team member that accelerates every phase of the development process, from initial concept through digital product prototyping, while ensuring teams focus on solving tomorrow’s customer needs rather than just today’s problems. In this episode, Mike will take us through the steps he led product teams through during his AI Design Sprint workshop. The Critical Role of Strategic Foresight in Product Innovation At the beginning of the workshop, Mike explained the importance of strategic foresight. He emphasized a fundamental shift in how we should approach product development. Instead of focusing solely on today’s customer problems, product teams need to look 2-5 years into the future. This strategic foresight approach to product development isn’t just about making predictions – it’s about understanding how customer needs and market conditions will evolve over time. Mike shared a sobering statistic that highlights why this forward-thinking approach matters: 42% of companies cite “no market need” as their main reason for failure. This happens when teams solve today’s problems without considering how those needs might change by the time their product actually launches. As I’ve seen in my own product management experience, the traditional product development cycle can take months or even years. By the time we launch, the market may have moved on from the problem we originally set out to solve. The Triple Diamond Framework Components To address this challenge, Mike introduced the Triple Diamond Decision Framework, a structured approach that helps teams look ahead while making concrete decisions. Here’s how the framework breaks down: Jobs to be Done Diamond Explore future customer problems and needs Identify emerging pain points Converge on the most critical future needs Customer Analysis Diamond Map potential future customer segments Analyze evolving customer behaviors Focus on the most promising future customers Market Analysis Diamond Investigate market trends and opportunities Evaluate potential market sizes Select the most viable future markets What makes this framework particularly powerful in an AI design sprint is how quickly teams can move through each diamond. Mike explains that traditional market analysis might take weeks of research, but with AI assistance, teams can gather initial market insights, including total addressable market (TAM) and serviceable market data, in minutes rather than weeks. The key to success with this approach lies in the balance between divergent and convergent thinking at each stage. Teams start by thinking broadly about all possible needs, customers, or markets, then use data and insights to narrow down to the most promising opportunities. Mike emphasizes that this isn’t about rushing through the process – it’s about using AI tools to accelerate the research and analysis phases so teams can spend more time on creative problem-solving and validation. This strategic foresight foundation sets the stage for the entire AI design sprint process. By st

How product managers can move from ideas to action Watch on YouTube TLDR In this episode, I speak with Atif Rafiq about how senior product leaders approach strategy development and execution. Atif brings valuable insights from a recent PDMA executive workshop where leaders discussed their real-world challenges with strategic decision making and innovation strategy. Key topics from our discussion: Main challenges product leaders face when developing strategy A practical framework for exploring product opportunities How AI tools can help with strategic decision making The importance of early-stage product work Ways to improve alignment across organizations Real-world example using a subscription service concept Introduction In this episode, I’m interviewing Atif Rafiq, who recently led an executive workshop at the PDMA conference, where senior leaders discussed challenges they face, including navigating ambiguity and making decisions with more clarity. In this episode, he shares some insights from that workshop and his experience in product leadership. Atif has spent 25 years working in both Silicon Valley and Fortune 500 companies, including leadership roles at Amazon, McDonald’s (as their first Chief Digital Officer), Volvo, and MGM Resorts. He has developed a systematic approach to problem-solving that forms the basis of his book, Decision Sprint: The New Way to Innovate into the Unknown. Key Challenges in Strategic Product Leadership During our discussion, Atif identifies three main challenges that senior leaders face when developing and implementing product strategy: 1. Alignment Challenges Organizations often struggle to get everyone moving in the same direction: Challenge Area Impact Common Problem Problem Understanding Teams interpret issues differently Resources going to wrong priorities Stakeholder Views Departments focus on different goals Competing objectives and metrics Customer Focus Too much focus on one perspective Missing business or operational needs 2. Input and Collaboration Issues Atif explains that product leaders often struggle to gather useful input and work effectively across teams. Common problems include: Meetings that don’t collect all needed information Difficulty managing different department viewpoints Challenges combining input from multiple sources Time pressures that cut short important discussions 3. Experimentation Challenges While many organizations value testing ideas, Atif notes several common issues: Starting experiments before understanding the problem Running tests without clear goals Weak links between test results and business strategy Racing through testing without proper planning Purposeful Exploration: A Better Approach In our discussion, Atif introduces “purposeful exploration” – a structured way to investigate and test product opportunities. This method helps organizations find balance between rushing into solutions and getting stuck in endless discussions. Key Elements of Purposeful Exploration Element Purpose Activities Problem Definition Get clear about the challenge Talk to stakeholders, analyze data, study market Question List Identify what we need to learn Team workshops, AI-assisted research Testing Strategy Check our assumptions Small pilots, focused tests, data gathering Making Sense of Results Draw useful conclusions Analysis, recommendations, team alignment Real-World Example: Coffee Subscription Service During the workshop, Atif walked the senior leaders through an exercise to get buy-in for a coffee subscription service at McDonald’s. Three different groups crafted a problem statement related to this idea and then identified key questions they needed to answer. This example demonstrates how to balance different business needs when exploring a new product idea. Strategic Questions to Consider The teams identified key questions, including: Business Area Key Questions What to Explore Revenue Impact Will subscribers visit more often and buy food? Visit patterns, additional purchases Operations Can stores handle increased coffee orders? Service speed, staff needs Customer Value How does this work with loyalty programs? Digital integration, easy redemption Business Model What makes this profitable? Pricing levels, program guidelines Next, each group shared their questions with the others, and they used AI to compare the breadth and depth of the questions. Key Insights from the Example Success depends on getting customers to visit more and buy additional items Testing needs to happen in stages to manage operational complexity Digital platform integration affects customer adoption Program rules must work for both customers and the business Workshop participants found they could work much faster when combining team expertise with AI capabilities Upstream Product Work Atif emphasizes the importance of early work—the foundation-setting activities before product development starts. He notes that this phase often determ

A framework for product launch success Watch on YouTube TLDR In this episode of Product Mastery Now, I interview James Whitman, author of LAUNCH Code and founder of Growth Guidepost. James shares insights from his research studying companies that consistently launch successful products. His LAUNCH Code framework offers a practical approach to product launch management that any organization can implement. Key Topics Covered: The LAUNCH Code: six essential components of successful product launches How AI is changing product launches and team dynamics Practical strategies for cross-team collaboration The Tranche Model for reducing launch risks Building a culture that supports successful launches Understanding the Launch Code Framework James explains that Launch Code emerged from studying public companies that grew successfully through their product portfolios. These organizations share common practices that form the foundation of the LAUNCH framework: Component Description Listen to clients Gather and analyze customer feedback systematically Assess the opportunity Evaluate market potential and strategic fit objectively Unify the team Build alignment across departments Navigate the launch Execute go-to-market activities strategically Control the risks Manage and reduce potential issues Hone the process Improve launch practices continuously Current Challenges in Product Launches The AI Impact Organizations are adapting to rapid changes in how AI affects product launches. James shares that many teams are now working with their second or third generation of AI tools, particularly in sales and marketing. This raises important questions about balancing human and machine roles in the launch process and keeping employees engaged when AI takes over some of their work. Financial Landscape Changes A significant shift has occurred in venture funding, with more money moving toward AI investments. James describes working with one organization that had five different sales leaders in 18 months due to these pressures. This example revealed a deeper structural issue: The company needed to move up-market from a commoditized position to remain competitive. Making Better Launch Decisions James points out common decision-making problems in product launches. He describes what he calls the “Your PowerPoint is better than mine, but you’re wrong” syndrome – where strong presentation skills can override better strategic choices. Instead, organizations need to: Focus on finding the best solution rather than winning arguments Challenge assumptions constructively Build collective ownership of decisions Create space for different perspectives Building Cross-Functional Success A key insight from our conversation is how product launches require coordination across departments. James shares an example where changing product strategy meant completely rethinking the sales approach. The company needed salespeople who could sell complex solutions instead of commoditized products, showing how product decisions affect the entire organization. Creating Common Language James emphasizes the importance of vocabulary in cross-team work. For example, he notes that “discovery” means different things to sales and product teams: Sales discovery: Understanding customer needs during the sales process Product discovery: Researching market problems and solutions Market discovery: Understanding broader market trends and opportunities Using clear, shared terms helps prevent misunderstandings and builds better collaboration. Building the Right Culture Culture plays a vital role in launch success. James points to Atlassian as an example of intentional culture-building that supports product success. Their approach includes: Creating systems for cross-team collaboration Building trust through consistent practices Focusing on employee satisfaction Maintaining strong customer connections Product Led Growth (PLG) in Action James explains that PLG companies like Zoom, ClickUp, and Pendo demonstrate the Launch Code principles naturally. These organizations: Get direct customer feedback through product usage Test features with specific user groups Make quick adjustments based on data Scale successful features systematically The Tranche Model: A Practical Launch Approach During our conversation, James shares how LinkedIn uses what he calls the “Tranche Model” for product launches. This approach involves: Testing with defined market segments (tranches) of 2 million users Learning from each group before expanding Making improvements based on real usage data Returning to early groups with refined offerings For smaller markets, James recommends adapting this approach by creating representative samples. For example, if targeting 1,000 CFOs, start with 150 that represent different company sizes and industries. Managing Launch Risks James describes several approaches to controlling launch risks: Risk Area Management Approach Market R