How product managers are transforming innovation with AI tools

Watch on YouTube

TLDR

In this deep dive into AI’s impact on product innovation and management, former PayPal Senior Director of Innovation Mike Todasco shares insights on how AI tools are revolutionizing product development. From enhancing team brainstorming and prototype development to product iteration, AI is becoming an essential tool for product managers. However, Mike emphasizes the importance of balancing AI capabilities with human oversight, warning against over-reliance on AI. The discussion explores practical applications of AI tools like ChatGPT and Claude in product development, including MVP refinement, customer testing, and marketing content creation. Drawing from his experience building PayPal’s Innovation Labs, Mike also shares valuable insights on creating an innovation culture that empowers all employees to contribute to product innovation, regardless of their role.

Key Topics:

• Building Innovation Culture (PayPal Case Study)
• AI as a Brainstorming Partner
• AI Tools in Product Development
• Product Development Acceleration
• AI Implementation Cautions
• Future of AI in Product Development
• Customer Testing and Validation

AI’s Impact on Product Innovation and Management: A New Era for Product Teams

In this episode of Product Mastery Now, I’m interviewing Mike Todasco, former Senior Director of Innovation at PayPal and current visiting fellow at the James Silberrad Brown Center for Artificial Intelligence. Mike brings valuable insights about the revolutionary transformation of product development through artificial intelligence. Through our discussion, Mike shares how this dramatic acceleration in product development processes signals a fundamental shift for product teams. Drawing from his experience leading innovation at PayPal and holding over 100 patents, Mike explains how AI tools are creating new opportunities for innovation, faster iteration cycles, and more comprehensive market understanding while maintaining a balance between artificial intelligence and human insight.

Building Innovation Culture: Lessons from PayPal’s Innovation Lab

In our discussion, Mike shares insights from his experience building PayPal’s Innovation Lab following the company’s separation from eBay in 2015. He explains that their approach to innovation deliberately avoided the common pitfall of creating a two-tiered system where only designated “innovators” were responsible for new ideas.

Creating an Inclusive Innovation Environment

The foundation of PayPal’s innovation success rested on a culture of trust and autonomy. Mike points to their unlimited vacation policy as a symbol of this trust-based culture, where employees were treated as responsible adults capable of managing their time and contributions. This philosophy extended to how employees could engage with the Innovation Lab, allowing them to pursue innovative projects alongside their regular responsibilities.

Traditional Innovation Model PayPal’s Inclusive Approach Designated innovation teams Open to all employees Structured innovation times Flexible engagement Rigid definition of innovation Adaptable interpretation Top-down innovation goals Self-directed innovation

Implementation Strategy

PayPal deliberately kept the definition of innovation flexible. Rather than imposing a strict interpretation, they allowed different roles to define innovation in ways that made sense for their work. Mike encouraged employees to include innovation in their annual goals but never forced this approach.

• Innovation goals were customized to individual roles and responsibilities
• The Innovation Lab served as a gathering space for collaborative work
• Employees had freedom to explore projects in their spare time
• Leadership encouraged but didn’t mandate innovation participation

This approach helped create a culture where innovation wasn’t seen as an additional burden but as an organic part of the workplace. While some areas of the company found this adjustment challenging, PayPal’s long-standing history of innovation made the cultural shift more natural. The success of this approach demonstrates how creating the right environment for innovation can be more effective than mandating it through formal structures.

Leveraging AI in Product Development: A Practical Approach

Mike shares examples of how AI is transforming product development, starting with his own daily interactions with tools like Claude and ChatGPT. His examples demonstrate the versatility of AI in both personal and professional contexts.

AI as Your Development Partner

Through our discussion, Mike explains how AI can serve as a brainstorming partner for product managers. He illustrates this with a recent experience helping an entrepreneur develop a video analysis product. What stands out is their approach to rapid iteration – continuously challenging themselves to simplify their concept, moving from four-week solutions to one-week versions, and ultimately to one-day tests. This methodology helps teams identify the core value proposition quickly.

Choosing the Right AI Tools

When it comes to selecting AI tools for product development, Mike shares several practical approaches to compare different models:

30-Minute Evaluation Method Quick Comparison Method Create test scenarios Open multiple tool windows Test across different AI models Input identical prompts Score responses systematically Compare immediate responses Evaluate reasoning patterns Assess response quality

Available AI Tools for Product Managers

Mike outlines several key AI platforms product managers should consider:

• Claude: Excels at analytical tasks and detailed explanations
• ChatGPT: Strong general-purpose tool with quick responses
• Gemini: Google’s AI with robust integration capabilities
• Copilot: Particularly useful for technical development
• Mistral: Emerging option worth exploring

The key takeaway from our discussion is that AI tools aren’t just about automation – they’re about augmenting human creativity and decision-making in product development. Mike notes that while no single tool is perfect for every task, having multiple AI resources available allows product managers to leverage the right tool for specific needs.

The quality of AI’s work is not as good as human’s work, but its speed is superhuman, and product managers can take advantage of that.

AI Applications Across Product Development Phases

In our discussion, Mike provides valuable insights into how AI can enhance each stage of product development, particularly emphasizing the importance of rapid testing and validation. His perspective on using AI to accelerate the MVP (Minimum Viable Product) process is particularly enlightening. Product managers can use AI to help make their tests simpler.

Early Stage Development with AI

Mike strongly advocates for the 24-hour testing principle – the idea that teams should strive to test core concepts within a single day. He explains that AI tools can help product teams:

• Rapidly refine MVP concepts through multiple iterations
• Generate and evaluate multiple solution approaches quickly
• Test core assumptions before investing significant resources
• Create basic prototypes for initial feedback

Customer Testing and Validation

One of the most innovative approaches Mike shares is using AI for initial customer testing. However, he emphasizes that this should complement, not replace, traditional customer research.

Testing Phase AI Role Human Role Initial Concept Rapid persona-based testing Define customer personas Early Validation Multiple iteration cycles Interpret results Market Testing Automated feedback analysis Customer interviews Launch Preparation Message testing Strategic decisions

Mike suggests an experimental approach to using AI in early customer testing, though he emphasizes this is something he hasn’t fully implemented yet. He explains that product teams could potentially feed customer personas into AI models and run multiple tests to gauge reactions to different product options. For example, if you run the same prompt ten times and the AI selects option A eight times versus option B two times, this might indicate a preference pattern.

However, Mike strongly emphasizes that this approach should never replace actual customer research. He explains that while AI might help teams get their product into a better place before customer testing, it’s important to remember that AI models are trained on internet data, not real customer thoughts and behaviors. As he puts it, “People are weird complex beings,” and AI might not always catch the nuances of real customer behavior.

The key takeaway from Mike’s discussion is that while AI can be a useful tool for early-stage testing and iteration, it should be used to supplement, not replace, traditional customer research methods.

Product Launch and Marketing

Mike shares how AI can significantly enhance product launch activities:

• Generating initial marketing messages for different customer segments
• Testing various positioning approaches
• Creating customized content for different channels
• Analyzing market response patterns

What makes Mike’s approach particularly effective is his emphasis on using AI to accelerate the learning process while maintaining human oversight for strategic decisions. He explains that the goal isn’t to automate the entire development process but to remove bottlenecks and speed up iteration cycles.

Cautions in AI Implementation

Mike provides a word of caution. He introduces the metaphor of “falling asleep at the wheel” – if we over-rely on a driverless car that is not 100% perfect, we could be in trouble. Similarly, we should not over-trust AI in product development. This analogy serves as a reminder of the importance of maintaining human oversight in AI-assisted processes.

Understanding the Risks

Mike shares real-world examples of AI implementation failures, citing incidents at Sports Illustrated and CNET where over-reliance on AI led to publishing errors. He explains that these situations often occur not because the AI tools failed completely, but because human oversight gradually decreased after seeing consistent success.

Risk Area Warning Signs Preventive Measures Customer Understanding Over-reliance on AI-generated personas Regular real customer interactions Decision Making Automatic acceptance of AI suggestions Structured human review process Content Creation Minimal editing of AI outputs Thorough human verification Market Analysis Exclusive use of AI interpretations Cross-reference with human insights

Balancing AI and Human Input

Mike emphasizes several key principles for maintaining effective AI integration:

• AI should not be a replacement for interactions with real customers
• Use AI as a complement to human expertise, not a replacement
• Maintain regular customer contact through traditional research methods
• Implement structured review processes for AI-generated content
• Regularly validate AI insights against real-world data

The most valuable insight Mike shares is that AI tools should enhance rather than replace human judgment. He explains that while AI can process information and generate options at superhuman speeds, the final decisions about product direction should always incorporate human experience and intuition. This balanced approach ensures that teams can benefit from AI’s capabilities while avoiding the pitfalls of over-automation.

The Future of AI in Product Development: Team Collaboration

In our discussion, Mike shares an exciting vision of how AI will transform team collaboration in product development. Drawing from his experience running innovation sessions at PayPal, where teams of 5-25 people would gather in the innovation lab, he explains how AI could enhance these collaborative environments.

AI as a Team Member

Mike describes several ways AI could augment team interactions:

• Acting as a neutral, knowledgeable participant in brainstorming sessions
• Capturing and synthesizing team discussions in real-time
• Providing fresh perspectives when conversations hit a lull
• Helping teams maintain energy and creativity during intensive sessions

Evolution of Workspace Integration

Looking five years ahead, Mike envisions AI becoming seamlessly integrated into everyday work environments:

Current State Future Integration Individual AI interactions AI-enabled conference rooms Manual note-taking Automated meeting synthesis Scheduled brainstorming Continuous AI collaboration Text-based AI interaction Multi-modal AI communication

Emerging Collaboration Patterns

Mike shares how these changes are already beginning to appear. He points to WhatsApp’s integration of AI into group chats as an example of how AI collaboration is evolving. In these environments, AI can:

• Contribute to group discussions when prompted
• Help teams find information or resources quickly
• Assist with scheduling and coordination
• Provide real-time analysis of ideas and suggestions

The key insight Mike emphasizes is that this future isn’t about replacing human collaboration but enhancing it. He explains that AI can help teams overcome common barriers in collaborative work, such as mental fatigue during intensive brainstorming sessions or the challenge of capturing and organizing multiple threads of discussion.

Conclusion

Throughout our discussion, Mike Todasco shares valuable insights about integrating AI tools into product development processes, drawing from his experience at PayPal’s Innovation Lab and his current work in artificial intelligence. His practical approach to using AI as a development partner while maintaining human oversight provides a blueprint for product managers looking to enhance their innovation processes.

The key to success lies in striking the right balance – using AI to accelerate ideation, streamline product development, and enhance team collaboration while maintaining the human judgment essential for product success. As Mike emphasizes, AI tools aren’t replacing product managers; they’re empowering them to work more efficiently and innovatively. For product teams ready to embrace this transformation, the combination of AI-powered product development tools and human creativity opens new horizons for product innovation and market success.

Useful links:

• Connect with Mike on LinkedIn
• Read Mike’s articles on Medium
• Subscribe to Mike’s Newsletter, AI Conversations
• Learn more about the James Silberrad Brown Center for Artificial Intelligence at San Diego State University SDSU

Innovation Quote

“The best way to have a good idea is to have lots of ideas.” – Linus Pauling

Application Questions

1. How could you restructure your current sprint process to incorporate AI tools while maintaining the most valuable human interactions?
2. How could your team use AI to get faster feedback on product concepts while ensuring you’re still capturing genuine customer insights?
3. What safeguards could you put in place to prevent over-reliance on AI while still taking full advantage of its capabilities?
4. How could you integrate AI into your team’s brainstorming sessions in a way that enhances rather than replaces human creativity?
5. How could you balance the speed of AI-powered development with the need for thoughtful product decisions and human oversight?

Bio

Mike Todasco is a former Senior Director of Innovation at PayPal and a current Visiting Fellow at the James Silberrad Brown Center for Artificial Intelligence at SDSU. With over 100 patents to his name, Mike played a key role in fostering a culture of innovation across PayPal’s 20,000+ employees. A recognized expert in AI and innovation, he explores how AI can enhance creativity and revolutionize business processes and personal tasks. Passionate about democratizing advanced technology, Mike advocates for enabling innovation without requiring deep technical expertise. He frequently shares his insights on AI’s impact on innovation, decision-making, and cognition through articles on Medium and LinkedIn. 

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.

