Product Mastery Now for Product Managers, Leaders, and Innovators

Questions product managers ask me about how to improve innovation Watch on YouTube TLDR Product managers are pivotal in driving innovation within organizations. Today I’m answering common questions I get asked about product innovation and management, including: Supply-side vs. demand-side innovation The Business Model Canvas Strategic planning Portfolio management Project selection criteria I also discuss the importance of ongoing learning and professional growth for product managers. By mastering these areas, product managers can improve their skills, boost their influence, and contribute more effectively to their organization’s success. Introduction: The Role of Product Managers in Innovation As product managers, we’re at the forefront of innovation in our companies. We spot important ideas, uncover customer needs, turn concepts into products or features, and work to increase market share. But there’s more to innovation than just creating new products. Innovation is the economic engine for organizations and a key source of new value. It’s about creating an innovation culture that drives growth and keeps companies competitive. In this article, we’ll explore key ideas and strategies to help you become a better product innovator and manager. Supply-Side vs. Demand-Side Innovation: Finding the Right Mix One of the basic concepts in product innovation is understanding the difference between supply-side and demand-side innovation. Let’s break down these approaches and look at their pros and cons. Supply-Side Innovation: Creates new products or technologies based on the company’s expertise Often results in “new-to-world” products Usually needs a lot of R&D investment Can lead to big breakthroughs but carries higher risk Demand-Side Innovation: Starts with customer needs and market research Aims to solve existing customer problems Generally carries lower risk as it addresses known market demands Can lead to improvements or new products that better serve customers While both approaches have their good points, demand-side innovation often has less risk and can lead to quicker success. However, a balanced approach that includes elements of both can be ideal for many companies. Examples of Supply-Side Innovation: Product Company Outcome Post-it Notes 3M Accidental discovery of weak glue led to a widely used product Humulin Eli Lilly Synthetic insulin development that initially overshot market needs Electric Actuator Caterpillar Solution developed before a problem was identified, later found use in smaller excavators These examples show that while supply-side innovation can lead to revolutionary products, it often takes time to find the right market fit. The Business Model Canvas: A Tool for Product Innovation The Business Model Canvas is a valuable tool for product managers involved in innovation. It gives a complete view of how a product or business creates, delivers, and captures value. Let’s explore the nine key elements of the Business Model Canvas: Customer Segments: Define the specific groups of customers you aim to serve Channels: Identify how you’ll reach and communicate with your customers Customer Relationships: Determine the type of relationship you want to have with each customer segment Value Proposition: Explain the unique value your product offers to solve customer problems Key Partners: List the external partners crucial to your success Key Activities: Outline the most important actions your company must take to operate successfully Key Resources: Identify the most important assets required to make your business model work Cost Structure: Describe all costs incurred to operate your business model Revenue Streams: Detail how your company will make money from each customer segment Using the Business Model Canvas in product management can help you: Align your product strategy with overall business goals Spot potential gaps or inconsistencies in your product plan Improve cross-functional teamwork and communication Refine your product concept based on a complete view of the business Strategy in Product Innovation: Aligning with Company Goals To be effective product innovators, we need to understand how our work fits into the broader company strategy. Let’s look at the strategy hierarchy and how it relates to product innovation: Mission, Vision, and Values: The basic elements that define the company’s purpose and direction Corporate Strategy: The overall plan for achieving competitive advantage and meeting company goals Business Strategy: Specific strategies for individual business units or product lines Innovation Strategy: The approach to creating new products, services, or processes that align with corporate and business strategies As product managers, we mainly work at the innovation strategy level. However, it’s important to understand how our work supports and aligns with higher-level strategies. The Miles and Snow Strategy Model offers another view on company approaches to innovation: Strategy Type Description Innovation Approach Prospector First-to-market with new products or technologies High investment in R&D, focus on breakthrough innovations Analyzer (Fast Follower) Quickly adopts and improves upon successful innovations Strong market research, focus on customer insights and incremental improvements Defender Maintains market share in stable niches Focuses on efficiency and incremental improvements to existing products Reactor Responds only when forced by competitive pressures Limited proactive innovation, reactive improvements to maintain relevance Understanding your company’s strategic approach can help you align your product innovation efforts more effectively. Case Study: Apple as an Analyzer (Fast Follower) While Apple is often seen as a highly innovative company, its success comes more from its role as an analyzer or fast follower. Apple excels at taking existing concepts and greatly improving them: Macintosh: Improved upon existing personal computer concepts with a user-friendly graphical interface iPod: Enhanced the MP3 player experience with sleek design and seamless music management (iTunes) iPhone: Revolutionized the smartphone market by refining and integrating existing technologies This approach allows Apple to learn from others’ mistakes, focus on user experience, and bring highly polished products to market. Portfolio Management: Balancing Innovation Investments Effective portfolio management is crucial for companies to allocate resources efficiently and maximize the value of their innovation efforts. Here are some methods for structuring innovation portfolios: Strategic Buckets: Allocate resources to different categories of projects Three Horizons Approach: Balance investments across core, adjacent, and transformative innovations Business Unit Organization: Align innovation efforts with specific business unit objectives Example of Strategic Buckets Allocation: Project Type Resource Allocation Breakthrough Projects 10% Platform Development 10% Derivative Products 20% Support and Incremental Improvement 60% This allocation ensures a balance between maintaining current products and investing in future growth opportunities. Project Selection Criteria for Innovation Choosing the right projects for your innovation portfolio is critical. Here are key criteria to consider: Strategic fit with company objectives Sales potential and market size Competitive landscape User experience and customer value Technical feasibility and complexity Financial metrics (e.g., ROI, NPV) Resource requirements Risk assessment Various methods can help in project selection, such as the Analytical Hierarchy Approach or the Selenese Factors model, which considers: Strategic fit Strategic leverage Technical feasibility Market desirability Reward to the company By using a structured approach to project selection, you can ensure that your innovation efforts align with company goals and have the highest potential for success. Continuous Learning and Professional Development for Product Managers To stay at the forefront of product innovation and management, it’s essential to engage in ongoing learning and professional development. The Product Development and Management Association (PDMA) offers valuable resources and certification programs for product managers. The Rapid Product Master Experience (RPM) is a comprehensive training program that covers seven research-backed knowledge areas for product mastery: Strategy and portfolio management Market research and customer insights Innovation and new product development processes Product lifecycle management Product design and development tools Launch and commercialization Product management and leadership By investing in your professional development and staying current with industry best practices, you can enhance your skills, increase your influence within your organization, and drive more successful product innovations. Developing an Innovation Culture Creating a culture of innovation within your organization is crucial for long-term success. Here are some strategies to foster innovation: Encourage risk-taking and learning from failures Promote cross-functional collaboration Provide time and resources for experimentation Recognize and reward innovative ideas and efforts Create channels for employees to share and discuss new ideas By cultivating an environment that values and supports innovation, you can tap into the creative potential of your entire organization. Measuring Innovation Success To ensure your innovation efforts are on track, it’s important to establish and track key performance indicators (KPIs). Some relevant metrics for product innovation include: Percentage of revenue from new products Time to market for new products Customer adoption and satisfaction rates Return on investment (ROI) for innovation projects Number of patents filed or granted Employee engagement in innovation activities Regularly reviewing these metrics can help you adjust your innovation strategy and improve outcomes over time. Conclusion As product managers, we play a vital role in driving innovation and creating value for our companies and customers. By understanding key concepts like supply-side vs. demand-side innovation, using tools like the Business Model Canvas, aligning with company strategy, and implementing effective portfolio management, we can significantly improve our product innovation outcomes. Remember, the path to successful product innovation is not always straightforward. As the Cheshire Cat in Alice in Wonderland said, “If you don’t know where you’re going, any road will take you there.” By continually improving our skills, staying informed about industry trends, and applying best practices in product management, we can chart a clear course towards creating products that truly resonate with customers and drive company success. Innovation Quote “If you don’t know where you’re going, any road will take you there.” – the Cheshire Cat, from Alice’s Adventures in Wonderland by Lewis Carroll Application Questions How does your company currently balance supply-side and demand-side innovation? Are there opportunities to adjust this balance to improve innovation outcomes? In what ways can you use the Business Model Canvas to enhance your current product development process? Are there any elements of the canvas that you typically overlook? How well does your product innovation strategy align with your company’s overall strategy? What steps can you take to improve this alignment? Evaluate your company’s approach to portfolio management. Are you effectively balancing investments across different types of innovation projects? How might you improve resource allocation? What criteria does your company use for project selection in innovation? Are there any important factors missing from your current evaluation process? Bio Chad McAllister, PhD, is a product management professor, practitioner, trainer, and host of the Product Mastery Now podcast. He has 30+ years of professional experience in product and leadership roles across large and small organizations and dynamic startups, and now devotes his time to teaching and helping others improve. He co-authored “Product Development and Management Body of Knowledge: A Guide Book for Product Innovation Training and Certification.” The book distills five decades of industry research and current practice into actionable wisdom, empowering product professionals to innovate and excel. Chad also teaches the next generation of product leaders through advanced graduate courses at institutions including Boston University and Colorado State University and notably re-engineered the Innovation MBA program at the University of Fredericton, significantly broadening its impact. Further, he provides online training for product managers and leaders to prepare for their next career step — see https://productmasterynow.com/. Thanks! Thank you for taking the journey to product mastery and learning with me from the successes and failures of product innovators, managers, and developers. If you enjoyed the discussion, help out a fellow product manager by sharing it using the social media buttons you see below. Source

