Marty Cagan

Partner at Silicon Valley Product Group, author of Inspired and Transformed

Marty Cagan has spent over 20 years helping product teams and product managers improve their craft, and wrote Inspired, Empowered and Transformed. He splits the world into what he calls the project model and the product model. A feature team gets a roadmap of features, while an empowered product team is given problems to solve. The job of product, he says, is to solve problems for customers and achieve outcomes for the business.

Lenny's Podcast 00:45 00:50 21:32 Lenny's Podcast 00:55 02:31

Marty Cagan's key ideas, in short

  • Product strategy: The Product Operating Model
  • Empowered Product Team vs Feature Team Framework
  • If teams are given features to build rather than problems to solve, they're feature teams not product teams

By , founder of Gavel

Updated

Stuck on a real call of your own? Gavel answers startup questions with what a named founder did, and links to the minute they said it. Ask Gavel free

Frameworks
1
Problems
1
Ideas
2
Recordings
4

Key ideas

Product strategy

When AI changes what's worth building

Product

The Product Operating Model

Not a process you install. A conceptual model: how you decide what to work on, how you solve problems, how you build.

There's a set of principles around the more cultural things, like innovation is more important than predictability.
Cagan, on the cultural principles Watch at 1:08:44
Read the framework

More

Empowered Product Team vs Feature Team Framework

Feature teams receive roadmaps of output (features/projects) and are measured by delivery. Empowered product teams receive problems to solve and are measured by… Product management theater

If teams are given features to build rather than problems to solve, they're feature teams not product teams

Diagnosing team empowerment Product management theater

Disagreements

Is discovery a team capability, or the founder and five users?

Marty Cagan describes a model where teams are given problems, not features, and anyone in the building can run discovery and land on something that works for the customer and the business. Installing the titles and the ceremonies without that is why most adoptions change nothing.

Garry Tan is describing a company that has none of that yet: ship the jankiest version, filter a hundred curious people down to the five or six with a hair-on-fire problem, and let their reaction decide what is real. Discovery at that stage is the founder and five users, not a capability you distribute.

From The Product Operating Model

Sources

Stuck on a real call of your own? Gavel answers startup questions with what a named founder did, and links to the minute they said it. Ask Gavel free