Product management theater | Marty Cagan (Silicon Valley Product Group)
Marty Kagan, author and product expert, discusses the evolving product management field, including the pitfalls of "product management theater," how to avoid being a project manager, and essential skills for incredible PMs, especially with AI. He also introduces his new book, "Transformed."
Deep Dive Analysis
18 Topic Outline
Marty Cagan's Background and Recent 'Spiciness'
Current State of Product Management and Macro Factors
Understanding Product Management Theater vs. Real PMs
Distinguishing Feature Teams from Empowered Product Teams
Essential Skills for Empowered Product Managers
The Looming Reckoning for Product Owners and Feature PMs
Taking Ownership of Your Product Management Career
Challenges in Finding Reliable Product Management Advice
Disconnect Between Good Product Companies and Online Advice
Clarifying Top-Down vs. Bottom-Up in Product Strategy
Post-ZIRP Shift in Product Management Focus
Impact of Generative AI on Product Management Skills
Introduction to Marty Cagan's New Book: Transformed
Defining the Product Operating Model
Four Core Competencies for Product Organizations
Perspectives on Product Operations
Advice for Founders on Hiring Product Managers
Lightning Round: Books, Products, and Life Motto
7 Key Concepts
Product Management Theater
This refers to people holding product manager titles but not performing the core responsibilities of an empowered PM, often acting as project managers or backlog administrators, and being overpaid for the value they provide in these roles.
Feature Team
A team that is given a roadmap of specific features or projects to design, build, test, and deploy. Their success is measured by delivering output (shipping the feature) rather than by achieving specific customer or business outcomes.
Empowered Product Team
A team that is given problems to solve, which can be customer or business problems, and is measured by the outcomes achieved. They are responsible for coming up with solutions that are not only usable and feasible but also valuable and viable.
Value and Viability
These are key responsibilities of an empowered product manager. Value refers to ensuring the product solves a real customer problem, while viability means the solution works for the business, considering aspects like sales, marketing, legal, compliance, and monetization.
Product Operating Model
A conceptual model, not a process, that describes a set of 20 common principles found in the best product companies. It outlines how these companies decide what to work on, how they solve problems, and how they build, test, and deploy products reliably.
Product Owner (vs. PM)
In Marty Cagan's view, a Product Owner is a role within a delivery process, primarily focused on administering a backlog, and often does not require a dedicated person. This role is distinct from an empowered Product Manager who is responsible for value and viability.
Product Ops (Good vs. Bad)
Good Product Ops integrates user research and data analysts to provide high-leverage support to product teams. Bad Product Ops, however, often focuses on process, governance, or provides unnecessary administrative assistance to product managers, making these roles vulnerable.
12 Questions Answered
Marty Cagan's increased 'spiciness' is driven by a convergence of macro factors: widespread overhiring during the pandemic, changes in the financial world increasing the cost of funds, the predicted impact of generative AI, inflated team sizes with redundant roles, and challenges with innovation and velocity in remote work environments.
Product management theater refers to situations where individuals hold product manager titles but are not performing the core responsibilities of an empowered PM. Instead, they often engage in project management tasks or backlog administration, leading to them being overpaid for the actual value they provide.
A feature team is given a roadmap of specific features to build, with success measured by delivering output, whereas an empowered product team is given problems to solve and is measured by the outcomes achieved, requiring them to find valuable, viable, usable, and feasible solutions.
A real product manager needs deep expertise in their users and customers, data analysis, market understanding, and the ability to represent compliance, sales, marketing, financial cost, monetization, and general go-to-market issues, all while being responsible for value and viability.
A significant portion of online product management content, including certifications and community advice, propagates the model of feature teams or project management, rather than the practices of truly empowered product companies, making it difficult for new PMs to learn effective approaches.
While some sales-driven B2B companies operate as feature factories, this approach often leads to subpar products and makes them vulnerable to competition. Empowered product teams are capable of everything a feature team can do and more, ultimately building better products.
There's a general shift from a focus on pure optimization and growth hacking to a renewed emphasis on building, finding product-market fit, validation, and discovery. This change is less about interest rates and more about the quality of leadership and the business's need for more than just optimization.
Roles primarily focused on backlog administration or administrative project management tasks are highly vulnerable to AI disruption. This emphasizes the need for product managers to up-level their skills to focus on complex value and viability questions that AI cannot yet fully address.
The product operating model is a conceptual framework based on 20 common principles observed in the best product companies. It defines how these organizations strategically decide what to work on, effectively solve problems, and reliably build, test, and deploy products to achieve desired outcomes.
Successful product organizations require four core competencies: a serious product manager (focused on value/viability), a real product designer (covering service, interaction, visual design, and user research), a real tech lead, and a real product leader (who can coach and develop product strategy).
Marty Cagan views good Product Ops as integrating user research and data analysts to provide high-leverage support to product teams. However, he cautions against Product Ops roles that focus on process, governance, or act as unnecessary administrative assistants to product managers, as these roles are vulnerable.
Founders should generally avoid hiring a product manager too soon, as the founder typically performs the product management role in early stages. It's usually more beneficial to hire a dedicated product manager once the company reaches a certain scale, often around 20 to 25 engineers.
54 Actionable Insights
1. Focus on Outcomes, Not Output
Differentiate between delivering ‘output’ (features from a roadmap) and ‘outcomes’ (solving customer/business problems), understanding that true product value comes from achieving outcomes.
2. Empower Teams with Problems
Empower your product teams by giving them specific customer or business problems to solve, rather than a fixed roadmap of features, and measure their success by problem resolution.
3. PMs Essential for Outcomes
Understand that a true Product Manager is essential when teams are responsible for achieving outcomes, as this requires skills in value and viability beyond just usability and feasibility.
4. Ensure Solutions are Valuable & Viable
When solving problems, ensure solutions are not only usable and feasible but also valuable to customers and viable for the business, requiring a broader skill set.
5. Raise Your Product Skills
Take personal responsibility for skill development to elevate your contribution as a product manager, as acquiring necessary skills is achievable with motivation.
6. Proactively Raise Your Skills
Proactively raise your product management skills beyond the scope of delivery or feature team roles to adapt to evolving industry demands and secure your career.
7. Future-Proof Your PM Role
If you are a delivery team product owner or feature team product manager, be aware that these roles are vulnerable to being cut or automated, especially with Gen AI, and proactively up-level your skills.
8. Take Agency in Your Career
Take agency in your career, even if you feel stuck in a ‘feature team,’ because there are many actions you can take beyond quitting to improve your situation.
9. Individual Agency for Change
Recognize that individual contributors have significant agency to influence their company’s direction towards better product practices, rather than feeling like a victim of their circumstances.
10. Cultivate Customer Passion
Cultivate a genuine passion for understanding and improving customers’ lives through your products, as this customer-centricity is a fundamental trait of successful product people.
11. Be a Product Creator
Define your role as a product manager as a creator responsible for ensuring product value and business viability, rather than merely facilitating or communicating.
12. Become Customer Expert
To effectively represent value and viability, become a deep expert on your users and customers, understanding their needs and behaviors.
13. Conduct Extensive Customer Visits
Gain deep customer understanding by conducting extensive in-person customer visits (e.g., 30 visits) to truly grasp their perspectives, as this can be life-changing.
14. Be Data Usage Expert
Be the team’s expert on product usage data, understanding how the product is used, how usage evolves, and how it’s purchased.
15. Master Business Constraints
As a product manager, be the central point of knowledge for critical business aspects like compliance, sales, marketing, financial costs, monetization, and legal constraints.
16. Cultivate Market Understanding
Cultivate a deep understanding of the market your product operates in to inform strategic decisions and ensure viability.
17. Avoid Backlog Administrator Role
Avoid being solely a backlog administrator, as this role is highly susceptible to automation by AI and offers poor long-term career prospects.
18. Focus on Business Viability
As an empowered product manager, focus intensely on viability (what works for the business, including legal, ethical, and financial aspects), as this becomes increasingly critical with emerging technologies like Gen AI.
19. Ensure Business Viability
When developing products, ensure they are viable for your business by considering aspects like marketability, sales, legal compliance, serviceability, and financial constraints.
20. AI: Refine, Don’t Start
When using AI tools like ChatGPT, first formulate your own thoughts and ideas, then use the AI to refine, challenge, or tighten your arguments, rather than relying on it to generate initial answers.
21. Critically Evaluate PM Content
Be highly critical of online product management content and certifications, as a vast majority may propagate outdated or ineffective ‘feature team’ models.
22. Own Your Career Path
Take ownership of your career path by actively deciding what kind of product manager you aspire to be and exercising judgment in your learning and development choices.
23. Research Your Future Manager
When seeking a new role, thoroughly research your potential direct manager’s background, past companies, and products on LinkedIn, as their coaching ability is more critical than the company itself.
24. Critically Review Product Methods
Conduct a critical review of your product development and customer service methods, comparing them to leading companies that achieve superior results with less spend, to identify areas for transformation.
25. Prioritize Proven Innovation Principles
When evaluating new techniques or methods, prioritize those consistently used by several companies proven to innovate successfully, as these principles tend to last.
26. Monitor Disruptive Factors
Continuously monitor for disruptive factors that could impact your product or company, both positively and negatively, to anticipate change.
27. Prepare for Gen AI Impact
Acknowledge the inevitable, real impact of disruptive technologies like Gen AI, even if the exact timeline is uncertain, and prepare for its effects.
28. Optimize Team Size & Roles
Evaluate organizational structure for ‘ridiculous roles’ and consider reducing team sizes, as smaller, focused teams often achieve more and better results.
29. Scrutinize Process-Heavy Roles
Scrutinize the necessity of numerous ‘assistant’ or process-heavy roles (e.g., agile coaches, product owners, product ops) as they can lead to inefficiency and waste.
30. Address Remote Work Challenges
Acknowledge that fully remote setups can negatively impact innovation and velocity, and explore strategies to mitigate these challenges.
31. Re-evaluate PM Role in Feature Teams
If your team primarily focuses on delivering pre-defined features (a ‘feature team’), recognize that a dedicated Product Manager role might be redundant or overpaid, as it often devolves into project management.
32. Recognize Feature Team Clues
If engineers or designers express dissatisfaction with PMs, it’s a strong indicator you might be operating as a ‘feature team’ rather than an empowered product team.
33. Avoid Design by Committee
Avoid ‘design by committee’ by ensuring a product manager brings essential business and customer knowledge to empowered teams, enabling efficient decision-making without numerous stakeholder meetings.
34. CEO Must Drive Product Shift
If your company is sales-driven and not product-led, recognize that a fundamental shift often requires the CEO to acknowledge the current model’s shortcomings, typically spurred by market competition.
35. Strive for Empowered Teams
Strive to build or join an empowered product team, as this model is superior to a feature team and capable of achieving more comprehensive results.
36. Product Leaders Own Strategy
Understand that product strategy is the responsibility of product leaders, not individual product teams, to ensure alignment and focus.
37. Empowerment: Leaders Set Bets
Define empowerment as leaders setting strategic ‘bets’ (problems to solve) and teams having the autonomy to discover the best solutions, rather than teams deciding what to work on independently.
38. Employ Transformation Techniques
To drive organizational change, employ specific transformation techniques such as using pilot teams or a ‘divide and conquer’ approach to spread new ways of working.
39. Seek Diverse Transformation Examples
Look for inspiration and case studies from companies outside the Silicon Valley bubble, especially older, established businesses that successfully transformed, to understand broader applicability.
40. Embrace Experimentation
Embrace experimentation as a core principle in product development, as it is foundational for learning and achieving successful outcomes.
41. Instrument Every Release
Instrument every product release to collect data that proves whether desired outcomes are achieved, enabling data-driven validation.
42. Prioritize Innovation & Learning
Prioritize innovation over strict predictability, learning over avoiding failure, and foundational principles over rigid processes to foster a dynamic product culture.
43. Foster Team Ownership
Foster a strong sense of ownership within empowered teams by entrusting them with problems to solve, making the solutions truly ’theirs.’
44. Focus on Discovery Principles
In product discovery, focus on principles like proactively addressing product risks, conducting quick experiments, and responsibly testing ideas.
45. Implement CI/CD Practices
Implement continuous integration/continuous delivery (CI/CD) practices, including small, frequent, uncoupled releases, and comprehensive instrumentation and monitoring, to improve product delivery.
46. Separate Internal & Marketing Releases
Separate internal product releases (frequent, often daily) from external marketing announcements; ensure that by the time a feature is marketed, it is already live and proven in production.
47. Centralize Research & Data
If implementing Product Ops, structure it to centralize and enhance user research and data analysis functions, rather than focusing on process and governance.
48. Avoid Process-Heavy Product Ops
Avoid product ops roles or initiatives that primarily focus on ‘process and governance,’ as this indicates a red flag and a potentially unproductive environment.
49. Hire PMs After Scale
Founders should defer hiring a dedicated product manager until reaching a certain scale (e.g., 20-25 engineers), as the founder should initially own value and viability to avoid conflict and inefficiency.
50. Founder as PM for Small Teams
As a heuristic, if you have fewer than 20-25 engineers, the co-founder should ideally serve as the primary product person, owning value and viability.
51. Write to Clarify Thinking
Develop your critical thinking skills by regularly writing down your thoughts, as writing helps clarify and solidify ideas that might otherwise remain unexamined.
52. Critically Evaluate Company Claims
Be aware that how companies describe their practices externally may differ from internal reality; maintain a critical perspective when evaluating claims.
53. Embrace Uncomfortable Truths
Be prepared to deliver and receive uncomfortable truths that are necessary for improvement, even if they are not what people want to hear.
54. Engage with Peers & Experts
Engage with peers and experts regularly to develop theories and strategies for protecting your career and company amidst industry changes.
5 Key Quotes
It is a lot easier to deliver output than it is to deliver outcomes.
Marty Cagan
I have been warning for several years that delivery team product owners and feature team product managers are likely to be facing a reckoning as companies realize that these roles are not what they thought they were. From what I can tell, that reckoning has begun.
Marty Cagan
Too many people in our industry view themselves as a victim of their company. Like they're stuck in a feature team and there's nothing they can do about it other than quit. I think that's not true. There is so much they can do.
Marty Cagan
If you're thinking without writing, you just think you're thinking.
Leslie Lamport (quoted by Marty Cagan)
I don't know what I think until I've written it down.
Joan Didion (quoted by Marty Cagan)