Why market research is product managers’ secret ingredient for successful products Watch on YouTube TLDR Market research is a key part of product development and management. In this episode, Chip Chonym explains why market research matters throughout the innovation process, discussing both qualitative and quantitative methods. He covers the “double diamond” approach, how to talk about value, pricing strategies, and how market research helps make smart decisions. Chip emphasizes that product managers should see market research as an ongoing process and provides practical tips for doing effective research. Introduction In the world of product management and innovation, market research is like a compass. It guides product managers through the complex landscape of what customers need, want, and how they behave. Chip digs into the world of market research, exploring why it’s important, how to do it, and how to use it when developing products. Why Market Research Matters in Product Development Market research is one of the seven key areas of knowledge that make up Product Mastery, according to the Product Development and Management Association (PDMA). It’s important because it helps uncover what customers need and want, even if they don’t know it themselves. This information is gold for creating successful new products. Understanding how different areas of knowledge work together is crucial for product managers. Market research doesn’t exist in a bubble; it connects with and informs other parts of product development, like creating strategies, how teams work together, and understanding the bigger business picture. This holistic approach ensures that decisions about products are based on a full understanding of both the market and the broader business context. Market Research: An Ongoing Journey One big misconception about market research is that it’s a one-time thing. In reality, effective market research is an ongoing process that continues throughout a product’s life. From the first idea to checking how well it’s doing after launch, market research plays a vital role at every stage. The Double Diamond Approach in Market Research The “double diamond” approach is a helpful way to understand how market research works in product development: Diamond Phase What It Means Research Activities First Diamond – Discover Exploring widely to understand the problem Watching customers, open-ended interviews First Diamond – Define Narrowing down to specific problems Defining the problem, identifying customer groups Second Diamond – Develop Coming up with lots of potential solutions Testing concepts, evaluating prototypes Second Diamond – Deliver Refining and implementing the chosen solution Testing with users, validating in the market This approach emphasizes the importance of alternating between thinking broadly (exploring) and focusing in (refining) throughout the research process. Qualitative Research: Getting to Know Your Customers Qualitative research methods provide rich, detailed insights into how customers behave, what motivates them, and what problems they face. These methods are especially valuable in the early stages of product development when you’re still trying to understand the problem. Key Qualitative Research Methods Ethnography: Observing customers in their natural environment to gain real insights into their behaviors and needs. One-on-One Interviews: In-depth conversations with individual customers to explore their experiences and perspectives. Small Group Sessions: Discussions with 3-4 participants, encouraging dynamic interactions and idea generation. Small group sessions are often more valuable than traditional focus groups. In smaller groups, people feel more comfortable challenging each other’s ideas, leading to more honest and insightful discussions. For example, a product manager developing a new project management tool might conduct small group sessions with team leaders from different industries. These sessions could reveal unexpected pain points in current tools and spark ideas for innovative features. Quantitative Research: Measuring What Matters While qualitative methods provide depth, quantitative techniques offer breadth and statistical reliability. These methods are particularly useful in later stages of product development when you need to test specific concepts or refine your ideas. Essential Quantitative Research Tools Conjoint Analysis: A statistical technique that determines how people value different features that make up a product or service. MaxDiff (Maximum Difference Scaling): A method for understanding customer preferences by making them choose between different options. Surveys: Structured questionnaires that can reach many respondents, providing statistically significant data. These quantitative methods allow product managers to make data-driven decisions about product features, pricing, and market positioning. For instance, a company developing a new smartphone might use conjoint analysis to understand how much customers value different features like battery life, camera quality, or screen size. This information could help prioritize which features to focus on in the final product. Talking About Value: The Art of Communication in Market Research One of the challenges in market research is translating product features into benefits and value for customers. Engineers and product developers often focus on the technical aspects of a product, but customers are mainly interested in what they get out of it. Effective market research requires crafting questions and descriptions that resonate with customers. This involves: Focusing on benefits rather than features Using language that customers understand and relate to Presenting concepts in terms of the problems they solve or the value they provide For example, instead of asking customers about a “5000mAh battery,” you might ask about their frustrations with battery life and how a phone that lasts two full days without charging might change their daily routine. Pricing Strategies for New Products: Beyond Cost-Based Approaches Pricing is a critical part of product strategy, and market research plays a vital role in determining the right price. Many product managers and engineers default to cost-based pricing, but this approach often leaves money on the table and fails to capture the true value of innovative products. Key Considerations in Value-Based Pricing Differential Value: Understanding what makes your product different from alternatives in the market. Customer Segmentation: Identifying the specific groups of customers who value your product’s unique benefits. Willingness to Pay: Determining how much customers are willing to pay for the value your product provides. Portfolio Pricing: Considering how your product fits into your overall product lineup and pricing strategy. Value-based pricing requires a deep understanding of customer needs, market dynamics, and competitive positioning. Market research provides the insights necessary to implement this more sophisticated pricing approach. Case Study: The Mechanical Pencil Example To illustrate the principles of value-based pricing and market research, let’s consider the example of a mechanical pencil. At first glance, it might seem challenging to differentiate or price such a common product. However, by applying market research techniques, we can uncover opportunities for innovation and value creation. Steps in Researching and Pricing a Mechanical Pencil Identify Differentiation Factors: Comfort during extended use, reliability of lead advancement mechanism, eraser quality and longevity. Understand Target Customer Segment: Professional artists, architects, or students who use pencils extensively and value precision and comfort. Determine Willingness to Pay: Through techniques like conjoint analysis, assess how much target customers would pay for specific improvements in comfort, reliability, or functionality. By focusing on the specific needs of a target segment and the value provided by unique features, it’s possible to justify a premium price for what might otherwise be considered a basic product. For instance, a mechanical pencil designed for architects might command a much higher price than a standard pencil due to its precision, comfort during long drafting sessions, and specialized features like integrated scale rulers. The Power of “Why” in Market Research Throughout the market research process, the most powerful question a product manager can ask is “why?” Understanding the underlying motivations, frustrations, and desires of customers is key to developing truly innovative products. The “why” question applies at multiple levels: Why do customers choose one product over another? Why do they perform certain tasks in a particular way? Why do they value certain features or benefits? By consistently probing deeper with “why” questions, product managers can uncover insights that lead to breakthrough innovations and products that truly resonate with customers. For example, when researching a new coffee maker, asking “Why do you prefer your current brand?” might reveal that it’s not just about the taste of the coffee, but also about the ritual of preparation or the aesthetic appeal of the machine in their kitchen. Balancing Qualitative and Quantitative Research Methods Effective market research requires a balance between qualitative and quantitative methods. Each approach has its strengths and limitations, and the most robust insights often come from combining both types of research. Complementary Roles of Qualitative and Quantitative Research Research Type Strengths Limitations Qualitative Rich, detailed insights; Discovery of unexpected issues Limited sample size; Potential for researcher bias Quantitative Statistical reliability; Large sample sizes May miss context or underlying motivations Product managers should strive to leverage the strengths of both approaches, using qualitative methods to explore and generate hypotheses, and quantitative methods to validate and quantify findings. Adapting Research Techniques to Specific Situations There’s no one-size-fits-all approach to market research. The specific techniques and methodologies used should be tailored to the product, market, and stage of development. Factors to consider include: The maturity of the market and product category The complexity of the product or service The target customer segment (e.g., consumers vs. businesses) Available resources and timelines Product managers must be flexible and creative in their research approaches, adapting methodologies to fit the unique needs of each project. For instance, researching a new B2B software product might involve in-depth interviews with IT decision-makers, while a consumer snack food might rely more heavily on taste tests and quantitative surveys. The Role of Market Research in Making Smart Decisions Ultimately, the goal of market research is to enable better business decisions. By providing data-driven insights into customer needs, market trends, and competitive dynamics, market research empowers product managers to: Prioritize features and development efforts Identify new market opportunities Optimize pricing and positioning strategies Reduce risks associated with product launches When integrated into the product development process, market research becomes a powerful tool for reducing uncertainty and increasing the likelihood of market success. For example, a company developing a new line of athletic wear might use market research to identify which features (moisture-wicking, odor control, eco-friendly materials) are most important to their target customers. This information could guide product development, marketing messages, and pricing strategies. Conclusion Market research is not just a set of tools and techniques; it’s a mindset that puts the customer at the center of product development. By embracing market research throughout the innovation process, product managers can: Develop products that truly meet customer needs Make more informed decisions about product strategy Reduce the risk of product failure Create sustainable competitive advantages As the business world continues to change, the importance of market research in product management will only grow. Product managers who master these techniques and integrate them into their development processes will be well-positioned to create successful, customer-centric products. Remember, effective market research is an ongoing process, not a one-time event. By continuously seeking to understand your customers and market, you can stay ahead of trends, anticipate needs, and create products that truly resonate with your target audience. Useful links: Check out AMG Research Innovation Quote “What is your why?” – Simon Sinek Application Questions How does your organization currently use market research in product development? Are there opportunities to make it more of an ongoing, iterative process Think about a recent product launch or feature development. How might the outcome have been different if you had applied some of the market research techniques discussed in this article? Consider your current pricing strategy. How could you use market research to move towards a more value-based approach? What information would you need to gather? Reflect on a time when you were surprised by customer feedback or market reception to a product. How could better market research have helped anticipate or prevent this surprise? How can you better balance qualitative and quantitative research methods in your product development process? Are there areas where you’re relying too much on one type of research? Bio Chip Chomyn is the President and Managing Principal at AMG Research, a research-based consulting and insights company based in Pittsburgh, PA. Chip brings more than 20 years experience in marketing and sales and, over that time, has been involved in more than 1,000 market research studies. He has degrees in Bioengineering and Mechanical Engineering, which explains in part his special interest in helping medical and industrial businesses in new product development, pricing, segmentation, and market analysis. Thanks! Thank you for taking the journey to product mastery and learning with me from the successes and failures of product innovators, managers, and developers. If you enjoyed the discussion, help out a fellow product manager by sharing it using the social media buttons you see below. Source