How product managers can adapt core responsibilities across different organizations and contexts

Watch on YouTube

TLDR

Through his research and practical experience at MasterCard, Nishant Parikh identified 19 key activities that define the role of software product managers. He emphasizes that these activities vary based on context (large vs. small organizations, B2B vs. B2C, Agile vs. Waterfall). The discussion reveals how product management has evolved since 1931 and highlights the importance of clear role definition to prevent job frustration. The core focus of these activities is on thorough market research, continuous customer engagement, and strategic product development.

Key Topics:

• Market research as the foundation of product success
• Evolution from problem space to solution identification
  Product positioning and vision development
• Differences between product manager and product owner roles
• Flexible vs. fixed roadmapping approaches
• Continuous customer engagement throughout product lifecycle
• Financial analysis and business case development
• Impact of organizational size on PM responsibilities
• Role of AI tools in modernizing product management
• Importance of cross-functional collaboration

Introduction

In this episode, I’m interviewing Nishant Parikh, Director of Product Management at MasterCard. We explored the 19 essential activities that define successful software product management today.

Drawing from his 20+ years of technology experience and extensive research, Nishant shared insights about how these activities vary across different organizational contexts – from startups to enterprises, B2B to B2C, and Agile to Waterfall environments. He emphasized the importance of role clarity and how the lack of it often leads to frustrated product managers leaving their positions.

In this article, I’ll share the key takeaways from our discussion, including why market research should be your foundation, how customer engagement has evolved to become a continuous process, and the ways AI is reshaping traditional product management activities.

Why study the 19 key activities of software product managers?

Nishant’s motivation came from his personal experience navigating different product management roles over six years. Each position required vastly different responsibilities:

• In his first PM role, he focused on high-level solution development and feature writing
• His next position emphasized go-to-market activities
• At a small MasterCard acquisition company, he had to handle everything from product development to writing stories and epics
• Currently at MasterCard’s foundry team, his focus is on innovation and ideation

This variety of experiences left him confused about the core responsibilities of a product manager. This confusion motivated him to pursue research to better understand:

• What a product manager’s key responsibilities should be
• How the discipline has evolved since its inception in 1931
• Why many PMs leave their jobs due to lack of role clarity
• How to address the overlapping responsibilities between product managers, product leaders, and innovators

He noted that while large organizations might have 100 defined activities for product managers, it’s impossible for one person to handle them all. This led him to research and identify 19 core activities specific to product management, with clear separation from product marketing, sales, and go-to-market functions.

Consolidating insights from different bodies of knowledge

Nishant identified three main bodies of knowledge in product management, each with distinct limitations:

1. PDMA (Product Development and Management Association)
2. ISPMA (International Software Product Management Association) – focused specifically on software industry
3. Product Marketing Body of Knowledge – combines product management and product marketing

The key problem he identified is that none of these bodies of knowledge clearly distinguish between different product management roles or account for various contextual factors that affect how product managers should work, such as:

• Organization size (large vs. small companies)
• Development methodology (Agile vs. Waterfall)
• Product type (AI vs. non-AI products)
• Market focus (B2B vs. B2C)

He emphasized that these contextual factors significantly impact a product manager’s role. For example:

• In large companies, different departments handle specialized functions
• In small companies, one product manager might handle all responsibilities
• The same role can look very different between B2B and B2C products

Nishant’s research aimed to consolidate insights from these different bodies of knowledge and account for various contextual factors to provide a clearer, more comprehensive perspective for product managers and leaders. His goal was to help product managers understand how their role should adapt based on their specific organizational context and product type.

1. Market Research

As software product managers navigate the complex landscape of product development, market research emerges as a crucial first activity. Thorough market research in the problem space is fundamental to product success.

Understanding the Problem Space

The primary goal of market research is to validate whether a real problem exists and if customers truly care about solving it. This validation process requires intensive effort but sets the foundation for all subsequent product development activities. As Nishant emphasizes from his own research experience, investing time in understanding and defining the problem statement pays significant dividends later in the product lifecycle.

Organizational Differences in Market Research

How market research is conducted varies significantly between large and small organizations:

Large Companies:

• Have dedicated research departments
• Access to specialized agencies
• Multiple partnership resources
• Challenge: Information silos between departments
• Need for effective cross-functional communication to share insights

Small Companies:

• Limited budget for research
• Often lack dedicated research resources
• Product managers typically handle research directly
• Despite resource constraints, market research remains crucial for innovation success

The Impact of AI on Market Research

Modern market research has been transformed by artificial intelligence tools:

• Secondary research benefits significantly from tools like Perplexity.AI and ChatGPT
• Primary research, especially customer interviews, still requires direct human involvement
• AI tools complement but don’t replace the need for direct customer interaction

Best Practices for Product Managers

The key takeaway for software product managers is clear: invest heavily in market research regardless of organizational size or resources. A solid understanding of the problem space leads to:

• Better solution development
• Higher likelihood of customer adoption
• Increased chances of customers willing to pay for the solution
• More efficient product development process

2. Solution Identification

After establishing a clear understanding of the market through research, the next critical activity for software product managers is solution identification.

A Straightforward but Critical Process

Solution identification represents the transition from problem space to solution space, involving two key components:

• Developing solution concepts or prototypes
• Validating these potential solutions with customers

What makes this activity unique is its relative simplicity and consistency – regardless of organization size, industry, or methodology, the core process remains largely the same.

The Validation Component

The heart of solution identification lies in customer validation. Product managers must:

• Present potential solutions to customers
• Gather feedback on solution concepts
• Verify that proposed solutions effectively address the validated problem

Unlike other product management activities that vary significantly based on organizational context, solution identification maintains its fundamental approach whether you’re working at a startup or an enterprise company like MasterCard.

Building the Foundation for Product Vision

This activity serves as a bridge between problem validation and product vision development. By identifying and validating solutions before creating a product vision, product managers ensure they’re building on solid ground rather than assumptions.

The straightforward nature of solution identification shouldn’t diminish its importance – it’s a critical step that transforms validated problems into potential products. Its success relies heavily on the thoroughness of the preceding market research phase while setting the stage for subsequent product positioning and vision development.

3. Product Positioning

A Common Pitfall in Vision Development

Nishant highlighted a lesson from his early career: the mistake of creating a product vision before completing market research.

The Correct Sequence

The proper approach to product positioning involves:

1. Understanding the market space
2. Validating the problem
3. Assessing implementation feasibility
4. Developing the product vision

Components of Product Positioning

A well-positioned product should include:

• Clear product vision
• Initial feature set
• Value proposition
• Preliminary go-to-market strategy
• Concise documentation

Documentation and Modern Tools

Product positioning represents the first step in formal product documentation, serving as:

• A foundation for detailed technical breakdowns
• The basis for epics and stories in Agile tools like Jira
• A reference point for future development decisions

Generative AI has become valuable in this phase by:

• Enhancing PR (Product Requirements) documentation
• Suggesting features based on competitive analysis
• Providing narrative structure for product stories

Internal vs External Focus

While primarily focused on internal alignment, product positioning can serve both internal and external purposes:

• Internal: Getting leadership support and aligning teams
• External: Early market validation and customer feedback, similar to Amazon’s “working backwards” approach

This positioning phase creates the foundation for all subsequent product development activities, making it important to get right through proper sequencing and thorough documentation.

4. Product Roadmapping

Once product positioning is established, product managers move into the more action-oriented activity of roadmapping. This planning phase requires careful consideration of multiple contextual factors that significantly impact how roadmaps should be developed and managed.

Agile vs. Waterfall Approaches

The methodology used has a significant impact on roadmap development:

Agile Roadmapping

• Uses flexible roadmaps with varying confidence levels:
  • 3 months: Concrete, high-confidence plans
  • 6 months: Medium confidence projections
  • 9 months: Low confidence forecasting
• Allows for frequent adjustments based on market and customer demands
• Prioritizes adaptability over predictability

Waterfall Roadmapping

• Features more solid, predictable roadmaps
• Offers clearer communication of delivery dates to customers
• Less flexible to change

B2B vs. B2C Considerations

Market focus significantly influences roadmap development and release strategies:

B2B Products

• Less frequent releases
• Focus on core feature delivery
• May conflict with traditional Agile principles of frequent releases
• Emphasis on completing essential functionality before release

B2C Products

• More frequent releases
• Greater focus on user experience improvements
• Regular updates to address UI/UX issues
• Continuous enhancement approach

As Nishant points out from his experience at MasterCard, B2B products often don’t require the same frequency of releases as B2C products. Once core features are delivered and customers are satisfied, there’s less need for constant updates focused on minor UI/UX improvements.

Key Considerations for Product Managers

When developing product roadmaps, product managers should:

• Consider their specific business context (B2B vs. B2C)
• Align roadmap structure with development methodology
• Balance customer needs with development capabilities
• Maintain appropriate levels of flexibility based on market type

Understanding these contextual factors helps product managers create more effective roadmaps that better serve both their organization and their customers.

5. Requirements Engineering

Following roadmap creation, requirements engineering emerges as a crucial activity where product strategy meets technical execution. This phase highlights the important distinction between product manager and product owner roles, particularly in Agile environments.

Historical Evolution of Roles

Nishant provided valuable historical context about how these roles evolved:

• Pre-2001: Only product management existed
• 2001: Agile Manifesto introduced the Product Owner role
• Initial Scrum methodology focused solely on Product Owners
• Later frameworks like SAFe introduced clearer distinction between roles

Role Distinctions

Product Owner

• Specific to Agile methodologies
• Focuses on development team interaction
• Transforms leadership vision into engineering tasks
• Handles detailed story breakdown and sprint planning

Product Manager

• More outbound-focused role
• Works with cross-functional teams
• Handles market-facing responsibilities
• Manages broader product strategy

Organizational Impact

How these roles are implemented varies by organization size:

• Large Companies: Often maintain separate roles for Product Manager and Product Owner
• Small Companies: Usually combine roles into a single position
• Startups: Often rely on founders for product management with dedicated Product Owners

Key Challenges

The separation of roles can create:

• Communication gaps between external and internal focus
• Potential misalignment between strategy and execution
• Need for careful coordination between roles

As requirements engineering continues to evolve, organizations must carefully consider how to structure these roles to maintain effective product development while avoiding communication gaps and ensuring clear accountability.

6. Product Verification

In discussing product verification, Nishant highlighted how this crucial activity has transformed dramatically with the adoption of different development methodologies, particularly in the software industry.

Methodology Differences

Traditional Waterfall Approach

• Relied heavily on User Acceptance Testing (UAT)
• Testing conducted after complete development
• Single verification phase at project end
• Higher risk of late-stage discoveries

Modern Agile Approach

• Eliminates traditional UAT
• Implements continuous validation through sprint demos
• Customer feedback gathered during development
• Story-level validation within each sprint

Industry-Specific Considerations

The approach to product verification varies significantly by industry:

Software Industry

• Moved away from traditional UAT
• Embraces continuous validation
• Allows for rapid iterations
• Enables quick course corrections

Physical Products

• Still largely follows sequential processes
• Cannot easily deliver products in pieces
• Exploring ways to implement Agile principles
• Uses prototyping cycles for validation

Key Benefits of Modern Verification

The evolution to continuous verification offers several advantages:

• Earlier detection of issues
• Reduced risk of major problems late in development
• More frequent customer feedback
• Greater flexibility to make adjustments

As Nishant notes, this transformation in product verification represents a fundamental shift in how products are validated, moving from a single checkpoint to an ongoing process integrated throughout the development lifecycle.

7. Customer Insight

According to Nishant’s research, customer insight represents a fundamental shift in how product managers engage with their users throughout the product lifecycle. This shift moves from periodic customer engagement to continuous involvement at every stage of product development.

Evolution of Customer Engagement

Historically, customer engagement was limited to specific points in the process:

• Early problem validation
• Initial solution validation
• Requirements gathering
• Final product verification

Modern Approach: Continuous Customer Engagement

