The Three Sacred Accesses
Delegate anything off the PM's plate except direct access to customers, engineers, and stakeholders
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 5
- Confidence
- 95%
Cagan is flexible about almost every PM responsibility except three: unencumbered access to users and customers, to the engineers, and to the stakeholders. Everything else — project management, QA, product marketing, runtime operations — can be handed to other people as a company grows. The three accesses map directly onto what makes a good product possible: what's just now possible (engineers), what real users need (customers), in a way that works for the business (stakeholders). This doubles as the test for whether a product-ops or product-owner role is helping or hollowing out the PM.
Origin
Marty Cagan / SVPG, formulated as an answer to the recurring 'the PM job is too big, let's split it' move he sees companies make.
Core principles
- 01Companies split the PM role with good intentions and no idea of the damage they cause.
- 02A mediator between the PM and the engineers is why companies stop innovating.
- 03Anything that is not one of the three accesses is fair game to delegate.
- 04The three accesses correspond to the three inputs of a good product: technology, users, business.
How to run it
- 1
Audit access to customers
Check whether anyone sits between the PM and real users and customers. Well-intentioned gatekeeping from sales, customer success, or research counts as a break. If you are cut off from your customers, you cannot be a product manager.
Watch out The gatekeepers are usually helpful, well-meaning people — which is exactly why the break goes unnoticed.
- 2
Audit access to engineers
Check that the PM works with a set of engineers every day on solving problems. Product owners, project managers, or delivery leads playing 'interface to the developers' break this.
Watch out Cagan's blunt test: 'if you're not working every day with a set of engineers on solving problems you are not a product manager.'
- 3
Audit access to stakeholders
Check that the PM can go directly to the parts of the business — marketing, sales, finance, legal, security — that constrain the solution. This is what makes 'viable' ownable.
- 4
Offload everything else, deliberately
As the product grows, hand off project management, QA, product marketing, runtime/production operations. This is a good thing to do — it is how a PM keeps a sane life without losing the job.
Pro tip Use overload as a signal to shed non-sacred work, not as an argument to split the role in half.
- 5
Apply the test to product ops
Score any proposed product-ops (or product-owner) definition against the three accesses. Good: absorbing overwhelming runtime/production firefighting so there is time to figure out what to build next; or building tools that make PMs more productive. Bad: any definition that replaces one of the three accesses.
Watch out The common-but-toxic definition: a product-ops person who sorts through usage data and tells the PM what they think the PM should hear.
In the wild
A company decides the PM job is too hard for one person and splits it in half, inserting a product owner or project manager as the interface to the developers. Cagan: 'they don't understand why they haven't innovated for years — that's why, they cut that critical thing.'
→ The company preserves throughput and loses innovation, without ever connecting the two.
Cagan accepts product ops that absorbs a crushing runtime/production load (triaging bugs, firefighting) so the PM has time to figure out what to build next, and product ops that builds tooling to make PMs more productive. He rejects the version where product ops sorts the usage data and reports upward to the PM.
→ The three-access test cleanly separates the helpful definitions from the ones that hollow out the role.
Common mistakes
Solving PM overload by splitting the role
The intention is good — take work off the PM's plate — but splitting typically severs one of the three accesses. The right move is to offload project management, QA, product marketing, and operations while keeping all three accesses intact.
Letting a well-intentioned function own the customer relationship
Sales or customer success claiming 'it's my job to talk to the customer' cuts the PM off from the raw signal the whole role depends on. Cagan: 'you get cut off from your customers, you're screwed as a product manager.'
Is it for you?
Best for
Product leaders and heads of product designing (or resisting) role splits, product-owner structures, and product-ops functions as the organisation scales
Not ideal for
Very early startups where the founder is the PM and all three accesses are trivially present
From the transcript
“forget all these stupid roles and terms and all this there's really three things that are sacred for a product manager”
“second product manager needs unencumbered access to the engineers there's a you know if you're not working every day with a set of engineers on…”
“and the third is unencumbered access to the stakeholders because a good product is solving what's just now possible”
“yeah direct access to customers direct access to the engineers direct access to the stakeholders”
“life you can take all this other stuff project management quality assurance product marketing all this stuff run time production operations literally you can pass…”
“if product ops is created to replace one of those three things”
“another good definition are the people who create the tools to help product managers be more productive”
From the episode
The nature of product
Marty Cagan, Silicon Valley Product Group