The future of culture and teams in the age of AI – for product managers Watch on YouTube TLDR: AI is reshaping how we work, especially in product management. In this episode, Tiffany Price explains how AI affects workplace culture, team dynamics, and leadership. Key points include: Adapting organizational values for the AI era Building psychological safety in AI-augmented teams Embracing vulnerability to drive innovation Managing employee concerns about AI integration Upskilling teams to work effectively with AI Balancing human skills with AI capabilities Enhancing team culture in hybrid work environments Product leaders will find strategies to navigate these changes and prepare their teams for an AI-driven future. Introduction Artificial intelligence (AI) is changing how we work, especially in product management. As AI tools become more common, product leaders face new challenges in managing teams, fostering innovation, and maintaining a positive work environment. In this episode, Tiffany Price explains how AI impacts workplace culture, team dynamics, and leadership strategies, offering insights for product managers in this evolving landscape. The Impact of Generative AI on Workplace Culture Generative AI, like ChatGPT, is a hot topic in many organizations. It has the potential to change how we work, automate tasks, and enhance human capabilities. This creates both excitement and uncertainty among employees and leaders. Uncertainty and Ambiguity in Adoption Integrating generative AI into existing work processes isn’t always straightforward. Organizations are trying to figure out how to use these technologies effectively while keeping employees productive and motivated. This uncertainty can lead to: Employees worrying about their job security Challenges in defining new roles and responsibilities Difficulties in measuring performance when AI is involved Predictions for the Future of Work Recent research has highlighted some interesting predictions for how AI might change work: Prediction Timeframe Potential Impact Smart robots outnumbering frontline workers By 2028 Big changes in manufacturing, retail, and logistics industries 1000% increase in unionization among knowledge workers By 2028 Shift in power dynamics and employee representation in tech and other knowledge-based sectors These predictions show that product leaders need to prepare for significant changes in how teams are structured and how employees are represented. Cultural Challenges in the AI Era Bringing AI into the workplace creates several cultural challenges that product leaders must address: Fear and Uncertainty Among Employees As AI capabilities grow, many employees worry about losing their jobs or facing big changes in their roles. This anxiety can lead to: Resistance to using AI tools Lower productivity and engagement Increased turnover as employees look for jobs they perceive as more secure Need for Transparency in Job Transformation To address these fears, organizations need to be open about how AI will change job roles and responsibilities. This includes: Clearly explaining the organization’s AI strategy Regularly updating employees on how AI is being integrated into work processes Having open discussions about the skills employees need to develop to work alongside AI Alignment with Organizational Values As AI changes how work is done, organizations may need to revisit and update their core values. This might involve: Redefining what teamwork means when AI is part of the team Emphasizing the importance of human creativity and critical thinking Including ethical considerations about AI use in the organization’s values Leadership in the Age of AI Integrating AI into product development and management requires leaders to adapt their approaches: Role of Executives and C-suite Senior leaders must: Develop a clear vision for how AI will be used in the organization Allocate resources for adopting AI and training employees Show adaptability and openness to AI-driven changes Importance of Middle Management Middle managers play a crucial role in successfully integrating AI: Training teams to work effectively with AI tools Overseeing how AI is used in day-to-day operations Building high-performing teams that combine human and AI capabilities Shift from Industrial Age Mindset Leaders need to move away from top-down, command-and-control styles towards more flexible approaches that: Encourage trying new things and learning from mistakes Promote collaboration across different departments Value human skills that complement what AI can do Building a Positive Culture in the AI Era To thrive in the age of AI, organizations need to create a positive culture that embraces new technology while valuing human contributions: The Three T’s: Trust, Transparency, and Training Trust: Create an environment where employees feel secure in their roles and valued for their unique skills Transparency: Keep communication open about AI initiatives and how they affect the workforce Training: Provide ongoing opportunities for employees to learn AI-related skills Importance of Employee Experience and Value Proposition As work changes, organizations must: Redefine what they offer employees to attract and keep talent in an AI-driven workplace Focus on creating positive experiences that blend human interaction with AI-enabled efficiencies Emphasize the unique contributions that human workers make alongside AI tools Evolving Organizational Values Organizations should: Review and update their values to reflect the integration of AI Ensure that values are put into practice, not just written on a wall Develop specific behaviors that show these values in action in an AI-augmented workplace Risk Tolerance and Embracing Failure To foster innovation in an AI-driven environment, organizations should: Encourage calculated risk-taking and experimentation with AI technologies View failures as opportunities to learn and gather valuable data Create a culture where teams feel comfortable trying new approaches and sharing both successes and setbacks Psychological Safety in Teams Building psychological safety is essential for teams working with AI: Encourage open discussion of concerns and ideas related to AI integration Create an environment where team members feel comfortable asking questions and admitting when they don’t know something Recognize and value different perspectives on AI adoption and use Strategies for Enhancing Team Culture As AI transforms work processes, product leaders must adapt their strategies for building and maintaining strong team cultures: Building Connections in Remote and Hybrid Environments With many teams now working remotely or in hybrid settings, leaders should: Prioritize virtual team-building activities Encourage informal virtual interactions to replicate casual office conversations Use AI tools to facilitate better communication and collaboration across distributed teams Importance of Informal Conversations and Ad Hoc Interactions To preserve the benefits of spontaneous interactions in a more structured digital environment: Create virtual spaces for casual conversations Encourage the use of instant messaging for quick questions and idea-sharing Schedule regular “open office hours” for team members to drop in and chat Balancing In-Person and Virtual Collaboration As teams adopt hybrid work models, it’s important to: Make the most of in-person time for activities that benefit from face-to-face interaction, such as brainstorming and team building Use AI tools to enhance virtual collaboration, making remote work more effective Regularly assess and adjust the balance between in-person and virtual work based on team needs and project requirements For example, one product manager mentioned in the podcast that they now use their in-office days primarily for collaborative activities and ideation sessions, reserving focused individual work for remote days. Addressing Generational Differences in Workplace Preferences With multiple generations in the workforce, leaders should: Recognize and accommodate different preferences for technology use and communication styles Create mentoring opportunities that allow for knowledge sharing between generations Develop flexible work arrangements that cater to diverse needs and preferences Interestingly, the podcast highlighted that younger generations often prefer more in-office time, valuing the opportunity to learn from more experienced colleagues through informal interactions. The Role of Vulnerability in Innovation Embracing vulnerability is increasingly recognized as a key factor in fostering innovation and creativity in AI-driven workplaces: Shift Towards More Open and Transparent Leadership Leaders should: Model vulnerability by admitting when they don’t know something and seeking input from team members Create an environment where asking questions and expressing uncertainty is encouraged Share personal experiences of adapting to AI-driven changes Generational Differences in Approaching Vulnerability Recognize that younger generations may be more comfortable with open discussions about mental health and personal challenges Provide training and support for older generations to develop comfort with vulnerability in the workplace Create opportunities for cross-generational dialogue to bridge different approaches to vulnerability Tiffany shared an example of a leader who started team meetings with a brief check-in question unrelated to work, such as “What are you looking forward to this weekend?” Initially skeptical, they found that this practice significantly improved team dynamics and collaboration over time. Preparing for the Future of Work As AI continues to reshape the workplace, product leaders must focus on preparing their teams for ongoing change: Continuous Learning and Adaptation Foster a culture of lifelong learning, encouraging employees to continuously update their skills Provide resources and time for employees to explore new AI technologies and their applications Recognize and reward employees who demonstrate adaptability and willingness to learn Balancing Human Skills with AI Augmentation Identify and cultivate uniquely human skills that complement AI capabilities, such as emotional intelligence and creative problem-solving Develop strategies for effective human-AI collaboration in product development processes Regularly assess the balance between AI-driven tasks and those requiring human judgment Importance of Critical Thinking in Working with AI Tools Train employees to critically evaluate AI-generated outputs and recommendations Encourage the development of skills in data interpretation and ethical decision-making Create processes for human oversight and intervention in AI-driven workflows Tiffany highlighted an example where a product manager asked an AI tool to summarize content from a book, but the AI made a mistake. The manager politely pointed out the error and asked the AI to reread the section, resulting in a much-improved summary. This underscores the importance of human oversight and critical thinking when working with AI tools. Conclusion The integration of AI into product management and development processes presents both challenges and opportunities for organizational culture and team dynamics. By focusing on transparency, adaptability, and human-centric values, product leaders can create resilient, innovative teams capable of thriving in an AI-augmented workplace. As we move forward, the ability to balance technological advancement with human skills and creativity will be key to success in the evolving landscape of product management. Useful links: Check out Tiffany’s website Check out Top of the Mountain Leadership Connect with Tiffany on LinkedIn Innovation Quote “Vulnerability is the birthplace of innovation, creativity, and change.” – Brené Brown Application Questions How can our product team use AI tools to improve collaboration and productivity while maintaining strong human connections? What specific steps can we take to build trust and psychological safety within our team as we integrate more AI into our workflows? How might we need to adapt our leadership style and communication strategies to effectively manage a team that includes both human members and AI assistants? What uniquely human skills should we focus on developing within our team to complement and enhance our use of AI in product development? How can we create a culture of continuous learning and adaptation that keeps pace with the rapid advancements in AI technology? Bio Tiffany Prince is an international speaker, a consultant, a coach, and the owner of Prince Performance. She helps organizations with change management techniques and business strategy processes. Tiffany has also analyzed, designed and delivered customized leadership and learning programs, enabling organizations to meet critical strategic goals. 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. Source

