Everything you’ve ever wanted to know about SAFe and the product owner role | Melissa Perri
Executive Summary
Melissa Perri joins Lenny Rachitsky to discuss development frameworks, product operating models and product-owner responsibilities. This selected coverage presents her critical view of SAFe rather than a neutral verdict; it omits detailed company-failure anecdotes and does not assess every implementation. Company examples are her account, unverified here. Untimed topics are editorial, not video chapters.
Key Takeaways
Understand why a large organization wants rigor
Perri says companies that did not grow up building software often adopt frameworks to coordinate work at scale. She values conversations that clarify and break down the work, but questions ceremony for its own sake. Her criticism does not imply that every use of Scrum or SAFe has failed.
Separate development coordination from product management
She calls agile frameworks part of a development operating model, not a complete answer to go-to-market or product strategy. Being able to build on a cadence does not establish that the right product is being built or launched well. This distinction is her view of the operating model.
Connect strategy with organizational design
Perri asks how product strategy is set, how the organization is arranged around products and whether skilled PMs exist throughout it. A transformation needs more than changing team names. Responsibilities and the portfolio should connect to business goals.
Give teams access to customers and evidence
She includes product operations and infrastructure in the model: can teams get useful data and talk with customers? Bureaucracy can block capable people from doing good work. Leaders need to address those constraints rather than only request better decisions.
Review what the incentives reward
Perri contrasts rewarding a large release backlog with asking whether the work creates business and customer value. She accepts enough process to make a large organization transparent and efficient. Her concern is process displacing the conversation about what the organization is achieving.
Pair training with experienced leadership
She supports developing existing people while bringing in leaders who have done the work before. Training followed by an unsupported instruction to go may not create ongoing learning. Her transformation examples are her account, not independently verified results.
Ask for strategic ownership and an outcome
For product owners seeking a broader role, she suggests joining customer research, asking about career paths and asking what a release should change. Start a constructive discussion about goals and measurement. Her advice is not a promise that pushback is safe or will lead to promotion in every workplace.
The Conversation Breakdown
Understand why a large organization wants rigor
⏱ Untimed topicPerri says companies that did not grow up building software often adopt frameworks to coordinate work at scale. She values conversations that clarify and break down the work, but questions ceremony for its own sake. Her criticism does not imply that every use of Scrum or SAFe has failed.
Separate development coordination from product management
⏱ Untimed topicShe calls agile frameworks part of a development operating model, not a complete answer to go-to-market or product strategy. Being able to build on a cadence does not establish that the right product is being built or launched well. This distinction is her view of the operating model.
Connect strategy with organizational design
⏱ Untimed topicPerri asks how product strategy is set, how the organization is arranged around products and whether skilled PMs exist throughout it. A transformation needs more than changing team names. Responsibilities and the portfolio should connect to business goals.
Give teams access to customers and evidence
⏱ Untimed topicShe includes product operations and infrastructure in the model: can teams get useful data and talk with customers? Bureaucracy can block capable people from doing good work. Leaders need to address those constraints rather than only request better decisions.
Review what the incentives reward
⏱ Untimed topicPerri contrasts rewarding a large release backlog with asking whether the work creates business and customer value. She accepts enough process to make a large organization transparent and efficient. Her concern is process displacing the conversation about what the organization is achieving.
Pair training with experienced leadership
⏱ Untimed topicShe supports developing existing people while bringing in leaders who have done the work before. Training followed by an unsupported instruction to go may not create ongoing learning. Her transformation examples are her account, not independently verified results.
Ask for strategic ownership and an outcome
⏱ Untimed topicFor product owners seeking a broader role, she suggests joining customer research, asking about career paths and asking what a release should change. Start a constructive discussion about goals and measurement. Her advice is not a promise that pushback is safe or will lead to promotion in every workplace.
Core Frameworks & Ideas
Development versus product operating model
Distinguish delivery coordination from deciding, organizing and launching valuable products.
Strategy, design, skills, operations
Review product direction, organizational structure, capabilities and the infrastructure teams need.
Training with experienced support
Pair skill development with leaders and peers who can demonstrate and coach the work.
Actionable Next Steps
- ✓Audit whether the team can reach customers and obtain useful product data.
- ✓Link a release to the customer and business change it should create.
- ✓Review whether process makes work visible or distracts from its value.
- ✓Discuss strategic responsibility and ongoing coaching with the relevant leader.
Notable Quotes
“Can they get the data to make decisions?”
“There's not a lot in SAFe about doing good product management.”
“If you're going to spend money upskilling your people, do that, but you also have to intersperse people who know what they're doing.”
The One Thing to Remember
A delivery framework cannot replace product strategy, customer access and people who know how to turn evidence into value.