Marty Cagan vs Melissa Perri: Empowered Product Teams or Escaping the Build Trap?
Comparing Marty Cagan's product model with Melissa Perri's Escaping the Build Trap: both attack the feature factory, with different emphases on team capability and organizational strategy.
The most common complaint among product teams is that they ship a lot and little changes. Two authors have named the problem and a way out: Marty Cagan, who argues for empowered product teams, and Melissa Perri, who calls the pattern the build trap. People compare them because both want product organizations to focus on outcomes.
What is the core difference?
Cagan starts with the team. A product team should have the skills and authority to find solutions that customers love and that work for the business. When teams are treated as delivery units for stakeholder requests, the model fails.
Perri starts with the organization. If success is measured by shipped features, and strategy does not connect to what teams work on, even capable teams will fall into the build trap. The fix involves goals, metrics, planning, and governance.
One asks whether the team is empowered and skilled. The other asks whether the organization lets it succeed.
What does Cagan say?
Marty Cagan founded the Silicon Valley Product Group after leading product at companies such as eBay and Netscape. Inspired (2008, updated 2017) describes how the best product companies work, including product discovery, and Empowered (2020), written with Chris Jones, addresses product leadership.
His four risks are value, usability, feasibility, and viability. He distinguishes feature teams from empowered product teams and argues that most companies are built on the former. His work is a practitioner's account and is distributed through books and training.
What does Perri say?
Melissa Perri is the founder of Produx Labs, a product management consultancy and training company. Escaping the Build Trap (2018) uses case stories to argue that organizations get stuck valuing output. She describes product strategy as connecting company vision to the work through a hierarchy of goals, and gives guidance on measuring outcomes and on structure.
Product Operations (2023), with Denise Tilles, covers the supporting function. Her tone is practical and organizational, focused on how a company can change how it plans and decides.
How do they compare?
| Dimension | Cagan | Perri |
|---|---|---|
| Focus | Team capability, empowerment, and discovery | Organizational strategy, metrics, and structure |
| Key idea | Empowered product teams; four risks | The build trap; outcomes over output |
| Typical question | Is the team skilled and empowered to solve problems? | Do our goals, metrics, and planning reward outcomes? |
| Main audience | Product leaders and teams | Executives, product leaders, and managers |
| Business | SVPG advising and training | Produx Labs consulting and training |
| Main risk | Empowerment without strategy or alignment | Metrics and strategy without capable teams |
| Best known for | Inspired (2008, 2017), Empowered (2020) | Escaping the Build Trap (2018) |
When does each one fit?
Cagan's work fits when the symptoms are inside the team: weak discovery, poor product sense, or a team that implements what it is told. It describes competencies to build and leadership to supply.
Perri's fits when the symptoms are organizational: shifting priorities, roadmaps as promises, success defined by shipping, and no link between company goals and team work. It offers a way to restructure planning.
In practice, both sets of symptoms often appear. An empowered team needs a clear strategy, and a clear strategy needs a team that can execute it.
What does this look like in practice?
A company runs a quarterly roadmap that lists features promised to customers and sales. A Perri-style response is to replace the feature list with outcomes tied to company goals, and to define how each outcome will be measured. The roadmap becomes a set of problems to solve.
A Cagan-style response asks whether the product teams have the discovery skills to find solutions, and whether leaders will let them decide how to meet the outcomes. Without that, the outcomes just become a new way to dictate features. Each fix protects the other.
"Here is our current roadmap: [paste]. First, using Perri's approach, rewrite each item as a problem or outcome tied to a company goal, with a metric. Then, using Cagan's four risks (value, usability, feasibility, viability), tell me what the team would need to learn before building each one, and who needs to be empowered to decide."
Why it works: reframing the roadmap changes what is asked, and the risks show what the team must be able to do.
Can you use both together?
Yes, and they reinforce each other. A company that changes its planning but does not build team capability will see little improvement, and one that builds capable teams but keeps output metrics will frustrate them.
Both depend on leaders changing their behavior. Reading about the model is easier than changing how decisions are made.
"Describe how work is chosen, measured, and reported in our organization: [describe]. Using Perri's description of the build trap and Cagan's contrast of feature teams and empowered teams, tell me which signs apply, whether the main cause looks structural or about team capability, and the first change I should propose to leadership."
Why it works: separating organizational causes from team causes points to the right first change.
For a related comparison, see Marty Cagan vs Teresa Torres.
Where to go next
Marty Cagan and Melissa Perri both sit in the Product Leader category. For the originals, read Inspired and Empowered by Cagan and Escaping the Build Trap by Perri. Both authors' organizations sell training, so use the books to judge fit.
Frequently asked questions
What is the build trap?
In Escaping the Build Trap (2018), Perri describes it as the condition in which an organization measures success by what it ships, such as features and releases, rather than by the outcomes for customers and the business. Teams get busier and results do not improve. Her remedy is to manage by outcomes, tie product work to strategy, and structure the organization accordingly. The shared point is that output alone is a poor measure of product success.
How does the build trap compare with a feature factory?
They describe the same pattern from slightly different angles. A feature factory delivers a list of features requested by stakeholders. The build trap, in Perri's account, is the broader organizational condition that produces such behavior, including incentives, structure, and leadership habits. Cagan's term for the opposite is empowered product teams that solve problems for customers and the business. Seen together, a feature factory is the visible behavior, and the build trap is the underlying organizational cause.
What does Cagan add?
Cagan's Inspired (2008, updated 2017) and Empowered (2020, with Chris Jones) describe how strong product companies work: teams with the skills to discover solutions, empowered to own problems, and supported by product leaders. His four risks of value, usability, feasibility, and viability give a structure for discovery. His emphasis is on team competence and leadership. His books also stress the role of product leaders in coaching teams, which he treats as essential to the model.
What does Perri add?
Perri adds attention to product strategy, governance, and the way organizations plan and fund work. She discusses how to connect company goals to product outcomes, how to restructure around outcomes, and the role of product operations in her later book. Her practice is as a consultant working with organizations making this shift, and she runs training. Her work is often used by executives who want to change how planning and prioritization are done.
Do they agree on the cause?
Largely. Both say that organizations fall into delivering features because leaders define success by output, and that the cure involves leadership change. Cagan stresses the competence and empowerment of teams, and Perri the structures and metrics. They are different entry points to a shared diagnosis, and many practitioners use both. The practical test is to ask whether your teams can say what problem they are solving and how they will know they solved it.
Can AI help escape the build trap?
It can help rewrite feature requests as problems, draft outcome metrics, and map a roadmap to goals. It cannot change incentives or leadership behavior. Use it to prepare materials, and treat the organizational change as a human effort. Ask it also to identify which metrics currently reward shipping, since changing those is usually the first lever. Treat its suggestions as drafts to be discussed with your leadership team.
Written by Gareth Hoyle. Last updated 8 October 2026. Part of the authority.md guides library.
More guides.
Daron Acemoglu vs Ha-Joon Chang: Do Good Institutions Cause Growth, or Follow It?
Comparing Daron Acemoglu's institutions-first account of national prosperity in Why Nations Fail with Ha-Joon Chang's historical critique of the institutions literature: two views of development, with the main point of disagreement. General education.
Bill Ackman vs Carl Icahn: Two Styles of Activist Investing. Not Investment Advice
Comparing Bill Ackman's public, thesis-driven activism with Carl Icahn's decades of corporate pressure campaigns: how each approaches companies, boards, and the public. Not investment advice.
Adam Smith vs Ha-Joon Chang: The Founder of Market Economics and One of Its Historical Critics
Comparing Adam Smith's Wealth of Nations and Theory of Moral Sentiments with Ha-Joon Chang's history-based critique in Kicking Away the Ladder: what Smith actually argued, what Chang adds, and where they differ. General education.