The Product Operating Model
Three dimensions and four competencies that separate companies that consistently innovate from the rest.
- Difficulty
- Expert
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 92%
After twenty years of refusing to name it, Cagan settled on 'product operating model' as the label for the set of ~20 principles shared by companies that consistently innovate. It is deliberately a conceptual model, not a process or methodology: three dimensions describe how a company works, and four competencies describe the roles it must genuinely have (not merely have titles for). It is the spine of his book TRANSFORMED.
Origin
Marty Cagan and the SVPG partners (Christian, Jonathan, Christopher, Leah). Cagan is explicit that SVPG invents none of it — the model is distilled from principles observed repeatedly across companies that can consistently innovate. The term itself was borrowed from companies SVPG worked with, chosen over 'product-led' or 'product-driven' because those read as a power grab to the rest of the business.
Core principles
- 01Principles are more important than process; innovation is more important than predictability; learning is more important than failure.
- 02A technique only enters the model if several proven, consistently-innovating companies use it productively.
- 03Companies usually have people with the four titles but not people doing the four jobs.
- 04Teams are empowered with problems to solve and given real ownership.
- 05Everything released must be instrumented so the outcome can be proven.
How to run it
- 1
Audit dimension one — how you decide what to work on
Examine how the company chooses which problems to solve. In most companies this is annual planning producing a feature list; in the model it is a real product strategy owned by product leaders, which places bets and hands teams problems.
Pro tip Product teams do not do product strategy — product leaders do. Confusing the two produces anarchy or theatre.
- 2
Audit dimension two — how you solve problems
Assess whether the organisation actually has product discovery skills: addressing product risks, embracing quick experimentation, testing ideas responsibly, and arriving at solutions that work for both the customer and the business.
Pro tip If all the team can fit around the roadmap is A/B tests on call-to-action copy, that is optimization, not discovery.
- 3
Audit dimension three — how you build, test and deploy
Check delivery: small, frequent, uncoupled releases (CI/CD), instrumentation of everything, monitoring of everything — so that outcomes are demonstrable rather than asserted.
Pro tip Separate engineering releases from marketing releases: strong companies release ~20 times a day and batch the messaging periodically, so what is announced is already live and proven.
Watch out Monthly or quarterly actual releases make it impossible to learn at the needed pace, and quality suffers too.
- 4
Install the four competencies for real
Confirm you have, in substance and not just in title: a real product manager (not a product owner or feature-team PM), a real product designer (service, interaction, visual design and user research), a real tech lead, and a real product leader who can coach people and craft a real product strategy.
Pro tip The first three are the classic triad; the product leader is the addition — teams doing their job is not enough if leadership isn't doing theirs.
Watch out Having people with those titles is the trap; the roles must be institutionalized, not renamed.
- 5
Transform by piloting, not by decree
Change techniques matter as much as product techniques: run pilot teams, divide and conquer the transformation, and use the results to spread. Get non-product leaders (CEO, CFO, head of sales) to understand the model, since they must sponsor it.
Pro tip TRANSFORMED was deliberately written for non-product readers so a PM can hand it to their CEO.
In the wild
Cagan cites a Saudi Arabian travel agency, Almosafer — a company he had never heard of a few years earlier — that moved to the product model and now holds, by his account, over 80% of its market against Expedia and the big US players.
→ It became one of the non-Silicon-Valley case studies in TRANSFORMED, evidence that the model is not a Bay Area artefact.
Writing TRANSFORMED, the authors made a rule for themselves: no Silicon Valley case studies, because companies like Airbnb were born in the model and thus prove nothing about changing. Every example — Trainline in the UK, companies in Brazil, Virginia, healthcare, car sales, fitness — is a mostly pre-internet company that had to change.
→ The book shows both how those companies changed and what innovation they were able to produce afterwards, which Cagan rates as comparable to Amazon's.
Common mistakes
Buying process instead of principles
Companies adopt SAFe, scrum ceremonies, and certification programmes and end up with enormous cost and headcount but almost no outcomes to show. There are a million methodologies and frameworks; what matters is the principles.
Confusing product ops with the product operating model
The name collision is unfortunate and unrelated. Product ops is analogous to DevOps/DesignOps; at good companies it is a small, high-leverage group of user researchers and data analysts under one leader — not a process-and-governance function and not an assistant corps for overloaded PMs.
Hiring product ops to cover for absent product leadership
Cagan sees companies where product leaders aren't doing their job, so product ops is hired to educate the product managers. That is a leadership abdication, and it leaves those product ops people highly vulnerable.
Is it for you?
Best for
Executives and product leaders at a non-tech-native company (bank, retailer, insurer, travel) who want to work like the best product companies and need a structured audit and change path
Not ideal for
A small startup still founder-led and pre-product-market-fit, where the founders themselves are effectively performing all four competencies
From the transcript
“the four competencies are product manager again we're talking a serious product manager here not a product owner not a feature team product manager”
“Innovation is more important than predictability that's a principle that's uh learning is more important than failure that principles are more important than process”
“it's not a process it's not really a thing it's more of a set of principles”
“you have to make sure that everything you release is instrumented so that we can prove the outcome”
“focus on the whole phrase of uh process in governance that's like a huge red flag”
From the episode
Product management theater
Marty Cagan (Silicon Valley Product Group)