The Value and Viability Skill Ladder
Climb from backlog administrator to real product manager by owning the two risks nobody else can.
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 95%
Cagan's antidote to 'product management theater' is a concrete self-assessment and upskilling path. Engineers own feasibility; designers own usability; the product manager exists to own value (does it work for the customer) and viability (does it work for the business). The ladder runs product owner → feature-team PM → empowered PM, and moving up means acquiring four bodies of knowledge that no one else on the team has.
Origin
Marty Cagan (SVPG). The value/viability/usability/feasibility risk split is Cagan's own long-standing 'four risks' model from INSPIRED; the 30-customer rule came from the manager who coached him early in his own career.
Core principles
- 01A product manager is a creator, not a facilitator.
- 02Value is for the customer; viability is for the business (sales, marketing, legal, compliance, monetization, cost, go-to-market).
- 03'My job is to say why' is a non-job — the why comes from the product strategy, which leaders own.
- 04Backlog administration in Jira is a tool skill, not a job — like knowing Google Docs.
- 05The most automatable PM work is exactly the administrative work; the value/viability judgment is what survives generative AI.
How to run it
- 1
Locate yourself on the spectrum
Place yourself honestly: product owner (backlog administration inside a delivery process), feature-team PM (backlog plus project management), or empowered PM (owns value and viability). Write down the actual activities filling your week as evidence.
Pro tip If your week is meetings, status, tickets, and handoffs, you are not yet doing product management, whatever your title says.
Watch out Being 'busy with too much work' is not proof you are doing the job — feature-team PMs are the ones most often asking for assistants.
- 2
Become an expert on users and customers
Get in front of real customers in person, at volume. Cagan's own coach forbade him from taking a PM role until he had visited 30 customers in person — 15 in the US, 15 in Europe. Set a comparable personal quota and work through it.
Pro tip Assume you do NOT already know your customers; Cagan thought he did, and the 30 visits changed his life.
- 3
Become the expert on the data
Own the answers to: how is our product actually used, how is that usage changing over time, and how is it purchased. This is quantitative fluency, not a dashboard someone else reads to you.
- 4
Become the team's single source on business constraints
Carry compliance, legal, sales, marketing, financial cost, monetization, and go-to-market knowledge into the team so it can make decisions without convening twenty stakeholders. This is the core of viability.
Pro tip This is the concrete argument for your existence: without you, the team either guesses or reverts to design by committee.
Watch out Absent this knowledge, empowerment degrades into a twenty-person meeting — design by committee wearing an agile hat.
- 5
Add deep market understanding, then create side by side
Layer competitive and market knowledge on top, then work as a creator alongside design and engineering to produce solutions — rather than wireframing over the designer's shoulder or policing the developers.
Pro tip A PM genuinely doing value and viability has no time left to micromanage the designer; if you have that time, you are not doing the job.
In the wild
Early in his career, the person coaching Cagan refused to let him take a product manager role until he had visited 30 customers in person — 15 in the US and 15 in Europe. He went in believing he already understood the customers.
→ The 30 visits changed his view of the customer base entirely and became the foundation of his definition of the PM job.
Cagan describes explaining these responsibilities to a typical certified product owner, who has been trained to manage a backlog in Jira. The reaction is that they are 'on different planets' — none of the value/viability work was ever part of the training.
→ It reveals the certification content as project management relabelled, and gives the individual a concrete, closeable skill gap rather than a vague sense of being stuck.
Common mistakes
Defining the job as facilitation
Answers like 'I facilitate, I communicate, I herd the cats' or 'my job is to say why' cannot be defended to a CEO and describe nobody's real job — the why comes from the product strategy.
Mistaking tool proficiency for the craft
Managing a backlog in Jira is like knowing how to operate Google Docs — something you do daily, but not the job. Developers are in Jira daily too; their job is to build.
Learning the craft from the loudest online sources
Cagan estimates roughly 90% of online product content comes from the feature-team world or worse — well-meaning people describing what they learned at a weak company, which self-propagates through communities, books, and conference talks.
Is it for you?
Best for
A product manager or product owner who suspects their role is administrative and wants a concrete, self-directed path to a defensible product job
Not ideal for
Someone happy in a delivery/project-management role who has no intention of taking on business and customer risk
From the transcript
“a product manager is responsible for value and viability”
“product manager is a Creator not a facilitator”
“I was not allowed to take product manager role until I had visited 30 customers in person”
“value means for the customer viability means for your business”
“what they learned in a csbo or a psbo class was how to manage a backlog in jir which to me is very analogous to…”
“fundamentally a backlog administrator good luck protecting that”
From the episode
Product management theater
Marty Cagan (Silicon Valley Product Group)