Today’s best practices involve customers at every stage:

Market Space Phase

• Problem validation
• Market need confirmation
• Initial concept feedback

Solution Space Phase

• Solution validation
• Feature prioritization
• Concept testing

Development Phase

• Value delivery verification
• Ongoing feedback collection
• Feature refinement

Production Phase

• Complete product evaluation
• User satisfaction surveys
• Continuous enhancement feedback

Key Message for Product Managers

Nishant emphasizes one critical point for all product managers: Stay close to customer as much as possible and as early as in the process. This continuous engagement ensures:

• Better alignment with customer needs
• Reduced risk of building unwanted features
• Faster identification of problems
• More successful product outcomes

In the software world particularly, this continuous customer insight loop enables ongoing product enhancement and ensures the product continues to meet evolving customer needs.

8. Financial Analysis

Nishant described financial analysis as one of the more challenging product management activities, with significant variations between different organizational contexts. This activity encompasses business case development, pricing strategies, and ongoing financial validation.

Organizational Differences

Small Companies

• Business cases often handled by founders or CEO
• Limited PM involvement due to confidentiality
• Focus typically on single product financials
• Less formal financial analysis processes

Large Companies

• Major responsibility for product managers
• Second only to cross-functional collaboration in complexity
• Requires coordination across multiple departments
• Complex pricing and costing calculations

Components of Financial Analysis

A comprehensive financial analysis includes:

• Product pricing strategy
• Engineering cost calculations
• Marketing expense projections
• Sales cost estimations
• Complete business case development

Evolution of Business Cases

Business case development is a continuous process that evolves through several stages:

Early Stage

• Total addressable market assessment
• Initial revenue projections
• Preliminary pricing strategy

Development Stage

• Cost identification with development teams
• Refined revenue projections
• Updated business case calculations

Market Testing

• Validation of initial projections
• Adjustment of revenue expectations
• Refinement of business case based on real data

Key Considerations

Product managers should understand that:

• Financial analysis is not a one-time activity
• Business cases require continuous refinement
• Market feedback may significantly impact initial projections
• Success metrics need regular validation and adjustment

As Nishant notes, while initial projections are important, the true test comes when products hit the market, often requiring significant adjustments to the business case based on real-world performance.

Conclusion

Software product management is far more nuanced and context-dependent than many realize. Nishant’s research-backed framework of 19 key activities provides clarity for product managers struggling to define their roles and responsibilities. Whether working in large enterprises or small startups, understanding how these activities adapt to different organizational contexts is necessary for success.

Today’s successful product managers must maintain ongoing dialogues with customers, constantly refine their business cases, and adapt their strategies based on real-world feedback. As the field continues to evolve, those who understand these core activities and how to adapt them to their specific context will be best positioned to create successful products that truly meet customer needs while delivering business value.

Useful links:

• Check out Nishant’s articles on Google Scholar:
  • The Software Product Manager’s Framework
  • The Impact of Generative AI in Software Product Management
  • The Role of AI Product Managers

Innovation Quote

“Innovation is a dynamic process that applies scientific thinking to transform customer problems into valuable business opportunities.”   – Nishant Parikh

Application Questions

1. How could you adapt your market research approach based on your organizational context? Consider the differences between how large and small companies conduct research – if you’re in a large organization, how could you better leverage existing research resources and break down silos? If you’re in a smaller organization with limited resources, how could you conduct meaningful research on a budget?
2. How would you describe the current balance between your product manager and product owner responsibilities? Whether these are separate roles in your organization or combined in your position, what steps could you take to improve the handoff between strategic product management and tactical development work, especially with the assistance of AI tools?
3. Looking at your current customer engagement practices, how could you evolve from periodic touchpoints to more continuous customer involvement throughout your product lifecycle? What specific opportunities exist in your product development process to gather more frequent customer feedback?
4. How could your team improve its approach to business case development and financial analysis? Consider how you currently update financial projections throughout the product lifecycle – what triggers could you establish for reviewing and refining your business case based on new market information or customer feedback?
5. How could you better align your roadmapping approach with your specific business context (B2B vs. B2C)? If you’re currently using an Agile methodology but serving B2B customers, what adjustments could you make to better balance frequent releases with your customers’ needs for stability?

Bio

Nishant A. Parikh is a dynamic professional with a diverse academic background and extensive experience in computer science and product management. Graduating with a Bachelor’s degree in Computer Science from Gujarat University in 2005 and an MBA from Webster University in 2020, Nishant combines technical expertise with business acumen. Currently serving as the Director in Product Management at Mastercard, he drives strategic direction and spearheads the development of innovative software solutions. Passionate about the field, Nishant has immersed himself in research at Capitol Technology University since 2022, exploring the challenges, trends, and solutions in product management. As an avid writer, he shares his insights, addressing the multifaceted issues faced by product managers. Nishant’s visionary leadership, industry knowledge, and commitment to innovation make him a driving force in shaping the future of software product management.

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.

Why product managers need to stop the stupid

Watch on YouTube

TLDR

Innovation expert Doug Hall reveals why most organizations struggle with innovation despite recognizing its importance. Through his experience running Eureka! Ranch and Dexter Bourbon Distillery, Hall discovered that successful innovation requires a bottom-up transformation focusing first on empowering frontline employees to fix inefficiencies (“stop the stupid”), then enabling middle managers to improve systems, and finally allowing leadership to pursue bigger strategic innovations. This three-level approach has shown to increase innovation value by 28% versus the typical 50% decline seen in traditional top-down approaches.

Key Topics:

• The Innovation Paradox: While 80% of CEOs say innovation is critical, only 20% believe their organizations are good at it
• Employee Innovation Barriers: 37% don’t see innovation as their job, 29% don’t know what to do about it
• Middle Management Challenge: Managers waste 3.5 hours daily dealing with mistakes and system flaws
• System vs. People Problems: 78% of issues come from flawed company systems, only 22% from employee mistakes
• The “Stop the Stupid” Approach: Start with empowering employees to fix immediate inefficiencies before pursuing larger innovations
• Three-Step Framework: 1) Teach innovation fundamentals, 2) Build confidence through early wins, 3) Develop systems thinking
• Measurable Impact: Organizations can achieve 4 improvement actions per employee per month
• Cultural Transformation: Focus on intrinsic motivation rather than external incentives

The Innovation Paradox in Organizations: Why Companies Struggle to Innovate

Doug shared that when you look at any survey of CEOs, more than 80% will say that innovation is crucial for their organization’s future success. However, when asked about their organization’s current innovation capabilities, the numbers flip dramatically – only about 20% believe their organizations are effectively innovating.

Doug illustrated this disconnect with a story from his consulting work. His team had just presented breakthrough solutions to a problem that a CEO had previously deemed impossible. Rather than excitement, the CEO’s response was, “Huh, wow. I guess you did figure it out. Now what do I do? I guess I gotta do it.” The disappointment in the executive’s voice revealed a deeper truth about organizational resistance to innovation.

This resistance manifests in various ways:

• Departments operating in silos resist changes that affect their established processes
• Middle managers hesitate to support innovations that might impact their performance metrics
• Frontline employees don’t see innovation as part of their role
• Existing systems and procedures inadvertently suppress new ideas

Doug explained why simply having good ideas isn’t enough. Successful innovation requires addressing deeper organizational dynamics and systems that either enable or inhibit change. As we explored in our conversation, resolving this paradox requires a fundamental shift in how organizations approach innovation, starting not with grand strategies but with empowering employees to make small, meaningful improvements in their daily work.

Breaking through this paradox requires recognizing that innovation isn’t just about generating new ideas – it’s about transforming how organizations think about and implement change at every level. This understanding forms the foundation for a more effective approach to organizational innovation.

The Problem with Traditional Innovation Approaches: Why Good Ideas Often Fail

Doug shared a startling insight from three separate studies that crystallizes why traditional innovation approaches often fall short. When organizations take an innovative idea into development, its forecasted value typically declines by 50% before launch.

The Innovation Value Loss Problem

A truly disruptive idea will challenge multiple departments in an organization. A genuinely innovative product might require:

• Changes to the supply chain
• Different manufacturing equipment
• New customer service processes
• Alternative sales channels
• Modified operational procedures

When these departmental challenges arise, organizations typically respond by compromising the original idea. As Doug put it, “It’s like you’re managing the death of ideas.” Each department makes small compromises to fit within existing systems until the final product barely resembles the original innovative concept.

The Hidden Organizational Barriers

Through our discussion, Doug revealed how organizational silos create powerful resistance to innovation:

Performance Metrics Conflict

Manufacturing departments hesitate to support innovations that might lower their productivity metrics.

Departmental Isolation

In many corporations, departments operate as separate units where promotion and income depend on making their individual department heads happy, not on supporting cross-functional innovation.

System Constraints

Standard Operating Procedures (SOPs) and existing systems often can’t accommodate truly innovative ideas without significant modification.

The Traditional Approach Trap

Most organizations try to overcome these barriers through:

• Special innovation teams
• Suggestion boxes
• Innovation training programs

However, Doug found these approaches usually fail because they don’t address the underlying system issues. Traditional innovation approaches weren’t working because they ignored a fundamental truth: most employees face daily operational challenges that make innovation feel like an extra burden rather than an opportunity.

A New Framework: Starting with Employee Engagement

Understanding the Real Barriers to Innovation

The data Doug shared revealed two primary barriers preventing employee participation in innovation:

• 37% of employees don’t see innovation as part of their job
• 29% don’t know what to do even if they wanted to innovate

These statistics point to a clear problem: organizations aren’t making innovation accessible and actionable for their employees.

The “Stop the Stupid” Revolution

This insight led to a radical shift in approach. Instead of pushing employees to create breakthrough innovations, Doug’s team started by addressing the daily frustrations and inefficiencies that drain employee energy and enthusiasm.

For example, at his distillery, while Doug was excited about developing new custom bourbon experiences, his employees were more concerned about immediate challenges like:

• Back pain from lifting heavy crates
• Inefficient paperwork processes
• Workflow bottlenecks
• Equipment issues

Building Momentum Through Small Wins

The power of this approach became clear as employees started solving these immediate problems. By focusing on improvements within their sphere of influence, employees:

• Gained confidence in their problem-solving abilities
• Developed practical innovation skills
• Experienced intrinsic satisfaction from making meaningful improvements
• Built collaborative relationships across departments

From Frustration to Innovation

This employee-first approach transforms how organizations think about innovation. Rather than treating innovation as a special initiative, it becomes part of everyone’s daily work. The results speak for themselves – organizations implementing this approach see an average of four improvement actions per employee per month.

More importantly, this foundation of employee engagement creates an environment where larger innovations can thrive. When employees feel empowered to solve problems and improve systems, they become natural allies in implementing bigger strategic changes.

The Three-Level Organizational Transformation: Creating a Culture of Innovation

Through his work at Eureka! Ranch and his own experiences running a bourbon distillery, Doug has developed a practical framework for transforming how each level contributes to innovation.

Level 1: Frontline Employees

The transformation begins at the front lines, where employees are closest to daily operations. Instead of imposing top-down innovation mandates, organizations need to:

• Provide basic innovation and problem-solving tools
• Set clear boundaries for decision-making authority
• Support immediate improvements within teams
• Celebrate small wins that eliminate inefficiencies

Level 2: Middle Managers

One of the most striking statistics Doug shared was that middle managers waste an average of 3.5 hours daily dealing with problems. Breaking this down:

• 78% of issues stem from flawed company systems
• 22% come from employee mistakes
• Most time is spent on reactive problem-solving

The solution involves transforming middle managers from reactive problem-solvers into system improvers. This means:

• Teaching managers to identify system-level issues
• Empowering them to implement systemic solutions
• Shifting focus from blame to improvement
• Creating clear protocols for change implementation

Level 3: Leadership

At the leadership level, the transformation focuses on enabling rather than directing innovation. Leaders need to:

• Set appropriate vision and strategy
• Avoid compromising innovation goals to fit current capabilities
• Support system-wide improvements
• Remove organizational barriers to change

The Power of Alignment

When these three levels work together, organizations can achieve remarkable results. For example, one B2B company Doug worked with saw their marketing department transform from one of the lowest-rated departments to generating 100 times more leads within three months of implementing this approach.

