The nature of product | Marty Cagan, Silicon Valley Product Group
Marty Cagan, founder of SVPG and author of Empowered and Inspired, discusses product management misconceptions, contrasting "feature teams" with "real product teams." He offers actionable advice for PMs to foster empowered, outcome-driven cultures, drawing insights from Steve Jobs.
Deep Dive Analysis
14 Topic Outline
Core Misconceptions About Product Teams and Strong Product Culture
Distinguishing Feature Teams from Real Product Teams
Prevalence of Good Product Companies in the Industry
Steve Jobs' Theory on Why Companies Lose Product Mojo
The Danger of Focusing Only on Value Capture (Optimization)
The 'Disease of Stakeholders' and the Value of Ideas
The Importance of Solution Discovery Over Problem Validation
Product Manager's Role in 'How' a Product is Built
The Purpose and Pitfalls of User Research
How Individual Contributors Can Initiate Product Culture Change
Setting Up PMs for Success in Driving Cultural Change
Evolution of the Product Management Role
The Three Sacred Responsibilities of a Product Manager
Concerns About Product Management Trends and Process-Driven Scaling
6 Key Concepts
Feature Team
A feature team is typically handed a prioritized list of features to build, focusing on output rather than outcomes. Their primary role is to implement predefined solutions, serving the business by delivering specific features rather than solving underlying problems.
Real Product Team
A real product team is given problems to solve, whether customer or company problems, and is empowered with the skills and autonomy to discover the best solution. They are outcome-oriented, celebrating when they actually solve the problem and achieve results, rather than just releasing features.
Product Discovery
Product discovery involves two main aspects: discovering the problem to solve and discovering the solution to deliver. While understanding the problem is important, the majority of effort should be on solution discovery—iterating and testing prototypes to find a solution that is valuable, usable, feasible, and viable.
Disease of the Stakeholders
This concept, highlighted by Steve Jobs, describes managers who believe an idea constitutes 90% of the work. They fail to appreciate the craftsmanship and iterative process of going from an initial idea to a successful product, often leading to top-down feature mandates rather than true product discovery.
Disease of Process People
Also from Steve Jobs, this refers to the tendency for companies to scale by implementing rigid processes rather than by developing strong leaders. This approach often leads to repackaged waterfall methodologies and stifles innovation, ultimately destroying a company's product capability.
Generative vs. Evaluative User Research
Generative research aims to understand user needs and problems to inform new ideas, while evaluative research focuses on testing existing prototypes or solutions to identify reasons why users might not use them. Most valuable insights for product improvement come from evaluative research, focusing on what users dislike or find difficult.
6 Questions Answered
Signs include being handed a roadmap of prioritized features (possible solutions) rather than problems to solve, focusing on output (shipping features) instead of outcomes (solving problems), and the product manager primarily acting as a project manager to 'herd cats' and document requirements.
Yes, real product teams exist at many successful companies globally, including well-known brands like Amazon, Netflix, Apple, Stripe, Shopify, and Slack, though they represent a small fraction of total companies.
According to Steve Jobs, as companies grow, product development often becomes less important, with marketing, sales, and finance roles being celebrated and promoted. This leads to good product people leaving, resulting in a decline in innovation and a focus on optimization over value creation.
While understanding the problem is crucial, people ultimately buy solutions, not problems. Founders often already know the core problem, so product teams should prioritize saving time to develop and test winning solutions that are better than competitors, as this is where success or failure is determined.
User research, particularly evaluative research, is primarily used to identify reasons why users *wouldn't* use a product, rather than just confirming if they like it. It helps refine the product by uncovering usability issues, unmet needs, and areas for improvement, contributing to a deeper mental model of the user.
A product manager must maintain unencumbered direct access to their users and customers, direct access to the engineers they work with, and direct access to stakeholders to ensure the product solves real problems, is feasible, and works for the business.
18 Actionable Insights
1. Sacred PM Access
Ensure you maintain direct, unencumbered access to users/customers, engineers, and stakeholders. These three types of access are critical for understanding problems, collaborating on solutions, and ensuring business viability; delegating them damages product innovation.
2. PM Self-Development
To be an effective PM on an empowered team, develop expertise in four areas: users/customers, product data, business functions (marketing, sales, finance, compliance), and the competitive landscape/industry trends. This comprehensive knowledge is essential for contributing valuable and viable solutions to the team.
3. Prioritize Solution Discovery
When the problem is already well-understood (e.g., by founders), minimize time spent on problem validation and maximize effort on discovering the winning solution. People ultimately buy solutions, and this is where success or failure is determined.
4. Experiment Empowered Teams
Propose a short-term experiment (1-2 quarters) to your manager to operate as an empowered product team. Frame it as a low-risk trial to demonstrate the value of this working model.
5. Transition to Problem-Solving
If given a feature to build, “reverse engineer” it by asking stakeholders about the underlying problem it’s meant to solve and how success will be measured. This shifts the focus from output to desired outcomes.
6. Learn Discovery Skills
Actively learn and apply modern product discovery skills and techniques from resources like “Inspired,” “Continuous Discovery Habits,” or “Sprint.” These tools are essential for effective solution discovery and are dramatically better than older methods.
7. PMs Responsible for “How”
Product managers are deeply responsible for how a solution is built, specifically ensuring it is valuable and viable, in collaboration with designers (usable) and engineers (feasible). This goes beyond merely defining what to build.
8. User Research for Problems
Conduct user research with a primary focus on identifying all the reasons users won’t use your product (evaluative research). This approach helps uncover critical flaws and leads to more impactful product improvements.
9. PMs Attend User Research
Product managers and designers must be present during user research sessions and product tests. Direct observation provides invaluable firsthand insights and ensures the research is directly utilized by the team.
10. Avoid Optimization-Only
Do not solely rely on low-risk optimization (A/B testing, tweaking existing workflows) for growth. Ensure your team also engages in “real discovery” to innovate and drive major improvements, as optimization alone won’t lead to significant innovation.
11. Gain Strategic Context
Empowered teams need to understand the big picture, including the product vision, product strategy, and how their work relates to other teams. This strategic context is crucial for making informed decisions and aligning solutions with company goals.
12. Delegate Non-Sacred Tasks
To optimize workload and focus on core responsibilities, delegate non-critical tasks such as project management, quality assurance, product marketing, or production operations to other roles. Ensure this delegation does not interfere with the three sacred PM accesses.
13. Beware Process People
Recognize that scaling with rigid processes (e.g., “repackaged waterfall” methodologies) can destroy a company’s ability to innovate. Instead, advocate for scaling through strong leadership and empowered teams.
14. Focus on Outcomes
In a real product team, success is measured and celebrated when the actual problem is solved and desired results are accomplished, not merely by the number of features released or outputs generated.
15. Recognize Feature Factory
Understand if your team is a “feature factory” (given prioritized features/solutions) or a “real product team” (given problems to solve and empowered to find solutions). This self-assessment helps clarify your current working environment.
16. Learn from Best Teams
When evaluating new product practices or tools, check if they are actively used by several leading product companies. This heuristic helps identify proven and effective methods rather than unproven theories.
17. Avoid Stakeholder “Disease”
Understand that an idea is a minor part of product development; the true “craftsmanship” lies in the discovery and iteration process of transforming an idea into a successful product. Executives often overestimate the value of initial ideas.
18. Seek Coaching/Mentorship
Actively seek out experienced coaches or mentors who can provide guidance and support in developing your product management skills and career. This personal guidance is a highly effective way to learn and improve.
5 Key Quotes
People don't buy the problem, they buy your solution.
Marty Cagan
The engineers aren't there to just implement your dumb ideas. They are there to help you come up with a great solution. The designer's not just there to make your thing look pretty. They're there to help create a great experience.
Marty Cagan
If the product manager and the designer are not available to be there during your product, their products test, cancel the test. They need to be there.
Marty Cagan
When you do user research, you should be focused on finding all the reasons they won't use your product.
Elon Musk (quoted by Marty Cagan)
The idea is minor. The idea is just the start. Getting to a product is what matters. And that's work.
Steve Jobs (quoted by Marty Cagan)
1 Protocols
Transitioning a Feature Team to a Real Product Team (Experiment)
Marty Cagan- Propose an experiment to your manager to run like a real product team for one or two quarters.
- Reverse-engineer features into problems: If given a feature, ask stakeholders how success is measured to understand the underlying problem or KPI it aims to impact.
- Product Manager preparation: Become an expert on users/customers, understand product usage data, learn different parts of the business (marketing, sales, finance, compliance), and know the competitive landscape and industry trends.
- Ensure the team has strategic context: Understand the product vision, strategy, and how their work relates to other teams.
- Learn discovery skills and techniques: Utilize resources like 'Inspired', 'Continuous Discovery Habits', or 'Sprint' to acquire modern product discovery techniques.