Our reading notes

Product vs. Feature Teams

Essay by Marty Cagan

An opinionated distinction between delivering a prescribed feature list and owning a customer problem with a cross-functional team.

The idea to take with you

Teams need real authority over solutions if they are going to be held responsible for outcomes.

What to look for

01
Clarify who owns value, usability, feasibility, and business viability risks.
02
Distinguish receiving a roadmap from receiving a problem to solve.
03
Make the team’s actual decision rights visible.

The author explicitly introduces non-standard terminology. Use the distinction to discuss work, not to label teams as morally better or worse.

Put it to work

Choose one roadmap item. Write the underlying customer problem, evidence of demand, constraints, and which parts the team may change.

Notes and exercises by Awesome CTO. The original work belongs to Marty Cagan.

Our product guide connects the reading to a practical approach and a template.