Perri argues that small, experienced teams do not need the overhead of scrum. At Open Sky her team shipped weekly instead of in two-week sprints and skipped daily stand-ups because they already talked constantly. The value of a framework is forcing conversation about the work; if you already do that, the framework is unnecessary overhead.

Scrum's overhead is designed for larger-scale companies, not small experienced teams.
At Open Sky the team shipped weekly and dropped daily stand-ups.
Frameworks help by forcing teams to talk about the work; if you already do, you don't need one.
A defined methodology isn't required as long as you have a way of shipping value to customers.

“we skipped daily stand stand-ups we didn't need to stand around and talk about it”
Melissa Perri · 23:00

“you don't need scrum you don't need to be prescribed to this two week Sprint”
Melissa Perri · 23:30

#startups#scrum#process#hot-take

Myth Buster43:30

Processes Aren't the Enemy at Scale

Pushing back on the anti-process crowd (including Marty Cagan), Perri argues that large organizations genuinely need tooling like roadmapping software for transparency. When you have thousands of teams, you have no way to see whether they're tied back to business goals without that infrastructure.

Perri disagrees with blanket anti-process sentiment aimed at large organizations.
Roadmapping tools provide necessary transparency across thousands of teams.
Blocking-and-tackling process is required for a software transformation to be efficient.
The problem with SAFe isn't process itself, it's failing to connect value back to product teams.

“I don't think processes are the enemy here”
Melissa Perri · 43:30

“you have no idea what your 4,000 teams are doing”
Melissa Perri · 44:00

#process#scale#transparency#roadmaps

Hot Take· 4

Hot Take34:30

SAFe Turns Product Owners Into Order Takers

Perri explains how SAFe formally splits the product manager and product owner, putting discovery with the PM and leaving the PO purely tactical. The result is product owners who become order takers with no exposure to strategy, and a career track that often doesn't even connect back to product management.

SAFe splits PM (with system architect and release train engineer) from PO (with the scrum team).
Discovery work goes to the product manager, leaving the PO tactical and order-taking.
Product owners get no exposure to strategy, market research or deciding what's valuable.
In many orgs the PO and PM tracks report to different people and aren't the same career path.

“you are basically making these product owners order takers they are extremely tactical”
Melissa Perri · 34:30

#safe#product-owner#careers#hot-take

Hot Take49:00

Why She Does Not Recommend Using SAFe

Perri states flatly that she does not recommend SAFe. Everyone she's talked to who found success with it ultimately ripped it up and turned it into something else, meaning they weren't really doing SAFe by the book. SAFe brings some rigor but has almost nothing about doing good product management, and taken too far it destroys things.

Perri does not recommend using SAFe.
Everyone who succeeded with SAFe ended up ripping it up and changing it.
There is very little in SAFe about doing good product management.
It can help bring rigor in certain areas, but pushed too far it will destroy things.

“I do not recommend using safe”
Melissa Perri · 49:00

“every single person I have talked to who likes safe found success was safe they ended up ripping it up and making it into something…”
Melissa Perri · 49:00

#safe#hot-take#product-management

Hot Take56:00

Take Scrum Away and the Product Owner Doesn't Exist

Perri's core thesis: the product owner is only a role inside scrum and doesn't exist without it, but product management is always needed. Therefore every product owner should fundamentally be a product manager, and companies shouldn't maintain separate PO and PM career tracks.

Take scrum away and you still need product management, but the product owner role vanishes.
All product owners should fundamentally be product managers.
Principal IC product managers are fine, but there's no real difference between an IC PO and IC PM.
Separate PO and PM titles just confuse everyone.

“product owner doesn't exist without scrum that's not a thing but you still need product managers”
Melissa Perri · 56:00

“all product owners should be product managers”
Melissa Perri · 56:00

#product-owner#product-management#careers#hot-take

Hot Take1:07:00

The Agile Industrial Complex and Its Certifications

