📖 Business
Empowered Product Teams
Most companies organize around "feature teams" — groups that receive a prioritized list of features from stakeholders and build them. Cagan argues this model is the root cause of most product failure. The alternative is the **empowered product team**: a cross-functional squad of a product manager, product designer, and engineers who are given a problem to solve rather than a feature to build. They own the outcome (did the metric move?) rather than the output (did we ship the thing?). The difference is not cosmetic — it fundamentally changes what gets built, how decisions are made, and whether the team attracts missionaries or mercenaries.
2
Minutes
2
Concepts
+45
XP
1
How It Works
- Feature teams are measured by delivery velocity: stories completed, features shipped, roadmap items checked off. None of these measure customer or business value
- Empowered teams are measured by business outcomes: retention improved, revenue increased, support tickets decreased, activation rate lifted
- Empowerment requires three preconditions: (1) competence — the team has the skills to solve the problem, (2) trust — leadership believes the team can figure out the right solution, (3) strategic context — the team understands the company vision, strategy, and constraints well enough to make good decisions autonomously
- The PM on an empowered team is not a project manager or requirements gatherer — they are the person responsible for ensuring the solution is valuable and viable
- Engineers are not "resources" allocated to tickets — they are creative problem-solvers who participate in discovery and often generate the best solutions
- Empowered teams need stable composition. Shuffling people across teams every quarter destroys the deep context that enables good product decisions