The key is understanding that each level plays a distinct but interconnected role in innovation:

• Frontline employees drive immediate improvements
• Middle managers enable system-level changes
• Leaders create the environment for transformation

This three-level alignment creates a foundation for sustainable innovation, where improvements build upon each other rather than getting stuck in organizational resistance.

Implementation Framework: Making Innovation Work at Every Level

After decades of helping companies innovate and running his own bourbon distillery, Doug has distilled his process down to fundamental steps that any organization can follow.

Step 1: Teach Innovation Fundamentals

The first step focuses on giving everyone the basic tools they need to innovate. Doug has simplified complex innovation principles into accessible tools. This includes:

• Basic problem-solving techniques
• Simple formats for communicating ideas
• Clear methods for identifying system issues
• Frameworks for evaluating potential improvements

Step 2: Build Confidence Through Early Wins

The second step involves what Doug calls the “stop the stupid” phase. Organizations should:

• Focus first on obvious inefficiencies
• Address longstanding employee frustrations
• Create visible improvements quickly
• Celebrate small victories

For example, at Doug’s distillery, they transformed a painful box-lifting process by simply redesigning how boxes were assembled around products rather than lifting products into pre-made boxes.

Step 3: Develop Systems Thinking

The final step moves from individual improvements to systematic change. This involves:

Making Systems Visible

• Identify key organizational systems
• Map process flows and dependencies
• Understand cross-departmental impacts

Focusing on Key Metrics

• Choose single, clear metrics for each system
• Avoid conflicting performance measures
• Track improvement impacts systematically

Understanding Error Types

• Distinguish between system errors (94%) and worker errors (6%)
• Focus on fixing processes rather than blaming individuals
• Address root causes rather than symptoms

Creating Sustainable Change

What makes this framework powerful is its focus on building internal capability rather than relying on external consultants or temporary initiatives. Organizations implementing this approach can expect:

• Four improvement actions per employee per month
• 28% increase in innovation value (versus traditional 50% decline)
• Higher employee engagement and satisfaction
• Sustained innovation capability

Results and Impact: Measuring Innovation Success

Doug described the tangible results organizations achieve when they transform their approach to innovation. The metrics he shared demonstrate why this bottom-up, system-focused approach delivers dramatically different outcomes from traditional innovation methods.

Measurable Transformation

The contrast in results is striking:

Metric Traditional Approach New Framework Innovation Value 50% decline during development 28% increase in value Employee Engagement Limited participation 4 improvements per person monthly Implementation Success Ideas compromised to fit systems Systems improved to support ideas

Real-World Success Stories

The impact extends across various types of organizations:

• A B2B company’s marketing department increased lead generation 100x in three months
• Manufacturing teams eliminated chronic efficiency problems
• Service organizations dramatically improved customer satisfaction
• Doug’s own distillery became one of the fastest-growing and most innovative in the industry

Cultural Transformation

Beyond the numbers, organizations experience fundamental shifts in how they operate:

• Employees become naturally proactive in solving problems
• Managers spend less time fighting fires
• Departments collaborate more effectively
• Innovation becomes part of daily work rather than a special initiative

Long-Term Benefits

Organizations implementing this approach see sustained improvements in:

• Employee retention and satisfaction
• Operational efficiency
• Innovation implementation success
• Cross-functional collaboration
• Strategic capability

Getting Started

This transformation doesn’t require massive resources or restructuring. Instead, it starts with simple steps:

• Empower employees to solve problems within their sphere
• Give managers tools to improve systems
• Create clear boundaries for decision-making
• Focus first on eliminating obvious inefficiencies

The key is starting with small, achievable improvements that build confidence and capability for bigger innovations. As organizations prove they can successfully implement positive changes, they create momentum for larger transformations.

Conclusion

Transforming organizational innovation isn’t about generating more ideas or launching special initiatives. It’s about creating an environment where positive change can happen naturally at every level. By starting with employee-driven improvements, building middle management capabilities, and enabling leadership to pursue bigger strategic innovations, organizations can break free from the traditional innovation paradox where great ideas lose value during implementation.

The path forward is clear: empower employees to “stop the stupid” in their daily work, give managers tools to improve systems rather than just fight fires, and allow leaders to set ambitious goals without compromising them to fit current capabilities. When organizations align these three levels and follow a systematic implementation framework, they can achieve the holy grail of innovation – sustained, positive change that builds value rather than eroding it. The result isn’t just better products and services, but a more engaged workforce and a more adaptable organization ready to tackle future challenges.

Useful links:

• Check out Doug’s book, Proactive Problem Solving, available December 10th, 2024, on Amazon or at an independent bookseller near you
• Learn more about Eureka! Ranch
• Learn more about Dexter Bourbon
• Learn more about PDMA

Innovation Quote

“Stop the Stupid.”  – Doug Hall

Application Questions

1. How could you adapt the “stop the stupid” approach to your product development process? Consider what daily inefficiencies or frustrations your team encounters that, if eliminated, would free up energy and enthusiasm for innovation.
2. How could your team reframe its innovation strategy to focus on building confidence through small wins before tackling larger transformational projects? What would be the equivalent of “fixing the broken box” in your product organization?
3. When you think about your last few product innovations that lost value or momentum during development, how much of that decline was due to system constraints versus individual mistakes? How could you start addressing those systemic barriers?
4. How could you empower your product team members to identify and solve problems within their sphere of influence? What boundaries and decision-making frameworks would you need to put in place to make this successful?
5. How could you apply the concept of “common cause vs. special cause” errors to your product development process? Consider where your team might be blaming individuals for what are actually system-level problems.

Bio

Doug Hall is on a relentless, never-ever ending quest to enable everyone to think smarter, faster and more creatively.  His learning laboratories over the past 50+ years have included 10 years at Procter & Gamble where he rose to the rank of Master Inventor shipping a record 9 innovations in a 9 months and 40+ years as an entrepreneur including as founder of the Eureka! Ranch in Cincinnati Ohio – where he and his team have invented and quantified over 20,000 innovations for organizations such as Nike, Walt Disney, USA Department of Commerce, American Express and hundreds more.  Doug’s newest book,  out in December, PROACTIVE Problem Solving, was inspired by his experiences founding and leading a fast-growing manufacturing company, the Brain Brew Bourbon Distillery. Despite the COVID pandemic, Brain Brew grew from shipping a few thousand cases to shipping over 100,000 cases a year by enabling employee engagement. 

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.

A custom ChatGPT model that helps accelerate product innovation

Watch on YouTube

TLDR

In this episode, I interview Mike Hyzy, Senior Principal Consultant at Daugherty Business Solutions. He explains how to conduct an AI-powered design sprint that transforms product concepts into clickable prototypes in just hours instead of weeks. Using a custom ChatGPT model combined with collaborative team workshops, product teams can rapidly move from initial customer insights to validated prototypes while incorporating strategic foresight and market analysis.

Key Topics:

• Strategic foresight approach to product development, focusing on customer needs 2-5 years ahead
• Triple diamond decision framework for analyzing problems, customers, and markets
• Integration of team collaboration, AI assistance, and external validation
• Rapid wireframe and UI design generation using ChatGPT and DALL-E
• Creation of interactive prototypes using CodePen for immediate testing
• Custom AI model prompts and best practices for design sprint facilitation
• Early go-to-market strategy integration in the product development process
• Practical implementation of AI tools to accelerate product innovation

Introduction

Imagine taking a product concept from initial customer insight to clickable prototype in just a few hours. That’s exactly what I witnessed at PDMA’s recent Inspire Innovation Conference, where Mike Hyzy demonstrated a groundbreaking approach to AI Design Sprints that’s revolutionizing product development acceleration.

By combining strategic foresight, a custom ChatGPT model, and collaborative workshop techniques, Mike led how six teams to achieve what typically takes weeks of work in just under three hours. As a product management professor and practitioner, I’ve seen many methodologies for speeding up innovation, but this approach was different – transforming ChatGPT into a virtual team member that accelerates every phase of the development process, from initial concept through digital product prototyping, while ensuring teams focus on solving tomorrow’s customer needs rather than just today’s problems.

In this episode, Mike will take us through the steps he led product teams through during his AI Design Sprint workshop.

The Critical Role of Strategic Foresight in Product Innovation

At the beginning of the workshop, Mike explained the importance of strategic foresight. He emphasized a fundamental shift in how we should approach product development. Instead of focusing solely on today’s customer problems, product teams need to look 2-5 years into the future. This strategic foresight approach to product development isn’t just about making predictions – it’s about understanding how customer needs and market conditions will evolve over time.

Mike shared a sobering statistic that highlights why this forward-thinking approach matters: 42% of companies cite “no market need” as their main reason for failure. This happens when teams solve today’s problems without considering how those needs might change by the time their product actually launches. As I’ve seen in my own product management experience, the traditional product development cycle can take months or even years. By the time we launch, the market may have moved on from the problem we originally set out to solve.

The Triple Diamond Framework Components

To address this challenge, Mike introduced the Triple Diamond Decision Framework, a structured approach that helps teams look ahead while making concrete decisions. Here’s how the framework breaks down:

1. Jobs to be Done Diamond
   • Explore future customer problems and needs
   • Identify emerging pain points
   • Converge on the most critical future needs
2. Customer Analysis Diamond
   • Map potential future customer segments
   • Analyze evolving customer behaviors
   • Focus on the most promising future customers
3. Market Analysis Diamond
   • Investigate market trends and opportunities
   • Evaluate potential market sizes
   • Select the most viable future markets

What makes this framework particularly powerful in an AI design sprint is how quickly teams can move through each diamond. Mike explains that traditional market analysis might take weeks of research, but with AI assistance, teams can gather initial market insights, including total addressable market (TAM) and serviceable market data, in minutes rather than weeks.

The key to success with this approach lies in the balance between divergent and convergent thinking at each stage. Teams start by thinking broadly about all possible needs, customers, or markets, then use data and insights to narrow down to the most promising opportunities. Mike emphasizes that this isn’t about rushing through the process – it’s about using AI tools to accelerate the research and analysis phases so teams can spend more time on creative problem-solving and validation.

This strategic foresight foundation sets the stage for the entire AI design sprint process. By starting with a future-focused mindset and using AI to accelerate market research, teams can avoid the common trap of building products for yesterday’s problems while ensuring they’re creating solutions that will still be relevant when they reach the market.

Three Key Elements That Power AI-Powered Design Sprints

In this episode, Mike outlines how the success of an AI design sprint relies on the synergy between three core elements. Rather than simply replacing traditional methods with AI tools, this approach creates a powerful combination of human creativity, artificial intelligence, and real-world validation.

1. Team Collaboration

The foundation of every successful AI design sprint starts with effective team collaboration. As I observe during the workshop, the magic happens when small groups work together to explore ideas and challenge assumptions. Mike explains that having multiple perspectives around the table leads to insights that neither AI nor individual team members would discover alone.

For example, during our workshop session, when one team member mentioned the need for pricing tiers in their product concept, it triggered a deeper discussion about what would motivate users to upgrade from a free version to a paid tier. This kind of nuanced thinking emerges naturally from team interactions.

2. AI Tool Integration

The integration of AI tools, particularly through Mike’s custom ChatGPT model, serves as a catalyst for rapid product development. Here’s how AI enhances the process:

• Accelerates market research and data gathering
• Identifies potential blind spots in thinking
• Suggests alternative approaches and solutions
• Generates rapid prototypes and iterations
• Provides structured frameworks for decision-making

What makes this element particularly powerful is how the AI tool becomes like another team member, offering insights and suggestions while the human team maintains control over creative decisions and strategic direction.

3. External Validation

The third critical element involves getting feedback from outside the immediate team. During the workshop, Mike structures this through team-to-team interactions, where each group presents their concepts to another team for feedback. In a real-world setting, this would involve:

Validation Level Purpose Timing Initial Feedback Quick reality check on concepts Early in the sprint Feature Validation Confirm priority features Mid-sprint Prototype Testing User experience validation Late sprint