Perri calls the ecosystem of agile coaches, trainers and certification bodies the 'agile industrial complex.' They make money by consulting on processes and charging around $2,500 per person for two-day certification classes. A certified scrum product owner credential doesn't mean someone can actually do the job.

Agile coaches, trainers and scrum orgs make money via consulting and certifications.
A CSPO comes from a two-day class costing roughly $2,500 per person.
The certificate doesn't prove someone can do product management.
Certifications may open doors at scrum/SAFe shops but signal the opposite at top tech firms.

“we call it the agile industrial complex”
Melissa Perri · 1:07:00

“a certificate at the end of a two-day class that says they're certified scrum product owner doesn't necessarily mean they could do the job”
Melissa Perri · 1:07:30

#agile#certifications#hot-take#consulting

Explainer· 2

Explainer13:00

The Agile Manifesto Was Written by Developers, Not PMs

Melissa Perri traces the origin of agile to the 2001 Agile Manifesto, written by software developers in Park City, Utah, who were independently working on ways to build software better. She stresses that no product manager was in the room, which is why the product owner role that emerged from scrum was never really about product management.

The Agile Manifesto was written in 2001 by developers practicing scrum, XP, kanban and other methods.
No product manager signed it or attended the meeting; Jeff Patton was close but never signed it.
Everything was approached from a 'how do we build better software' developer perspective.
The product owner role therefore did not originate from product management as practiced in Silicon Valley.

“nobody who wrote the agile Manifesto was actually a product manager”
Melissa Perri · 13:00

#agile#history#product-owner#scrum

Explainer20:00

The Product Owner Role Was Built to Feed Developers, Not Do Product

Perri explains that the product owner role was created inside scrum simply to help developers prioritize what to work on and keep the backlog full. Product owner training is typically a two-day class covering backlogs, stand-ups and prioritization, but nothing about experimentation, market research or data, which is what real product management requires.

Product owner was a mechanism to prioritize work for developers, held accountable for working on the highest-value things.
Standard training is a two-day class on backlogs, stand-ups and prioritization.
It teaches nothing about experimentation, market research or data.
Early scrum guides said the product owner could be the customer, a developer, or a department manager, not necessarily a PM.

“this product owner rooll did not emerge from product management as we know it today it was a way to help the developers prioritize what…”
Melissa Perri · 20:00

#product-owner#scrum#product-management

Story· 4

Story28:00

The Bank PO Writing User Stories 40 Hours a Week for a Login API

Perri recounts her first encounter with SAFe while training product managers at a bank in 2015. A product owner told her she had no time to talk to customers because she spent all week writing user stories, and her entire scope was the login API. It crystallized how SAFe reduced product owners to backlog-filling order takers.

A bank product owner said she couldn't talk to customers because she wrote user stories full time.
Her entire product scope was the login API, which already worked.
A separate product manager talked to customers and told her what to build.
This was Perri's first real exposure to how SAFe splits and narrows these roles.

“she's like the login API for a bank I'm like can you log in she's like yeah”
Melissa Perri · 29:00

#safe#product-owner#banking#story

Story50:00

The Dutch Water Company That Went Bankrupt Adopting SAFe

Perri shares a news story about a water company in the Netherlands that adopted SAFe in its IT teams and went bankrupt. The teams got so caught up learning SAFe processes that their new invoicing and payment-collection system took too long to deploy, and they couldn't collect payments from customers.

A Netherlands water company adopted SAFe in its IT teams.
Teams were so consumed by learning the process that deployment dragged on.
They couldn't collect payments because the invoicing system wasn't shipped in time.
The company went bankrupt, an extreme case of process crowding out customer value.

“they couldn't collect payments from customers because they got so caught up in the process”
Melissa Perri · 50:30

#safe#story#failure#process

Story58:00

The Product Owner Who Pushed Back and Got Promoted

