Product Mastery Now for Product Managers, Leaders, and Innovators

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 process that works well in academic settings. This expanded approach gives students a clearer roadmap through the often messy innovation journey. Design Thinking isn’t a linear process. It’s intentionally messy and iterative, allowing teams to jump back and forth between phases as they incorporate new data and feedback. This flexibility is important for product innovation because the path to understanding customer needs is rarely straightforward. What makes this framework particularly effective is how it encourages teams to stay open to new insights throughout the process. When teaching Design Thinking to his students, John helps them understand that the framework serves as a guide rather than a rigid set of steps. This approach helps product teams remain adaptable while still maintaining a structured approach to innovation. Voice of the Customer: Mastering the Art of Problem Discovery Effective product innovation begins with truly understanding the customer’s problem, through Voice of the Customer (VOC) research (477: Three-step VOC system – with Andrea Ruttenberg, PhD). The Depth of Customer Interviews Creating effective customer interview questions is just the beginning. The real value comes from analyzing the responses properly. John teaches his students to look beyond the obvious answers and find deeper insights that might not be immediately apparent. VOC Challenge How to Address It Asking the right questions Focus on problems, not solutions; ask about specific experiences The curse of knowledge Turn off your expertise; listen without imposing your understanding Analyzing responses Look for patterns across multiple interviews; have others analyze your interviews Personal bias Depersonalize the process; focus on customer needs, not your vision John referenced the seminal Voice of the Customer paper by Abby Griffin and John Hauser from 1993, which laid the groundwork for many modern customer discovery methodologies. Avoiding the Curse of Knowledge One of the most challenging aspects of customer discovery is what John called “the curse of knowledge.” This happens when product teams have so much expertise in their field that they can’t see problems from a beginner’s perspective.  Good Design Thinking practices minimize the team members’ personal desires and wishes. For more on this, see 483: Nailing the customer experience to improve product value – with Jason Friedman. John talked about how he uses classroom exercises to help students overcome this challenge. He has them develop solutions for problems in innovation and leadership, then forces them to “turn off” their own knowledge and focus solely on what the customer experiences. The “aha moment” comes when students realize that even though they’re knowledgeable about a topic, their product will only succeed if it addresses the customer’s actual experience of the problem, not their expert understanding of it. Effective innovation requires setting aside your expertise long enough to truly empathize with and understand your customers’ experiences. Divergent and Convergent Thinking: The Rhythm of Innovation We discussed the powerful combination of divergent and convergent thinking in the innovation process. This approach to problem-solving has deep roots in creative thinking methodologies, particularly the Osborn Parnes Creative Problem Solving process. Understanding the Dual Process Effective innovation follows a rhythm of opening up possibilities (divergent thinking) and then narrowing down to practical solutions (convergent thinking). This pattern repeats throughout the product development journey. Phase Divergent Thinking Convergent Thinking Problem Definition “Wouldn’t it be nice if we could solve…?” Selecting the most impactful problem to solve Customer Research Generating many possible interview questions Choosing the most revealing questions to ask Solution Development Brainstorming many possible solutions Evaluating solutions against criteria Prototyping & Testing Exploring different ways users interact with prototype Deciding what the product should be John detailed how this dual process works in practice. In the early stages, teams use invitational language like “Wouldn’t it be nice if we could solve this problem?” or “In what ways might we approach this challenge?” This open phrasing encourages broad thinking without limiting possibilities. The Language of Creative Problem Solving John pays attention to the language used during innovation sessions. He explained that phrases like “How might we…” create mental space for exploring options without judgment. This invitational language is fundamental to the Creative Problem Solving methodology. The real power comes from alternating between these two modes of thinking throughout the product development journey: Expand possibilities through divergent thinking (generate many options) Narrow focus through convergent thinking (select the best options) Repeat this pattern at each stage of development John referenced 522: Stop the stupid using proactive problem solving – with Doug Hall on breaking free from reactive problem solving. Defining problems effectively is challenging, but getting ahead of problems is even more difficult. This proactive approach to problem-solving requires both creative exploration and disciplined evaluation—the essence of divergent and convergent thinking. This approach isn’t just theoretical. John explained how these techniques were applied in his corporate work at Praxair and Linde, helping teams tackle complex engineering and product challenges more effectively by balancing creative exploration with practical decision-making. Tackling the “Fuzzy Front End” of Innovation John shared his team’s approach to reducing uncertainty in the early stages of product development—what innovation professionals often call the “fuzzy front end.” Accelerating Innovation Decision-Making John’s team at Praxair adopted an approach for solving complex problems similar to the two-hour Design Spring (499: How to implement a 2-hour design sprint to solve complex problems – with Teresa Cain). They faced a common challenge in product development: how to quickly determine if an idea deserved further investment without spending months in preliminary investigation. Their solution was to bring together a diverse team to “declutter the fuzziness” in a single day or two, rather than having one person spend weeks or months investigating. This approach allowed them to: Quickly gather all available knowledge about customer needs Assess technical feasibility from multiple perspectives Evaluate business potential with input from various stakeholders Make faster decisions about whether to move ideas into the formal Stage-Gate process This accelerated approach delivered significant value by reducing the time to make go/no-go decisions. Teams could either advance promising ideas more quickly or fail fast on concepts that wouldn’t work, freeing up resources for more promising opportunities. Traditional Approach Accelerated Approach One person investigating an idea Cross-functional team evaluating together 1-2 months of preliminary work 1-2 days of intensive collaboration Sequential information gathering Parallel processing of information Slow entry into Stage-Gate process Rapid movement into Stage-Gate evaluation The approach aligns with lean innovation principles: Gather just enough information to make an informed decision, test assumptions quickly, and don’t waste resources on extended analysis when a faster process can achieve similar results. For product managers facing pressure to innovate more quickly, this compressed fuzzy front end approach offers a practical solution to balance thoroughness with speed. By gathering the right people in a focused session, teams can achieve in days what might otherwise take months. Facilitation Tools for Better Innovation John highlighted several facilitation tools that product teams can use to improve their innovation process. These structured approaches help teams think more effectively and overcome common biases in problem-solving. The Phoenix Checklist: A Declassified Problem-Solving Tool One resource John mentioned was the Phoenix Checklist, a problem-solving tool originally developed by the CIA and declassified in the 1990s. This comprehensive list of questions helps teams thoroughly define problems and develop solution plans. Problem Definition Questions Solution Planning Questions What is the real problem we’re trying to solve? How can we test this solution? Why does this problem need solving? What resources will we need? Can we look at this problem differently? How will we know if we’ve succeeded? Experienced product managers would recognize many of these questions as ones they already use intuitively. The structured format, however, ensures that teams don’t miss critical aspects of problem definition or solution planning. Six Thinking Hats: Different Perspectives for Better Decisions Another facilitation tool John mentioned was Edward de Bono’s Six Thinking Hats. This method helps teams look at problems and decisions from multiple perspectives by having everyone adopt the same thinking mode simultaneously. Thinking Hat Focus Area White Hat Facts and information Red Hat Emotions and feelings Black Hat Risks and potential problems Yellow Hat Benefits and positive aspects Green Hat Creative ideas and alternatives Blue Hat Process management and overview John prefers to have everyone adopt the same “hat” or thinking role simultaneously, rather than assigning different perspectives to different team members. This helps prevent people from becoming entrenched in one perspective and creates a safer space for various types of thinking. By incorporating these facilitation tools into the product development process, teams can overcome biases, explore problems more thoroughly, and arrive at better solutions. For product managers looking to improve their team’s innovation capabilities, these structured approaches offer practical, immediately applicable techniques. Prototype Development Best Practices We discussed John’s approach to prototyping—the process of creating early versions of products to test with customers (458: Selecting, planning, and prototyping product features – with Matt Genovese and 509: Prototyping mastery for product managers – with Matthew Wettergreen, PhD). The Art of Minimum Viable Prototypes John observed that many innovators, especially students new to product development, struggle with creating appropriately minimal prototypes. The tendency is to build too much functionality too early, wasting time and resources on features that might not deliver value. Common Prototyping Mistakes Best Practices Building too many features Focus on the core value proposition only Perfecting the prototype Create just enough to test the core concept Delayed testing with users Test with users as early as possible Becoming attached to initial ideas Be willing to pivot or abandon based on feedback To illustrate the power of simplicity in prototyping, John shared a historical example: Microsoft Word in 1987. The original product came on two 5.25-inch floppy disks and offered just the essential text editing capabilities—type, format with a few fonts, underline, and bold text. It was, by today’s standards, incredibly basic. Yet even this minimal version was sufficient to test the core value proposition. John pointed out that what we consider essential functionality today was built incrementally over decades, not delivered all at once in the first version. Pretotyping: Fake It Before You Make It John highlighted Alberto Savoia’s concept of “pretotyping”—creating even simpler simulations of product ideas to test market interest before building actual prototypes. This approach focuses on quickly validating whether people would use a product concept before investing in development. The core principle is “fake it before you make it”: Create the simplest possible simulation of your product idea Test it with potential users to see if there’s genuine interest If people use it, proceed to more developed prototypes If people ignore it or lose interest quickly, move on to other ideas John shared how he encourages students to test their concepts with classmates, friends, and family first. For example, one student with a sustainable clothing concept was advised to test it with friends before investing time in more elaborate prototypes. If the idea doesn’t resonate with their immediate circle, it’s unlikely to work at a larger scale. This “fail fast” approach to prototyping aligns perfectly with lean innovation principles. By recognizing that most new product ideas will fail, teams can use rapid prototyping to discover which ideas have promise without wasting resources on elaborate development for concepts that won’t succeed in the market. Teaching Innovation in Graduate Programs John shared how he structures his graduate-level innovation course to help students develop practical skills they can apply in their organizations. The innovation course at Daemen University is part of a Leadership and Innovation graduate program that attracts professionals from diverse backgrounds—healthcare, higher education, industry, and nonprofits. Rather than focusing solely on theoretical concepts, John helps students understand how to apply innovation frameworks in their specific organizational contexts. Course Element Learning Approach Shared class example Five-week collaborative project applying innovation frameworks Digital collaboration Daily standups via Zoom when not in class Visual documentation Using tools like Mural to make work visible to all team members Adaptive teaching First four weeks structured, then adapting based on student needs John structures the first four weeks of his course rigorously, setting a solid foundation of innovation principles. Then, as he observes how students are progressing, he adapts the curriculum to address their specific challenges. This mirrors how product teams should approach innovation—starting with a framework but remaining adaptable as new information emerges. Creating “Aha Moments” About Innovation One of John’s primary goals is to help students experience breakthrough moments when they truly grasp how product development works. These “aha moments” typically occur about 3-4 weeks into the course, when students begin to understand how to use customer feedback to develop viable products. John brings a cardboard box into the classroom and asks students to consider how ubiquitous this innovation is—appearing in countless forms across the world—and how different our lives would be without it. This helps students recognize that innovation isn’t always about dramatic technological breakthroughs; sometimes it’s about simple solutions that solve widespread problems effectively. This teaching approach offers valuable lessons for product leaders. By focusing on the fundamentals while remaining adaptable, and by recognizing innovation in everyday objects, professionals can develop a more nuanced understanding of what makes products successful. Conclusion Innovation is never a straight line from problem to solution. As John Spero shared through Robert Quinn’s quote about “building the bridge as you walk on it,” effective product managers must balance structure with adaptability. The frameworks and tools he discussed—from design thinking and divergent-convergent problem solving to facilitation techniques like Six Thinking Hats—provide practical resources that can immediately improve how product teams innovate together. Perhaps most importantly, John’s journey reminds us that innovation requires continuous learning. Even after 15 years as an R&D leader, he found tremendous value in comprehensive product management training. For product managers looking to enhance their capabilities, his advice is clear: understand the entire product development landscape, not just your specialty; learn practical frameworks; master facilitation tools; and don’t overlook leadership development. By approaching innovation as a continuous learning journey rather than a destination, you’ll be better equipped to create products that truly solve customer problems. Useful Links Connect with John on LinkedIn Learn more about Daeman University’s Leadership and Innovation program Read about the Phoenix Checklist Innovation Quote “Build the bridge as you walk on it.” – Robert Quinn Application Questions How could your team implement the divergent-convergent thinking approach in your next innovation challenge? What specific areas of your product development process would benefit most from deliberately separating idea generation from evaluation? How might your understanding of team members’ work styles and preferences (like DISC profiles) improve collaboration on your current product initiatives? What tensions exist between different work styles on your team, and how could you address them? How could you apply the “fuzzy front end” acceleration technique to reduce uncertainty in the early stages of your next product concept? What would a 1-2 day intensive session look like for your team, and who would need to be involved? In what ways could your prototyping process be simplified to test core concepts more quickly? What are you currently over-building in your prototypes that could be eliminated without compromising your ability to validate key assumptions? How might you incorporate facilitation tools like Six Thinking Hats or the Phoenix Checklist into your next product decision meeting? Which specific product challenges would benefit most from these structured approaches to thinking? Bio John Spero 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 is an adjunct professor at Daemen University in their Leadership & Innovation program, focusing on critical thinking, decision making, and problem-solving skills for complex innovation situations. Thanks! Thank you for taking the journey to product mastery and learning with me from the successes and failures of product innovators, managers, and developers. If you enjoyed the discussion, help out a fellow product manager by sharing it using the social media buttons you see below. Source

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 opportunities to pursue before investing significant resources in development. The Value of the PRFAQ Process The PRFAQ document itself is useful, but Marcelo explained that its real value comes from the process of creating it. This process consists of three key phases that help teams discover, debate, and decide on the right product strategy. Discovery, Debate, and Decision The PRFAQ framework creates a structured approach to product innovation: Discovery: Identify what you know (facts) and don’t know (assumptions) Debate: Get input from various stakeholders to strengthen the concept Decision: Build conviction to move forward or not with the opportunity The PRFAQ is what you do “before day one” – before you start planning, developing roadmaps, designing user experiences, or building proof of concepts. The goal is to answer one fundamental question: Should we pursue this opportunity? Forcing Critical Questions One of the framework’s greatest strengths is that it forces teams to answer hard questions about customers and problems before committing resources to development: Critical Questions Why They Matter Who is the customer? Ensures you’re targeting the right audience What problem are we solving? Confirms you’re addressing a real need How are they solving it today? Identifies competitors and alternatives Is the problem growing or shrinking? Determines future market potential Is it urgent? Affects adoption rate and pricing power Do they have a satisfactory solution already? Indicates how difficult displacement will be By addressing these questions early in the process, teams can identify what they know with certainty and what assumptions need validation. Writing a coherent PRFAQ requires either facts or assumptions – and identifying assumptions is the first step toward turning them into facts through market research. Distinguishing Facts from Assumptions A well-crafted PRFAQ clearly distinguishes between: Facts about customers – Their problems, existing solutions, and market conditions Assumptions about your solution – How it will deliver value and differentiate from alternatives Marcelo pointed out that many product failures stem from treating assumptions as facts. The PRFAQ process helps teams recognize what they don’t know, creating opportunities to validate assumptions before making significant investments. When you identify gaps in your knowledge through this process, you can develop targeted research to fill those gaps, significantly improving your chances of creating a product customers actually want. The PRFAQ Review Process At Amazon, the PRFAQ isn’t just written – it’s reviewed, debated, and improved through a structured process. Review Session Structure The PRFAQ review follows a specific format designed to generate productive feedback: Led by a “single threaded leader” responsible for the document Small groups of 2-6 people per session First 20 minutes: Everyone reads the document Next 40 minutes: Questions and feedback This structure might seem awkward at first – Marcelo admitted it felt strange during his first weeks at Amazon – but it offers distinct advantages over traditional review methods. The Power of Reading During Meetings Having everyone read the document during the meeting offers several benefits: Allows people to read at their own pace Provides time to highlight unclear points Enables reviewers to revisit sections for better understanding Ensures everyone has actually read the document before providing feedback During the discussion portion, reviewers typically ask for clarifications or point out potential issues with the concept. This feedback strengthens the PRFAQ and helps you identify blind spots in the strategy. Recommended Review Sequence Marcelo suggested a specific order for conducting PRFAQ reviews: Start with other product managers who are comfortable with ambiguity Expand to other departments with relevant expertise Include executives and key stakeholders This progression helps refine the concept gradually before it faces more rigorous scrutiny from decision-makers. Typical PRFAQ Cadence At Amazon, product managers are deeply immersed in this process: A typical product manager reads 1-2 PRFAQs per week They lead creation of one PRFAQ every 6-12 months Most reviews involve stakeholders with direct interest in the product This regular exposure to others’ PRFAQs provides learning opportunities, helping product managers understand what kinds of questions they should anticipate when developing their own documents. After gathering feedback, Marcelo recommended waiting a day before making edits. This pause allows the product manager to digest comments, think through implications, and make thoughtful improvements rather than reactive changes. The review process creates alignment and buy-in across teams, ensuring that if the project moves forward, everyone understands the vision and feels ownership in its success. Practical Applications of the PRFAQ The PRFAQ framework isn’t just for large companies like Amazon. Marcelo shared how he’s applied this approach to his own projects, demonstrating its versatility across different contexts. Case Study: Using PRFAQ for a Book Project Marcelo explained how he used the PRFAQ framework to prepare for writing for his own book, The PRFAQ Framework. By treating the book as a product, he gained valuable insights: Initially planned to write “PRFAQ for Founders” as his working title Through the PRFAQ process, discovered the target audience was too narrow Market research revealed 20 times more product managers than founders Expanded focus to “innovators” regardless of title This shift in target audience wouldn’t have happened without the structured thinking the PRFAQ framework enforced. By questioning his assumptions about who would benefit from his book, Marcelo made a strategic pivot that significantly expanded his potential readership. Market Research Through PRFAQ Another valuable application Marcelo described was using the framework for competitive analysis: Identifying what solutions already exist in the market Understanding how customers are currently solving their problems Finding gaps and opportunities for differentiation For his book project, this meant researching other product strategy frameworks (like OKRs and Business Model Canvas) to ensure he was offering something unique and valuable. Simply providing a PRFAQ template wouldn’t be sufficient – just as explaining OKRs without implementation guidance wouldn’t be helpful. This insight led him to focus on the method behind creating and using the PRFAQ, not just the document structure. By applying the framework to his own project, Marcelo demonstrated how it helps innovators validate their ideas before investing significant time and resources. This practical example shows how product managers in any organization can benefit from this strategic thinking approach. Common Mistakes to Avoid Marcelo identified several common mistakes that can undermine the PRFAQ framework’s effectiveness. Understanding these pitfalls can help product teams implement the approach more successfully. Treating the PRFAQ as a Marketing Tool The most common mistake Marcelo has seen is treating the PRFAQ as a marketing document rather than a product strategy tool. The PRFAQ is not what you create a month before launch It’s not a substitute for launch marketing materials Marketing teams have better tools for launch preparation Using the PRFAQ only at launch time misses the entire point of the framework, which is to validate ideas before significant resources are invested in development. Treating the PRFAQ as a Roadmap Another common mistake is packing the PRFAQ with excessive plans and details about execution: What to Avoid Why It’s Problematic Detailed wireframes Suggests design decisions are already made Feature lists Shifts focus to solutions before problems are validated Technical architecture Implies technical approach is predetermined Roadmap details Assumes timeline before strategy is approved Proof of concepts Represents significant investment before validation If you’ve already done all this work, you’re halfway committed to this project, but the PRFAQ is supposed to help you decide whether to invest in development, not document decisions you’ve already made. Not Distinguishing Facts from Assumptions Another mistake is failing to differentiate between: Facts: Information about customers and their problems that is supported by evidence Assumptions: Hypotheses about your solution and its potential impact Many PRFAQs present assumptions as facts, which can lead to flawed decision-making. Statements like “most users will love this feature” without supporting data would never be acceptable in an Amazon PRFAQ review. Instead, assumptions should be clearly labeled: “We assume that most users would prefer this approach.” This clarity helps teams identify what needs to be validated before proceeding. Not Right-Sizing the Effort Marcelo suggested that a PRFAQ should take about 1-2 weeks to develop (after you’ve done a few of them), not months. This timeframe: Is substantial enough to think through the strategy Isn’t so lengthy that it becomes a project in itself Allows you to decide whether to invest 3-9 months in development The PRFAQ is meant to be a strategic tool that helps you make good decisions quickly, not an exhaustive planning document that delays action. By avoiding these common mistakes, product teams can use the PRFAQ framework as intended – as a focused strategic exercise that helps determine which opportunities are worth pursuing. Key Benefits of the PRFAQ Approach The PRFAQ framework offers substantial benefits that extend beyond product planning. Marcelo highlighted several advantages that make this approach valuable for organizations of all sizes. Stakeholder Buy-in Through Participation One of the most significant benefits is how the PRFAQ process creates natural buy-in across the organization: Team members feel part of the decision process Energy and commitment to approved projects increases dramatically Avoids the “throwing over the wall” problem many organizations face Traditional approaches where product teams develop plans in isolation and then try to “sell” them to other departments often create resistance. Marcelo contrasted this with the PRFAQ approach, where stakeholders participate in shaping the strategy from the beginning. This collaborative process transforms how teams engage with new initiatives. Instead of being told what to execute, they help decide what’s worth pursuing in the first place. Better Alignment During Execution The PRFAQ creates remarkable alignment when implementation begins: Team members share a common understanding of strategy Less need for constant checking and clarification Fewer misunderstandings about vision and goals Marcelo identified this alignment as critical to execution success. When everyone has participated in early strategic discussions, they understand not just what they’re building, but why they’re building it. This shared context prevents the confusion that often plagues product development projects. As Marcelo noted, “the biggest problem with most product projects is a lack of strategy, not a bad strategy.” Conclusion The Amazon PRFAQ framework offers product teams a powerful way to validate ideas before investing significant resources in development. By writing a press release and FAQs for a product that doesn’t yet exist, teams are forced to clarify their vision, understand customer problems, and make better strategic decisions. As Marcelo demonstrated through his own experience applying the framework to his book project, this approach works for organizations of all sizes and can transform how teams approach innovation. While implementing the PRFAQ process requires some cultural adaptation, the benefits far outweigh the initial awkwardness. Teams gain stronger alignment, better decision-making capabilities, and a clearer distinction between facts and assumptions. By focusing on strategy before execution, organizations can avoid building products nobody wants and instead create solutions that truly solve customer problems. Whether you’re a product manager, founder, or innovator within your organization, the PRFAQ approach provides a structured path to more successful product development. Useful Links Check out The PRFAQ Framework Connect with Marcelo on LinkedIn Innovation Quote “If I had asked people what they wanted, they would have said faster horses.” – attributed to Henry Ford Application Questions How could you adapt the PRFAQ review process to fit your organization’s current meeting culture? What specific changes would you need to make to ensure stakeholders engage meaningfully with the document? How could your team better distinguish between facts and assumptions in your current product planning process? Where do you see assumptions being treated as facts, and what steps could you take to validate these assumptions? How might you implement the PRFAQ approach for an existing product that needs significant improvement? What would be different compared to using it for a completely new product? How could you use the PRFAQ framework to evaluate multiple competing opportunities? What additional criteria might you add to help prioritize between several promising PRFAQs? How could you measure the effectiveness of implementing the PRFAQ process in your organization? What indicators would show that it’s improving your product development outcomes? Bio Marcelo Calbucci is an entrepreneur, innovator, and technologist. He’s been building software products for over thirty years, having sold his first software at age fourteen. He has worked at Microsoft (Exchange Server & Bing) and Amazon (People eXperience & Technology), leading software engineering, product, data science, and UX. He has founded six startups in Seattle and London and launched a dozen tech projects. He’s the inventor of eleven patents. Marcelo has been a community builder in Seattle, organizing dozens of meetups, events, and conferences, and he has written over one thousand blog posts and articles on his web-site and other tech publications. Outside of tech and startups, Marcelo loves to cook elaborate meals for friends, run marathons (eight and counting), and travel with his wife and kids. Thanks! Thank you for taking the journey to product mastery and learning with me from the successes and failures of product innovators, managers, and developers. If you enjoyed the discussion, help out a fellow product manager by sharing it using the social media buttons you see below. Source

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 rational thinking. The brain prefers activities like daydreaming, which require less energy than analytical thinking. This presents a major opportunity for product teams: If you can trigger your customer’s brain to daydream about your product, you’ve found a neurological shortcut to desire. The Coveted Condition Framework Building on this understanding of brain function, Laurier introduced the “coveted condition” framework – a tool for creating products that trigger emotional buying decisions. The framework focuses on what customers dream of becoming through using your product. It follows a simple structure: “I need [product] to become [coveted condition/desired future state].” The coveted condition isn’t about the product’s features – it’s about the better version of themselves that customers aspire to become. When you understand this aspirational state, you can design products that naturally trigger emotional desire. For example, truck commercials rarely show the everyday uses of pickup trucks. Instead, they show vehicles conquering rugged terrain, conveying power and freedom. The actual product experience might involve commuting and hauling supplies, but the coveted condition is about adventure and capability – emotional states that trigger the “I need that” response. By focusing on the coveted condition in your product development and marketing, you can bypass rational feature comparison and tap directly into your customers’ emotional decision-making system – making your product feel like a necessity rather than just an option. Integrating Product Development and Marketing Laurier described the value of integrating product development and marketing from the earliest stages of product development. In many organizations, these functions operate as distinct phases – engineers and product managers build the product, then throw it “over the wall” to marketing to make people want it. Breaking Down Functional Silos This separation creates a fundamental problem in product development. Engineers and product managers tend to excel at functional outcomes, while marketers are better at understanding emotional connections. When these teams work in isolation, the result is often a product that functions well but fails to create the emotional response needed for the “I need that” reaction. Laurier explained that successful companies introduce marketing thinking at the concept stage, having marketers involved in early product discussions. This approach ensures products are designed with emotional triggers in mind from the beginning. Learning from Apple’s Approach The interview highlighted Apple’s approach under Johnny Ive, who designed many of their most successful products starting with the colorful iMac. Ive often discussed how product development, design, and marketing were inextricably linked at Apple. This integration created feedback loops that ensured products weren’t just functional but emotionally compelling. Steps to Better Integration For product managers looking to implement this approach, consider these practical steps: Invite marketing team members to early concept discussions Focus early conversations on emotional reactions you want to trigger Create cross-functional feedback loops throughout development Prioritize features that spark emotion, not just solve problems Design onboarding experiences that deliver immediate gratification Build in shareable moments that encourage word-of-mouth marketing The 10X Better Rule for Product Success For a product to breakthrough the competition, it must be at least 10 times better than the existing product. Incremental improvements often fail to generate significant market traction, despite seeming like they should be sufficient. Why Incremental Improvements Don’t Break Through Many product managers assume that making a product twice as good as existing solutions should be enough to drive adoption. However, Laurier explained that a major psychological barrier stands in the way: the dramatic mismatch between how consumers and innovators perceive value. Research shows two critical factors at play: Consumers overvalue what they already have (the status quo) by a factor of 3 Innovators overvalue their new product by a factor of 3 This creates a 9:1 perception gap that must be overcome for a new product to break through. This means your product needs to be 10 times better than existing solutions to truly trigger the “I need that” response. Examples of 10X Better Products Laurier shared several examples of products that achieved this 10X improvement threshold: Tesla’s early electric vehicles: Not just electric, but better in nearly every measurable category – more powerful, more user-friendly, and featuring innovative details like pop-out door handles The original iPhone: Dramatically superior to stylus-based touchscreens on devices like the Palm Trio and Blackberry, making the interface vastly more intuitive A cycling computer: Compared to a basic speedometer, it tracked multiple metrics simultaneously, providing transformative data for serious cyclists Implementing the 10X Better Rule For product managers looking to apply this principle, consider these strategies: Identify the emotional metrics that matter most to your target customers Focus innovation on dimensions with high emotional impact Don’t spread improvements thinly across many features Concentrate resources on making a few aspects dramatically better Test whether your improvements actually trigger the “I need that” response The 10X Better Rule reminds us that breaking through consumer inertia and triggering psychological need requires dramatic improvement, not incremental change. This understanding helps explain why some innovative products succeed while others with seemingly good improvements fail to gain traction. The Role of Customer Research Understanding customers is fundamental to creating products they feel compelled to buy. Going Beyond Surface-Level Research Traditional customer research often focuses on functional needs and use cases. While this information is valuable, Laurier suggested that product teams need to dig deeper to uncover the emotional drivers that trigger the “I need that” response. Effective customer research for compelling products should: Identify what outcomes customers truly want to achieve Uncover the “coveted condition” customers dream about Determine what triggers genuine excitement Test emotional reactions, not just feature preferences Discover pain points that have emotional weight Finding the Emotional Connection Laurier explained that great products transcend being mere tools – they become pathways to who customers want to be. This perspective shifts customer research from focusing solely on what tasks customers need to accomplish to understanding how they want to feel when using your product. Testing for Emotional Response One advantage of modern digital marketing is the ability to test different emotional triggers quickly. Laurier described how nimble ad testing allows teams to: Try multiple emotional angles simultaneously Measure which messages create the strongest response Scale up approaches that trigger genuine excitement Quickly discard messaging that fails to connect emotionally By incorporating emotional testing into customer research, product teams can better understand what will transform their product from useful to necessary in the minds of their customers. This deeper approach to customer research provides the foundation for applying the frameworks Laurier discussed, ensuring that products aren’t just built to functional specifications but designed to trigger the psychological transformation that makes customers feel they need your product. The CLIMB Framework for Identifying Product Needs Laurier shared the CLIMB framework – an acronym for Customer Life Improving Mechanisms and Benefits. This tool helps product teams identify four levels of need that compelling products address. The Four Levels of Need The CLIMB framework breaks down customer needs into a hierarchy from basic functional benefits to transcendent impacts: Functional Needs: The practical benefits like saving time, reducing costs, and improving performance Emotional Needs: Feelings such as security, pride, belonging, enjoyment, and status Transformative Needs: Personal growth areas including health, sense of purpose, relationships, and confidence Transcendent Needs: Impact beyond the user, such as helping others, environmental benefits, and legacy building Laurier explained that while any good product addresses at least one level, the most compelling products typically address needs at multiple levels of the framework. Applying the CLIMB Framework For product managers, the CLIMB framework offers a structured approach to creating more compelling products: Identify your product’s position: Which levels of need does your product currently address? Find gaps and opportunities: Which higher-level needs could you incorporate? Prioritize applications: Determine which needs are most important for your target customers Guide marketing: Use insights to craft messaging that resonates emotionally Target audience selection: Identify customer segments most likely to value the needs your product addresses Using CLIMB for Persona Development Laurier described how the framework can enhance persona development by viewing needs through the eyes of specific customer types. For example, a family-oriented vehicle buyer might prioritize the transformative need of being a better parent (through safety features) while also valuing the emotional need of appearing successful and responsible. By systematically applying the CLIMB framework, product teams can move beyond feature-focused development to create products that connect with customers at deeper psychological levels – making them far more likely to trigger the coveted “I need that” response. The Role of Craftsmanship in Product Value Laurier explained that perceived craftsmanship creates emotional connections to products. This aspect of product development is often overlooked but can significantly influence whether customers feel compelled to purchase. How Craftsmanship Creates Emotional Value Laurier explained that when customers perceive craftsmanship in a product, they value it more highly – even for seemingly utilitarian items. This principle applies across product categories: Physical products: Attention to detail in design and construction signals value Digital products: Clean interfaces and thoughtful user experiences create emotional connection Services: Care and precision in delivery builds trust and loyalty The “Made with Love” Effect During our discussion, Laurier shared a personal example – telling his 10-year-old daughter that he made her sandwich “with love” genuinely enhances her enjoyment of it. This illustrates how the perception of care and intention transfers emotional value to the product experience. Similarly, when companies share behind-the-scenes glimpses of their development process, they tap into what Laurier called the “IKEA effect” – people value things more when they see or participate in their creation. Applying Craftsmanship Principles Product managers can leverage this insight by: Highlighting the care and attention in your development process Ensuring user interfaces reflect thoughtful design decisions Creating “evidence of craftsmanship” in product details Communicating the expertise behind your product Showing rather than telling about quality By incorporating craftsmanship into both your product development and marketing approaches, you can create deeper emotional connections that help trigger the “I need that” response from customers. Conclusion Creating products that customers feel compelled to buy isn’t about clever marketing tricks or feature overload—it’s about understanding the psychology that transforms wants into needs. By focusing on the emotional brain’s role in decision-making, integrating marketing and product development from the start, and applying frameworks like CLIMB, product managers can create offerings that trigger that coveted “I need that” response. As Laurier demonstrated throughout our conversation, successful products don’t just solve problems—they connect to customers’ aspirations and help them become who they want to be. The journey from product-market fit to creating products customers can’t resist requires a fundamental shift in approach. Rather than asking “What features should we build?” successful product teams ask “What will delight customers?” By aiming to be 10x better in ways that matter emotionally, showcasing craftsmanship in every detail, and focusing on innovation rather than imitation, product managers can create offerings that transcend rational comparison. When customers imagine their lives with your product and feel genuine excitement about owning it, you’ve created something truly compelling—a product they don’t just want, but absolutely need. Useful Links Visit Laurier’s website to get his book and sign up for emails with key takeaways Check out Laurier’s book, I Need That: Creating and Marketing Products People Are Compelled to Buy Connect with Laurier on LinkedIn Learn more about Graphos Product Search for Product: Knowledge on your podcast player Innovation Quote “Innovation distinguishes between a leader and a follower.”  – Steve Jobs Application Questions How could you identify the “coveted condition” that your product helps customers achieve? What specific aspirational state does your product enable, and how might you redesign your development and marketing approach to emphasize this transformation? Where in your current product development process could you integrate marketing thinking earlier? What specific changes to your team structure, meeting cadence, or decision-making process would help bridge the gap between engineering and marketing perspectives? Consider the CLIMB framework (functional, emotional, transformative, and transcendent needs). Which levels does your product currently address? How could your team elevate your product to address higher-level needs that might trigger stronger emotional connections? How could your team apply the 10X better rule to your current product roadmap? Which aspects of your product could realistically be made dramatically better in ways that matter emotionally to customers, rather than pursuing incremental improvements across many features? Where could you enhance the perception of craftsmanship in your product? What specific details could you improve to signal quality and care to customers, and how might you better showcase the expertise and intentionality behind your product’s development? Bio Laurier Mandin is a product marketing strategist and go-to-market expert who has guided hundreds of innovative products to market success. As founder and CEO of Graphos Product, he brings over three decades of expertise in helping product makers identify and penetrate resistant markets through visionary positioning and strategy.  Laurier developed the company’s proprietary CLIMB scoring system and Innovative Product Go-to-Market Roadmap process, which have become trusted frameworks for reducing launch risk and maximizing product success. His strategic insights have transformed struggling products into category leaders and helped numerous B2B and consumer innovations achieve breakthrough market performance.  A recognized thought leader in product marketing, Laurier is the author of “I Need That” and creator of the Product Knowledge podcast as well as an award-winning business columnist. When not working with clients to craft winning product strategies, he can be found cycling, cross-country skiing, hiking or enjoying paddle sports in his local community.  Thanks! Thank you for taking the journey to product mastery and learning with me from the successes and failures of product innovators, managers, and developers. If you enjoyed the discussion, help out a fellow product manager by sharing it using the social media buttons you see below. Source

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 phase transforms insights into action. When I work with product teams, I often see an overemphasis on the “during” phase – selecting cool activities or techniques – while neglecting thoughtful preparation and consistent follow-up. Alison’s framework provides a more balanced approach. For product managers, this three-part process applies to various collaborative scenarios: Customer journey mapping sessions Feature prioritization workshops Roadmap planning meetings Retrospectives and lessons-learned reviews Cross-functional problem-solving sessions By treating each phase with equal importance, you significantly increase the likelihood that your collaborative efforts will produce meaningful results rather than just generating ideas that never see implementation. Starting with the End in Mind When preparing your workshop, rather than starting with activities or exercises, Alison advised beginning with what happens after the workshop ends. Imagine yourself at the end of the workshop. What results did you get? What did you achieve? This approach resembles the “pre-mortem” technique I often use with product teams. While a post-mortem analyzes what went wrong after a project ends, a pre-mortem imagines potential failures before you begin. Alison’s method takes this concept further by envisioning success and working backward. Here’s how product managers can apply this approach: Envision successful implementation: Picture your team three months after the workshop. What specific changes have occurred? What decisions have been implemented? How has your product development process improved? Identify necessary outputs: Based on your vision of success, determine what tangible deliverables the workshop needs to produce. These might include prioritized feature lists, customer journey maps, or action plans with clear ownership. Research context thoroughly: Understanding team dynamics and project history represents about 50-60% of effective workshop planning. Connect with key stakeholders: Conduct one-on-one conversations with participants before the workshop to understand their perspectives, concerns, and desired outcomes. This approach transforms workshops from isolated events into strategic inflection points in your product development process. By starting with the end in mind, you ensure that every activity and discussion directly contributes to tangible progress rather than just generating ideas that never see implementation. Designing an Effective Workshop Once you’ve envisioned what success looks like after your workshop, Alison recommended a structured approach to designing the session itself. This process helps product managers move beyond generic brainstorming to create truly purposeful collaborative experiences. Alison outlined key steps that form the backbone of effective workshop design: 1. Identify Clear Purpose and Outcomes Begin with a concise statement of why you’re bringing people together and what you intend to achieve. For product managers, this might be “Align on our Q3 roadmap priorities” or “Identify the top customer pain points to address in our next release.” 2. Determine Tangible Outputs Define the specific deliverables you need the workshop to produce. These tangible outputs should directly support your post-workshop implementation plan. Examples include: Prioritized feature list with effort/impact estimates Refined user personas with key insights Journey maps highlighting critical moments Decision matrix for evaluating options 3. Brainstorm Essential Questions Instead of jumping to activities, Alison suggested brainstorming all the questions you need answered during the session. This question-based approach focuses on curiosity rather than predetermined outcomes. 4. Design Agenda Based on Questions Structure your agenda to address these questions in a logical flow. This ensures your workshop tackles the right problems in the right order. 5. Select Appropriate Activities Only now should you select specific exercises and techniques that will help answer your essential questions and produce your desired outputs. This methodical approach prevents a common pitfall I’ve observed in product teams—choosing workshop activities because they seem fun or trendy rather than because they serve your specific purpose. By following Alison’s process, you create workshops that deliver meaningful results rather than just generating temporary enthusiasm. Facilitation During the Workshop Even the best-planned workshop agenda must be held lightly. When facilitating product team sessions, you’ll need to adapt to the dynamics that emerge once everyone is in the room together. Setting the Tone Alison recommended starting workshops with an interactive exercise that signals “this isn’t a normal meeting.” These opening activities establish psychological safety and participation norms that carry through the entire session. Foundational Facilitation Techniques Alison shared several foundational techniques that she frequently includes in workshops. Breakout discussions: split into smaller groups for more intimate discussions. Individual reflection: Provide time for people to think about a question individually before discussing it. The Cycle of Facilitation Alison broke down effective facilitation into a repeating four-part cycle that product managers can master: Asking questions: Pose clear, thoughtful questions that drive toward your workshop goals. Active listening: Pay close attention to responses, watching for both verbal and non-verbal cues. Managing discomfort and chaos: Get comfortable with the messiness of divergent thinking. Synthesizing insights: Connect ideas and identify patterns to move the group forward. This cycle repeats throughout your workshop as you guide participants through different activities and discussions. For product managers, effective facilitation is about creating the conditions where your team’s collective intelligence can emerge. By mastering these techniques, you’ll transform unproductive debates into collaborative problem-solving that drives your product forward. The Facilitator’s Role The Advantage of Not Being the Expert As product managers, we often feel pressure to be the domain experts, but this can actually hinder effective workshop facilitation. Alison explained that she has successfully facilitated workshops in industries where she had no specific expertise—finance, pharmaceuticals, energy—precisely because her outsider perspective allowed her to: Ask basic questions that insiders might avoid Notice when discussions become too detailed or technical Pull the group back to higher-level objectives Help participants explain concepts in clearer terms While evolutionary improvements may benefit from deep domain knowledge, revolutionary innovation often requires fresh thinking unencumbered by the way things have always been done. Separating Facilitation from Content A subject-matter expert acting as a facilitator may have difficulty separating the needs of the group from their own preconceived ideas about what the workshop’s outcomes should be. For product managers, this means making a conscious choice before each workshop: Will you participate as a content contributor, or will you focus on facilitating the process? Trying to do both simultaneously often leads to suboptimal results in both roles. Facilitator as Process Guide As a facilitator, your primary responsibility is to keep your eyes on the process level: Is the team headed in the right direction? Are we getting into too much detail? Are we managing time effectively? Is everyone contributing? By focusing on these process questions rather than content details, you create space for your team’s collective expertise to emerge in ways that a single expert’s perspective never could. Physical Workshop Environment The environment of a workshop sends powerful signals about the type of interaction expected. Walking into a properly set up workshop space immediately communicates “this is different from a normal meeting.” Key elements can include: Post-it notes arranged on tables Flip charts positioned around the room Different seating arrangement from standard meetings Visible thinking tools and workshop materials These visual cues prime participants to engage differently from how they would in routine meetings. Dynamic Movement and Interaction Effective workshops should feel physically dynamic. Participants should: Get up and move around the room Interact with different team members Physically manipulate ideas (moving post-its, drawing on boards) Stand together while discussing concepts Research shows that standing meetings can be more productive because they engage participants physically as well as mentally. Choreographing the Workshop Space Alison thinks about the choreography of a workshop, viewing the room as a canvas for collaboration. She likes to get an image of what the workshop room looks like beforehand, so she can start planning the physical setup of the workshop. For product managers, this might mean planning specific areas for customer journey mapping, another for prioritization exercises, and separate spaces for small group discussions. This intentional use of space helps guide the energy and focus of your team throughout the workshop. Following Through Post-Workshop The excitement of a productive workshop often creates momentum that quickly dissipates once participants return to their daily responsibilities. Designing for Implementation Successful follow-through begins during the planning phase, not after the workshop ends: When designing your workshop, clearly define the specific outputs needed for implementation Create templates and frameworks that make post-workshop action straightforward Assign ownership for follow-up tasks before the workshop concludes Schedule check-in meetings to review progress on workshop outcomes The Reality of Behavior Change Workshops often aim to change behaviors and working relationships. Alison explained that behavior change does not happen overnight. Workshop culture involves the workshops themselves and the work afterward to make sure changes stick. For product managers, this means viewing workshops as catalysts within a longer transformation journey rather than one-time solutions. Persistent Follow-Up Effective post-workshop implementation requires: Regular check-ins with participants Revisiting key conversations and decisions Potentially scheduling follow-up workshops to continue progress Consistent reinforcement of new collaborative behaviors This persistent attention to implementation is what distinguishes workshops that create lasting impact from those that generate only temporary enthusiasm. For product teams, this might mean incorporating workshop outputs into sprint planning, creating visible artifacts that remind the team of decisions made, or establishing new rituals that reinforce workshop outcomes. Real-World Example: Creative Agency Transformation To illustrate how workshop culture transforms organizations, Alison shared a case study from her consulting work. She described a creative agency with ambitious growth goals that struggled with departmental silos despite producing high-quality work. Breaking Down Silos The agency’s challenge was familiar: Departments worked effectively in isolation but rarely collaborated across boundaries. Their meetings were primarily transactional, focusing on immediate deliverables rather than strategic thinking or innovation. Alison’s approach involved: Bringing teams together in regular workshop settings Facilitating conversations they wouldn’t normally have Moving beyond transactional interactions to forward-looking discussions Creating space for big-picture thinking and creative collaboration A Framework for Team Development Alison implemented a structured framework to guide the agency’s transformation: Framework Stage Focus Area Workshop Purpose Alignment Shared vision Creating clarity on collective direction and success metrics Cohesion Role clarity Understanding how individual contributions connect to the bigger picture This methodical approach helped team members see beyond their departmental boundaries and understand how their work contributed to the organization’s larger goals. Measuring Success The transformation became evident when team members began saying, “We need to run more of our meetings like these workshops.” This shift in mindset indicated they had recognized the value of structured collaboration not just in special sessions but in their everyday work. For product managers, this case study demonstrates how workshop culture can transform siloed product development into true cross-functional collaboration. By creating structured opportunities for alignment and cohesion, you can break down the barriers that often separate product, engineering, design, and business teams. Conclusion Workshop culture offers product managers a framework for transforming how teams collaborate and solve problems. As Alison explained, it’s not about running constant workshops but about applying workshop principles to everyday work: starting with the end in mind, creating space for diverse thinking styles, facilitating effectively without dominating, and following through persistently. These practices help break down the silos that often impede product innovation. If you’re looking to improve cross-functional collaboration and drive more effective product decisions, consider how you might implement these workshop principles in your next meeting or problem-solving session. Small changes in how you approach collaboration can yield significant improvements in both team dynamics and product outcomes. Useful Links Check out Alison’s book, Workshop Culture: A Guide to Building Teams That Thrive Connect with Alison on LinkedIn Learn more about Bracket Creative Innovation Quote “Leaders encourage and support the individuals in those groups because they are the source of ideas that constitute the raw material of innovation. Yet the ultimate innovation will almost always be a collective outcome, something devised through group interaction.” – Linda Hill, Collective Genius Application Questions How could you adapt your current product planning meetings to incorporate workshop culture principles? Which specific meeting would benefit most from being redesigned as a workshop? When facilitating cross-functional collaboration, how could you better balance the needs of both introverted and extroverted team members? What specific techniques might you implement in your next product discovery session? Think about your last product workshop or collaborative session that didn’t lead to effective implementation. How could you have designed it differently, starting with the end in mind? What specific post-workshop mechanisms could you put in place for your next session? How could your team apply the concept of “workshop choreography” to your physical or virtual workspace? What signals or environmental changes could help transition your regular meetings into more collaborative problem-solving sessions? Consider the tension between individual contributions and collective outcomes in your product development process. How could you structure your next feature prioritization or roadmap planning session to better harness both individual creativity and collective wisdom? Bio Alison Coward is the founder of Bracket, a consultancy that partners with ambitious, forward-thinking companies to help them build high-performing team cultures. She is a team culture coach, workshop facilitator, trainer, keynote speaker and author of “Workshop Culture: a guide to building teams that thrive” and “A Pocket Guide to Effective Workshops”. Clients include: Google, Meta, Wellcome and the V&A. With 20 years’ experience working in, leading and facilitating creative teams, Alison is passionate about finding the balance between creativity, productivity and collaboration so that teams can thrive and do their best work together.  Thanks! Thank you for taking the journey to product mastery and learning with me from the successes and failures of product innovators, managers, and developers. If you enjoyed the discussion, help out a fellow product manager by sharing it using the social media buttons you see below. Source

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 confuse users. AI accelerates this process, allowing teams to get clarity on user experiences sooner and save significant time and money during development. AI Application Value for Product Professionals Brainstorming partner Overcomes creative blocks and inertia Idea validation Tests concepts quickly without scheduling meetings Prototyping assistance Accelerates creation of user interfaces and workflows No-code development Allows faster proof-of-concept creation Design iteration Enables rapid exploration of alternative approaches AI-Enhanced Product Management Platforms The integration of AI into existing product management tools represents a significant opportunity for enhancing team effectiveness. ProdPad, one of the more popular platforms for managing product management work, and many competitors, have recently added AI capabilities—currently called Co-pilot—to their toolkit. What makes these integrated platforms valuable is their ability to serve as a central repository for product information. They help teams maintain alignment with overall strategy, track progress toward objectives, and understand user stories. With AI enhancement, these platforms can now help identify gaps in strategy alignment, surface unmet customer needs based on existing data, and answer questions from stakeholders outside the immediate product team. Matt and I discussed an important consideration when choosing AI solutions: whether to invest in specialized AI products or use general-purpose AI with custom prompts. Many specialized tools are essentially using the same large language models as ChatGPT but with carefully engineered prompts and workflows tailored to specific use cases. For organizations making these decisions, Matt shared insights from his experience co-leading AI initiatives at his law firm. They’ve taken a tiered approach, using one solid general-purpose language model for most applications while investing in legal-specific AI products for their revenue-generating lawyers. For highly specific tactical use cases, they evaluate additional specialized tools—but only when the return on investment justifies the significant cost. AI Tool Approach Pros Cons General-purpose AI (e.g., ChatGPT, Claude) Lower cost, versatility, continuous updates May require custom prompt engineering, less specialized Industry-specific AI solutions Optimized for domain-specific knowledge and workflows Higher cost, potential duplication of capabilities Integrated platform with AI features Seamless workflow integration, centralized data May have less advanced AI capabilities than specialized tools Custom-built internal AI tools Precisely tailored to organization’s needs Resource-intensive to develop and maintain Matt emphasized that the bar should be high for investing in specialized products when general tools can accomplish 90% of the required tasks. Organizations must consider whether the additional 10% improvement justifies spending five to six figures on multiple specialized tools, which could quickly add up to a million-dollar investment. Workflow integration is important for successful AI implementation. Matt provided an example: if an organization has employees manually uploading invoices to ChatGPT, extracting data, and re-entering it into systems, they’re missing efficiency opportunities. The real value comes from automating these workflows to minimize manual steps. Implementation Focus Key Considerations Model Selection Balance between general and specialized capabilities Integration Level How seamlessly AI fits into existing workflows Data Strategy What information AI can access to maximize value ROI Analysis Justification for specialized AI investments User Adoption Support for different user groups based on needs Matt also reflected on the current state of AI capabilities. He noted that today’s models are becoming so robust that it’s increasingly difficult to find use cases they can’t handle, at least for English language applications. This growing general applicability raises the bar for specialized solutions to prove their value. We briefly touched on the debate around artificial general intelligence (AGI), acknowledging that while the term itself may be somewhat ambiguous, the general applicability of today’s AI tools is already impressive. This evolution has significant implications for how organizations approach their AI strategy, suggesting that for many use cases, the focus should be on integration and workflow rather than pursuing incrementally more powerful specialized models. Addressing AI Challenges and Concerns Implementing AI in product development isn’t without challenges. Matt and I explored several concerns that organizations must address to effectively leverage these tools. We discussed the potential impact on professional development, particularly in apprenticeship-model professions. If senior staff rely on AI instead of junior team members for certain tasks, how will those juniors develop expertise? Matt raised this concern for lawyers and software developers, and we discussed its relevance for product management as well. However, we identified a potential upside: AI could handle routine tasks that would previously occupy junior employees’ time, freeing them to engage in higher-value learning experiences. By eliminating basic tasks like fixing simple coding errors or catching obvious document mistakes, AI might actually create more meaningful mentorship opportunities focused on strategic thinking and core professional skills. Product managers should be aware of risks of AI hallucinations AI hallucinations—where models generate plausible but incorrect information—remain a persistent challenge despite recent improvements. I shared a personal experience using AI to analyze a detailed lease agreement. While the AI successfully identified unfavorable clauses and accurately referenced their location in the document, I was initially concerned it might fabricate issues. In other contexts, I’ve frequently encountered hallucinations where AI adds information not present in the source material. Both hallucinations and omissions pose serious risks, particularly in contexts like legal work. Matt’s firm strongly advises lawyers to verify all AI outputs, treating them as they would work from a junior associate. As Matt put it, the AI is like “a first-year associate that doesn’t sleep and is always there,” but still requires careful review. Type of AI Error Risk Mitigation Strategy Hallucination Introducing incorrect information Verify all outputs against source material Omission Missing critical information Verify outputs and use multiple prompts to ensure comprehensive analysis Misinterpretation Drawing incorrect conclusions Apply domain expertise to evaluate outputs Over-confidence Presenting speculation as fact Require citation of sources for key claims For organizations implementing AI, establishing appropriate guardrails is essential. Matt described how his firm has developed policies that provide guidance without outright prohibiting most AI use cases. They focus on education about appropriate usage contexts, data confidentiality protections, and verification requirements, creating a balanced approach that manages risks while capturing benefits. AI Adoption in Risk-Averse Industries The legal profession offers insights into how AI transforms traditionally cautious industries. As a product management professional, I pay special attention to adoption patterns in risk-averse sectors—when they embrace new technology, it often signals well-established value and manageable risks. Matt shared a progression of attitudes toward AI within law firms over the past two years. Initially, many leaders experienced fear about AI’s potential to disrupt their profession. This concern was both practical and financial: AI tools represented a significant investment while potentially reducing billable hours by increasing efficiency—a challenging value proposition in an hourly billing model. Over time, with education and exposure, these perspectives evolved into more nuanced views. Today, many firms, including Matt’s, are bullish on AI’s capabilities within appropriate boundaries. Some see it as a competitive differentiator, while others pursue AI implementation to avoid falling behind competitors. The adoption curve among individual lawyers follows patterns familiar to any technology implementation. Matt observed that his organization has moved beyond early adopters and is now entering the early majority phase. While some users try AI briefly before abandoning it, those who integrate it into their workflow show steadily increasing usage over time. AI Use Case in Legal Description Value Content summarization Condensing contracts, briefs, proceedings, and statutes Saves time on document review Synthesis Combining information from multiple sources Creates comprehensive understanding Drafting assistance Generating initial document drafts Accelerates document preparation Strategy brainstorming Exploring alternative approaches and counterarguments Enhances case preparation Provision analysis Identifying favorable/unfavorable contract terms Improves negotiation position What particularly impressed Matt after 25 years in the AI space was how dramatically the technology has evolved. The systems he worked with 15 years ago were fragile, expensive, rules-based, and easily broken when applied to adjacent use cases. Today’s models understand language nuance, adapt to specialized terminology, and apply reasoning to novel situations—capabilities previously thought to require years more development. For product managers serving risk-averse industries, this evolution suggests several insights: emphasize verification and human oversight in your AI implementation, focus on specific high-value use cases with clear ROI, and recognize that resistance often transforms into enthusiasm as users experience benefits firsthand. The legal industry’s journey provides a roadmap for introducing AI into other conservative sectors, from healthcare and finance to government and education. The Future of AI in Product Management The most successful AI implementations in product management will be those that seamlessly integrate into existing workflows. Matt and I agreed that transparent integration represents the next frontier for AI tools, moving beyond standalone applications to become embedded features within the systems product teams already use. This parallels our experience at LexisNexis, where we worked together on a product that integrated new capabilities without requiring users to change their behavior. I expect platforms like ProdPad to succeed by making AI assistance transparent and aligned with users’ natural work patterns. By contrast, Microsoft’s Copilot approach in Office applications often feels disconnected from the actual workflow. As I mentioned to Matt, I frequently close the Copilot prompt when opening Word because it feels like an extra step that interrupts my process rather than enhancing it. Our conversation also touched on recent developments in AI democratization. We discussed Deep Seek, which enables running sophisticated AI models on relatively inexpensive hardware—from Raspberry Pi devices to modest servers. This trend capability allows organizations concerned about data privacy and security to maintain complete control over their AI systems and data. Matt predicted this will lead to a bifurcated market: cutting-edge models will continue to require substantial computing resources, while slightly older generations will become commoditized and available for edge computing applications. He envisioned an “AIOT” (AI + Internet of Things) future where smart devices incorporate local AI processing. Future AI Trend Impact on Product Management Workflow integration Reduced friction in adoption and usage Local AI models Enhanced data privacy and security control Edge computing AI New product possibilities with embedded intelligence Democratized access More accessible AI for smaller teams and organizations Specialized fine-tuning Tailored models for specific product domains Beyond technical advancements, Matt expressed enthusiasm about AI’s potential social impact. He’s personally focused on applying AI to health and climate challenges. He noted that while large pharmaceutical companies are exploring AI applications, there’s tremendous untapped potential for nonprofits, NGOs, and small mission-driven organizations to leverage these tools. This social dimension presents an opportunity for product managers to apply their skills beyond traditional business contexts. As AI becomes more accessible, product professionals can help mission-driven organizations integrate these capabilities into their workflows, potentially creating outsized impact through enhanced efficiency and effectiveness in addressing critical social challenges. Key Insights for Product Managers Throughout our conversation, several actionable insights emerged that product managers can apply immediately to their work with AI. We discussed the need to reframe executive demands for adding AI into customer-focused questions. Matt and I both encountered situations where leadership teams push for AI integration without clarity about the specific value it will provide. Too often, senior executives make broad statements like “we need to add AI to what we’re doing” without understanding what that actually means for products or customers. As product professionals, our responsibility is to translate these directives into customer-oriented questions: How can we enhance our product’s value using AI to solve problems customers actually care about? Will AI help solve these problems faster, better, or more comprehensively? This reframing helps ensure AI serves genuine customer needs rather than becoming a superficial feature. Another opportunity Matt highlighted was AI’s ability to process unstructured data. He noted how frequently we encounter friction in our daily lives—retyping information into forms or manually extracting data from documents only to re-enter it elsewhere. These pain points represent prime opportunities for AI-enhanced products. Customer Pain Point AI Application Opportunity Form completion Auto-extraction of information from existing documents Data transcription Converting formats without manual retyping Information synthesis Combining data from multiple sources automatically Content transformation Converting between visual and text formats Pattern recognition Identifying trends in unstructured information Matt shared personal examples of AI’s potential, including using it to solve scientific puzzles from Scientific American and helping his daughter understand idioms in her schoolwork. These seemingly simple applications demonstrate how AI can remove friction points that we’ve previously accepted as unavoidable. Conclusion The integration of AI into product management isn’t just a passing trend—it’s fundamentally transforming how we research customer needs, prototype solutions, and create value. AI has evolved from a specialized, experimental technology to an essential tool in the product manager’s toolkit. The question is no longer whether to incorporate AI into product development processes, but how to do so most effectively. As you incorporate AI into your product management practice, remember that the technology itself is just a tool. The true value comes from how you apply it to understand customer needs, solve meaningful problems, and create products that improve people’s lives. By focusing on these fundamentals while embracing AI’s capabilities, you’ll be well-positioned to thrive in this new era of product innovation. Useful Links Connect with Matt on LinkedIn Learn more about Matt’s mission-based organization, 10 Billion Ventures Innovation Quotes  “The best way to predict the future is to create it.” – attributed to Alan Kay and Peter Drucker  “The way to get started is to quit talking and begin doing.” – Walt Disney Application Questions How could you integrate AI as a brainstorming partner in your current product development process? What specific activities (customer research, feature ideation, user story creation) might benefit most from this partnership approach? In what ways could your team use AI to accelerate prototyping without sacrificing quality? How might this change your current approach to validating product concepts before full development? How could you transform executive requests to “add AI” into customer-focused initiatives? What specific customer problems in your product area could AI help solve more effectively? How could your organization balance investment in specialized AI tools versus leveraging general-purpose AI models with custom prompts? What ROI metrics would you use to make these decisions? How could you ensure AI integration enhances rather than disrupts your existing product workflows? What would seamless integration look like for your specific product and team? Bio Matt Coatney is a seasoned C-level AI and product executive with 25 years of diverse experience. His expertise includes: artificial intelligence, business growth, and product development. Matt has also supported a wide range of industries such as manufacturing, media, law, life sciences, government, and finance. His client list includes some of the largest, most well-known organizations in the world, including Microsoft, IBM, the Bill and Melinda Gates Foundation, Pfizer, Deloitte, HP, and the US government. Matt writes and speaks frequently on technology and product topics. In addition to a TED talk and keynotes, his work has been published by MIT, HarperCollins, and O’Reilly and has appeared in books, journals, and international conferences. Matt’s latest book is The Human Cloud: How Today’s Changemakers Use Artificial Intelligence and the Freelance Economy to Transform Work, with Matthew Mottola. Thanks! Thank you for taking the journey to product mastery and learning with me from the successes and failures of product innovators, managers, and developers. If you enjoyed the discussion, help out a fellow product manager by sharing it using the social media buttons you see below. Source