What makes this three-element approach particularly effective is how each component complements the others. The team’s creative energy feeds into the AI tool’s capabilities, while external validation helps refine and improve the outputs from both human and AI contributions.

Mike emphasizes that the real power comes from the rapid iteration possible when these three elements work together. Teams can quickly move from initial concept to validated prototype, with each element providing different types of input and validation along the way. This combination helps ensure that the final product concept isn’t just technically feasible but also genuinely meets market needs.

Breaking Down the AI Design Sprint Process

In this episode, Mike walks us through the step-by-step process of conducting an AI-powered design sprint. In his workshop, teams used Mike’s custom ChatGPT model, AI Design Sprint. What’s particularly impressive is how this approach compresses what traditionally takes weeks into just a few hours, while still maintaining the rigor needed for effective product development.

Discovery Phase

The discovery phase sets the foundation for the entire sprint. Mike structures this phase into distinct segments, each building on the previous one:

1. Initial Idea Generation

The first prompt for ChatGPT tells it that you’re going to use the triple diamond decision framing to explore needs, customers, and markets. You’ll work through it one stage at a time, starting with the discovery stage. It directs ChatGPT to read your input and ask corresponding questions. You’ll finish one section before moving on to the next one.

The AI tool supports this process by:

• Providing prompting questions to spark discussion
• Suggesting potential angles teams might have missed
• Organizing ideas into structured formats
• Documenting key insights for later reference

During the workshop, my team worked on the question, How do I use the space I have in my yard to create a garden? During the Discovery phase, once we told ChatGPT our initial ideas, its asked us the questions:

• Who would benefit from this product?
• What are their needs?

We typed our answers into ChatGPT, which used them to build a customer persona.

2. Needs Analysis

Once initial ideas are captured, teams dive deeper into understanding customer needs. The AI assistant helps accelerate this process by:

Analysis Type AI Support Team Input Customer Pain Points Market research synthesis Real-world experience validation Unmet Needs Pattern recognition Context and nuance addition Future Needs Trend analysis Industry expertise application

Definition Phase

Moving into definition, teams begin to shape their solution. Mike shows how the AI tool helps teams:

Synthesize Key Insights

• Compile user insights from discovery
• Identify core opportunities
• Define essential functionality

Prioritize Features

• Create MVP feature sets
• Identify secondary features
• Tag nice-to-have additions

Development Phase

The development phase is where the AI-powered approach really shines. Mike demonstrates how teams can rapidly move through:

1. Wireframing

Using the AI tool’s connection to DALL-E, teams can generate wireframes for each feature. What’s remarkable is how quickly teams can iterate on these designs. Mike shows us how to:

• Generate individual screens for each feature
• Refine layouts based on team feedback
• Maintain consistency across the interface

2. UI Design

The sprint moves from wireframes to more detailed UI designs. Teams can specify:

• Color schemes (like “Earth tones similar to Whole Foods”)
• Design patterns (such as Google’s Material Design)
• Typography and spacing preferences

3. Interactive Prototype

The final step involves creating a clickable prototype using:

• HTML generated by the AI tool
• CSS for styling
• JavaScript for interactivity

Mike shows how teams can use CodePen as a free platform to bring these elements together into a working prototype. This allows for immediate testing and validation of the user experience.

What makes this process particularly valuable is its flexibility. While Mike guides us through all these steps, he emphasizes that teams can adjust the focus based on their specific needs. Some teams might spend more time in discovery, while others might need to iterate more on the prototype phase.

Best Practices for Implementing AI Design Sprints

Drawing from his experience leading multiple AI-powered design sprints, Mike shares key tips and strategies to help teams maximize the value of this approach. These implementation guidelines ensure teams can effectively combine human creativity with AI capabilities while maintaining focus on creating valuable products.

AI Interaction Best Practices

Mike emphasizes the importance of structuring your interaction with AI tools effectively. Here’s how to get the best results:

Practice Purpose Example One Stage at a Time Maintain focus and clarity Complete market analysis before moving to features Clear, Specific Prompts Get targeted responses “Create separate wireframes for each feature” Regular Progress Saving Preserve work across sessions Save summaries after each major phase

Prototype Development Guidelines

When it comes to creating prototypes, Mike shares several key strategies:

Wireframe Creation

• Request separate screens for each feature
• Be specific about design preferences
• Iterate based on team feedback

Code Structure

• Keep HTML, CSS, and JavaScript organized
• Use CodePen for quick testing
• Maintain consistent naming conventions

Feedback Integration

• Capture team input immediately
• Make rapid adjustments
• Test changes in real-time

Go-to-Market Integration

One of Mike’s most valuable insights is the importance of thinking about go-to-market strategy early in the process. He recommends:

• Developing marketing messages during the sprint
• Creating 30-second elevator pitches
• Testing value propositions with other teams
• Planning launch strategies alongside development

Time Management Tips

To keep the sprint moving efficiently, Mike suggests:

• Use 10-minute focused sessions for each activity
• Set clear objectives for each sprint segment
• Build in quick breaks between major phases
• Allow flexibility for deeper exploration when needed

Common Pitfalls to Avoid

Through his experience, Mike has identified several challenges teams should watch out for:

• Getting stuck in endless iterations without moving forward
• Relying too heavily on AI without human insight
• Skipping validation steps to save time
• Forgetting to save progress between sessions

What I find particularly valuable about Mike’s approach is how he balances efficiency with effectiveness. While the AI-powered sprint can move quickly, he ensures teams don’t sacrifice quality for speed. He emphasizes that the goal isn’t just to create a prototype faster – it’s to create a better product by allowing teams to explore more options and gather more feedback in less time.

Making AI Design Sprints Work: Key Success Factors

In this episode, Mike shares the critical elements that determine the success of an AI-powered design sprint. As I observe during the workshop, these factors make the difference between simply using AI tools and truly transforming the product development process.

Team Dynamics

The human element remains crucial even in AI-powered sprints. Mike identifies several key team factors:

Factor Impact Implementation Balanced Input Ensures diverse perspectives Mix of technical and business roles Cross-functional Expertise Enriches solution development Include design, tech, and product skills Collaborative Spirit Drives rapid iteration Encourage building on others’ ideas

Strategic Foresight Integration

Mike emphasizes that successful teams consistently maintain a future focus throughout the sprint:

Market Evolution

• Consider technological trends
• Anticipate changing customer needs
• Factor in competitive landscape shifts

Solution Longevity

• Design for future scalability
• Plan for evolving user expectations
• Build in adaptation capabilities

Validation Approach

Effective validation proves crucial for sprint success. Mike recommends:

• Test concepts with other teams during the sprint
• Use AI insights to challenge assumptions
• Maintain a balance between human feedback and AI analysis
• Document validation findings for future reference

Tool Mastery

Understanding how to effectively use AI tools makes a significant difference. Mike shares these best practices:

• Start with simple prompts and build complexity
• Save successful prompts for future use
• Learn from how the AI responds to different input styles
• Maintain a library of effective prompt patterns

Outcome Focus

Successful teams keep their eyes on meaningful outcomes:

Outcome Type Success Indicator Product Concept Clear value proposition validated by feedback Market Fit Identified target market with validated need Technical Feasibility Realistic implementation path defined Business Viability Compelling business case established

What makes these success factors particularly powerful is their interconnected nature. Mike demonstrates how each element supports the others, creating a robust framework for innovation. The combination of human creativity, AI capabilities, and structured validation helps teams not just move faster, but also make better decisions throughout the product development process.

Real Results: Workshop Outcomes and Next Steps

In this episode, Mike shares the impressive results from the PDMA workshop, demonstrating how AI-powered design sprints can transform product development. The outcomes show both the immediate value and long-term potential of this approach.

Workshop Achievements

The teams in the workshop accomplished several key deliverables in under three hours:

Deliverable Traditional Timeline Sprint Timeline Market Analysis 2-3 weeks 15-20 minutes Feature Definition 1-2 weeks 30 minutes UI Design 1-2 weeks 45 minutes Interactive Prototype 1-3 weeks 60 minutes

Practical Applications

Mike explains how teams can apply this methodology in different contexts:

Startup Environment

• Rapid concept validation
• Quick pivot capability
• Efficient resource use

Enterprise Setting

• Innovation acceleration
• Cross-team collaboration
• Risk reduction through rapid testing

Product Enhancement

• Feature validation
• User experience improvement
• Competitive response

Next Steps for Implementation

For teams looking to implement AI-powered design sprints, Mike recommends:

• Start with a small, focused project to build team confidence
• Use the provided custom ChatGPT model as a starting point
• Document and adapt the process for your organization’s needs
• Build a library of successful prompts and approaches

Long-term Benefits

Beyond the immediate sprint outcomes, Mike highlights several lasting advantages:

• Improved team collaboration patterns
• Enhanced decision-making processes
• Better integration of strategic foresight
• More efficient resource utilization
• Faster time to market for new products

Future Possibilities

Looking ahead, Mike sees several exciting possibilities:

• Integration with more sophisticated AI tools
• Enhanced prototype generation capabilities
• Improved market analysis accuracy
• More automated validation processes

What makes these outcomes particularly compelling is their practical nature. As I observe during the workshop, teams aren’t just creating theoretical concepts – they’re developing viable product solutions that could move directly into development. The combination of speed and quality demonstrates why AI-powered design sprints represent a significant evolution in product development methodology.

Mike emphasizes that while the technology is impressive, the real value comes from how it enables teams to spend more time on creative problem-solving and less time on routine tasks. This shift in focus helps ensure that the increased speed of development doesn’t come at the expense of innovation or product quality.

Conclusion

As this episode demonstrates, AI-powered design sprints represent a significant leap forward in product development methodology. Mike’s approach successfully combines the creative power of human teams with the efficiency of AI tools, enabling product managers to compress weeks of work into focused sessions while maintaining high-quality outcomes. The custom ChatGPT model he’s created, coupled with structured team activities and validation steps, provides a practical framework that any product team can implement.

What makes this methodology particularly valuable is its focus on future needs and market evolution. Rather than simply accelerating existing processes, these AI-powered design sprints help teams create better products by enabling rapid iteration, comprehensive market analysis, and meaningful validation. As Mike shows us, the future of product development isn’t just about working faster – it’s about working smarter by leveraging AI to enhance human creativity and strategic thinking.

Useful links:

• Check out Mike’s Custom AI Model for the AI Design Sprint
• Connect with Mike on LinkedIn
• Check out Mike’s website
• Check out Mike’s Substack
• Check out Mike’s book, Gamification for Product Excellence
• Learn more about PDMA

Innovation Quote

“Product innovation is about having the foresight, which is not about creating solutions for problems that we know exist today, but about anticipating challenges and opportunities that might emerge in the future.” – Mike Hyzy

Application Questions

1. How could your team integrate strategic foresight into your current product development process? Consider which aspects of your market and customer needs are most likely to evolve in the next 2-5 years.
2. How could you use AI tools to accelerate the parts of your product development process that currently take the most time? Think about areas like market research, competitive analysis, or prototype creation.
3. Looking at your most recent product development initiative, how could the triple diamond framework have helped you better validate the market need before investing in development?
4. How could your team structure a compressed design sprint using these AI-powered techniques while still ensuring you get meaningful validation from actual customers or stakeholders?

Bio

Mike Hyzy is a senior principal consultant at Daugherty Business Solutions.  He advises executive teams on AI, innovation and strategic product management, combining data-driven insights with cutting-edge technology to drive transformational change. Previously he has been a product management consultant and has held senior product management roles. 

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.

How product managers can move from ideas to action

Watch on YouTube

TLDR

In this episode, I speak with Atif Rafiq about how senior product leaders approach strategy development and execution. Atif brings valuable insights from a recent PDMA executive workshop where leaders discussed their real-world challenges with strategic decision making and innovation strategy.

Key topics from our discussion:

• Main challenges product leaders face when developing strategy
• A practical framework for exploring product opportunities
• How AI tools can help with strategic decision making
• The importance of early-stage product work
• Ways to improve alignment across organizations
• Real-world example using a subscription service concept

Introduction