A guide to successful product launches – for product managers Watch on YouTube TLDR The LAUNCH framework, created by James Whitman, offers a complete approach to successful product launches. It has six main parts: Listen to your clients, Assess the opportunity, Unify the team, Navigate the launch, Control the risks, and Hone the process. This framework helps solve common problems in product launches by encouraging teamwork, constant improvement, and strategic planning. By using the LAUNCH framework, companies can improve how they bring products to market, reduce launch failures, and make their product launch processes better over time. The LAUNCH Framework Launching a new product successfully is a big challenge for many companies. More than half of B2B product launches don’t reach their financial goals. This shows that companies need a well-planned approach to product launches. The LAUNCH framework, developed by James Whitman, helps organizations bring new products to market more effectively. In this article, we’ll explore the LAUNCH framework in detail. We’ll provide insights and practical tips for product managers and leaders who want to improve their launch strategies. We’ll cover each part of the framework, discuss common challenges, and offer best practices for putting it into action. Understanding the LAUNCH Framework The LAUNCH framework has six main parts: L – Listen to your clients A – Assess the opportunity U – Unify the team N – Navigate the launch C – Control the risks H – Hone the process Each part deals with specific aspects of the product launch process, providing a complete approach to launch management. Let’s explore each element in detail. 1. Listen to Your Clients Listening to clients effectively is the foundation of successful product launches. Many companies struggle with this step, falling into common traps that can derail their launch efforts. Common mistakes in client listening: Not talking to enough clients Only focusing on the happiest clients Relying on outdated experience Building features for just one specific client To avoid these mistakes, companies should use best practices for client listening: Best Practice Description Involve product leaders in client interactions Follow Bloomberg’s approach of having product leaders participate directly in client meetings and discussions Create a sales cabinet Form a group of experienced salespeople to help with early product design and provide market insights Set up regular client feedback systems Create organized ways to gather and analyze client feedback throughout the product development process By making client listening a priority, companies can make sure their products meet market needs and solve real customer problems. Example: Bloomberg’s Approach to Client Listening Bloomberg, a financial software and media company, has an effective way of listening to clients. They make product leaders part of their service model. Once a year, clients get to meet with a senior product manager to discuss their priorities. This approach has several benefits: It gives product managers direct access to client feedback It helps build stronger relationships with clients It allows product managers to gather insights from many different clients It makes it easier for product managers to get time with clients, without having to go through the sales team This method helps Bloomberg create products that truly meet their clients’ needs. 2. Assess the Opportunity Assessing opportunities is a critical step in the launch process, but it often comes with challenges: Personal biases that affect judgment Discussions that focus on conflict rather than collaboration Too much data that makes it hard to find useful insights To overcome these challenges and assess opportunities effectively, companies should focus on: Reducing bias by using structured decision-making processes Encouraging cooperative, growth-focused discussions among team members Setting specific, date-based targets and milestones for the launch By using these practices, product teams can make better decisions about which opportunities to pursue and how to position their products in the market. 3. Unify the Team Working together across different departments is essential for successful product launches. However, many companies struggle with departments that don’t communicate well and trust issues, especially between product and sales teams. To bring the team together and improve launch results, consider these strategies: Create launch teams with members from product, sales, marketing, and other relevant departments Address trust issues directly through open communication and shared goals Use the strengths of different departments, taking advantage of each team’s unique expertise Use collaborative tools and processes to make communication and information sharing easier By encouraging a unified approach to product launches, companies can ensure that all team members are working towards the same goals. The Sales Cabinet One effective way to unify the team is by creating a “sales cabinet.” Here’s how it works: The product manager asks the head of sales to choose a few experienced salespeople for a special assignment These salespeople become part of a group that helps with early product design The sales cabinet provides valuable market insights to the product team This approach helps build better relationships between the product and sales teams It gives salespeople a chance to contribute to product development, making them more invested in the product’s success By creating a sales cabinet, companies can improve communication between departments and create better products that meet market needs. 4. Navigate the Launch The actual launch phase is a crucial moment in the product’s life. To navigate this phase successfully, companies should focus on: Building excitement and anticipation around the launch day Implementing a fast-paced schedule with daily and weekly activities Continuously listening to market feedback and adjusting strategies as needed Considering different launch approaches, such as phased or soft launches, depending on the product and market conditions A well-executed launch can set the stage for long-term product success and help companies gain an advantage over their competitors. The Importance of Launch Day James Whitman emphasizes that the launch day should be a big deal for the entire company. Here’s why: It marks the start of a new growth opportunity for the company It’s the result of significant investment in time and resources It’s a chance to create excitement among employees and customers It sets the tone for how the market will perceive the new product To make the most of launch day, companies should: Create a sense of anticipation within the company Prepare all departments for their roles in the launch Plan special events or communications to mark the occasion Ensure that customer support and sales teams are ready to handle inquiries By treating the launch day as a significant event, companies can generate momentum and enthusiasm for the new product. 5. Control the Risks Managing risks is a crucial part of product launches. Companies must be ready to identify, assess, and reduce various risks throughout the launch process. Key strategies for controlling risks include: Staying flexible in launch strategies to adapt to changing market conditions Using a phased approach to market release, starting with a smaller target audience and expanding gradually Continuously assessing and adjusting based on market feedback Developing backup plans for potential problems or setbacks By actively managing risks, companies can increase their chances of a successful launch and minimize potential negative impacts on the business. The Importance of Flexibility Whitman emphasizes the need for flexibility in product launches. Here’s an example of how this might work: A company plans to launch a new software product with a specific set of features They start with a small group of beta testers Based on feedback, they realize that one feature isn’t as valuable as they thought, but users want a different feature they hadn’t considered Instead of sticking to the original plan, they adjust the product before the full launch This flexibility allows them to launch a product that better meets market needs By staying flexible and responsive to feedback, companies can reduce the risk of launching a product that doesn’t meet customer needs. 6. Hone the Process The final part of the LAUNCH framework focuses on continuous improvement. This involves: Refining the current product based on market feedback Improving the launch process itself for future products Establishing consistent performance metrics to track progress and identify areas for improvement Creating a culture of learning and adaptation within the company By continuously improving both the product and the launch process, companies can build a competitive advantage and increase their success rates over time. Implementing the LAUNCH Framework: Best Practices and Considerations To effectively implement the LAUNCH framework in your company, consider these best practices: 1. Align with Strategic Goals Make sure your product launch strategy fits with your company’s overall goals. This alignment helps prioritize resources and gain support from senior leadership. 2. Invest in Cross-Functional Training Provide training opportunities for team members to build skills across different areas. This can improve collaboration and reduce communication barriers within the company. 3. Use Technology Implement project management and collaboration tools to make communication easier and streamline the launch process across teams. 4. Establish Clear Metrics Define clear success metrics for each launch and track them consistently. This data-driven approach can help identify areas for improvement and inform future launch strategies. 5. Foster a Culture of Innovation Encourage experimentation and learning from failures. Create an environment where team members feel comfortable sharing ideas and taking calculated risks. 6. Continuously Gather and Act on Feedback Implement systematic processes for gathering feedback from customers, partners, and internal stakeholders throughout the launch process and beyond. 7. Develop a Launch Playbook Create a standardized launch playbook that outlines key processes, templates, and best practices. This resource can help ensure consistency across launches and make it easier to onboard new team members. Conclusion The LAUNCH framework provides a complete approach to product launch management, addressing key challenges and offering practical strategies for success. By focusing on client listening, opportunity assessment, team unification, launch navigation, risk control, and process improvement, companies can significantly enhance their product launch outcomes. Implementing the LAUNCH framework requires commitment, cross-functional collaboration, and a willingness to continuously learn and adapt. Its benefits – including improved go-to-market strategies, reduced launch failures, and optimized product launch processes – make it a valuable investment for companies looking to gain a competitive edge in today’s dynamic market landscape. As you consider implementing the LAUNCH framework in your company, remember that success often comes from consistent application and gradual improvement. Start by focusing on one or two areas where you see the greatest opportunity for improvement, and slowly expand your efforts as you build momentum and gain support from stakeholders. By embracing a structured approach to product launches and fostering a culture of continuous improvement, your company can develop a lasting competitive advantage and drive long-term growth through successful product introductions. Remember, the key to successful product launches lies in listening to your clients, assessing opportunities carefully, unifying your team, navigating the launch process strategically, controlling risks effectively, and continuously honing your approach. With the LAUNCH framework as your guide, you’ll be well-equipped to bring innovative products to market and achieve your business goals. Useful links: Check out LaunchCodeProject.com Connect with James on LinkedIn Innovation Quote “Growth is started internally as a strategic initiative but hired operationally.” – Leah Tharin Application Questions How can we improve our client listening processes to gather more diverse and actionable feedback? What strategies can we implement to better unify our cross-functional teams during product launches? How can we build more flexibility into our launch strategies to better control risks and adapt to market feedback? What metrics should we track to effectively measure the success of our product launches and improve our processes over time? How can we create a culture that supports continuous improvement and learning from both successful and unsuccessful launches? Bio James Whitman is the founder of Growth Guidepost which helps mission-driven leaders bring their visions into the world through product launch and commercialization support. He has dedicated his career to leveraging technology to solve pressing global challenges. His diverse work includes launching businesses to drive post-Soviet economic development, supporting government leaders to speed the delivery of healthcare, bringing excluded groups into the tech workforce, and commercializing innovative technologies to improve the health of our oceans. James held a series of senior commercial roles at Corporate Executive Board (Gartner) through its most dynamic growth period, where he successfully launched more than 20 new products and led the commercial integration of several acquisitions. He has led commercial organizations for ExecOnline, Catalyte, PeaceTechLab, and Oasis Marinas, generating value by creating repeatable commercial practices. James holds an MBA and BA Honours from McGill University, a GC from the London School of Economics, and is a graduate of the Middlebury College Language School. He splits his time between Washington DC and Massachusetts with his wife Anna El-Eini, an accomplished fiction author who inspires him daily to strengthen his writing.   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. Source

