The nature of product

Marty Cagan, author of Inspired and Empowered and founder of Silicon Valley Product Group, discusses why most companies fail to adopt strong product culture, the difference between feature teams and empowered product teams, and the responsibilities of the product manager. The conversation draws on Steve Jobs' 1995 interview to explore why companies lose their product mojo as they scale, and offers practical steps for PMs trying to shift their team's way of working.

01Key learnings

• Empowered product teams are handed problems to solve with measurable outcomes, not prioritized feature lists to ship; celebrate results, not releases.
• Product managers are equally responsible for the 'how' - ensuring a solution is valuable, usable, feasible, and viable - not just defining the 'what'.
• Limit problem validation time when the founder already understands the problem; spend most effort on solution discovery through prototyping and testing.
• User research should aim to uncover reasons users won't adopt the product, and PMs, designers, and engineers should attend sessions rather than relying on a researcher's report.
• To try a stronger product approach within a feature organization, pitch a one- or two-quarter pilot with one team, asking for the problem and success metrics behind each requested feature.
• PMs should build expertise in users and data, the business (marketing, sales, compliance), the competitive landscape, and discovery techniques before expecting to make decisions.
• Protect three things for a PM: direct access to customers, to engineers, and to stakeholders; other responsibilities can be delegated, but these cannot.
• Scaling with leaders and coaching works; scaling with process and bureaucracy tends to destroy product culture.

02Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.