In this episode, I’m interviewing Atif Rafiq, who recently led an executive workshop at the PDMA conference, where senior leaders discussed challenges they face, including navigating ambiguity and making decisions with more clarity. In this episode, he shares some insights from that workshop and his experience in product leadership. Atif has spent 25 years working in both Silicon Valley and Fortune 500 companies, including leadership roles at Amazon, McDonald’s (as their first Chief Digital Officer), Volvo, and MGM Resorts. He has developed a systematic approach to problem-solving that forms the basis of his book, Decision Sprint: The New Way to Innovate into the Unknown.

Key Challenges in Strategic Product Leadership

During our discussion, Atif identifies three main challenges that senior leaders face when developing and implementing product strategy:

1. Alignment Challenges

Organizations often struggle to get everyone moving in the same direction:

Challenge Area Impact Common Problem Problem Understanding Teams interpret issues differently Resources going to wrong priorities Stakeholder Views Departments focus on different goals Competing objectives and metrics Customer Focus Too much focus on one perspective Missing business or operational needs

2. Input and Collaboration Issues

Atif explains that product leaders often struggle to gather useful input and work effectively across teams. Common problems include:

• Meetings that don’t collect all needed information
• Difficulty managing different department viewpoints
• Challenges combining input from multiple sources
• Time pressures that cut short important discussions

3. Experimentation Challenges

While many organizations value testing ideas, Atif notes several common issues:

• Starting experiments before understanding the problem
• Running tests without clear goals
• Weak links between test results and business strategy
• Racing through testing without proper planning

Purposeful Exploration: A Better Approach

In our discussion, Atif introduces “purposeful exploration” – a structured way to investigate and test product opportunities. This method helps organizations find balance between rushing into solutions and getting stuck in endless discussions.

Key Elements of Purposeful Exploration

Element Purpose Activities Problem Definition Get clear about the challenge Talk to stakeholders, analyze data, study market Question List Identify what we need to learn Team workshops, AI-assisted research Testing Strategy Check our assumptions Small pilots, focused tests, data gathering Making Sense of Results Draw useful conclusions Analysis, recommendations, team alignment

Real-World Example: Coffee Subscription Service

During the workshop, Atif walked the senior leaders through an exercise to get buy-in for a coffee subscription service at McDonald’s. Three different groups crafted a problem statement related to this idea and then identified key questions they needed to answer. This example demonstrates how to balance different business needs when exploring a new product idea.

Strategic Questions to Consider

The teams identified key questions, including:

Business Area Key Questions What to Explore Revenue Impact Will subscribers visit more often and buy food? Visit patterns, additional purchases Operations Can stores handle increased coffee orders? Service speed, staff needs Customer Value How does this work with loyalty programs? Digital integration, easy redemption Business Model What makes this profitable? Pricing levels, program guidelines

Next, each group shared their questions with the others, and they used AI to compare the breadth and depth of the questions.

Key Insights from the Example

• Success depends on getting customers to visit more and buy additional items
• Testing needs to happen in stages to manage operational complexity
• Digital platform integration affects customer adoption
• Program rules must work for both customers and the business
• Workshop participants found they could work much faster when combining team expertise with AI capabilities

Upstream Product Work

Atif emphasizes the importance of early work—the foundation-setting activities before product development starts. He notes that this phase often determines success or failure.

Essential Early Activities

Activity Purpose Result Problem Definition Get clear about the challenge Shared understanding Question List Identify unknowns Focus areas Team Alignment Build agreement Clear direction Resource Planning Ensure enough support Available resources

Ritual: An AI Tool to Support Strategic Decision-Making

During our discussion, Atif introduces Ritual, a tool he and his team developed to support strategic decision-making processes. Ritual combines workflow management with AI capabilities to help teams move from initial ideas to solid recommendations. The tool reflects Atif’s experience leading organizations through strategic decisions, incorporating features that support building and running explorations, gathering team input, and producing strategy documents.

Workshop participants using Ritual noticed significant improvements in their exploration process, with AI assistance helping teams work up to ten times faster while maintaining quality. The tool helps teams develop strategy memos and recommendation documents that include context, problem statements, goals and constraints, key issues, analysis insights, and final recommendations. While Atif emphasizes that good strategic thinking remains fundamental, tools like Ritual can help teams work more efficiently and maintain consistency in their strategic exploration process.

Putting It Into Practice

Atif recommends these steps for using these ideas:

1. Define Problems Well

• Write down the challenge clearly
• Get team agreement on the problem
• Choose how to measure success

2. Plan Your Exploration

• List key questions
• Design useful tests
• Set clear deadlines

3. Use Tools Wisely

• Add AI where it helps
• Keep human oversight
• Record what you learn

4. Build Team Skills

• Train people in new methods
• Create clear processes
• Set up ways to learn and improve

Conclusion

Throughout our conversation, Atif emphasizes that product strategy works best when teams balance thorough analysis with timely action. The methods and frameworks we discussed can help product leaders work through strategic challenges more effectively.

Remember that improving how you make strategic decisions takes time and practice. Start with small changes, see what works, and adjust your approach based on results.

Useful links:

• Check out Atif’s book, Decision Sprint
• Check out Ritual, an AI tool for Purposeful Exploration
• Connect with Atif on LinkedIn and sign up for his Rewire newsletter
• Learn more about the Product Development and Management Association (PDMA)

Innovation Quote

“There are one-way doors and two-way doors.” – Jeff Bezos

Application Questions

1. How could your team spend more time understanding problems before jumping to solutions? What process changes would this require?
2. What steps could your team take to balance customer needs with business requirements when exploring new opportunities?
3. How might your team use AI tools to speed up the early stages of product development while maintaining quality?
4. What changes would help your organization align different departments when exploring new opportunities?

Bio

Atif Rafiq invented a system for problem-solving based on his 25-year career spanning Silicon Valley and the Fortune 500. His ideas proved so impactful as a competitive advantage that they sped his rise at Amazon and later to C-suite positions he held at companies, including McDonald’s as their first Chief Digital Officer, and at Volvo and MGM Resorts.

He wrote DECISION SPRINT: The New Way to Innovate into the Unknown and Move from Strategy to Action based on what he learned leading organizations from a product perspective.

 

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.

A framework for product launch success

Watch on YouTube

TLDR

In this episode of Product Mastery Now, I interview James Whitman, author of LAUNCH Code and founder of Growth Guidepost. James shares insights from his research studying companies that consistently launch successful products. His LAUNCH Code framework offers a practical approach to product launch management that any organization can implement.

Key Topics Covered:

• The LAUNCH Code: six essential components of successful product launches
• How AI is changing product launches and team dynamics
• Practical strategies for cross-team collaboration
• The Tranche Model for reducing launch risks
• Building a culture that supports successful launches

Understanding the Launch Code Framework

James explains that Launch Code emerged from studying public companies that grew successfully through their product portfolios. These organizations share common practices that form the foundation of the LAUNCH framework:

Component Description Listen to clients Gather and analyze customer feedback systematically Assess the opportunity Evaluate market potential and strategic fit objectively Unify the team Build alignment across departments Navigate the launch Execute go-to-market activities strategically Control the risks Manage and reduce potential issues Hone the process Improve launch practices continuously

Current Challenges in Product Launches

The AI Impact

Organizations are adapting to rapid changes in how AI affects product launches. James shares that many teams are now working with their second or third generation of AI tools, particularly in sales and marketing. This raises important questions about balancing human and machine roles in the launch process and keeping employees engaged when AI takes over some of their work.

Financial Landscape Changes

A significant shift has occurred in venture funding, with more money moving toward AI investments. James describes working with one organization that had five different sales leaders in 18 months due to these pressures. This example revealed a deeper structural issue: The company needed to move up-market from a commoditized position to remain competitive.

Making Better Launch Decisions

James points out common decision-making problems in product launches. He describes what he calls the “Your PowerPoint is better than mine, but you’re wrong” syndrome – where strong presentation skills can override better strategic choices. Instead, organizations need to:

• Focus on finding the best solution rather than winning arguments
• Challenge assumptions constructively
• Build collective ownership of decisions
• Create space for different perspectives

Building Cross-Functional Success

A key insight from our conversation is how product launches require coordination across departments. James shares an example where changing product strategy meant completely rethinking the sales approach. The company needed salespeople who could sell complex solutions instead of commoditized products, showing how product decisions affect the entire organization.

Creating Common Language

James emphasizes the importance of vocabulary in cross-team work. For example, he notes that “discovery” means different things to sales and product teams:

• Sales discovery: Understanding customer needs during the sales process
• Product discovery: Researching market problems and solutions
• Market discovery: Understanding broader market trends and opportunities

Using clear, shared terms helps prevent misunderstandings and builds better collaboration.

Building the Right Culture

Culture plays a vital role in launch success. James points to Atlassian as an example of intentional culture-building that supports product success. Their approach includes:

• Creating systems for cross-team collaboration
• Building trust through consistent practices
• Focusing on employee satisfaction
• Maintaining strong customer connections

Product Led Growth (PLG) in Action

James explains that PLG companies like Zoom, ClickUp, and Pendo demonstrate the Launch Code principles naturally. These organizations:

• Get direct customer feedback through product usage
• Test features with specific user groups
• Make quick adjustments based on data
• Scale successful features systematically

The Tranche Model: A Practical Launch Approach

During our conversation, James shares how LinkedIn uses what he calls the “Tranche Model” for product launches. This approach involves:

• Testing with defined market segments (tranches) of 2 million users
• Learning from each group before expanding
• Making improvements based on real usage data
• Returning to early groups with refined offerings

For smaller markets, James recommends adapting this approach by creating representative samples. For example, if targeting 1,000 CFOs, start with 150 that represent different company sizes and industries.

Managing Launch Risks

James describes several approaches to controlling launch risks:

Risk Area Management Approach Market Reception Use tranche testing to validate before full release Team Alignment Build clear governance and communication structures Resource Management Maintain flexible budgets for quick adjustments Customer Response Monitor early indicators and feedback channels

Testing New Ideas Through Launches

James shares an interesting observation: organizations often find it easier to test new approaches with new products. For example, if a new service guarantee works well during a launch, teams might then apply it to existing products. This makes product launches valuable testing grounds for innovation.

Common Launch Challenges

James identifies several patterns that can reduce launch effectiveness:

• Making assumptions about customer needs without validation
• Leading research participants toward desired answers
• Missing important market signals
• Working in isolated departmental silos
• Resisting changes to established products

Conclusion

In this episode, James Whitman shares valuable insights about creating reliable product launch processes. The LAUNCH Code framework offers a structured approach that organizations can adapt to their needs. By focusing on continuous improvement, cross-functional alignment, and risk management, teams can build sustainable launch practices that support growth through innovation.

Remember that successful launches depend on more than just the product itself—they require careful attention to organizational dynamics, market conditions, and emerging technologies. Organizations that build these capabilities systematically while remaining adaptable position themselves for sustained growth.

Useful links:

• Learn more about LAUNCH Code
• Learn more about PDMA
• Listen to episode 502: Use LAUNCH Code to ease the overwhelm when launching a B2B product – with James Whitman

Innovation Quote

“Build self-correcting mechanisms to dampen issues as they emerge.” – James Whitman

Application Questions

1. How could you apply the Tranche Model in your market? What would appropriate customer segments look like for your products?
2. What mechanisms could improve collaboration between your product, sales, and marketing teams during launches?
3. How could you build early warning systems into your launch process? Which metrics would matter most?
4. What changes to your current launch approach would enable better feedback and continuous improvement?

Bio

James Whitman is the author of LAUNCH Code: A Playbook for Continuous Growth and the founder of Growth Guidepost. He works with corporate leaders to help them make their most important decisions and achieve critical growth objectives. He has held senior positions in public and private organizations, where he successfully established repeatable commercial practices, launching dozens of products, building high-performing teams, and scaling organizations.

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.

Elevating product strategy through advanced competitive intelligence

Watch on YouTube

TLDR

In this episode of Product Mastery Now, I interview Jay Nakagawa, Director of Competitive Intelligence at Dell Technologies and a 25-year product management veteran. Our discussion reveals proven methods for understanding competitors and developing effective product strategies. Jay shares practical tools and frameworks product managers can use to gather competitive intelligence ethically and systematically. One compelling insight is that looking at competitors through our own lens often leads to misunderstandings – we need frameworks and methods to see the market from their perspective.

