Podcast Episode Summary
Podcast: Scrum Master Toolbox Podcast: Agile storytelling from the trenches
Episode Title: From Requirements Documents to Customer Obsession—Redefining the PO Role
Guest: Karim Harbott
Host: Vasco Duarte
Date: November 7, 2025
Episode Overview
This episode delves into the changing nature of the Product Owner (PO) role in Agile environments, moving from the mechanical handling of requirements to a more strategic, customer-obsessed approach. Karim Harbott, Agile coach, thought leader, and author, shares his perspectives on common Product Owner anti-patterns, practical ways to foster true teamwork, and what makes a great Product Owner stand out. The conversation is rich with actionable insights and illustrative stories aimed at Scrum Masters and Agile practitioners eager to raise the bar on product ownership.
Key Discussion Points and Insights
1. Common Product Owner Anti-patterns
- PO as Requirements Scribe:
- The most common anti-pattern Karim sees is the Product Owner as a mere writer of user stories and acceptance criteria—essentially, a spec-writer who deposits lengthy requirements into Jira and expects the team to implement them without further involvement ([01:33]).
- Quote:
“User story writer, acceptance criteria writer, product owner who thinks it's their job to basically write big long requirements documents... and say, go away and deliver that stuff for me, that is so far away from what user stories were supposed to be and what product ownership is supposed to be.” – Karim Harbott [01:41]
- Over-Specifying Solutions:
- Sometimes POs go further by prescribing how things should be implemented, intruding into the solution space that should belong to the development team ([01:57]).
2. Empowering Teams & Collaboration
- Letting Teams Own Their Work:
- Karim emphasizes the shift from teams just working for the Product Owner to collaborating with them ([02:46]).
- He highlights the importance of pushing down decisions that were once the domain of project managers, thereby making teams more autonomous and engaged.
- Design Thinking and Risk Management:
- Karim describes “the mantra of design thinking” with four main risks to address together: desirability (customer value), viability (business value), feasibility (can it be built), and usability (ease for users). These are shared responsibilities:
- PO: desirability & viability
- Designer: usability
- Developer/Tech Lead: feasibility ([03:22])
- Quote:
“That sounds a lot like a collaboration or the product trio... This is a team sport. There are elements of ‘are we building the right thing?’ and ‘are we building the thing right?’ but this is a team sport. It’s not ‘me do this, you do that.’” – Karim Harbott [04:20]
- Karim describes “the mantra of design thinking” with four main risks to address together: desirability (customer value), viability (business value), feasibility (can it be built), and usability (ease for users). These are shared responsibilities:
- Team Sport Analogy:
- Host Vasco and Karim both stress how underused but apt the “team sport” metaphor is for Agile, underlining that meaningful product development is always a collaborative act ([05:22]).
3. What Makes a Great Product Owner
- Strategic, Not Just Tactical:
- Great POs focus on direction—defining the problem, target customer, value proposition, business model, and strategy—while leveraging the team’s expertise to fulfill that vision ([06:14]).
- Quote:
“Your role on that team is strategic. It’s direction. It’s what problem are we solving and for whom? … And how can I collaborate with this other group of awesome people to make that a reality?” – Karim Harbott [06:20]
- Customer Obsession:
- Karim regards customer focus as the PO’s superpower, whether the customers are external users or internal stakeholders ([07:27]).
- Quote:
“They are customer obsessed… obsessed with the purpose of the product, the why of the product, what problem are we solving and for whom?” – Karim Harbott [07:29]
- Leading with Vision, Not Just Features:
- The best POs always begin by defining outcomes, use methods like “working backwards” from customer need (as at Amazon), and ensure the team is actively involved in both problem solving and ideation—not just feature delivery ([07:27]-[09:11]).
- Collaboration Fosters Creativity:
- With a shared purpose, teams are more likely to contribute great ideas aligned with business value, freeing the PO from micromanagement and sign-off bottlenecks ([08:56]).
- Quote:
“You don’t have to have every great idea. You don’t have to sign everything off because they know too. So, it’s collaborative, but you’re also leading and painting that vision: wouldn’t it be great if we solved this?” – Karim Harbott [08:56]
4. Advice and Takeaways for Teams and Scrum Masters
- This episode doubles as a checklist for organizations seeking to realign their POs with high-impact behaviors:
- Shift from tactical requirements writing to strategic product leadership
- Cultivate a shared sense of mission and customer obsession
- Enable cross-functional collaboration and push ownership into the team
- Encourage POs to articulate vision and outcomes, not just features ([09:11])
Notable Quotes
- “It's the most common one that I see... acceptance criteria writer, product owner who thinks it's their job to basically write big long requirements documents...”
— Karim Harbott [01:35] - “We are a product team. We are a scrum team. Our job is to deliver value. Here's my skill set. Here's your skill set.”
— Karim Harbott [05:10] - “[Great product owners] focus on the customer, they focus on outcomes, they focus on the strategy and collaborate with the team to make that a reality.”
— Karim Harbott [06:46] - “They're always talking about the customer. They're always talking to the customer. They're always thinking about, how can I solve this problem for my customers, deliver more value for my customers, capture some of that value for the business, and how can I get the team working with me to do that?”
— Karim Harbott [07:45]
Timestamps for Key Segments
- 01:33: Anti-pattern: PO as spec-writer and solution prescriber
- 02:46: Role of POs in enabling team ownership; design thinking risks
- 05:22: Team sport analogy for Agile
- 06:14: What sets great POs apart—strategic vs. tactical focus
- 07:27: Customer obsession as PO’s north star; “working backwards”
- 08:56: Teams aligned on vision foster innovation and self-management
- 09:11: Checklist for impactful product ownership
Further Resources
- Connect with Karim Harbott: LinkedIn – Karim Harbott ([09:42])
- Karim’s Book: The Six Enablers of Business Agility – Lessons from 15 years of organizational transformation ([09:48])
Episode Tone
The conversation is candid, insightful, and laced with practical wisdom drawn from extensive field experience. Karim’s tone is direct and passionate, advocating for empowering, customer-focused product ownership and authentic team collaboration.
In Summary
This episode is a must-listen for Scrum Masters and Product Owners wanting to escape the trap of tactical busyness and embrace a strategic, outcome-driven, truly collaborative approach to building products that matter. If your teams still see the PO as just a ticket-writer, this episode—and Karim’s practical checklist—could spark the mindset shift you need.
