The Value-Framed Product Résumé
Rewrite every bullet from process to problem, decision, and metric moved
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 5
- Confidence
- 94%
Perri, who reads large volumes of product résumés up to CPO level, rejects anything framed as process ('implemented scrum across the org', 'I prioritized the backlog'). Her rewrite recipe: take the same piece of work and re-tell it as the problem you owned, the customers and stakeholders you engaged, the decisions you made, and the measurable outcome. It converts a product owner's narrow scope into a credible product management story without exaggerating anything.
Origin
Melissa Perri, from hiring product people and from advising product owners at enterprises trying to move into software-native companies.
Core principles
- 01Process bullets signal you were told what to build; value bullets signal you decided what to build.
- 02Even a narrow scope (a login API) has a value story hiding inside it.
- 03The product owner title carries baggage in tech hiring — neutralize it in the bullets, not by lying about the title.
- 04Certifications (CSPO) help in enterprises adopting scrum, and hurt in software-native companies.
How to run it
- 1
Delete every process bullet
Strike anything of the form: I prioritized the backlog, I broke down work with developers, I wrote user stories, I did acceptance criteria, I implemented scrum. Get scrum and agile cadences off the résumé entirely.
Watch out A CPO-level résumé led by 'implemented scrum processes across the organization' is an instant no for Perri.
- 2
Restate each item as a problem you owned
Name the feature or surface you led and the problem behind it — e.g. 'I led the work around the login API; the problem was enhancing security for our login protocols to meet regulatory requirements.'
- 3
Show the discovery and the stakeholders
State who you talked to: users you interviewed, customers you interfaced with, legal and compliance teams you worked with to translate requirements. If you had zero customer contact, say who you did engage.
Pro tip If you're customer-facing, always answer 'who are your customers and did you talk to them?' explicitly.
- 4
Land on a measurable outcome
Close each bullet with the result: compliance met, several million dollars saved, transition delivered without disrupting service for four million customers, or the specific metric that moved.
Pro tip Money saved, risk avoided and customers unaffected are legitimate outcomes when you don't own a growth metric.
- 5
Handle the title and the certification honestly
Write the title as 'Product Owner / Product Manager' so readers know the scope. If you hold a CSPO, be ready to explain in the résumé and interview that you did the work, not just the two-day class.
Pro tip The bullets do the reframing work — a strong value-framed body outweighs a bad title.
Watch out A CSPO on a résumé is read by software-native tech companies as evidence the person does not know what they're doing; enterprises adopting scrum read it as a plus. Know which door you're knocking on.
In the wild
Before: 'I prioritized the backlog and shipped it off to developers.' After: 'I led the work around the login API. The problem was enhancing security for our login protocols to meet regulatory requirements. I interviewed users, got up to speed on the regulations, and worked closely with legal and compliance to translate them into something that would secure the bank.'
→ Perri's version ends: we met compliance, saved the bank a couple of million dollars, and transitioned smoothly to new security requirements without disrupting service for four million customers — a completely different story from identical underlying work.
Perri reads a Chief Product Officer résumé that opens with 'implemented scrum processes across the organization'.
→ Immediate rejection — she was looking for what the candidate would do to push strategy and build better products for customers, not which methodology they installed.
Common mistakes
Leading with methodology instead of value
Process bullets appear over and over in product owner résumés and describe activities, not judgment or results. Hiring managers reading for strategic capability screen them out immediately.
Buying a certification as a shortcut into product management
A two-day CSPO class certifies attendance, not capability. It can open enterprise doors that require it, but in tech companies it actively signals a gap — spend the money only if it's demonstrably on the path you want.
Is it for you?
Best for
Product owners and enterprise PMs trying to move into a software-native product management role
Not ideal for
Applications to enterprises that explicitly require SAFe/scrum certification and screen on it
From the transcript
“they always approach it from a process standpoint I prioritize the backlog”
“get scrum out of there right talk about what value you brought to the users and what metrics you moved”
“I led the work around the login API the problem that I was solving around it was you know trying to enhance security for our…”
“if I see immediately like implemented scrum processes across the organization I'm like nope that's not what I need”
From the episode
Everything you’ve ever wanted to know about SAFe and the product owner role
Melissa Perri (author, founder of Product Institute)