Understanding Competitive Intelligence in Product Management

The Evolution of Competitive Intelligence

Jay has an interesting background that shapes his perspective on competitive intelligence. After spending over 20 years as a product manager, he found himself increasingly drawn to analyzing competition and developing strategies to outperform rivals. When Dell acquired EMC, Jay had the opportunity to transform this skill into a new career direction, leading competitive intelligence efforts.

His experience reveals an important shift in how companies approach competitive analysis. While understanding customer needs remains essential, gaining deep competitive insights has become equally valuable for product success.

The Problem with Traditional Analysis

Many product managers rely on SWOT analysis for competitive insights. However, Jay explains that in his field, they jokingly call SWOT a “Silly Waste of Time” because it reveals little about competition. Instead of providing deep insights into competitor strategies and capabilities, SWOT tends to focus on internal factors and broad market opportunities.

Core Functions of Modern Competitive Intelligence

Jay learned about competitive intelligence from the Academy of Competitive Intelligence, which teaches product managers not only frameworks but also how to use them practically. Based on Jay’s experience at Dell Technologies, effective competitive intelligence includes:

Function Description Business Impact Competition Analysis Understanding competitor products and strategies Improved product differentiation Strategic Evaluation Assessment of corporate and product strategies Better strategic planning Market Motion Analysis Understanding go-to-market approaches Enhanced market positioning Sales Support Enabling sales teams with competitive insights Increased win rates Product Direction Informing product management decisions More effective roadmap planning

Essential Frameworks for Competitive Analysis

Porter’s Five Forces in Practice

Jay shares an example of how to apply Porter’s Five Forces using the large aircraft manufacturing industry:

1. Threat of New Entry
   • High capital requirements
   • Strict government regulations
   • Example: China’s emerging presence in aircraft manufacturing
2. Supplier Power
   • Impact of supply chain disruptions
   • Limited supplier options
   • Complex component requirements
3. Buyer Power
   • Airlines as major customers
   • Long-term purchase commitments
   • High switching costs

Understanding Competitor Perspective

Jay shares a metaphor about competitor analysis: Picture a kitten looking in a mirror and seeing a lion’s reflection. While we see the kitten, we need to understand that the competitor sees themselves as a lion. This perspective helps explain why competitors’ actions that seem irrational often make perfect sense from their viewpoint.

Jack recommends you focus on your primary competitors. Use Four Corners Analysis to understand their market:

1. What’s driving their business?
2. What’s motivating them?
3. How do they view themselves?
4. What do they want to do?

The answers to these questions give you a good idea of what your competitor will do over the next 24 months. Then understand their biases and blind spots that you can exploit.

Advanced Competitive Intelligence Techniques

The Triangulation Method

Jay explains how his team combines multiple sources to build reliable competitive insights:

• Internal Knowledge
  • Team members with competitor experience
  • Product telemetry data
  • Sales team feedback
• Public Information
  • Job postings
  • Trade journals
  • Financial reports
• Industry Intelligence
  • Analyst reports
  • Conference insights
  • Customer feedback

Creative Research Methods

Jay shares an example about a team that used a creative but ethical way to gather competitive intelligence for a pharmaceutical company. The team needed to understand a competitor’s capacity for manufacturing vaccines but couldn’t access internal information. Their solution? They contacted the local fire department to review the building’s fire mitigation plan, which revealed details about the facility’s size and potential production capacity.

Practical Information Sources

Here are specific places where product managers can find competitive insights:

Source Type Examples Information Gained Professional Publications McKinsey reports, Boston Consulting Group articles Strategic direction, market trends Career Sites LinkedIn, Glassdoor, company career pages Technology investments, skill requirements Industry Events Conferences, trade shows, webinars Product roadmaps, partnership strategies Financial Sources Annual reports, investor presentations Investment priorities, market focus

Connecting Intelligence to Product Strategy

Common Product Management Challenges

Jay observes that many product managers have become highly specialized, focusing deeply on specific features or release optimization. While specialization has its benefits, it can lead to:

1. Limited market understanding
2. Missed competitive threats
3. Reactive rather than proactive strategy
4. Insufficient competitive differentiation

Predicting Competitor Actions

Jay shares four common ways competitors respond to market moves:

1. Imitation Response

When competitors can’t innovate quickly, they often try to copy successful features. Jay references Tony Fadell’s experience with the Nest thermostat as an example of how established companies respond to innovative products.

2. Innovation Response

Some competitors will develop alternative approaches rather than direct copies. This often leads to market differentiation and can benefit customers through increased choice.

3. Legal Response

Jay notes that when competitors can’t compete effectively through products, they may turn to legal challenges, particularly around patents or regulatory compliance.

4. Acquisition Response

Larger competitors might attempt to buy innovative companies rather than competing directly, especially when facing significant technical or market barriers.

Evaluating Competitor Claims

Assessing Investment Levels

Jay’s organization looks at publicly available data to figure out the market direction where competitors are going in the next four years. They try to answer the questions, “Why does a company do what they’re doing? Why are they investing in that technology?”

Jay shares a quote from a friend: “Vision without execution is called delusion.” If a competitor claims a particular business objective is part of their vision, you should investigate whether they really have the ability to execute on that vision.

Vision vs. Execution

Drawing from his experience, Jay shares these warning signs of a disconnect between vision and execution:

• Repeated announcements without progress
• Misalignment between stated goals and resource allocation
• Lack of supporting technical capabilities
• Missing market validation

Innovation Through Competitive Intelligence

Finding Market Opportunities

Jay shares how competitive intelligence can reveal innovation opportunities. He uses the example of Tony Fadell’s development of the Nest thermostat:

1. Personal Problem Recognition
   • Cold mountain cabin on arrival
   • No remote temperature control
   • Manual programming challenges
2. Market Research
   • Competitor analysis (Honeywell)
   • Technology assessment
   • User need validation

Conclusion

Throughout our discussion, Jay emphasizes that competitive intelligence isn’t about following competitors – it’s about understanding the market landscape to make better product decisions. The goal is creating differentiated products that solve real customer problems while maintaining awareness of competitive dynamics.

Useful links:

• Connect with Jay on LinkedIn
• Learn more about PDMA

Innovation Quote

“Ideas can come from anywhere.” – based on the story of Tony Fadell, inventor of the Nest thermostat

Application Questions

1. How could your team implement a systematic approach to gathering competitive intelligence that goes beyond basic SWOT analysis?
2. What frameworks from this episode could you start using immediately to better understand your competitors’ strategic direction?
3. How could you integrate competitive intelligence gathering into your current product development process without disrupting your existing workflow?
4. In what ways could your team better utilize publicly available information sources to predict competitor moves?

Bio

Jay Nakagawa is a 25+ year veteran product manager, with a track record of successfully building new products and developing turn-around strategies resulting in high revenue growth. As director of Competitive Intelligence with Dell Technologies, he and his team have been instrumental in providing critical guidance to product management teams providing insights that encompass how to create differentiated offerings to the market.

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.

Tips for managing global innovation projects

Watch on YouTube

TLDR

In this episode of Product Mastery Now, I speak with Jack Hsieh about successful product development strategies. Jack brings 20 years of experience managing innovation projects at companies like Sony Ericsson and Logitech. He shares practical insights from the Product Development and Management Association (PDMA) framework and explains how product managers can use these principles to improve their product development process. Through real examples from his work in consumer electronics and aerospace industries, Jack shows how PDMA’s body of knowledge helps create successful products while avoiding common pitfalls in portfolio management.

Key topics discussed:

• Innovation requires both strategy and execution
• Market research remains fundamental
• Process choice should match organization culture
• Portfolio decisions need global perspective
• Technical expertise matters in leadership

Introduction

While recording this episode at the PDMA Inspire Innovation Conference, I had the opportunity to talk with Jack Hsieh about product development evolution. PDMA has been supporting product professionals since 1976, making it the oldest organization dedicated to product management. Jack explains how PDMA’s comprehensive knowledge base helps companies innovate effectively across different industries and cultures.

Understanding New Product Development

Jack breaks down new product development (NPD) into clear components that every product manager should understand:

• Turning ideas into products and services that customers will buy
• Finding market opportunities that create value for organizations
• Making existing products better through strategic improvements
• Creating new value for established markets

The PDMA Body of Knowledge Framework

1. Strategic Alignment

Jack describes how product development needs alignment at multiple levels:

Strategy Level What It Means Why It Matters Corporate Strategy Company’s overall direction Guides all product decisions Business Unit Strategy Market-specific plans Focuses resources effectively Innovation Strategy Product development priorities Directs innovation efforts Capability Strategy Resource planning Ensures successful execution

2. Portfolio Management

During our conversation, Jack shares valuable insights from managing product portfolios at Sony Ericsson. He explains how the company handled three distinct product lines:

• Smartphones
• High-end feature phones
• Low-end feature phones

This experience taught him important lessons about resource allocation. For example, his business unit needed to coordinate holidays across three regions: Sweden, Taiwan, and Japan. The overlapping work schedule only provided 190 days per year for full team collaboration, making resource planning especially important.

Jack uses Boeing and Airbus as examples to illustrate key portfolio management principles:

Portfolio Decision Impact Lesson Learned Boeing’s 737 platform extension Technical challenges with aging platform Need for balanced technical and business leadership Resource allocation across product lines Product cannibalization between categories Importance of global portfolio optimization Technical vs. business leadership Impact on long-term product decisions Value of technical expertise in leadership

3. Process Management

Organizations need different development processes based on their specific needs. Jack explains several approaches:

Integrated Product Development (IPD)

• Works well for complex products
• Requires strong cross-functional coordination
• Popular in companies like Huawei

Agile Development

• Suited for rapid market feedback
• Enables quick product iterations
• Best for software and digital products

Waterfall Method

• Effective for well-defined requirements
• Provides clear project structure
• Works in regulated industries

Hybrid Approaches

• Combines planning from Waterfall
• Uses Agile for execution
• Balances structure and flexibility

4. Tools and Techniques

Jack mentions that he has personally used more than 70% of the tools in PDMA’s Body of Knowledge. These tools span different product development stages:

Development Stage Tools Used Purpose Concept Development Design thinking methods Generate and evaluate ideas Product Testing Alpha and beta testing Validate product concepts Manufacturing Pilot production models Verify production capability

5. Market Research

Jack emphasizes that market research remains the most important skill for product managers. Modern approaches include:

Advanced Research Technologies

• Eye tracking for user experience studies
• AI-powered customer insight analysis
• Predictive analytics for market trends
• Sensory analysis techniques

6. Culture and Organization

Organizational culture significantly affects product development success. Jack shares team structures that work:

• Cross-functional collaboration
• Clear role definitions
• Balanced technical and business input

7. Product Lifecycle Management

Jack shares a personal story about understanding market adoption patterns. When he started his consulting business, he initially focused on multinational companies in Taiwan, thinking his experience with foreign companies would be an advantage. Despite getting over 50 inquiries in his first year, he secured no deals. Reading Crossing the Chasm helped him understand why – these companies were early majority adopters, not early adopters, making them hesitant to work with a new consulting firm.

Real-World Applications

The Logitech Left-Handed Mouse Project

Left-handed boy using computer and mouse

Jack shares an interesting case study from his time at Logitech. The project, named “Sicily Left,” aimed to create a mouse specifically for left-handed users. Key insights include:

• Market opportunity analysis:
  • Left-handed users represent 10% of population
  • Right-handed users could use the mouse with their left hand while writing
• Technical challenges:
  • 30% of internal components needed redesign
  • Simple mirroring wasn’t possible
  • Full testing required for new design
• Product outcomes:
  • Successful project execution
  • Six-year product lifespan
  • Lower than expected sales volume

Jack learned that the wrong business case for a project leads to a sub-optimal result.

Sony Ericsson Portfolio Management

Jack’s experience managing mobile phone portfolios provides valuable lessons:

Challenge Solution Outcome Resource allocation across regions Cross-cultural negotiation Balanced compromise on project numbers Product line overlap Price point coordination Reduced internal competition Global team coordination Holiday schedule planning Improved workflow management

