Sample frameDay 189·Product · Teams

Morning. Your team was handed a list of features. Then asked why it isn't innovating.

Product.

The Empowered Product Team

5 min read·Apply by lunch

The question

Of the last three things your product team shipped, how many arrived as a problem with a number attached to it — and how many arrived as a feature with a date on it, chosen somewhere above the team by people who won't be in the room when a customer ignores it?

The idea

Marty Cagan and his Silicon Valley Product Group partner Chris Jones published EMPOWERED: Ordinary People, Extraordinary Products in 2020, and the subtitle carries the argument. Strong product companies aren't staffed with better people than yours; they're constituted differently, and the difference shows up in what a team gets handed on a Monday morning. Cagan names three kinds. A delivery team exists to build what it's given, with someone administering a backlog rather than managing a product. A feature team is properly cross-functional — product, design and engineering together — but it is assigned features and projects off a roadmap, and held to whether those shipped on the promised date. An empowered product team is handed a problem to solve, plus the strategic context needed to solve it well, and held to whether the problem moved. Yesterday's four risks are what make this structural rather than cultural: they only get worked at once if the people who own them are in the room together from the start. Split the work across a specification and a handover and you've split the risks too. The trap is renaming. Teams get called product teams and handed a roadmap of dated features, and everybody learns the truth from the artefact rather than the announcement.

The framework

01
Read the roadmap, not the org chart.
The test of which kind of team you're running isn't the name on the chart; it's what lands in front of it. A problem arrives as a customer difficulty with a number that would move if it were solved, and the solution genuinely open. A feature arrives as an answer already chosen, with a date attached, leaving only estimation and sequencing. Go through your own roadmap this morning and mark each line as one or the other. Most teams find the count uncomfortable, because a roadmap of chosen answers means the choosing happened somewhere the team wasn't.
02
Whose head is the strategic context sitting in?
Cagan's empowerment has two conditions, and teams are routinely given the first without the second. A problem to solve is condition one. The strategic context to solve it well is condition two — the product vision, where the company has decided to compete this year, what the quarter can actually fund, which other teams are working the same customer. Without it a team either guesses or waits, and from above both of those look identical to the team simply not being good enough. Context you are carrying in your own head isn't context until somebody has said it out loud.
03
Engineers arrive at discovery, or they arrive too late.
This is the part that gets cut first and costs the most. If engineers see the work only after it's been specified, feasibility becomes a verdict delivered late rather than a risk worked early — and you have also given up the innovation they would otherwise have brought, since the people closest to what the technology can now do are the best placed to say what it should do. Put them in front of customers alongside the designer. A team that has met the customer argues about the problem; a team that has only met the spec argues about the estimate.
04
Outcome without authority is the worst deal on the table.
A feature team is held to output — shipped, on the date, to the scope agreed — and that is a fair question to ask of a team that didn't choose any of it. A product team is held to the outcome the problem was meant to move, which only becomes fair once the team was allowed to choose the solution. The two travel together or not at all. Handing down outcomes while keeping the solutions is the worst arrangement on offer: all of the accountability, none of the authority, and a team that learns very quickly to promise carefully.

Members only · 4 principles + template + AI mentor

364 more frameworks are waiting.

The Empowered Product Team is Day 1 of 365. One framework every morning for a year — across strategy, sales, negotiation, leadership, and more.

$1 /day

Billed $365/yr · cancel any time

365 frameworks

12 topics · templates · AI mentor

Reserve your place — $365/yr →

One payment a year · the whole library · no auto-renewal.

More Product frameworks

All 22 product frameworks →