In a workshop, a product owner told Perri she didn't think her team was working on the right things but feared getting fired if she said so. Perri encouraged her to raise it with her manager. She put together a case, said she didn't think they should be working on it, and was promoted instead.

A product owner feared being fired for questioning her team's priorities.
Perri urged her to bring the concern to her manager.
In product, your job isn't tied to a single project ending.
The PO made the case, and the company promoted her.

“she put together this whole thing went and said I don't think we should be working on this and they promoted her”
Melissa Perri · 58:30

#product-owner#careers#story#advice

Story1:14:00

At Athena Health, People Opted Out Once They Saw the PM Job

Perri describes transforming 365 product managers at Athena Health. After training everyone and giving them a chance to practice, many realized product management wasn't what they wanted, dealing with influence, people and accountability, and opted out. They were moved into operations, data, or user research roles rather than cut.

Athena Health had 365 people with scattered product titles, all converted to product managers.
After training and practice, many raised their hands and opted out of the PM role.
They found the influence and accountability demands too intense.
Nobody was cut; opt-outs moved into operations, data or user-research roles.

“when I did the transformation at Athena Health we had 365 product managers”
Melissa Perri · 1:14:00

“a lot of people raised their hand and said oh no no this is not what I wanted to do”
Melissa Perri · 1:14:30

#transformation#product-management#story#careers

Takeaway· 3

Takeaway41:30

A Development Framework Is Not a Product Operating Model

For companies trying to transform, Perri warns that agile methodologies are only a development operating model and won't help with strategy, go-to-market or product management. She lays out the real operating model: product strategy, organizational design, product operations infrastructure, and culture and incentives.

Agile methodologies are just a development operating model, not a full product operating model.
A real model covers product strategy, org design, product operations, and culture and incentives.
Many large orgs lack the infrastructure for teams to get data or talk to customers.
Leaders must ask whether they reward shipping volume or actual value tied to business goals.

“that's just a development operating model that's not actually going to help you with go to market with launching your products and with product management”
Melissa Perri · 41:30

#transformation#operating-model#product-strategy

Takeaway1:02:30

No Top Tech Company Has Product Owners

Perri and Lenny reinforce that the job-market data shows no top tech company uses the product owner title. Google, Amazon, Microsoft and Netflix all have product managers, not product owners. Product owners cluster in non-software-first companies like banks, telecoms and pharma.

No top software-first tech company uses a product owner role.
Google, Amazon, Microsoft and Netflix all staff product managers instead.
Product owners are concentrated in banks, telecoms and pharmaceutical companies.
The distinction reflects software-first vs non-software-first business models.

“no company you you've heard of that's a tech company has a product owner”
Lenny Rachitsky · 1:02:30

#product-owner#tech-industry#careers

Takeaway1:03:00

Get Scrum Off Your Resume and Show Value Instead

For product owners wanting to move into tech, Perri advises rewriting your resume around value and outcomes, not agile process. Instead of 'I prioritized the backlog,' describe the problem you solved, the customers you talked to, and the business metrics you moved, using a concrete login-API security example.

Describe your job from a value perspective, not agile cadences.
Don't list backlog prioritization; describe the problem solved and metrics moved.
Example: leading login-API security work to meet regulations and save the bank millions.
As a hiring CPO, Perri rejects resumes that lead with 'implemented scrum processes.'

“get scrum out of there right talk about what value you brought to the users and what metrics you moved”
Melissa Perri · 1:03:30

#careers#resume#product-management#advice

Frameworks in this episode

Baseline, Train, Practice, Level-Set

One Product Ladder (Kill the PO/PM Split)

The Agile Industrial Complex Test

The 'Can You See What Good Looks Like?' Staffing Test

The Four-Pillar Product Operating Model

The Product Owner Escape Ladder

The Value-Framed Product Résumé

Insights & moments

⚡Myth Buster· 2

If You Already Talk to Each Other, You Don't Need Scrum