The One-Quarter Empowered Team Experiment
Convert a single feature team into an empowered product team in one low-risk quarter
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 93%
Rather than waiting for a company-wide 'transformation', Cagan tells trapped PMs to run a bounded, reversible experiment on their own team for one or two quarters. The pitch to the manager is deliberately low-stakes ('if it goes well great, if it doesn't, no harm'), and the conversion itself requires exactly four things: a problem instead of a feature, a PM who has done their homework, strategic context, and discovery skills.
Origin
Marty Cagan / SVPG. The reverse-engineering move inside step 2 is Cagan's standard coaching answer to teams handed a solution by stakeholders.
Core principles
- 01Team-level change is cheap and reversible; business-unit change is expensive and risky — so start at team level.
- 02Any handed-down feature can be reverse-engineered back into the problem it was meant to solve.
- 03Empowerment without a competent PM is the single biggest failure mode, so the PM's prep is the long pole.
- 04The whole conversion takes weeks, except PM skill-building, which takes two to three months.
How to run it
- 1
Pitch a bounded experiment to your manager
Ask for one or two quarters to run the team differently, explicitly framed as reversible: if it works, great; if not, you go back to the old way. Support it with the observation that companies you admire don't work the way you currently do.
Pro tip Ask for a single team, not the business unit — that's what makes it cheap enough to be approved.
- 2
Reverse-engineer the feature into a problem
For the feature you were handed, go back to the requesting stakeholder and ask how they will measure success. Play their answer back ('your belief is that if we add this, X will move — do I have that right?') and capture whatever metric or motive they name. That metric is now the problem to solve, and the solution is once again open.
Pro tip Ask the success question in a collaborative register ('we want to make sure what we do, you consider successful') so it lands as diligence, not resistance.
Watch out Don't assume the obvious KPI — the stakeholder may reveal a completely different motive (e.g. an international expansion goal rather than conversion).
- 3
Get the PM prepared
The PM does their homework: become an expert on users and customers, on the product data, on the business (marketing, sales, monetisation, compliance, privacy, security), and on the industry and competitive landscape. The designer and engineers cannot bring this knowledge — only the PM can.
Watch out An ill-equipped PM is where empowered teams fall down most often; skipping this step guarantees the experiment fails.
- 4
Secure the strategic context
A team that will now make its own decisions needs the big picture: the product vision, the product strategy, and what other teams are doing. Normally leaders supply this; if they don't, the PM goes and learns it — especially the product strategy.
Watch out Decision rights without strategic context produces locally sensible, globally incoherent decisions.
- 5
Learn the discovery techniques
Pick up the modern discovery toolkit — prototyping, testing with users, customers, stakeholders and engineers. Cagan points to INSPIRED, Teresa Torres's Continuous Discovery Habits, and Jake Knapp's Sprint as hand-holding starting points, and recommends finding a coach or mentor if one is available.
Pro tip A manager or mentor who actually coaches you is how most practitioners learned this; ask for one explicitly.
In the wild
A team is told to implement buy-now-pay-later on their e-commerce site — a line item 'on a thousand roadmaps right now'. Instead of just building it, the PM goes to the requesting stakeholder and asks how success will be measured. The answer is usually an obvious KPI like conversion rate or average shopping cart value — but it might instead be something like international expansion.
→ The team converts a prescribed feature into a measurable problem, which reopens the solution space and gives them an outcome to be judged on.
Moving from engineering into product, Cagan's coach forbade him from making any team decisions until he had visited 30 customers — 15 in the US, 15 in Europe — on a three-week trip the coach arranged. Cagan assumed he already knew the customer because he had been a developer building for developers; the coach's reply was that this is 'never true'.
→ Cagan gained the customer expertise that the rest of the team could not bring, which he now treats as the first of the four homework areas.
Common mistakes
Trying to transform the whole business unit first
Company-wide transformation is expensive, risky and slow to approve. A single team is usually waved through, and a working example is far more persuasive than a proposal.
Empowering a team whose PM hasn't done the homework
Cagan: 'that is the single biggest area empowered teams fall down the product manager is ill-equipped.' Handing decision rights to a PM who doesn't know the users, the data, the business, or the industry produces bad decisions and discredits the whole model.
Is it for you?
Best for
A product manager inside a feature factory who wants to prove a better operating model on their own team before quitting or before leadership commits to a transformation
Not ideal for
Teams whose PM role has been split into an administrative 'product owner' with no access to customers, engineers, or stakeholders — fix the role first
From the transcript
“i suggest you go to your manager and say look what do you think about us doing an experiment for the next quarter or two…”
“the first is you need to make sure the team has a problem to solve rather than the feature to build”
“you got to go implement buy now pay later on our e-commerce site which is like on a thousand roadmaps right now right if somebody…”
“decisions they need the strategic context in other words they need to know the big picture what's the product vision what's the product strategy what…”
“skills uh discovery skills and techniques which to me is the fun part”
“long the longest one is the product manager learning you know those skills if they've never learned them before but even that typically takes two…”
“that is the single biggest area empowered teams fall down the product manager is ill-equipped”
From the episode
The nature of product
Marty Cagan, Silicon Valley Product Group