How product managers should use the five-step model for creating team culture Watch on YouTube TLDR Product managers often face the challenge of significant responsibilities without formal authority. Creating a people-first culture is essential for gaining influence and driving innovation. A five-step model helps build this culture: caring, trust, unity, accountability, and mentoring. Recognizing the value in every team member and leveraging constraints can lead to significant innovations. Clear purpose helps teams navigate complexity and maintain focus. Mentoring is crucial for developing future leaders and sustaining a strong organizational culture. Introduction: The Product Manager’s Unique Challenge Product managers often find themselves in a unique position: responsible for a company’s future success but lacking the formal authority to implement changes directly. This scenario is akin to steering a ship without having full command over the crew. The key to success in this role lies in the ability to influence and guide others effectively. This is where the concept of a people-first culture becomes invaluable. It’s not just a trendy phrase – it’s a fundamental approach that can significantly enhance a product manager’s effectiveness. In this article, we’ll explore how to build this culture and use it to increase your influence, foster innovation, and create high-performing teams. The Paradox: Technological Progress vs. Social Development Before considering solutions, it’s worth examining a paradox: Why have we made such remarkable progress in technology while seemingly stagnating in our ability to work together effectively? Consider the rapid advancement of technology in recent decades. We’ve progressed from basic mobile phones to sophisticated smartphones that function as portable computers. However, interpersonal challenges in the workplace remain largely unchanged from previous generations. This disparity can be attributed to two key factors: The physical world (including technology) operates on consistent, predictable principles. This consistency facilitates progress and innovation. The social world (human interactions) lacks a universal set of governing rules. This variability makes progress in social realms less linear and more complex. As product managers, we must navigate both these realms. Our role requires bringing people together to create innovative products. The challenge lies in fostering effective collaboration without a clear social framework to guide these interactions. The Three Pillars of Leadership: Know, Do, Be Effective product managers are more than just idea generators or task managers. They are leaders who inspire and guide their teams. To excel in this leadership role, focus on these three key areas: Know: Develop a comprehensive understanding of your product, market, and team dynamics. Do: Take strategic actions to advance your product and support your team. Be: Embody the leadership qualities that align with your values and organizational culture. This framework provides a holistic approach to leadership, encompassing knowledge, action, and personal attributes. The Five-Step Model for Cultivating a People-First Culture Let’s explore a five-step model for creating a culture where people are prioritized, leading to successful product development: 1. Care: Fostering Genuine Concern Envision a team where each member genuinely cares about their colleagues’ success. This forms the foundation of a people-first culture. When individuals feel valued, they’re more likely to take calculated risks, share innovative ideas, and exceed expectations. Demonstrating care: Inquire about team members’ lives outside of work. Take note of important personal details and follow up on them. Offer support when a colleague is facing challenges, even if not directly work-related. 2. Trust: The Catalyst for Collaboration Trust acts as a bridge between caring and effective teamwork. In an environment of trust, team members feel comfortable voicing their opinions, sharing unconventional ideas, and acknowledging mistakes. This openness is crucial for fostering innovation. Building trust: Maintain consistency between your words and actions. Acknowledge when you’re uncertain or have made a mistake. Respect confidentiality and avoid workplace gossip. 3. Unity: Synergy in Action Unity, or “oneness,” refers to creating a team that achieves more collectively than the sum of individual efforts. It’s comparable to a well-coordinated sports team where every member works in perfect harmony. Teams that achieve this level of unity can be 5-10 times more productive than average teams, significantly enhancing overall performance. Characteristics of high-performing teams: Aligned purpose and objectives Transparent and honest communication Mutual respect and support Ability to engage in constructive disagreement 4. Accountability: Ensuring Follow-Through Even highly effective teams benefit from structure. Accountability ensures that all team members fulfill their commitments. It’s not about imposing penalties, but rather about supporting collective success. Implementing effective accountability: Establish clear expectations and deadlines. Conduct regular progress check-ins. Acknowledge successes and learn from setbacks as a team. 5. Mentoring: Investing in Future Leaders The final step focuses on developing future leaders. Mentoring not only benefits individuals but also strengthens the entire organization. Benefits of mentoring: For Mentors For Mentees Refine leadership skills Gain insights from experienced professionals Gain fresh perspectives Develop professional confidence Create a lasting impact Expand professional network Implementing a People-First Approach in Product Management To apply these principles in the practical world of product management, consider the following strategies: Recognize potential in every team member: Approach each individual as a valuable contributor with unique strengths. View constraints as opportunities: Instead of viewing limitations as obstacles, see them as catalysts for creative problem-solving. Support personal and professional growth: Assist team members in achieving their individual goals, which in turn benefits the entire team. Navigate complexity with purpose: Use a clear sense of purpose as a guiding principle during challenging times. Case Study: Leveraging Constraints for Innovation Consider this real-world example of how embracing constraints can lead to significant innovations: A software company faced a major industry shift from text-based to graphical interfaces. Their primary competitor assigned 100 people to develop a next-generation product. Due to recent downsizing, our subject company had only five team members available for this crucial project. Rather than conceding defeat, they adopted a creative approach. Recognizing they couldn’t build everything from scratch, they sought existing tools they could leverage. They discovered Microsoft’s Visual Basic, a new tool at the time that wasn’t yet considered for serious development work. By thinking innovatively and working within their limitations, this small team of five managed to launch their product within 30 days of their much larger competitor. The outcome was remarkable: their company experienced 600% growth over the subsequent five years. This example illustrates how constraints, when approached with the right mindset, can serve as catalysts for innovation. Navigating Complexity: The Power of Purpose In the dynamic field of product management, complexity is a constant. However, a well-defined purpose serves as an effective tool for managing this complexity. A strong sense of purpose offers several advantages: Facilitates decision-making processes Maintains team motivation during challenging periods Simplifies feature and resource prioritization Enhances alignment across different teams and departments Consider purpose as your team’s guiding principle. When faced with uncertainty, it helps maintain direction and focus. Mentoring: Cultivating the Next Generation of Product Leaders Mentoring is a crucial component in creating a sustainable people-first culture. Its importance stems from several factors: It helps maintain and strengthen organizational culture Develops a pipeline of future leaders Improves employee retention by demonstrating investment in professional growth Enhances overall team performance and innovation capacity It’s important to note that mentoring is a reciprocal process. As a mentor, you often gain new insights and perspectives while guiding others. Integrating Timeless Principles in Modern Product Management While the principles discussed are universally applicable, it’s worth noting that many of these ideas have roots in long-standing biblical traditions. The concepts of valuing individuals, fostering unity, and purposeful leadership can be found in biblical wisdom. By incorporating these principles into your product management approach, you’re drawing on deep-rooted understanding of effective human collaboration. Practical Steps: From Theory to Practice While understanding these concepts is valuable, their true impact is realized through implementation. Here are some actionable steps to consider: Implement regular check-ins: Schedule time to connect with team members about their personal goals and challenges. Trust-building exercise: Share a professional learning experience with your team, discussing the insights gained. Unity workshop: Organize a team activity focused on aligning individual and collective purposes. Accountability system: Establish partnerships within the team for mutual support in achieving key objectives. Mentoring initiative: Develop a structured mentoring program within your product team or department. Conclusion: Embarking on Your Journey to a People-First Team Culture Developing a people-first culture is an ongoing process that requires consistent effort, reflection, and adaptability. The rewards, however, are substantial: increased influence, enhanced innovation, and a team capable of addressing complex challenges effectively. As a product manager, your role extends beyond product development – you’re shaping the future of your organization. By prioritizing people, you’re creating an environment conducive to exceptional outcomes. Useful links: Check out Gary’s website Check out Gary’s book, Built to Beat Chaos Innovation Quote “We are created to be victors over chaos, not victims.” – Gary Harpst Application Questions How can we demonstrate genuine concern for each other, particularly in remote or high-pressure work environments? What specific action could we take this week to enhance trust within our team? How might we reframe our most significant current challenge as an opportunity for innovation? What does peak performance look like for our specific product team? How can we balance accountability with fostering an environment that encourages calculated risk-taking and creativity? Bio Gary Harpst is the CEO of LeadFirst, creator of the first complete ERM employee relationship management system that does for leaders what CRM does for sales people. His passion is combining business excellence and biblical wisdom. He co-founded three high-tech businesses, including Solomon Software which merged with Great Plains and was sold to Microsoft.  Gary has authored three books with his latest “Built to Beat Chaos, Biblical Wisdom for Leading Yourself and Others” (Wiley) is being released April 2023. He has built an overflowing life with his wife, three children, and four grandchildren. 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.   Source

Outcome-Driven Innovation – for Product Managers Watch on YouTube TLDR Tony Ulwick, creator of Jobs-to-Be-Done, introduces Outcome-Driven Innovation (ODI), a revolutionary approach to product management. ODI shifts focus from generating ideas to understanding and addressing customer needs, leading to more successful products and innovations. ODI prioritizes understanding customer needs over generating product ideas The approach uses both qualitative and quantitative research to identify unmet customer needs Key components include the job map, need statements, and the opportunity algorithm ODI stays focused on customer problems, not potential solutions This customer-centric approach to innovation offers product managers a structured method to create products that truly meet market needs and drive business success. Introduction Welcome to the 500th episode of this podcast—that’s 500 weeks, or nearly 10 years of episodes for product managers and leaders. I have a special guest to discuss how we have seen product innovation change over the last several years—what has worked and what has not. As a product professional, you need perspective on where things are headed and what is working, which is aided by looking at the changes that have occurred. Let’s gain perspective from the knowledge and experience of one of the most influential people in product innovation, Tony Ulwick. The Birth of Outcome-Driven Innovation (ODI) Ulwick’s lightbulb moment came during his time at IBM. He was part of the team that created the PCjr, a product that flopped badly. This failure led to a crucial question: What if we knew beforehand how customers would judge our product? This idea became the foundation of Outcome-Driven Innovation. Ulwick realized that if we could predict how customers would measure a product’s value, we could design products to meet those criteria. Even better, if these criteria stayed the same over time, we could use them to guide long-term product development. Building the ODI Framework After the PCjr setback, Ulwick moved from engineering to product planning at IBM. He started exploring what makes innovation successful. His early research involved a simple but powerful method: asking customers to compare products. “What makes Product A better than Product B?” This question led to valuable insights. Ulwick found that customer needs fell into three main categories: Functional aspects: How well does the product do its job? Consumption aspects: How easy is it to use the product? Financial aspects: Is the product worth its cost? Over time, this categorization evolved into the Job Map concept. The Job Map breaks down what customers are trying to do into steps like planning, gathering materials, doing the task, and checking results. This framework made innovation more predictable and effective. Fine-Tuning the ODI Process As Ulwick refined ODI, he drew inspiration from various sources. Theodore Levitt’s famous quote, “People don’t want a quarter-inch drill, they want a quarter-inch hole,” resonated deeply. It reinforced the idea of focusing on the customer’s underlying goal. Collaborating with Clay Christensen led to the popular term “Jobs-to-Be-Done.” This catchy phrase made it easier to explain the concept of focusing on customer goals rather than product features. A key part of refining ODI was creating stable criteria for good need statements, which Ulwick calls “desired outcomes.” These statements are: Stable over time: They don’t change quickly Actionable: You can do something about them Measurable: You can tell if you’ve achieved them Controllable: You can influence them Predictive of success: They indicate if a product will do well The Research Process: Qualitative and Quantitative ODI uses both qualitative and quantitative research to understand customer needs deeply. Here’s how it works: Qualitative Phase: Understand the job to be done Break it down into steps Identify all the ways customers measure success Quantitative Phase: Create a survey based on qualitative findings Ask hundreds or thousands of customers to rate: How important each outcome is How satisfied they are with current solutions This data helps identify unmet needs – outcomes that are very important but not well satisfied by existing products. Ulwick introduced the opportunity algorithm in a 2002 Harvard Business Review article. This simple calculation helps prioritize needs based on importance and satisfaction scores. It’s been about 93.5% effective in spotting the best opportunities for innovation. A key principle of ODI is keeping customers focused on their problems, not potential solutions. This ensures that the research captures genuine needs rather than preconceived ideas about products. The Surprising State of Innovation Practices Despite ODI’s proven effectiveness, many companies still use an “ideas first” approach. They focus on generating and managing ideas rather than understanding customer needs. Ulwick finds this surprising and attributes it to the challenge of changing ingrained habits. This resistance to change is a significant hurdle in implementing more effective product innovation strategies. It highlights the need for education and training in customer-centric innovation methods. Making ODI Work Better To help companies implement ODI more successfully, Ulwick’s team has introduced several improvements: Project Cohorts: These are training sessions that guide teams through each step of the ODI process. They help team members understand how to use the data effectively. Deep Dive Research: After identifying top opportunities, researchers investigate why these needs are problems, what causes them, and how customers currently work around them. Ideation Support: With a deep understanding of unmet needs, teams are better equipped to come up with effective solutions. These enhancements have significantly improved the success rate of ODI implementations. For example, one company solved 14 unmet needs in just three hours after going through this process. Researching Customers in the Remote Work Era As more work happens remotely, product managers face new challenges in customer research. Ulwick suggests moving from observation to focused interviews. The key is to keep customers thinking about their problems, not potential solutions. Here are some strategies for effective remote research: Conduct interviews in a controlled online environment Train customers to be good interviewees Use immersion sessions with small groups of customers Collaborate on validating job steps and creating the job map Validate findings with a broader, global customer base This approach allows for deep insights while adapting to the realities of remote work and global markets. AI in Innovation: Promise and Limitations Artificial intelligence tools like ChatGPT are emerging as potential aids in innovation. These tools can help generate initial job maps and outcomes, providing useful background information. However, Ulwick emphasizes that AI should complement human expertise, not replace it. The most promising approach combines AI capabilities with human insight and experience. This blend of technology and human skills offers the best path forward in product innovation. Conclusion Outcome-Driven Innovation offers a structured, customer-focused approach to creating successful products. By understanding and addressing unmet customer needs, product managers can greatly improve their chances of market success. As business landscapes change and new technologies emerge, ODI principles remain relevant. They adapt to new challenges while keeping a laser focus on customer jobs and outcomes. For product managers aiming to boost their innovation game, mastering these concepts can provide a significant edge in the market. Useful links: Check out Tony’s book The Statue in the Stone Get a free ebook: JOBS TO BE DONE: Theory to Practice Watch Tony’s video What is Jobs-to-be-Done? Innovation Quote “If I had one hour to save the world, I would spend 55 minutes defining the problem and only five minutes finding the solution.” – Albert Einstein Application Questions How does your current product development process compare to ODI? What aspects of ODI could improve your process? Think about a recent product that didn’t do well in your company. How might using ODI have led to a different outcome? How could keeping customers focused on problems, not solutions, change your approach to customer research? How might you use the opportunity algorithm to prioritize product features or improvements? Discuss how AI tools could help your product innovation process. How would you balance AI insights with human expertise? Bio Tony is the originator of Jobs-to-be-Done. I first discovered Tony when I read his book, What Customers Want: Using Outcome-Driven Innovation to Create Breakthrough Products and Services and then invited him to speak at the Denver PDMA chapter, back in 2006. He published that book while I was working on my PhD in Innovation and it resonated so strongly with my research on why products fail and what to do instead. He is also the author of the more recent book Jobs to be Done: Theory to Practice. Both are valuable and should be in your library. Tony also has 12 patents to his name. He began his career as a mechanical engineer, product planner, and market researcher for IBM and founded his consulting firm, Strategyn, 10 years later, which has helped leading companies generate billions of dollars in revenue growth. Thanks! Thank you for taking the journey to product mastery and learning with me from the successes and failures of product innovators, managers, and developers. If you enjoyed the discussion, help out a fellow product manager by sharing it using the social media buttons you see below. Source