Project Management vs. Product Management

During our discussion, Jack helps clarify the important differences between project and product management:

Aspect Project Management Product Management Timeline Focus Specific project duration Full product lifecycle Success Metrics On-time, on-budget delivery Market success, customer satisfaction Scope Defined project requirements Evolving product strategy

Conclusion

In this episode, Jack demonstrates how PDMA’s framework guides successful product development. His experiences at global companies like Sony Ericsson and Logitech show how these principles help product managers handle complex challenges. Whether you’re managing consumer electronics, aerospace products, or software, these insights can help you create better products and advance your career in product management.

Useful links:

• Learn more about Jack’s consultancy, Maestro
• Learn more about PDMA

Innovation Quote

“Innovation takes dedication, but the choice is more important than the dedication.” – Jack Hsieh

Application Questions

1. How could you use PDMA’s portfolio management ideas to better manage your product mix?
2. Which parts of your development process might work better using the hybrid approach Jack describes?
3. What new market research methods could help your team understand customers better?
4. How could you improve the way project and product managers work together in your organization?

Bio

Jack Hsieh has 20 years of experience in planning, executing, managing, and consulting on innovation projects across the world. Jack is the President at Maestro Project Management Consultants, which helps clients with innovation management, new product development, and project management. Previously, at Sony Ericsson, he led a cross-functional international team to develop handheld devices that served millions of users worldwide.

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.

Product innovation lessons from social media content creation

Watch on YouTube

TLDR

In this episode of Product Mastery Now, I’m interviewing Leah and Philip Abraham, a creative duo with expertise in songwriting, acting, music production, and filmmaking. Their diverse background offers valuable lessons for product managers looking to improve their innovative thinking techniques. Throughout our conversation, we explore insights from their creative process that can be applied to product innovation and management.

• Innovation is a learnable process, not just an innate talent
• Complementary skills in teams can lead to more holistic product innovation
• Balancing intuition with data-driven decision-making enhances product development
• Rapid prototyping and iterative development accelerate learning and innovation
• Embracing a “no bad ideas” culture fosters creativity in product teams
• Learning from failures and maintaining enthusiasm through setbacks is crucial for long-term success
• Continuous learning and adaptation of innovation processes are essential in product management

This episode explores insights from creative professionals that can be applied to enhance innovation in product management, offering practical strategies for product managers to foster creativity, leverage rapid feedback cycles, and overcome challenges in the innovation process.

Dismantling Misconceptions About Innovation

We start by addressing common misconceptions about innovation, particularly the belief that creativity is an innate talent rather than a skill that can be developed. This idea is especially important for product managers and leaders responsible for driving innovation within their organizations. Leah and Philip share their experiences, showing that innovation is indeed a process that can be learned and improved over time.

Complementary Creativity in Partnerships

Leah and Phillip have experience in acting and film production and are now most famous for cinematic shorts on social media. They explain that they enjoy creative collaboration in many areas, including filmmaking, photography, music, and art.

Leah and Phillip share that their creativity is complementary and they bring out creativity in each other. Phillip has a technical background while Leah focuses on character arcs.

Innovation in the Creative Process

When making a skit, Leah and Phillip often start with a sketch of the story and improv to fill in the details. They’re often inspired to make a skit based off something that happens in their lives. For example, a recent video called “When they cancel plans but you’re both introverts,” was inspired by Leah and Phillip’s introvertedness.

Leah and Phillips use a  “no bad ideas” approach, which creates a safe space for sharing and building upon concepts. They give each other permission to throw out ideas without shame and then make those ideas better together.

Benefits of Rapid Feedback Cycles

Compared to producing a whole film, creating short-form content on social media provides more opportunity to receive rapid feedback and iterate. Analytics let Leah and Phillip see what aspects of their content viewers are engaging with most. Sometimes the parts of their content they almost didn’t include end up being the most popular with their audience.

Leah and Phillip share that feedback from viewers has been affirming and eye-opening, and the most fulfilling part of their creative process is figuring out what viewers like about their content and building an intuition for creating engaging content.

The Role of Intuition in Creativity and Innovation

Leah and Phillip explain that they’re learning about to balance intuition with data-driven decision making. I think of intuition as my experience taking shape that my brain hasn’t recognized yet. Leah describes intuition as your body knowing something before your mind can articulate it. She had an intuition that she and Phillip should start doing social media and that it made sense for their hodgepodge of creative skills. They observed that most viral TikTok videos were not high-quality narrative skits and decided to use their skills to fill that gap.

Conclusion

This episode offers valuable perspectives on fostering creativity and innovation in product management. By embracing collaborative approaches, rapid prototyping, and a willingness to learn from failures, product teams can enhance their innovation capabilities and create more successful and impactful products.

Key takeaways for product managers:

• View innovation as a learnable process, not just innate talent
• Leverage complementary skills within teams for holistic innovation
• Balance intuition with data-driven decision-making
• Embrace rapid prototyping and iterative development
• Foster a culture that encourages risk-taking and learns from failures
• Continuously evolve and adapt innovation processes

Useful links:

• Check out Leah and Phillip’s content on YouTube and other social media platforms @leahandphillip
• Watch the trailer for Leah and Phillip’s film, Where Were You

Innovation Quotes

“If opportunity doesn’t knock, build a door.” – unknown

“Success is stumbling from failure to failure without any loss of enthusiasm.” – Winston Churchill

Application Questions

1. How can you create a “no bad ideas” culture within your product development process? What obstacles might you face, and how can you overcome them?
2. In what ways can you implement rapid prototyping and testing in your current product development cycle? How might this affect your timelines and resource allocation?
3. How do you currently balance intuitive decision-making with data-driven approaches? Are there areas where you could improve this balance?
4. What strategies can you implement to better learn from your failures and maintain team enthusiasm through setbacks?
5. How can you encourage team members to step outside their comfort zones and explore new approaches to product innovation?

Bio

Leah and Phillip Abraham are an up-and-coming social media couple known for their highly cinematic viral skits, which have gained over 85 million views since their launch in February of 2024. Having both spent over a decade hustling in Hollywood, and acting on shows like Aquarius, CSI, Ballers, and Good Trouble, they found a ceiling placed on their potential as creatives, ultimately moving to Nashville and starting their production company, Philea Media. Together they wrote, produced, and acted in a feature-length musical that is loosely based on how they met, which is scheduled to premiere at film festivals in 2025. 

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.

How product managers can foster a culture of innovation

Watch on YouTube

https://youtu.be/14cLrVAu7BA

TLDR

In this episode of Product Mastery Now, I’m interviewing Chris Elmore, a tech entrepreneur and college professor who helped found Avid Exchange, a unicorn startup that went public in 2021. Chris brings years of experience in product innovation and management, and he’s here to share his thoughts on driving innovation and keeping businesses growing for the long haul. Here are the key points from our conversation:

• A simple definition of innovation: “It’s better than what it was”
• Rethinking organizational structure can improve the flow of innovative ideas
• Hiring should focus on cultural fit and alignment around organization mission and purpose
• Everyone in an organization can be an innovator

The Importance of Innovation in Today’s Business World

As we start our chat, Chris highlights why innovation matters so much in today’s fast-moving business world. Products and services don’t stay relevant as long as they used to. Because of this, companies can’t just rely on what worked in the past. Innovation is key to keeping a business growing and thriving.

Building a Culture That Supports Innovation

One of the main topics we explore in this episode is how a company’s culture can help or hinder innovation. Culture is the unwritten rules of an organization – what people are allowed and expected to do. Chris shares his experience of keeping a strong culture, and even improving it, as his company grew. This challenges the common idea that company culture always gets worse as a business gets bigger.

Chris says that the quickest way to destroy culture is to put someone in charge of it. When someone is in charge of culture, the culture becomes that person’s version of culture.

Instead of taking charge of culture, leaders can use stories to reinforce a culture of innovation. For example, Chris tells his teams a story of how he tells his kids that he doesn’t care about their grades as long as they’re putting in full effort, but usually full effort leads to good grades. This communicates to his team that effort will eventually lead to the desired outcome.

Rethinking How Companies Are Structured to Support Innovation

We also discuss Chris’s thoughts on how company structure can affect innovation. He critiques traditional hierarchies, suggesting they can make it hard for innovative ideas to flow, especially ideas from employees who work closely with customers.

Chris observes that most good ideas come from the middle third of an organizational chart. Often, people in the middle or bottom third of an organization try to communicate their ideas to leadership who don’t understand the idea or are scared of innovation, so many great ideas fail.

Instead of a traditional org chart, Chris proposes thinking of the organization as a curve that represents everyone’s understanding of where the organization is going. The beginning of the curve represents where the organization is today, and the end represents where the organization needs to go. The goal of a leader is to get the organization over the valleys to go further down the curve. This approach focuses on aligning everyone in the organization towards common goals and outcomes, rather than rigid reporting structures.

Producing Alignment

To explain what the organization is working toward and get a team aligned around common goals, Chris concentrates on three things: mission, purpose, and outcome. The mission and purpose should be aligned with the organization’s outcomes. If not, we have work to do. If someone can’t get behind the mission and purpose, they can’t be in the organization anymore.

Building Innovative Teams: A Fresh Approach to Hiring

Chris takes an unusual approach to hiring. He focuses on the person rather than their resume. In fact, he says he’s never read a resume in his life. This approach allows him to assess candidates based on their potential and how well they fit with the company culture, rather than just their past experiences and qualifications.

A Simple but Powerful Definition of Innovation

Chris offers a simple definition of innovation: “It’s better than what it was.” This straightforward idea makes innovation something everyone in the company can understand and participate in, not just the people in research and development or product design.

A Customer-Focused Approach to Innovation

Chris advocates for a broad definition of “customer” that goes beyond just the end-users of a product or service. He explains that customers include internal and external stakeholders and even employees’ families. Product managers should think about serving all of those customers.

This wider view encourages product managers and leaders to consider the needs and perspectives of various stakeholders when driving innovation. By considering a wider range of “customers,” organizations can ensure their innovations create value not just for end-users, but for employees, investors, partners, and even the families of team members.

Everyone can be an Innovator

Chris wants everyone in his organization to be aware that they can be an innovator. In his company, every time someone was hired, Chris gave them his definition of innovation and told them it’s their job to be an innovator.

The Power of Small, Continuous Improvements

While big, disruptive innovations often get the most attention, Chris emphasizes the importance of small, ongoing improvements. He explains that small innovations over a long period of time is a huge thing.

This view encourages product managers and leaders to focus not just on big breakthroughs, but also on the cumulative impact of smaller, incremental improvements over time.

Conclusion

Driving innovation in product management is about more than just developing new features or technologies. It’s about creating an environment where innovation can thrive at every level of the organization. A culture of innovation leads to better products and more resilient organizations. Innovation is simply about making things “better than they were.” As product managers and leaders, our challenge is to embody this principle in our daily work and inspire our teams to do the same so that we can ensure our organizations not only keep pace with change but lead the way in creating value for our customers and stakeholders.

Innovation Quote

“Luck is when opportunity meets preparedness.” – Earl Nightingale

Application Questions

1. How can you simplify your definition of innovation to make it more accessible to everyone in your organization?
2. Have you ever acted as an innovator while working in a role that is not traditionally innovative? Or have you seen another employee do this?
3. What small, incremental innovations could you implement in your products or processes that might lead to significant improvements over time?
4. How can you expand our definition of “customer” to include a wider range of stakeholders? How might this change your approach to innovation?
5. What aspects of your organizational structure or culture might be hindering innovation? How can you address these barriers?

Bio

Chris Elmore is a seasoned tech entrepreneur and a respected college professor. Chris played pivotal roles in the founding of fintech AvidXchange, a unicorn startup that went public in 2021 with a $2.3B valuation. At AvidXchange his roles spanned numerous functions, including development, product, marketing, and mergers and acquisitions. Chris is also a passionate musician, performing solo and in bands as a singer with his guitar and ukulele.

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.

How product managers can use AI to work more efficiently Watch on YouTube TLDR AI is changing how we manage products and come up with new ideas, giving us new tools to work faster and be more creative. AI can help in many parts of making a product, from research to writing product plans and […]