
Framework mapping / Empowered Product Teams
FRAMEWORK MAPPING
Empowered Product Teams, Mapped
Marty Cagan’s empowered product teams are given problems to solve, not features to build, and they are measured by outcomes. On the Org Topologies map, that is a clear step up from delivery teams. To stay empowered and relevant, a team cannot stay fixed to one thing.
What Empowered Product Teams Are
Marty Cagan did not coin the term, but over the last years he has become its best-known advocate, in his book Empowered and later in Transformed, where it is part of what he calls the product operating model. In our analysis, his own short definition sets the stage:
They [the teams] are cross-functional (product, design and engineering); they are focused on and measured by outcomes (rather than output); and they are empowered to figure out the best way to solve the problems they’ve been asked to solve.
He contrasts these teams with what he calls feature teams, or delivery teams: teams that are handed a solution, often without the underlying problem, and asked to build it. Their work is measured in output, so they cannot be held accountable for results. An empowered product team is handed a problem instead, a customer problem, a business problem or both, and it is free to find the solution that works. It still builds features, but it measures their effect and is ready to redesign or remove them.
A note on terms. In Large-Scale Scrum (LeSS), a feature team means something different from Cagan’s feature team: a cross-functional, cross-component, long-living, customer-facing team. To avoid confusion, this page uses “delivery team” for Cagan’s sense.
Above the teams, Cagan places product leadership: a product vision and a product strategy, from which leaders derive the problems each team is asked to solve, its team objectives. A team topology decides which team owns which part of the product.
Product Teams and Delivery Teams
The book 10X ORG names Marty Cagan’s Product Operating Model, next to Team Topologies, among the approaches that encourage and support the creation of Delivery Topology structures in IT and Product R&D. It also quotes Cagan, author of Inspired, Empowered and Transformed, on the limits of delivery:
The most common in terms of sheer numbers are not really product teams at all, they are delivery teams. Also referred to as ‘dev teams’ or ‘scrum teams’ or ‘engineering teams,’ and if your company is running something like SAFe, then unfortunately, this is you. In this situation, there are a number of developers and a product owner. The product owner in this model is what I refer to as a ‘backlog administrator.’ Someone does need to do this administrative work, but this is all about delivering output, and it’s really very little to do with what I am concerned about in terms of the need for true, consistent innovation on behalf of our customers.
Where Empowered Product Teams Sit on the Map
Placing a team on the Org Topologies map takes two questions. The first is about skills: can the team finish the work in front of it on its own, or does it depend on other units? An empowered product team brings product, design and engineering into one team. That is a lot of completeness. So on the horizontal axis, empowered product teams sit in the complete half of the map.
The second question is about work: how big is the part of the product the team is responsible for? Here the answer depends on how the teams are cut. In Cagan’s model, each team owns an area of the product. Picture an online shop with three empowered teams: one owns the catalog, one owns checkout, and one owns the mobile app. The catalog team receives real problems, for example “customers cannot find the right size”. That is a customer problem, not a feature request, and a real step up from delivery teams. But the problem always sits inside the catalog. The team’s responsibility ends where the catalog ends.
Put the two answers together, and you get what we call narrowly empowered teams: complete teams, each empowered within its own part of the product. On the map, they sit in Delivering, in the capabilities row.
Why a Fixed Area Limits the Impact
In Cagan’s model, a team topology gives each team its own part of the product, and the team keeps it, often for years. In the first months, the area is full of valuable problems. Over time, the team solves the big ones, and what is left gets smaller: the next improvement to the catalog moves the business less than the last one. Meanwhile, the most valuable problem for the business may sit in a different part of the product, owned by a different team, or by no team at all.
So a team fixed to one part of the product will keep finding work there, and it is unlikely to be working on the most relevant problem all the time. Every team does good work, and the product as a whole still moves slower than it could. This is a classic local optimization.
In practice, the new product operating model is often placed on top of the old structure. Product managers, discovery and OKRs arrive, but the teams keep their team-level backlogs on narrow modules or components of the system. The vocabulary changes, and the work stays where it was.
Divided this way, product teams are one more way of slicing an organization into parts, a pattern the book calls divide and conquer. The book makes the same point with LeSS’s Product Definition: the broader the definition, the more elements are seen not as separate small “products,” but as dependent parts of a larger product that must be managed holistically. Will you have many output-level “owners,” or one outcome-level Owner?
From Narrowly to Broadly Empowered Teams
To stay relevant and truly empowered, a team cannot be fixed to one thing. It needs to move within a broader customer domain, the whole problem space its customers live in, and find the next important problem to solve. We call these broadly empowered teams: the same complete teams, but not fixed to one area. On the map, they sit one level higher, in Driving, where the work is about outcomes.
What makes the step from narrow to broad possible is how the work reaches the teams. Instead of a fixed area per team, there is one list of the most important business objectives and customer problems in the domain, ordered by one senior product leader, and the teams help to discover what belongs on it. A team that keeps moving to the next most important problem has to keep learning new parts of the product, new customer groups and new technology. This is multi-learning. With AI agents at the team’s side, a small team can take on a problem in an unfamiliar part of the product much faster.
Practical Recommendations
- Let the most senior product leader own one list of priorities for the whole product. In a startup of about 50 people, this is often the CEO. This is close to what Cagan calls the product leader, with one difference: teams pull from one list instead of each team keeping its own.
- Write that backlog as business objectives and customer problems. That is the level at which empowered product teams do their best work.
- Place product managers and designers inside the teams, not in a separate group around the product leader. If there are not enough of them for every team, staff some teams fully rather than all teams partly, and let the fully staffed teams show the difference.
- Review team areas regularly. Ask, every quarter, whether each team’s area still holds the most valuable problems. If not, move the team’s focus, not just its objectives.
The book’s Elevating Katas point the same way: Expanding the Product Definition, so teams orient around real customer outcomes rather than narrow components, and Re-Centering Product Ownership on Strategy and Outcomes, which means avoiding team-level local product ownership and introducing shared or unified product ownership.
Read the full analysis, see the three topologies, or learn to map your organization in the C-OTC class. The whole argument is in the book 10X ORG at 10xorg.com.
Empowered and the Product Operating Model are the work of Marty Cagan and the Silicon Valley Product Group (SVPG). This page is our independent analysis; it is not endorsed by SVPG.
MAPPINGS
Empowered Product Teams on the map
Case studies and articles that map it with Org Topologies.
FAQ
Empowered Product Teams and Org Topologies: questions
- What is an empowered product team?
- In Marty Cagan’s words, such teams are cross-functional (product, design and engineering); they are focused on and measured by outcomes (rather than output); and they are empowered to figure out the best way to solve the problems they’ve been asked to solve. An empowered product team is handed a problem instead of a solution, and it is free to find the solution that works.
- Where do empowered product teams sit on the Org Topologies map?
- In Cagan’s model, each team owns an area of the product. Put skills and work together, and you get what we call narrowly empowered teams: complete teams, each empowered within its own part of the product. On the map, they sit in Delivering, in the capabilities row.
- What is the difference between a delivery team and an empowered product team?
- Cagan contrasts empowered product teams with what he calls feature teams, or delivery teams: teams that are handed a solution, often without the underlying problem, and asked to build it. Their work is measured in output, so they cannot be held accountable for results.
- What is a feature team?
- In Large-Scale Scrum (LeSS), a feature team means something different from Cagan’s feature team: a cross-functional, cross-component, long-living, customer-facing team.
- What are broadly empowered teams?
- The same complete teams, but not fixed to one area. They move within a broader customer domain, the whole problem space its customers live in, and find the next important problem to solve. On the map, they sit one level higher, in Driving, where the work is about outcomes.