Solve problems as a team in just two hours – for product managers Watch on YouTube TLDR Imagine solving big product problems in just two hours instead of five days. Sounds impossible, right? Not anymore! Teresa Cain has cracked the code with her two-hour design sprint method. This quick and efficient approach to product innovation is changing the game for companies big and small. In this article, we’ll explore: What a two-hour design sprint is and how it works Why it’s a game-changer for product teams How to run your own two-hour sprints Tools that make rapid innovation easier Real-world examples of two-hour sprints in action Get ready to supercharge your product development process and leave your competition in the dust! Why Speed Matters in Product Innovation In today’s fast-paced world, product teams are always racing against the clock. The traditional five-day design sprint, made famous by Google, has been a go-to method for solving tough problems. But let’s face it – not everyone has five whole days to spare. That’s where the two-hour design sprint comes in. It’s like the espresso shot of product innovation – quick, powerful, and gets the job done. But can you really solve complex problems in just 120 minutes? Teresa Cain says yes, and she’s got the results to prove it. The Two-Hour Design Sprint: A Crash Course So, what exactly is a two-hour design sprint? Think of it as a mini-version of the five-day process, but supercharged. Two hours is not a big time commitment, and it helps you get a group of stakeholders all together to solve a problem. Here’s how it breaks down: 1. Get to Know Your User (30 minutes) First things first – who are you solving for? This step is all about understanding who your user is. Example: Imagine you’re designing a new dashboard for a fintech app. You need to know if you’re building it for an analyst who’ll use it daily or an executive who might look at it once a year. Big difference, right? 2. Dig into the Problem (30 minutes) Now that you know your user, it’s time to get to the heart of the issue. What’s bugging them? What’s standing in their way? This is where you’ll use the classic “How might we…” question to frame the problem. Example: For our dashboard, we might ask, “How might we create a dashboard that helps analysts quickly spot trends and take action?” Perhaps users are spending a lot of time on manual tasks. Maybe they’re popping between screens. Maybe they are using their mobile device or not even on a desktop computer. Maybe they’re moving buildings while they’re doing their different tasks. 3. Brainstorm and Choose Solutions (60 minutes) This is where the magic happens. After you’ve thought about the problem as a group, you ideate and pitch your concepts as a group. Everyone puts their thinking caps on and starts throwing ideas around. At the end of the sprint, you will vote on the best solution and decide if you want to move forward to testing and prototyping. Why Two-Hour Sprints are a Game-Changer You might be thinking, “Sounds great, but does it really work?” According to Cain’s research, the answer is a resounding yes. Here’s why two-hour sprints are shaking things up: Benefit What It Means for You More Sprints, More Solutions Run up to 52 sprints a year instead of just a few Budget-Friendly Less time and money spent compared to five-day sprints, but similar results Team Bonding Brings people together more often, improving communication Faster Results Get from idea to action quicker than ever The best part? Cain found that 80% of the time, two-hour sprints led to the same solutions as five-day sprints. Talk about efficiency! Would you rather spend two hours and solve 50 problems in a year or do three, five-day design sprints and solve three problems? With two-hour sprints, you can solve more problems. How to Bring Two-Hour Sprints to Your Team Ready to give two-hour sprints a try? Here’s how to get started: Pick the Right Problems Not every issue needs a sprint. Look for problems that: Need a quick fix You already know something about Could benefit from a group brainstorm Cain suggests focusing on any problem that you need to solve immediately and already have ideation on, perhaps in your backlog or from a client request. Get the Right People in the Room Aim for a group of 15-20 stakeholders. Train Your Team The beauty of two-hour sprints is that anyone can lead them. This process is meant for anyone in the organization to run it as the moderator. So spread the knowledge! Follow Through The sprint might end after two hours, but the work doesn’t. Make sure to: Assign next steps to team members Set up time to test your ideas with real users Add your solutions to your product roadmap Tools to Make Your Sprints Zoom In today’s digital world, the right tools can make all the difference. Here are some top picks for two-hour sprints: Tool What It’s Great For Figma/FigJam Designing and brainstorming together Miro Digital whiteboarding and teamwork Mural Planning and organizing ideas visually These tools help teams work together smoothly, whether they’re in the same room or spread across the globe. Overcoming Speed Bumps Like any new method, two-hour sprints come with their own challenges. Here’s how to tackle them: Keeping the Customer in Mind With less time, it’s easy to forget about the user. To avoid this: Do your homework on user needs before the sprint Invite people who talk to customers regularly Use real data to guide your discussions Avoiding Hasty Decisions The clock is ticking, but don’t rush to solutions. Instead: Follow the sprint structure closely Encourage different viewpoints Keep asking “How might we…” to stay problem-focused Balancing Speed and Quality Fast doesn’t have to mean sloppy. To keep standards high: Set clear goals for each sprint Use timers to keep discussions on track Plan for follow-up research after the sprint AI: Friend or Foe in Design Sprints? With AI tools like ChatGPT making waves, it’s natural to wonder how they fit into the sprint process. Cain advises caution: Since ChatGPT doesn’t know your productor users, use it with a grain of salt. Real-World Success: Two-Hour Sprints in Action Want to see how two-hour sprints work in the real world? Let’s look at how Cain’s team at TreviPay, a leader in global billing, puts them to use: What They Do How They Do It Run 52 sprints a year One sprint every week Involve 30-40 team members Mix of product, UX, and design experts Focus on urgent needs Address client requests and market changes Act on results quickly Turn sprint outcomes into user stories right away This approach helps TreviPay stay ahead in a fast-moving industry with new competitors popping up all the time. The Future of Problem-Solving As we look ahead, it’s clear that quick thinking and adaptability are key. The two-hour sprint method is just the beginning of a shift in how we tackle product challenges. What’s on the horizon for product innovation? More AI and machine learning in the idea process Faster ways to build and test prototypes Better tools for remote and asynchronous teamwork Using data to drive more decisions in product development Conclusion The two-hour design sprint is a powerful tool for any product team looking to innovate faster and smarter. By packing the essence of design thinking into a compact, high-energy session, you can tackle more problems, involve more people, and drive innovation at warp speed. Ready to give it a shot? Here’s your quick-start guide: Learn the basics of the two-hour sprint method Teach your team how to run and participate in sprints Pick a small problem for your first sprint Run the sprint and gather feedback Keep refining your process and do sprints regularly By embracing this fast, user-focused approach to problem-solving, you’ll be well on your way to creating products that your customers will love and that will keep your business ahead of the curve. Useful links: Check out Teresa’s book Solving Problems in 2 Hours Visit Teresa’s website Connect with Teresa on LinkedIn Check out Teresa’s work on Figma and Udemy Listen to episode 288: Design sprints for product managers – with John Zeratsky Innovation Quote “We cannot solve our problems with the same thinking we used when we created them.” – Albert Einstein Application Questions How might we integrate two-hour design sprints into our current product development process? What specific challenges or opportunities in our workflow could benefit most from this rapid problem-solving approach? Considering our organization’s unique culture and team dynamics, how can we ensure that two-hour sprints maintain a deep understanding of user needs while leveraging the efficiency of the shorter format? In what ways could we use collaborative tools like Figma, Miro, or Mural to enhance our two-hour sprints, especially for remote or hybrid teams? How might these tools change the way we ideate and make decisions? How can we balance the quick pace of two-hour sprints with the need for thorough follow-up and implementation? What processes could we put in place to ensure sprint outcomes are effectively integrated into our product roadmap? Reflecting on our recent product challenges, can you identify a specific problem we faced that could have benefited from a two-hour sprint? How might the outcome have been different if we had used this method? Bio We’ve talked before about design sprints with John Zeratsky, who co-created a way to solve big problems at Google in just 5 days, resulting in the popular 5-day design sprint. What if you don’t have 5 days, but 2 hours? It turns out you can still solve a lot of complex problems in a 2 hour design sprint if you know how. Think about that — being able to confidently solve complex problems with a team in only 2 hours instead of days. To tell us how to gain have that confidence, Teresa Cain is with us. She is the bestselling author of Solving Problems in 2 Hours: How to Brainstorm and Create Solutions with Two Hour Design Sprints, whose first edition became an instant hit among tech teams worldwide. The all new edition, which includes new AI tools, is now available. She is currently the Director of Product Management, User Experience and Design for TreviPay, a leader in global billing and invoicing. She is also the founder of Lucid Startup Consulting, a training firm focused on research, strategy, and vision for product managers, UX teams, businesses and entrepreneurs.  Thanks! Thank you for taking the journey to product mastery and learning with me from the successes and failures of product innovators, managers, and developers. If you enjoyed the discussion, help out a fellow product manager by sharing it using the social media buttons you see below. Source