In a captivating discussion, Elizabeth Samara-Rubio, Chief Business Officer at SiMa.ai, shares her journey from product management to senior leadership, drawing from her experiences at HP and AWS. She emphasizes the importance of a clear vision and data-driven decision-making in leadership. Elizabeth discusses the potential of Edge AI, illustrating its benefits in privacy and cost savings. She also provides valuable insights for aspiring leaders on embracing calculated risks and fostering a culture of innovation to create lasting customer value.

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 described several experiments they conducted to validate the effectiveness of their AI approach. Experimental Approach One of their key experiments involved a blind testing methodology. They took authentic customer needs statements from previous VOC studies conducted by human analysts and mixed them with needs statements that the AI had generated. Then, they asked experienced human analysts to evaluate all the statements without knowing which were AI-generated and which were human-generated. The analysts evaluated each statement based on several criteria: Clarity – Was the need clearly articulated? Articulation quality – Was it well-expressed and understandable? Absence of hallucination – Was there any evidence of the AI inserting details that weren’t actually present in the customer data? Authenticity – How true was the need to what customers actually said? Surprising Results In these blind tests, the AI-generated needs statements performed just as well as—and in some cases better than—those crafted by human analysts. Key Benefits of AI-Powered Analysis Through these experiments, Carmel and her team identified several significant advantages of using AI for VOC research: BenefitDescriptionImpact on Product TeamsSpeedSignificantly accelerates the rate of gathering customer needsMore rapid product discovery and development cyclesVolume capacityNo practical limit on the amount of data that can be analyzedMore comprehensive understanding of customer needsMultiple data sourcesCan simultaneously analyze interviews, social media, forums, call center dataRicher, more diverse insights from various customer touchpointsReduced fatigueAI doesn’t experience the mental fatigue that affects human analystsConsistent quality throughout large datasetsReduced biasLess likely to have preconceived notions about what should be foundMore objective insights, potentially uncovering unexpected needs This last point about reduced bias is particularly important. As product managers, we sometimes unconsciously look for evidence that confirms our existing assumptions about customer needs or product direction. An AI system, properly implemented, doesn’t have these same motivations—it simply reports what it finds in the data. These benefits combine to create a more robust database of customer needs, which serves as the foundation for effective product innovation. The faster a product team can build this comprehensive understanding of customer needs, the more quickly they can move into solution development with confidence. AI’s Ability to Capture Emotional Needs One of the most surprising findings from AMS’s research was how effectively AI could identify emotion-infused customer needs. This discovery challenged a common assumption that machines would struggle with the emotional aspects of customer research due to their lack of human empathy. Why AI Excels at Finding Emotional Needs Humans conducting customer research are often unconsciously biased toward functional needs. As product professionals, we’re trained to identify problems and create solutions. We get rewarded professionally for finding practical issues that can be addressed with concrete features or improvements. This solution-oriented mindset can cause us to quickly move from emotional needs to functional needs to potential solutions. It’s simply how our professional brains are wired. AI, however, doesn’t have this bias. It gives equal weight to functional and emotional needs in customer data because it isn’t influenced by the pressure to jump to solutions. This creates a unique advantage in identifying the full spectrum of customer needs. Case Study: Wood Stains Category In analyzing customer feedback about staining furniture and wood products, the AI identified an emotional need that human analysts completely overlooked: Customers wanted “a manufacturer that values my feedback, will respond to my emails, and will address my concerns.” Human analysts had dismissed this as a generic desire that everyone would have, not recognizing it as a core need specific to this category. However, this need is particularly important for wood staining projects because customers often encounter problems and need responsive manufacturer support. The AI, without bias toward “important” functional needs, recognized this emotional need as significant based purely on the data. The Competitive Value of Emotional Needs There are three dimensions to any customer job: Functional – The obvious practical outcome the customer wants to achieve Emotional – How they want to feel (or avoid feeling) during and after the job Social – How they want to be perceived by others While functional needs are often the easiest to identify and address, emotional needs frequently drive purchasing decisions and brand loyalty. A product that connects strongly with customers’ emotional needs will typically outperform one that only addresses functional requirements. Even in highly functional categories like home heating and cooling systems, emotional needs like “feeling like a responsible homeowner” or “not feeling like I’m throwing money down the drain” are important to customer satisfaction. By leveraging AI to help identify these often-overlooked emotional needs, product teams can develop more holistic solutions that connect with customers on multiple levels, creating stronger competitive advantages. The Human-AI Partnership in VOC Research While the results from AI-powered analysis are impressive, Carmel emphasized that the most effective approach is using AI as a copilot rather than a complete replacement for human researchers. This partnership model leverages the strengths of both human expertise and AI capabilities to produce superior results. AI as a Copilot During our conversation, Carmel described how she views the relationship between human analysts and AI tools. The AI will find many things that humans overlook, but humans will also identify aspects that AI might miss. It’s similar to having two different analysts review the same data—each will notice different things. This copilot perspective emphasizes collaboration rather than replacement. Quantifiable Advantages of the Hybrid Approach The partnership between human researchers and AI creates measurable benefits for product teams. In their experiments, AMS examined the overlap between needs identified by humans and those identified by AI, creating a Venn diagram of findings. The results were eye-opening: When examining just the unique needs (those found by only one method), AI identified twice as many unique needs as human analysts AI didn’t suffer from the “I already heard that” fatigue that affects humans reviewing large datasets AI excelled at finding that “one new piece of data in a mountain of data” that might otherwise be missed These niche needs—ones that might be mentioned infrequently in customer feedback—are opportunities for innovation. As Carmel pointed out, the frequency with which a need is mentioned doesn’t necessarily correlate with its importance. Sometimes, these rarely mentioned needs represent the greatest opportunities for competitive differentiation. Case Study: Finding New Insights in Mature Industries To illustrate how the human-AI partnership can unlock unexpected value, Carmel shared an example from the snowplow industry. She worked with a client who had been in the snowplow and snow equipment business for 20 years—a veteran who deeply understood the industry. Initially, she wondered what new insights they could possibly discover for someone with such extensive experience. However, through their research process, they uncovered insights about visibility issues—specifically, that snowplows often have the worst visibility precisely when they need it most. These insights weren’t obvious even to industry experts, but they represented significant innovation opportunities. The client had never thought to ask certain questions, but the AI-augmented research process helped uncover these hidden needs. Breaking Through Subject Matter Expert Limitations AI-powered research can help overcome the limitations that come with deep domain expertise. When we’re very familiar with an industry, product, or customer base, we often make assumptions that limit our perspective. We might believe we’re in a commodity space or that we already understand all customer needs. In these situations, an outside perspective is valuable. Traditionally, this might come from new team members who aren’t constrained by industry conventions. Now, AI tools can provide a similar fresh perspective, almost like bringing in a consultant who specializes in finding customer needs across many different categories and can apply that expertise to your specific domain. Limitations of AI in VOC Research Despite the impressive capabilities of AI in VOC research, it’s important for product teams to understand its current limitations. During our conversation, Carmel highlighted several areas where human judgment and expertise remain essential. Equal Weighting of Data Sources One significant limitation is that AI algorithms like large language models tend to treat all data sources with equal weight. As Carmel explained, these tools currently can’t make sophisticated judgments about the relative validity or reliability of different data sources they analyze. This means that human expertise is still necessary for: Determining which data sources are worthy of the AI’s attention Evaluating the quality of inputs the AI is analyzing Deciding how much weight to give various pieces of feedback The AI is only as good as the data provided to it, so human selection and curation of input data is critical. The Continued Value of Direct Customer Conversations There’s still no substitute for real, live conversations with customers. While AI can extract tremendous value from interview transcripts and written feedback, direct customer interactions provide benefits that go beyond data collection: Benefit of Direct Customer InteractionWhy AI Can’t Replace ThisBuilding genuine customer empathyEmotional understanding comes from person-to-person connectionCapturing non-verbal cuesCurrent AI tools don’t analyze body language or vocal toneAsking follow-up questions in real-timeAI can’t yet dynamically probe based on subtle conversational cuesDeveloping organizational compassionTeams need direct exposure to customer challenges These human-to-human interactions develop deeper understanding within product teams that purely AI-mediated research might miss. The ideal approach combines direct customer conversations with AI-powered analysis of the resulting data. Prioritization Challenges Carmel also noted that AI currently can’t prioritize needs for innovation effectively. While AI excels at identifying the full spectrum of customer needs, it doesn’t yet have the capability to determine which of those needs represent the most valuable opportunities. The AI can identify all the needs that should go into a prioritization survey (what AMS calls “secondary needs”), but product teams still need to: Conduct surveys or other customer research to prioritize these needs Identify which needs are most important to customers Determine which needs are currently unmet or poorly met Decide which needs represent the best innovation opportunities This final step of prioritizing where to focus innovation efforts remains a human-driven process that requires business judgment, market understanding, and strategic thinking. Balancing AI Capabilities with Human Expertise Understanding these limitations helps product teams use AI tools more effectively. Rather than seeing AI as a complete replacement for traditional customer research methods, the most successful approach treats AI as one powerful tool in the product manager’s toolkit. By being realistic about what AI can and can’t currently do, product teams can design research processes that leverage the strengths of both AI analysis and human expertise, creating more comprehensive customer insights than either could achieve alone. Integrating AI into the Product Innovation Process With an understanding of both the capabilities and limitations of AI in VOC research, the next question becomes how product teams can effectively incorporate these tools into their innovation processes. Carmel shared several practical insights on this topic during our conversation. AI Throughout the Innovation Funnel Carmel described AI as providing product teams with “different lenses” to view customer needs. Unlike traditional research projects that often require extensive planning and formal structure, AI-powered approaches offer more agility and flexibility. Product teams can leverage AI at multiple stages of the innovation funnel: Innovation StageAI ApplicationBenefitsEarly discoveryBroadly identify customer needs across multiple data sourcesComprehensive understanding of the problem spaceFocus area explorationDig deeper into specific need areas identified as prioritiesRicher understanding of core underlying needsConcept testingAnalyze feedback on early conceptsRapid iteration based on customer responsesLater-stage validationVerify that solutions address original needsEnsuring alignment between solutions and customer needs Most Useful Application: Beginning of Innovation While AI can provide value throughout the innovation process, Carmel emphasized that its most useful application is at the very beginning—the discovery phase where teams are trying to understand the landscape of customer needs before diving into solutions. This aligns with best practices in product management, where thorough understanding of customer problems should precede solution development. AI can help product teams build this foundation more quickly and comprehensively than traditional methods alone. Filling Gaps in the Process AI can fill gaps when the ideal innovation process hasn’t been followed. In practice, product development doesn’t always follow a perfect linear path: Sometimes teams jump directly to solutions without thorough needs identification Sometimes they develop concepts first, then try to determine the right messaging Sometimes they’re already far along in development when they realize they need to verify customer needs In these situations, AI can quickly analyze customer data to ensure teams haven’t missed anything foundational before proceeding to later stages. The speed and efficiency of AI analysis makes it a highly agile tool for course correction. Broadening Innovation Horizons Another benefit of integrating AI into the product innovation process is how it can help teams break out of established patterns of thinking. By identifying needs that might be overlooked in conventional analysis, AI can point product teams toward unexpected innovation opportunities. This is particularly valuable in mature product categories or for teams working with products they’ve managed for a long time. The AI can help challenge assumptions and reveal new possibilities that might not have been considered. Practical Implementation of AI-Powered VOC Understanding the potential of AI in VOC research is one thing, but knowing how to practically implement these tools is another challenge entirely. During our conversation, Carmel provided insights into how product teams can begin leveraging these capabilities today. Current State: Client Service Model Currently, AMS is offering AI-powered VOC as a service to their clients. This approach allows product teams to benefit from advanced AI analysis without needing to develop the expertise or tools internally. Carmel explained that their goal is to help clients get insights faster and more efficiently than ever before. This service model makes sense given the specialized nature of the AI tools being used. The large language models employed by AMS have been fine-tuned with supervised learning based on 1,500 carefully selected customer needs from multiple case studies. This specialized training creates AI systems that are specifically optimized for VOC research rather than general-purpose AI. Benefits for Product Teams Implementing AI-powered VOC research, whether through a service provider like AMS or eventually through internal capabilities, offers several practical benefits for product teams: BenefitReal-World ImpactAccelerated insightsReducing research timelines from weeks to daysMore comprehensive analysisIdentifying needs that would be missed in traditional analysisGreater agilityAbility to quickly adapt research focus as project needs evolveBetter resource allocationFreeing up human analysts for higher-value strategic workCross-source integrationCombining insights from interviews, social media, support tickets, etc. Tailoring Implementation to Product Complexity Carmel noted that the level of detail needed from AI-powered analysis varies based on the complexity of the product and its development stage. Not all products require the same depth of customer needs exploration: Higher complexity products may need comprehensive needs identification Products already in development might need targeted analysis to verify assumptions Products nearing launch might need focused research on messaging alignment with needs The flexibility of AI-powered approaches allows teams to adjust the scope and depth of analysis to match their specific situation, making this a highly adaptable tool for diverse product development contexts. Conclusion The integration of AI into Voice of the Customer research represents a significant advancement for product teams seeking to better understand and address customer needs. These tools aren’t replacing human researchers but rather enhancing their capabilities, helping teams discover more customer needs—particularly emotional ones—faster and more comprehensively than traditional methods alone. The ability to process diverse data sources without fatigue or bias opens new possibilities for innovation, especially in mature product categories where fresh insights can be challenging to find. By leveraging AI to help us better understand customer needs—both functional and emotional—product teams can create solutions that connect more deeply with customers, driving both satisfaction and competitive advantage. Useful Links Register for the Supercharge Your VOC Webinar on March 5th, 2025, with Carmel Dibner and Artem Timoshenko Stay up-to-date on upcoming AMS workshops Connect with AMS on Instagram Innovation Quote “Simplicity is the ultimate sophistication.” – attributed to Leonardo da Vinci Application Questions How could you use AI as a “copilot” in your current customer research process? Consider specific points where AI analysis might complement your team’s human analysis and help identify needs that might otherwise be overlooked. What emotional needs might your customers have that your team hasn’t fully explored? How could you use AI tools to help uncover these less obvious but potentially valuable insights? How might your team’s subject matter expertise be creating blind spots in your understanding of customer needs? What “fresh perspective” could AI bring to challenge your established assumptions? Where in your product innovation funnel could AI-powered customer research create the most value? Consider both early-stage discovery and later validation activities. What data sources about your customers do you already have that could be analyzed more comprehensively with AI tools? Think beyond interviews to include support tickets, reviews, social media comments, and other text-based feedback. Bio Carmel Dibner is a principal in the Insights for Innovation practice at Applied Marketing Science (AMS) where she is responsible for client relationships, client service delivery, and business development. She has worked closely with researchers at the MIT Sloan School of Management to experiment with new AI techniques and has successfully applied machine learning to answer her clients’ most difficult research questions. These techniques became the basis for a research study for Boston Children’s Hospital that was awarded a 2023 Quirk’s Marketing Research and Insight Excellence Award in the Health Care/Pharmaceutical Research Project category. More recently, she’s collaborated with researchers from MIT and Northwestern University’s Kellogg School of Management on next generation AI. She regularly presents at leading industry conferences such as the Front End of Innovation Continued and The Market Research Event Continued. Carmel is passionate about the intersection of psychology and business. She holds a Bachelor of Arts in Psychology and Sociology with a Business and Organizations concentration from Cornell University. She also holds an Masters in Business Administration in Marketing and Management from The Wharton School of the University of Pennsylvania, where she was named a Palmer Scholar. Thanks! Thank you for taking the journey to product mastery and learning with me from the successes and failures of product innovators, managers, and developers. If you enjoyed the discussion, help out a fellow product manager by sharing it using the social media buttons you see below. Source

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 Developing the Value Proposition Based on this customer understanding, Taelor evolved into a comprehensive solution combining several key elements: Service Component Customer Benefit AI-Powered Recommendations Personalized outfit selections based on schedule and preferences Monthly Subscription Regular rotation of 10 clothing items Professional Styling Expert guidance without requiring fashion knowledge Laundry Service Elimination of cleaning and maintenance hassles Validating the Model Anya explained that although Taelor sells clothes, their real value proposition is helping customers save time while getting ready for the week.  The service attracted a surprisingly diverse customer base, ranging from 16 to 85 years old, including professionals across various industries – from sales executives to pastors. This broad appeal confirmed that the core problem (wanting to look good without spending time on fashion) resonated across demographics. Taelor’s customers pay a monthly fee and receive ten clothing items per month. They answer some questions about their current favorite clothes and clothing issues. They can upload a picture, get a 15-minute free consultation with a human stylist, and provide information about special events they’re dressing for each month. An AI uses this information to pick five clothing items that are mix-and-matched into two to three outfits, which are shipped to the customer. They can wear these clothes for two weeks, mail the dirty clothes back, and keep any pieces they want. The business model created multiple value streams: Monthly subscription fees for the core service Purchase options for items customers particularly like Significant discounts (30-70% off) on pre-owned items Thorough customer research and iterative development can transform a personal insight into a viable product with broad market appeal. The key was moving beyond initial assumptions to discover and validate deeper customer needs. Customer Research and Product Evolution: Uncovering Hidden Opportunities Anya emphasized how continuous customer research revealed unexpected opportunities and shaped Taelor’s product evolution. Her approach to gathering and acting on customer insights offers valuable lessons for product managers at any stage. Multi-Channel Research Approach Rather than relying on traditional surveys alone, Taelor implemented a comprehensive research strategy that combined multiple touchpoints: Research Channel Insights Gained Impact on Product Style Quiz Initial fit preferences and style comfort zones Improved AI recommendations Stylist Consultations Detailed customer concerns and aspirations Enhanced personalization features Direct Customer Communication Real-time feedback and emerging needs New service opportunities identified Post-Use Feedback Product quality and fit issues Refined clothing selection process Emerging Customer Needs This deep customer engagement revealed several unexpected opportunities for service expansion: Gift recommendations for special occasions Style guidance beyond clothing (haircuts, accessories) Corporate partnership opportunities for employee benefits Educational institution collaborations for student interview preparation The Human Touch in AI-Driven Products Taelor decided to maintain human stylists alongside AI capabilities. While they could have automated all customer communications, they discovered that human interaction provided invaluable product development insights. This human element helped them: Understand nuanced customer needs that might not appear in data Identify patterns in customer requests before they become trends Build stronger relationships with customers Gather qualitative feedback that improved their AI systems Strategic Partnerships The research also led to strategic partnership opportunities that expanded the product’s value proposition. These included: Collaborations with women’s rental companies for gift services Partnerships with dating apps for style preparation Corporate programs for employee benefits Educational institution partnerships for student career preparation This systematic approach to customer research and product evolution demonstrates how careful attention to customer feedback can reveal new opportunities while strengthening the core value proposition. Supply Side Innovation: Solving Industry-Wide Challenges Anya revealed how Taelor’s innovation extends beyond customer service to address significant industry challenges. This dual-sided approach to product development offers lessons for product managers about finding opportunities in industry-wide problems. Addressing Fashion Industry Waste The fashion industry faces two challenges that Taelor’s  business model helps address: Industry Challenge Scale of Impact Taelor’s Solution Direct-to-Landfill Waste 30% of new clothes Rental model extending clothing lifecycle Carbon Emissions 10% from fast fashion Sustainable clothing rotation system Creating Value for Suppliers What makes Taelor’s approach particularly innovative is how it transforms these industry challenges into opportunities for brands. The platform serves as: A real-world testing ground for new designs A direct feedback channel from customers A solution for inventory management A market research platform for future collections Market Testing Innovation Anya shared how Taelor has become a valuable testing platform for clothing brands in several ways: Testing Aspect Brand Benefit Pre-Release Testing Real customer feedback before full production Durability Assessment Quality testing through multiple wears and washes Fit Verification Customer feedback on specific design elements Market Validation Early indicators of design popularity Breaking Traditional Distribution Models The platform also solves a significant challenge for new brands: finding their initial customer base. Anya explained how traditional distribution channels often involve multiple intermediaries, resulting in: Delayed feedback from end customers Limited understanding of customer preferences Reduced ability to iterate on designs Increased inventory risk By providing direct access to customers and immediate feedback, Taelor helps brands make more informed decisions about their products while reducing waste and improving sustainability. This demonstrates how innovative product development can create value for multiple stakeholders while addressing larger industry challenges. Key Product Management Lessons: Trust, Testing, and Breaking Bubbles Anya shared several pivotal lessons from her product management journey that challenge conventional wisdom. These insights, drawn from both successes and failures, offer valuable guidance for product managers at any stage of their careers. Trust Your Product Knowledge Anya shared a story about her early pitching experiences that illustrated a common product manager challenge. In preparing for startup competitions, she initially focused on memorizing answers to potential questions, consulting 42 former judges. However, this over-preparation actually hindered her ability to respond authentically and confidently. Key lessons she learned about product leadership: Value your deep product knowledge as the product’s “parent” Trust your understanding developed through daily engagement Balance external input with your own expertise Respond authentically rather than reciting prepared answers Think Beyond Utility One of Anya’s most significant realizations came after transitioning from corporate to startup environments. She discovered that successful product development requires thinking beyond pure utility: Move beyond the corporate “usefulness” mindset Embrace curiosity about different perspectives Seek insights from unexpected sources Break out of industry and professional bubbles Value of Diverse Perspectives Anya emphasized how her most valuable insights often came from unexpected sources: Successful entrepreneurs outside tech Professionals from different industries Customers with unique use cases Team members with diverse backgrounds Successful product management isn’t just about following established frameworks – it’s about developing the judgment to know when to trust your instincts, question assumptions, and seek diverse perspectives. Conclusion Throughout my conversation with Anya Cheng, one theme consistently emerged: Successful product development isn’t about matching competitors feature-for-feature or trying to solve every customer problem. Instead, it’s about identifying a significant problem, solving it exceptionally, and having the discipline to maintain that focus even as your product grows. Her journey from leading product teams at major tech companies to founding Taelor demonstrates how this principle applies across different scales and industries. For product managers and innovators, the lessons from Anya’s experience offer a refreshing perspective on product development. Whether you’re working in a large corporation or leading a startup, success comes from deeply understanding your customers, questioning your assumptions, embracing diverse perspectives, and having the courage to maintain a singular focus on solving one problem exceptionally. Useful Links Connect with Anya on LinkedIn Check out Taelor and use code global30 to get 30% off your first month of subscription or globalgitft10 to get 10% off a gift card Innovation Quote “A great product solves a real problem with a singular, powerful value proposition.” – Anya Cheng Application Questions How could you simplify your current product down to one “giant check mark” – a single feature or capability that solves a crucial problem better than any alternative? What would you need to remove or change to achieve this focus? How could your team expand your customer research methods beyond traditional approaches? Consider Anya’s example of having customer service representatives purposefully engage with users to gather product development insights. What new channels could you create for deeper customer understanding? Looking at your product’s recent feature additions, how many were driven by competitor comparison versus genuine customer needs? How could you reframe your feature prioritization process to focus more on solving specific customer problems exceptionally? How could you break out of your industry bubble to gain fresh perspectives on your product challenges? What unexpected sources or diverse viewpoints could you engage with to inspire innovation in your product development process? Consider the Target iPad app example: How could your team apply radical feature minimization to your product? What would happen if you reduced your product to just two core capabilities that align perfectly with your key value proposition? Bio Anya Cheng is the Founder and CEO of Taelor, a leading men’s clothing subscription service that provides personal styling and curated rentals, powered by expert stylists and AI. A Girls in Tech 40 Under 40 honoree, she previously led eCommerce and digital innovation teams at Meta, eBay, Target, and McDonald’s. Experience effortless style with rental and personal styling services: Taelor: Get 25% OFF your first month of men’s clothing subscription. Use code: PODCAST25 Sign up at: https://taelor.style/pages/membership Armoire: Get 50% OFF your first month of women’s clothing subscription. Use code: ArmoirexTaelor Sign up at: https://www.armoire.style/refer/ArmoirexTaelor Give the gift of time, convenience, and effortless style: Taelor Gift Cards: Get 10% OFF Use code: PODCASTGIFT Purchase at: https://taelor.style/products/menswear-rental-gift-card   Thanks! Thank you for taking the journey to product mastery and learning with me from the successes and failures of product innovators, managers, and developers. If you enjoyed the discussion, help out a fellow product manager by sharing it using the social media buttons you see below. Source

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 from business stakeholders to define problems, then transmitting requirements to development teams to create solutions. This approach, while common, created several challenges: Information bottlenecks formed when all communication flowed through the product manager Stakeholders became disconnected from understanding product development complexities Development teams lost direct insight into business context and customer needs The product manager’s personal biases could inadvertently filter or alter important information The Modern Facilitator Model: A Better Approach As Francesca’s experience grew, she discovered that effective product management requires a different mindset. The role isn’t about being the sole decision-maker, but rather about: Key Responsibility Implementation Approach Facilitating Discussions Creating spaces for direct dialogue between stakeholders Identifying Decision Makers Understanding who is best positioned to make specific decisions Driving Progress Keeping initiatives moving forward through collaboration Building Understanding Helping teams grasp complex business and technical contexts This evolved understanding acknowledges that no single person, even a CEO, can be an expert in all areas. Instead, successful product managers excel at bringing together diverse perspectives and expertise to create better outcomes. This shift isn’t about abdicating responsibility. Rather, it’s about recognizing that the most effective product decisions emerge from collaborative processes where all stakeholders can contribute their expertise directly. This approach leads to better solutions and stronger buy-in from teams responsible for building and supporting the product. The facilitator model also addresses a common challenge in product management: the need to drive progress without direct authority over many of the people involved. By focusing on facilitation rather than control, product managers can maintain momentum while building the trust and relationships necessary for long-term success. This evolution in understanding reflects broader changes in how modern organizations approach product development. As products become more complex and teams more specialized, the ability to facilitate effective collaboration becomes increasingly valuable. Key Motivations and Misconceptions in Product Management Throughout my years of teaching and practicing product management, I’ve asked hundreds, if not thousands, of product managers why they chose this career path. During my conversation with Francesca, we explored these common motivations and the misconceptions that often accompany them. Why People Choose Product Management Three primary motivations consistently emerge when people discuss their attraction to product management: Motivation Reality Challenge Creating Customer Value Direct impact on solving customer problems Balancing customer needs with business constraints Organizational Influence Ability to shape product direction Learning to influence without authority Strategic Overview Understanding the bigger picture Managing competing priorities and perspectives Common Misunderstandings About the Role Francesca highlighted several misconceptions she encountered when working with and mentoring product managers: Many believe becoming a product manager automatically grants decision-making authority Some think their job is to have all the answers rather than facilitate finding solutions Product managers often struggle with undefined boundaries of their role These misconceptions can lead to frustration when new product managers encounter the reality of the role. Francesca shared that she often heard product managers say, “We can just solve this because I’m the CEO of the product,” not realizing that the product is much bigger than any individual’s authority. Bridging the Gap Successfully navigating these misconceptions requires understanding that: 1. Influence and authority are different skills 2. Product success depends on collaborative decision-making 3. Role boundaries vary significantly by organization 4. Leadership doesn’t always mean management Many professionals enter product management from technical backgrounds, such as engineering or development. While these backgrounds provide valuable technical knowledge, they don’t always prepare individuals for the people-focused aspects of product management. This transition often requires developing new skills and sometimes discovering whether you actually enjoy the highly collaborative nature of the role. This understanding leads to an important question that Francesca posed: “How do we know that this is what we like?” Not everyone who excels at technical work will enjoy or excel at the collaborative, facilitative aspects of product management. Recognizing this early can help professionals make better career choices and find roles that align with their strengths and preferences. Essential Skills for Product Management Success My discussion with Francesca revealed that success in product management hinges on two key competencies: building trust capital and mastering stakeholder management. These skills form the foundation for effective product leadership, regardless of organization size or industry context. Building Trust Capital A key element for product management success is trust capital—how much you’re able to make people around you trust you. Francesca explained that trust capital comes from two primary sources: Trust Component How to Develop It Why It Matters Deep Field Understanding Immerse in industry knowledge, market dynamics, and technical aspects Enables credible participation in strategic discussions People Skills Focus on empathy, communication, and relationship building Creates foundation for effective collaboration A significant insight Francesca shared was her evolution from trying to convince others of her ideas to truly empathizing with their perspectives. Early in her career, she focused on building compelling arguments to win support for her decisions. However, she discovered that success comes from understanding where others see opportunities and why they prioritize certain approaches over others. Mastering Stakeholder Management Effective stakeholder management requires a proactive approach. Francesca outlined several key strategies: Early Involvement: Engage stakeholders at the beginning of initiatives rather than presenting finished solutions Collaborative Ownership: Help stakeholders feel the solution is theirs by incorporating their input meaningfully Cross-functional Alignment: Ensure marketing, sales, and customer support believe in the product direction This approach doesn’t mean everyone needs input on every decision. Instead, it means identifying key stakeholders and involving them at appropriate points in the process. From Convincing to Collaborating The shift from convincing to collaborating represents a fundamental change in how product managers approach their role. Instead of preparing perfect presentations for the boardroom, successful product managers: 1. Hold preliminary discussions to understand concerns and perspectives 2. Build consensus through ongoing dialogue 3. Incorporate diverse viewpoints into product strategy 4. Create shared ownership of solutions This collaborative approach yields several benefits: Benefit Impact Stronger Solutions Multiple perspectives lead to more robust product decisions Better Buy-in Early involvement creates natural advocates for the product Faster Implementation Aligned teams move more quickly and effectively Sustainable Success Collaborative wins create foundation for future cooperation Francesca noted that these skills become increasingly important as product managers advance in their careers. Whether moving toward senior individual contributor roles or people management positions, the ability to build trust and manage stakeholders effectively remains crucial for success. The Varying Nature of Product Management Roles Product manager occupy various roles across different organization, so it is important for them to understand their specific context and adapt their approach accordingly. Impact of Organization Size The size of an organization significantly influences the scope and nature of product management roles: Company Stage Role Characteristics Key Challenges Startup Broad responsibilities, including customer support Wearing multiple hats while maintaining focus Scale-up (100-200 people) More defined role with clearer boundaries Establishing processes while maintaining agility Enterprise Specialized focus on specific features or products Navigating complex organizational structures Context-Specific Variations Francesca highlighted two distinct contexts that shape product management roles: 1. Product-as-Company Environment Digital-first businesses where the product is central Clear connection between product metrics and business success Direct influence on company revenue and growth 2. Product-as-Channel Environment Traditional businesses with digital components Product serves as one of multiple channels Need to align with broader business strategies For example, Francesca contrasted a digital marketplace with a luxury retailer like Gucci. While the marketplace’s product team directly drives business success, Gucci’s digital product team supports a broader retail strategy where physical products generate most revenue. Organizational Considerations The role’s scope can vary dramatically based on organizational structure: Scope Type Description Example Full Product Ownership of entire product or product line Complete marketplace platform Feature Focus Responsibility for specific functionality Search feature in office software Channel Management Digital presence for traditional business E-commerce platform for retailer Francesca noted that these differences often relate more to company stage than industry type. As organizations grow, product management roles typically become more specialized and focused on smaller components of the overall product strategy. Managing Internal Competition An important challenge Francesca highlighted was managing internal competition between products or channels. Product managers must navigate situations where: 1. Different products target overlapping market segments 2. New digital channels might cannibalize traditional sales 3. Multiple teams compete for the same resources 4. Various stakeholders have conflicting objectives Success in these situations requires strong stakeholder management skills and regular engagement with key decision-makers to understand their objectives and help them achieve their goals while maintaining product focus. Setting Clear Role Boundaries Francesca emphasized how important it is to establish clear boundaries and expectations in product management roles, especially as organizations scale and evolve. Establishing Expectations Francesca recommended conducting expectation workshops, particularly during key organizational transitions. These workshops should address: Expectation Area Key Questions to Address Why It Matters Role Definition What specific responsibilities fall under the PM role? Prevents scope creep and role confusion Success Metrics How will performance be measured? Aligns efforts with business goals Support Needs What resources are needed for success? Ensures proper enablement Stakeholder Engagement Who are the key stakeholders and how often to engage? Sets communication standards Managing Role Evolution As organizations grow, product management roles often shift dramatically. Francesca highlighted several key considerations: Different roles require different skills (individual contributor vs. management) Career progression isn’t always linear The higher you go, the less direct product work you do Not everyone wants or needs to become a people manager Creating Clear Guidelines Francesca recommended being explicit about expectations in several key areas: 1. Customer Interaction Required frequency of customer contact Expected depth of market understanding Methods for gathering customer feedback 2. Business Understanding Knowledge of revenue models Understanding of key metrics Grasp of market dynamics 3. Stakeholder Management Required meeting cadence Communication expectations Decision-making processes Adapting to Change Organizations need to revisit role boundaries regularly, especially during: Transition Point Required Actions Company Growth Phases Redefine roles and responsibilities Leadership Changes Align on new expectations Strategy Shifts Update success metrics Team Expansion Clarify reporting structures What works in one company or context might not work in another. Product managers often join new organizations with expectations based on previous experiences, which might not align with their new environment. Regular expectation alignment helps prevent confusion and ensures everyone understands their role in driving product success. Call out unreasonable expectations, such as excessive stakeholder meetings that prevent meaningful customer interaction. The key is approaching these discussions with solutions rather than complaints, showing how adjustments could improve overall impact. Practical Advice for Product Managers Francesca shared valuable insights for product managers navigating their roles, drawing from her experience both as a product leader and consultant to major European brands. Her advice focused on practical approaches to common challenges and sustainable professional development. Navigating Role Challenges When facing common product management challenges, Francesca recommended several key strategies: Challenge Solution Approach Expected Outcome Too Many Stakeholder Meetings Analyze impact of activities and propose alternatives More time for high-value work Unclear Decision Authority Define decision-making frameworks with leadership Faster progress on initiatives Limited Customer Interaction Make customer contact non-negotiable Better product decisions Execution Pressure Validate assumptions before full implementation Reduced risk of failure Avoiding Common Pitfalls Francesca highlighted several modern product management pitfalls to watch for: Following industry best practices without considering context Implementing frameworks without understanding their purpose Prioritizing execution speed over proper validation Losing touch with customer needs due to internal focus Professional Development Strategies For ongoing growth, Francesca recommended focusing on: 1. Context-Aware Learning Study industry best practices but adapt them to your environment Understand why certain approaches work in specific contexts Learn from both successes and failures 2. Expectation Management Regularly align with managers on priorities Document and track role expectations Proactively address misalignments 3. Impact Measurement Area Measurement Approach Value Creation Track key product metrics and customer outcomes Team Effectiveness Monitor collaboration quality and decision speed Stakeholder Satisfaction Regular feedback and alignment checks Customer Understanding Depth and frequency of customer insights Maintaining Focus on What Matters Product managers should: 1. Prioritize customer insights over internal politics 2. Focus on facilitating good decisions rather than making all decisions 3. Build collaborative relationships across the organization 4. Keep learning and adapting their approach as contexts change While books and frameworks provide valuable guidance, success comes from understanding your specific context and adapting best practices accordingly. Maintain a learning mindset while staying focused on creating value for customers and the business. Conclusion As product management continues to mature as a discipline, we’re seeing a shift away from the oversimplified “CEO of the product” concept toward a more nuanced understanding of the role. Success comes not from authority or control, but from the ability to facilitate collaboration, build trust, and maintain focus on creating value for customers. The most effective product managers embrace this evolution, recognizing that their impact comes not from making every decision, but from enabling better decisions through collaboration and shared understanding. By focusing on building trust capital, managing stakeholder relationships effectively, and adapting their approach to specific organizational contexts, product managers can drive success while maintaining enthusiasm through the inevitable challenges along the way. Useful Links Check out Francesca’s website to learn about her mentorship service and to get free resources Connect with Francesca on LinkedIn Innovation Quote “Success is being able to go from failure to failure without losing your enthusiasm.” – Winston Churchill Application Questions Which decisions about your product are you currently acting as a bottleneck for? How well do your current role boundaries and expectations align with your organization’s needs? How could your team benefit from improved stakeholder management? How could you build stronger trust capital in your organization? What internal activities could you eliminate or delegate to create more space for customer understanding? Bio With over a decade of product leadership experience, Francesca Cortesi knows what it takes to turn big ambitions into real, scalable outcomes. She specializes in helping growing companies go beyond market fit and scale sustainably, focusing on clear strategies, practical frameworks, and fostering strong collaboration across teams. Drawing from her experience as Chief Product Officer and Head of Product, Francesca enables businesses to drive results that matter—for both the business and its customers. A passionate advocate for human-centered leadership, she shares insights through speaking and thought leadership, helping founders and teams navigate the exciting (and messy!) journey of scaling. Thanks! Thank you for taking the journey to product mastery and learning with me from the successes and failures of product innovators, managers, and developers. If you enjoyed the discussion, help out a fellow product manager by sharing it using the social media buttons you see below. Source

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 Strategic Purpose Short, squat jar Communicates cream efficacy Pump mechanism Suggests absorption and precise dosing Large window carton Creates shelf visibility Simple graphics Encourage counter display Light-reflecting particles Reduce appearance of fine lines and wrinkles in the short-term Innovative combination of ingredients Reduces signs of aging in the long-term Consumer Research and Insight Development: Understanding the Skincare Market Nancy’s approach to consumer research demonstrated how product managers can gain deeper insights by going beyond traditional market research methods. Her commitment to understanding consumer behavior firsthand led to breakthrough insights that shaped Olay’s transformation. Research Methodology Nancy’s comprehensive research approach included: Personal conversations with over 1,000 women about their skincare routines and preferences In-home visits to observe real product usage patterns Shopping with customers to learn their packaging preferences Blind product testing without branding to understand true value perception Analysis of the consumer decision-making timeline in skincare Understanding the Consumer Journey By observing customers do their skincare routines, Nancy learned that after a customer first uses the product, she thinks about how it makes her feels. Over the next few days, she checks whether her fine lines and wrinkles are disappearing. After 2-3 weeks, she decides whether to keep using the product, but the bioactive ingredients take a few months to work. This knowledge led to Olay adding light-reflecting particles to reduce the appearance of fine lines and wrinkles, encouraging customers to keep using the product long enough for the bioactive ingredients to start working. Market Positioning and Pricing Strategy: Creating the Mass-Prestige Category Nancy learned from customer focus groups that customers perceived Olay’s product as a department store product that would cost $30-40. Olay created the “mass-prestige” skincare category, launching their Total Effects skincare as a $20 prestige product but in the mass channel. To validate the premium positioning, the team conducted extensive testing, including blind tests in which Olay outperformed leading department store brands in improving seven signs of aging. Developing a Different Product Nancy realized early-on that it wouldn’t be enough to develop a better product. Olay needed a different product. Rather than just staying comfortable as a product developer, Nancy acted as a serial innovator and took the risk of launching an entirely new brand. Nancy identified a significant market gap between cheap mass market skincare and expensive department store skincare. Their customers shopped at both places. They tested different price points and found that $20 was inexpensive enough for mass market shoppers and expensive enough to be a high-quality department store product. Navigating Organizational Challenges One of the most valuable insights Nancy shared was about managing the challenges serial innovators face within large organizations. She acknowledged that innovators often feel like “square pegs in round holes” and offered practical strategies for success: Make the “implicit explicit” by creating visual models and clear documentation of your thinking process Build a network of mentors and allies who understand and support your approach to innovation Identify and execute critical experiments that can validate your ideas to stakeholders Learn to communicate complex, interconnected ideas to linear thinkers in your organization Nancy’s experience showed that while holistic innovation might look simple once completed, the process of getting there can appear chaotic to others in the organization. The key is helping others understand your thought process and building support for your approach through clear evidence and results. The Spider Web Nancy compared the work of a serial innovator to a spider in its web: Intimacy with the Problem: Just as a spider is intimately connected to its web, successful innovators maintain close contact with the problems they’re solving. This means getting personally involved in consumer research and product testing. Multi-Domain Mastery: Like a spider’s expertise in web building, vibration analysis, and food capture, innovators need deep knowledge across multiple domains. Nancy called this becoming an “M-shaped innovator” rather than just having depth in a single area. Integration of Knowledge: Serial innovators must connect insights across different areas, similar to how a spider interprets various web vibrations to make decisions. Environmental Awareness: Understanding when and where to build the web is as crucial as knowing how to build it – timing and organizational context matter significantly. Conclusion The transformation of Olay from a declining brand into a market leader offers valuable lessons for today’s product managers and innovation leaders. Through Nancy’s systematic approach to consumer research, strategic product development, and market positioning, we see how breakthrough innovation happens when technical expertise meets deep consumer understanding. Her story demonstrates that successful product transformation requires more than just creating better products – it demands a holistic approach that considers every aspect of the consumer experience. For product managers looking to drive innovation in their organizations, the key takeaway is the importance of becoming what Nancy calls an “M-shaped innovator” – someone who can master multiple domains while connecting insights across disciplines. Whether you’re working to transform an existing product or create an entirely new category, success depends on your ability to combine consumer insights, technical innovation, and strategic thinking while building the organizational support needed to bring transformative ideas to market. The Olay case study shows that with the right approach and persistence, even the most challenging product transformations are possible. Useful Links Watch Nancy Dawes and Bruce Vojak’s webinar, “Serial Innovators” Check out Nancy and Bruce’s PDMA session, “Are You Firing the Wrong People?” Connect with Nancy on LinkedIn Innovation Quote “I see dead people.” – Nancy Dawes, based on The Sixth Sense Application Questions What research methods could you use to better understand your users’ unstated beliefs and assumptions about your product category? What evidence would you need to gather to validate a new price positioning for your product? Looking at your current product development process, how could you better integrate immediate user satisfaction with long-term benefits? What early indicators could you provide to users that would encourage them to stick with your product long enough to see its full benefits? How could you become more of an “M-shaped innovator” in your organization? What additional domains of expertise would help you better connect insights across different areas of your product development process? Think about a current challenge in your product line: How could you use small-scale experiments to validate your hypotheses before requesting major organizational investments? What would be your equivalent of Nancy’s early package testing? Bio Nancy is a recognized Serial Innovator from Procter & Gamble for her transformative work on Pringles, Olay, & Head & Shoulders.  She was instrumental in creating the anti-wrinkle, masstige skin care movement inside the $135 billion global skin care category via her pioneering work which turned a declining Olay brand into a $2.5 billion powerhouse.  She led global teams that demonstrated improvement in skin health and appearance, strategized proprietary materials, innovated packaging and product characteristics with uniquely strong consumer appeal and enabled pricing that led to holistic business wins for P&G.  Bookending this program, she employed similar methods and achieved similar results in P&G’s global Head & Shoulders and Pringles’ brands.  Nancy’s string of achievements caused P&G to elevate her to the level of its most elite scientists and engineers (Vic Mills society) and the Ohio State College of Engineering to award her the 2021 Benjamin Lamme Medal for Meritorious Achievement in Engineering.   After 38 years at P&G, Nancy leverages her innovation experience providing training to help companies/people improve their innovation capability.  She is an active volunteer for Girl Scouts and the College of Engineering at Ohio State. Thanks! Thank you for taking the journey to product mastery and learning with me from the successes and failures of product innovators, managers, and developers. If you enjoyed the discussion, help out a fellow product manager by sharing it using the social media buttons you see below. Source