Mastering product lifecycle management – for product managers Watch on YouTube TLDR Product lifecycle management is key to successful product development and innovation. This article explores the stages of a product’s life, from launch to retirement, and how they differ across industries and product types. Here are the main takeaways: The classic product lifecycle stages are introduction, growth, maturity, decline, and retirement. For software and SaaS products, development and lifecycle management often overlap. Ongoing customer feedback is vital throughout the product’s life. Teamwork across different departments is crucial for effective lifecycle management. Strategies need to be adapted for different types of products and industries. Innovation is key to extending and improving the product lifecycle. Understanding these ideas and using them well can help product managers handle the complexities of product lifecycle management and drive innovation in their companies. Introduction In today’s fast-moving business world, product lifecycle management is a must-have tool for product managers and innovators. As markets change and customer needs shift, knowing how to guide a product through its various life stages is crucial for staying competitive and growing. Today we’re with John Rovnan, who takes us through the details of product lifecycle management, explaining strategies and best practices to help product managers excel. Understanding the Product Lifecycle The product lifecycle is a core concept in product management and innovation strategies. It covers a product’s entire journey from idea to market retirement. Let’s break down the traditional stages of the product lifecycle: Stage What Happens Introduction The product is launched and introduced to customers Growth Sales and market share grow quickly Maturity Sales growth slows down, competition increases Decline Sales decrease as newer products enter the market Retirement The product is taken off the market It’s important to note that the product lifecycle can look very different depending on the type of product and its industry. For example, a software product’s lifecycle might be quite different from a medical device’s lifecycle. In regulated industries like healthcare, the product lifecycle often faces more constraints due to rules and regulations. This can affect how quickly changes can be made to a product and what strategies can be used throughout its life. When Product Development and Lifecycle Management Overlap One key insight from the podcast is that product development and lifecycle management are increasingly overlapping, especially in software and SaaS industries. This blending of stages offers both opportunities and challenges for product managers. On one hand, it allows for more flexible and responsive product development, with the ability to quickly make changes based on customer feedback. On the other hand, it can make it harder to clearly separate different stages of the product lifecycle. For software products, the traditional “big bang” launch is often replaced by a more gradual rollout, with features being introduced bit by bit. This approach allows product managers to: Use the software itself as part of the research process Try techniques like “concierge MVPs” and “fake doors” to gauge interest Continuously gather and use customer feedback However, this blurring of development and lifecycle management can also create challenges. For example, product managers can get mired in the backlog and not have enough time to talk to customers. Customer Feedback Throughout the Lifecycle One of the most important aspects of effective product lifecycle management is continuously gathering and using customer feedback. This feedback is crucial not just during initial development, but throughout the entire life of the product. The podcast emphasizes the importance of dedicating time to customer engagement, with some experts suggesting that product managers should spend about 30% of their time interacting with customers. However, the reality is often quite different, with many product managers struggling to find time for customer interactions among their other responsibilities. To address this challenge, product managers can use several strategies: Use existing resources: Get feedback from sales teams, customer service reps, and other customer-facing roles. Conduct formal Voice of Customer (VOC) sessions: Schedule dedicated time for in-depth customer interviews and feedback sessions. Use multiple channels: Incorporate feedback from various sources, including sales calls, customer support interactions, and user research. Involve team members from different departments: Invite colleagues from various teams to participate in customer interactions and share insights. It’s crucial to balance customer requests with the overall product vision. Navigating Different Lifecycle Stages Each stage of the product lifecycle presents unique challenges and opportunities. Let’s explore some strategies for effectively managing the growth, maturity, and decline stages. Growth Stage During the growth stage, product managers should focus on: Quickly increasing market share Scaling operations to meet growing demand Monitoring and responding to emerging competitors Continuously improving the product based on early customer feedback Maturity Stage As the product enters maturity, competition typically increases, and sales growth may slow. Key strategies for this stage include: Re-evaluating product positioning to stay relevant Enhancing product features to stand out from competitors Building and maintaining customer loyalty Optimizing pricing strategies Rovnan emphasizes the importance of maintaining strong relationships with customers during this stage, particularly in industries like healthcare where loyalty plays a significant role. Understanding emotional aspects can help in building products that truly resonate with users. Decline Stage When a product enters the decline stage, product managers must make tough decisions. Key considerations include: Recognizing when it’s time to retire the product Planning for a smooth transition away from the declining product Communicating effectively with customers, sales teams, and other stakeholders Using lessons from the declining product to inform future product development Teamwork in Lifecycle Management Effective product lifecycle management requires strong collaboration across various departments within an organization. Some strategies for fostering cross-functional collaboration include: Involving team members from different departments in customer interactions Sharing insights and learnings across teams Ensuring consistency in messaging and value proposition across all customer touchpoints Leveraging the expertise of different team members throughout the product lifecycle By fostering a collaborative environment, product managers can ensure that all aspects of the product lifecycle are effectively managed, from development and marketing to sales and support. Adapting to Different Product Types and Industries The approach to product lifecycle management can vary significantly depending on the type of product and its industry. For example: Regulated Industries (e.g., Medical Devices) Higher bar for making changes to products Longer development cycles More extensive documentation and testing requirements Greater emphasis on long-term reliability and support Software and SaaS Products More frequent updates and iterations Ability to quickly respond to customer feedback Continuous development and deployment Greater flexibility in feature rollouts Product managers must be aware of these differences and adapt their strategies accordingly to ensure effective lifecycle management across different product types and industries. Innovation in the Product Lifecycle Innovation plays a crucial role in product lifecycle management, helping to extend the life of existing products and create new opportunities for growth. Rovnan breaks down the innovation process into three key components: Creativity: Coming up with new ideas, regardless of feasibility Invention: Building something new and different Innovation: Creating solutions that change behavior or enable new possibilities Rovnan uses the example of the Segway to illustrate the difference between invention and innovation. While the Segway was a novel invention, it didn’t truly innovate because it failed to consider the broader context of urban living and user needs. Product managers should strive to balance small improvements with more transformative innovations throughout the product lifecycle. This approach can help maintain competitiveness in mature markets while also exploring new opportunities for growth. Key Skills for Effective Product Lifecycle Management To excel in product lifecycle management, product managers should develop and hone several key skills: Flexibility and adaptability: The ability to adjust strategies as market conditions change Cross-functional communication: Effective collaboration with various departments and stakeholders Customer-centric mindset: A focus on understanding and meeting customer needs throughout the product lifecycle Strategic thinking: The ability to balance short-term goals with long-term product vision Data analysis: Skill in interpreting market trends and customer feedback to inform decision-making By developing these skills, product managers can navigate the complexities of product lifecycle management more effectively and drive innovation within their organizations. Conclusion Product lifecycle management is a critical skill for product managers and innovators in today’s fast-paced business environment. By understanding the various stages of the product lifecycle, adapting strategies to different product types and industries, and fostering teamwork across departments, product managers can more effectively navigate the challenges of bringing products to market and maintaining their success over time. Useful link: Connect with John on LinkedIn Innovation Quote “Innovation changes behavior.” – John Rovnan Application Questions How does your company currently handle product lifecycle management? Are there areas where you see room for improvement? What strategies have you found most effective for gathering and using customer feedback throughout the product lifecycle? How do you balance the need for innovation with the constraints of your industry or product type? In what ways has the blending of product development and lifecycle management affected your role as a product manager? How do you encourage teamwork across different departments in your product lifecycle management efforts? Bio Today we are talking about life cycle management, which is a topic covered in the Innovation Management knowledge area. You’ll learn what the phases of a product life cycle are, how the life cycle is different for SaaS products vs products that involve hardware or take a physical form, and how you can better navigate the life cycles of your products. Joining us is John Rovnan. He has an extensive background in new product development, that spans marketing, engineering, verification & validation, and regulatory compliance, with deep experience in medical technologies. He was most recently a Principal Product Manager at ISACA, a non-profit organization helping IT professionals grow their skills in digital trust and is starting a new role as we speak. John has also served in several roles for the Pittsburgh PDMA chapter, including Chapter President. Thanks! Thank you for taking the journey to product mastery and learning with me from the successes and failures of product innovators, managers, and developers. If you enjoyed the discussion, help out a fellow product manager by sharing it using the social media buttons you see below. Source

Essential strategy tools and frameworks for product managers Watch on YouTube TLDR Want to level up your product management game? This guide dives into the world of product strategy, sharing insights from expert Andreas Maihoefer. We’ll explore key tools like the House of Strategy, which shows how different levels of strategy fit together, and the VRIO analysis, which helps you spot your competitive edge. You’ll learn how to define your business’s core and why planning is crucial, even if plans change. Whether you’re new to product management or looking to sharpen your skills, this article will help you think more strategically and create products your customers will love. Introduction Ever felt like you’re navigating the wild world of product management without a compass? You’re not alone. Many product managers know strategy is important, but struggle to develop and use it effectively. This knowledge gap can slow down your career and limit your impact on your company’s success. That’s where Andreas Maihoefer comes in. He’s a strategy whiz with experience in both the corporate world and academia. In this article, we’ll share his insights to help you level up your strategic thinking and become a product management superstar. Why Strategy Matters in Product Management Think of strategy as your product’s North Star. It guides your decisions, helps you prioritize features, and positions your product in the market. Without a solid strategy, you might end up with a cool product that nobody wants to buy. Maihoefer stresses that understanding strategy is crucial for product managers. It’s not just about creating great products – it’s about aligning your work with your company’s big-picture goals. Master this, and you’ll see your career take off as your influence in the company grows. Picking the Right Strategy Tools Before we dive into specific tools, let’s talk about what makes a strategy tool useful. Maihoefer says a good tool should: Help you plan and think clearly Make it easy to work with others Help you explain your ideas visually Let you track progress and put plans into action Here’s a pro tip: Don’t rely on just one tool. Using multiple tools gives you a more complete picture of your strategic landscape. The House of Strategy: Your Strategic Blueprint Imagine your company’s strategy as a house. This mental picture, called the House of Strategy, helps you see how different levels of strategy fit together. The Roof: Your Company’s Foundation At the top, we have your company’s mission (why you exist), vision (where you’re going), and values (how you behave). These guide all your strategic decisions. The Attic: Corporate Strategy Just below the roof is your overall company strategy. This is how you plan to achieve your mission and vision while sticking to your values. Upper Floors: Business Unit Strategies These strategies are for different parts of your company, like specific product lines. They need to line up with the corporate strategy above. Lower Floors: Functional and Operational Strategies At the ground level, we have strategies for different departments (like marketing or HR) and day-to-day operations. These show how each part of the company contributes to the bigger picture. The House of Strategy reminds us that all these levels need to work together. It’s like having an elevator connecting all the floors – information and ideas should flow up and down easily. Defining Your Core: What Makes You Special? Another key part of product strategy is knowing your company’s core – what makes you unique. This idea comes from Chris Zook of Bain & Company, and it’s more than just identifying your main product.   Zook suggests looking at seven areas to define your core: Products or Services Customer Segments Customer Needs Channels Geographies Vertical Integration Capabilities Many companies focus on the first three, but Maihoefer says capabilities are super important. These are the unique skills and resources that set you apart and are hard for competitors to copy. For example, Apple’s design capabilities and ecosystem integration are core strengths that go beyond just making phones or computers. Understanding your core helps you: Spot what gives you an edge over competitors Make smart choices about growing or diversifying Protect and strengthen what makes you special VRIO Analysis: Finding Your Competitive Edge Once you know your core capabilities, how do you tell if they give you a real advantage? That’s where the VRIO analysis comes in. It’s a tool to assess whether a capability or resource gives you a lasting competitive edge. By checking your capabilities against these criteria, you can see how valuable they are: All four? You’ve got a lasting competitive advantage. V, R, and O? You have a temporary edge. Just V and O? You’re on par with competitors. Only O or none? You’re at a disadvantage. This analysis helps you decide which capabilities to invest in and which might need work. More Tools for Your Strategy Toolkit While the House of Strategy, Core Definition, and VRIO analysis are great, there are other useful tools too: Boston Consulting Group’s Growth Share Matrix: This helps you analyze your product portfolio and decide where to invest. SWOT Analysis: This classic tool looks at Strengths, Weaknesses, Opportunities, and Threats. Maihoefer suggests adding ratings to make it more nuanced. SWOT+T Analysis: This adds Trends to the mix, helping you spot market changes. Putting Strategic Thinking into Action Ready to boost your strategic skills? Try these steps: Learn your company’s overall strategy, including its mission and values. Understand how your product fits into the bigger picture. Use tools like Core Definition and VRIO to find what makes your product special. Practice strategic planning, even for small projects. Work with people from different departments to get fresh perspectives. Stay updated on industry trends that could affect your product. Keep checking and adjusting your strategy based on how your product is doing. Do these things, and you’ll not only make better products but also stand out as a strategic thinker in your company. Conclusion Becoming a strategy master in product management is an ongoing journey. It takes practice, learning, and adapting. By using tools like the House of Strategy, Core Definition, and VRIO analysis, you can sharpen your strategic thinking and make better decisions. As you grow your strategic skills, you’ll not only create better products but also become more influential in your company. This will help your career take off and make you a true product master. Keep innovating. Useful links: Connect with Andreas on LinkedIn Visit Andreas’s website Innovation Quote “In preparing for battle, I have always found that plans are useless, but planning is indispensable.” – General Dwight D. Eisenhower Application Questions How well do we know our company’s overall strategy? How does our product strategy fit in? What are our core capabilities? How do they stack up in a VRIO analysis? How can we make our planning process better to prepare for market changes? Which strategy tools work best for us? Are there new ones we should try? How can we explain our product strategy better to people in different parts of the company? Bio Today our topic is strategy, which I expect our guest would argue is the most important of the 7 knowledge areas for product mastery. We all know strategy is important — it gets talked about enough. But, how a strategy is developed is seldomly talked about. Consequently, not many people can properly develop a strategy. That also means few people can evaluate a strategy. Since product innovation should be aligned with strategy, you need to be one of those few people who can properly develop and evaluate strategy. By the end of this episode, you’ll be on your way to do that. Joining us is a product management and strategy master Andreas Maihoefer. He has guided executives in developing organization strategy and led product organizations in developing product strategy. He also teaches at the University of Pittsburgh and previously at Carnegie Mellon University. Thanks! Thank you for taking the journey to product mastery and learning with me from the successes and failures of product innovators, managers, and developers. If you enjoyed the discussion, help out a fellow product manager by sharing it using the social media buttons you see below. Source

Product management and the tech industry Watch on YouTube TLDR In this episode, former Google product management director Tom Leung shares his experiences with recent tech industry layoffs and offers valuable advice for product managers facing career changes. Key takeaways include: Seeing layoffs as chances for personal and professional growth Embracing a “gap year” mindset to explore new experiences and skills Focusing on solving big customer problems in product development Adapting to the changing job market for product managers Balancing innovation with practical value in the age of AI and new tech Product managers can use these insights to navigate career shifts, boost their skills, and approach product development with a fresh focus on customer needs and market demand. The Changing Landscape of Tech Employment The tech world has seen big changes lately, with even giants like Google facing restructuring and layoffs. Tom Leung, who used to be a director of product management at Google, shares his firsthand experience with the company’s 2023 layoffs. His story gives us a peek into how the tech job market is changing and what it means for product managers, along with tips for navigating smartly. Google’s Restructuring and Layoffs in 2023 In January 2023, Google started a series of layoffs. Leung remembers the strange experience of telling team members about the changes. He joined Google in 2006, and up until 2023 he saw very few layoffs. The first wave of layoffs in January was followed by more throughout the year, affecting top-performing employees. This change in how Google treated its workers showed how unstable the tech job market can be and why product managers need to be ready for unexpected career changes. Impact on Company Culture and Feeling Safe at Work The layoffs had a big effect on Google’s company culture, especially when it came to feeling safe at work. Leung explains that one of Google’s core values is psychological safety because if you have really strong psychological safety in the team, you can bring out the best performance. The layoffs pierced the veil of safety. This shift made many employees rethink how secure their jobs were and what their career paths might look like. It shows why it’s important for product managers to be flexible and keep learning new skills. Personal Stories of Career Changes Leung’s journey from Google to new opportunities offers valuable lessons for product managers facing career changes. His experience shows the importance of embracing change and seeing setbacks as potential opportunities to grow. From Google to New Adventures After working at Google for 10 years, Leung was already thinking about a career change. When he was affected by the layoffs in 2023, he chose to see it as an opportunity rather than a problem. Embracing the “Gap Year” Mindset Leung suggests looking at career changes as a “paid sabbatical” or “gap year.” He encourages product managers to use this time to grow personally and professionally. He shares his own experiences: Working on a presidential primary campaign in New Hampshire Teaching product management classes Making angel investments in promising startups Exploring potential startup ideas This approach allows product managers to learn new skills, explore different interests, and maybe even find new career paths. Advice for Product Managers Facing Career Changes Drawing from his experiences, Leung offers valuable tips for product managers navigating career transitions in today’s tech world. Seeing Layoffs as Opportunities Instead of viewing layoffs as purely negative, Leung encourages product managers to see them as chances for growth and exploration. He tells people to think about being in between jobs like a gap year, assuming they received a good severance package. Since they won’t get one again for a while, he advises them to take full advantage of it. He suggests using this time to: Learn a new language Pick up a new coding skill Start a side business Write a book Travel to new places Spend more time with family or coaching your kid’s team The Current Job Market for Product Managers Leung gives insights into the current job market for product managers, highlighting the imbalance between available talent and open positions. He notes the increased competition and higher employer expectations. Right now is an extremely imbalanced time. There’s a massive surge of very capable talent on the market and very few new roles being opened up. Strategies for Job Seekers in a Tough Market Given the challenging job market, Leung recommends the following strategies for product managers: Keep learning and improving your skills Try new experiences and learn new things Be patient and persistent in your job search Use your personal networks and connections He emphasizes the importance of using this time for personal development. Take advantage of this time and invest in your own self-development learning new experiences. New Ways to Approach Product Development and Startups Leung’s experiences have led him to rethink traditional approaches to product development and startups. He advocates for a more problem-focused approach that prioritizes solving big customer issues. The Importance of Focusing on Customer Problems Leung contrasts his current approach with previous product-first methods. His advice is to force yourself to spend several weeks only thinking about the customer problem. Don’t go down the path of solutioning, even though as product people, we can’t help but want to do that. More to the point, everyone is quick to jump to solutions once a problem is uncovered. As product people, we need to be acutely sensitive to this and first gain a thorough understanding of the problem. This shift in thinking aligns more closely with design thinking principles, emphasizing the importance of deeply understanding customer needs before developing solutions. Common Mistakes in Product Development Leung identifies two major pitfalls in product development: Building solutions for problems that don’t really exist Overestimating how much people will value small improvements He warns against creating products that are only slightly better than existing solutions, emphasizing the need for truly innovative and impactful products. Evaluating if New Products are Really Needed Before starting a new product development journey, Leung encourages product managers to critically evaluate whether the world truly needs another solution to a given problem. He proposes a checklist for evaluating potential products: Is it solving a huge problem that people get really frustrated about? Are the current solutions really bad? Is your solution a big leap forward, not just a small improvement? Leung gives an example to illustrate this point. A product manager might want to create an AI-powered CRM solution. That’s an improvement over an existing CRM system. If AI is going to completely disrupt CRMs and not just accelerate existing workflows, that could be a cool product. But unless you work at a CRM company, Leung wouldn’t suggest starting a new CRM product. This example highlights the importance of not just improving existing solutions, but finding truly innovative ways to solve big problems. The Role of AI and New Technologies in Product Management As AI and other new technologies continue to shape the product management world, Leung offers a balanced view on their role in innovation and creating value. Being Careful Not to Get Too Excited About New Tech While recognizing the potential of AI and other new technologies, Leung cautions against getting caught up in the hype. He recognizes that it’s so tempting to just fall in love with Gen AI, but it’s just a tool that won’t change the laws of economics. He reminds product managers that while these technologies are powerful tools, they’re not solutions in themselves. The focus should always be on solving real customer problems. Balancing Innovation with Practical Value Leung emphasizes the importance of combining new technologies with significant customer problems to create truly innovative and valuable products. He encourages product managers to focus on solving real, substantial issues rather than simply applying new technologies to existing workflows. For example, instead of just making an existing process slightly faster with AI, product managers should look for ways to completely reimagine how a problem could be solved using these new tools. Conclusion: Thriving in a Changing Tech Landscape Navigating career changes and personal growth as a product manager in the ever-changing tech industry requires flexibility, continuous learning, and a focus on solving meaningful problems. By embracing the opportunities presented by career transitions, staying aware of market demands, and approaching product development with a customer-first mindset, product managers can thrive in challenging times and drive innovation that truly matters. Remember these key points: See career changes as opportunities for growth and exploration Stay flexible and keep learning new skills Focus on solving big, meaningful customer problems Don’t get caught up in the hype of new technologies – use them as tools to solve real issues Network and stay connected with other professionals in your field By applying these insights and strategies, product managers can better navigate career changes, enhance their skills, and create products that make a real difference in people’s lives. As the tech industry continues to evolve, adaptability, continuous learning, and a customer-centric mindset will be key to success in the exciting and challenging field of product management. Useful links: Connect with Tom on Linkedin or Twitter Check out the Fireside Product Management podcast Subscribe to Tom’s product management essays on Substack Check out Tom’s courses on Maven Innovation Quote “Product-market fit is important. But before you think about product market fit, convince yourself that the world needs yet another solution to this problem.” – Tom Leung Application Questions How can product managers best prepare themselves for unexpected career changes in the fast-moving tech industry? What strategies have you found work well for identifying and confirming significant customer problems before jumping into creating solutions? How do you balance the excitement of new technologies like AI with the need to create practical, value-driven products? In what ways can product managers use a “gap year” or career transition period for personal and professional growth? How might the changing job market for product managers influence the skills and experiences companies will look for in the future? Tom’s Bio   Joining us is Tom Leung, whom we talked with in episode 390 about experiences that help product managers grow. At that time, he was the Director of Product Management at Google Heath. We’ll find out what more he has learned about growth as a product manager, including through challenging changes.   Source