← Scrum Master Toolbox Podcast: Agile storytelling from the trenches

Product Owners Who Turn Feedback Into Agile Team Learning | Oluyomi Emmanuel

Evaluation and Summary

7.4/10

This 14-minute episode features Oluyomi Emmanuel, an Agile coach with seven years of experience, discussing how Product Owners can leverage team feedback to drive learning and improvement. The episode is structured around two contrasting archetypes: the great Product Owner and the absent Product Owner. The first segment highlights a Product Owner who excels at soliciting feedback, listening without defensiveness, and acting on what he hears. Emmanuel illustrates this with a concrete example: when a team raised concerns during a sprint review that completed work wasn't aligned with customer needs, the PO didn't defend the roadmap. Instead, he treated the feedback as evidence worth investigating. He secured training budget and enrolled both himself and the team in behavior-driven development (BDD) training. Critically, the PO didn't treat this as a checkbox exercise—he actively participated in the learning and helped integrate BDD practices into refinement, stakeholder conversations, and interviews. This shift moved team discussions from abstract requirements to specific situations and expected outcomes, surfacing hidden assumptions earlier and enabling constructive challenge of unclear requirements before implementation. The second segment addresses the absent Product Owner anti-pattern, which Emmanuel frames as a structural role design problem rather than individual time management failure. His example involves a PO who also served as a line manager, causing the PO responsibilities to be perpetually squeezed into leftover time. This created bottlenecks: epics lacked sufficient context for refinement, questions accumulated, and decisions stalled waiting for an unavailable person. Emmanuel's solution wasn't to demand more availability but to map stakeholders and invite relevant parties directly into refinement, giving developers access to context without funneling everything through a single person. The episode includes two self-reflection questions for listeners: how does your PO demonstrate that feedback changes behavior, and are you compensating for an unavailable PO in ways that hide organizational design problems? The material is grounded in practical examples and offers actionable frameworks (stakeholder mapping, BDD adoption, feedback loops) rather than abstract theory. Emmanuel's insights connect Agile principles to real organizational dynamics.

Verdict: A focused, practical episode with concrete examples and actionable frameworks that directly addresses its title; solid for Agile practitioners seeking PO insights, though limited depth and sourcing prevent a higher score.

News rubric

  • Accuracy and sourcing 3/5 20%

    Examples are concrete and plausible but presented as anecdotes without external sources or citations; Emmanuel's credentials are stated but not independently verified.

  • Balance and context 4/5 20%

    Episode presents both positive and negative PO archetypes with systemic explanations; reframes absent PO as design problem rather than personal failing, showing nuance and organizational perspective.

  • Timeliness and relevance 4/5 15%

    Product ownership and team feedback loops are evergreen Agile topics; the specific focus on feedback-driven learning and role design remains relevant to current Agile practice.

  • Substance 4/5 15%

    Dense with actionable insights (BDD integration, stakeholder mapping, feedback loops) and grounded examples; two distinct scenarios with clear lessons, though 14 minutes limits depth.

  • Delivers on its title 5/5 15%

    Title promises POs turning feedback into team learning; episode delivers exactly that through two detailed examples showing feedback mechanisms and learning outcomes.

  • Value for time 4/5 15%

    14 minutes is tight for two substantial scenarios plus reflection questions; pacing appears efficient with minimal filler, though brevity may limit exploration of implementation details.

How we score News

Worth it if you're a Scrum Master, Agile coach, or Product Owner looking for practical frameworks on feedback loops and organizational design in Agile teams.

Based on the episode description. AI-generated; it can be wrong.

Show notes

Oluyomi Emmanuel: Product Owners Who Turn Feedback Into Agile Team Learning The Great Product Owner: Listening, Investing, and Learning With the Team Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes . "A great product owner is not the person with all the answers. It is the person who creates access to the right evidence." - Oluyomi Emmanuel Oluyomi shares the example of a Product Owner whose strongest habit was asking the team for feedback, listening without defending himself, and then acting on what he heard. In one sprint review, the team looked at internal metrics and raised a difficult concern: they were completing work, but it did not always seem closely connected to what customers needed. The Product Owner could have defended the roadmap or blamed incomplete metrics. Instead, he treated the feedback as evidence worth investigating. He secured a training budget and enrolled both himself and the whole team in behavior-driven development training. More importantly, the training did not remain a certificate exercise. The Product Owner joined the learning and helped bring BDD practices into refinement, stakeholder conversations, and interviews. The team's conversations moved from abstract requirements to specific situations and expected outcomes. Hidden assumptions became visible earlier, and the team could challenge unclear requirements constructively before implementation began. Self-reflection Question: How does your Product Owner show the team that feedback changes real behavior? The Bad Product Owner: The Absent Product Owner as a Role Design Problem Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes . "An absent product owner is often not an individual time management problem. It is usually a role design problem." - Oluyomi Emmanuel Oluyomi also describes the absent Product Owner anti-pattern. In his example, the Product Owner was not careless or uninterested. The structural problem was that the same person was both Product Owner and line manager, so the Product Owner role kept being squeezed into whatever time remained. Epics existed, but the team lacked enough context to refine them. Questions accumulated, refinement became a place to discover missing information, and important decisions waited for someone who was rarely available. Oluyomi first asked for more Product Owner availability, but that did not change the system because the competing responsibilities remained. He then created a stakeholder map for the major areas of work: who had the business problem, who owned the desired outcome, who had specialist knowledge, and who would be affected by the change. Inviting relevant stakeholders into refinement gave developers direct access to context. The lesson was not to remove product ownership, but to stop making the Product Owner the only messenger between the team and every stakeholder. In this segment, we refer to behavior-driven development , product ownership , and stakeholder collaboration . Self-reflection Question: Are you compensating for an unavailable Product Owner in a way that keeps the real organizational design problem hidden? [The Scrum Master Toolbox Podcast Recommends] 🔥In the ruthless world of fintech, success isn't just about innovation—it's about coaching!🔥 Angela thought she was just there to coach a team. But now, she's caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn't just about the product—it's about the people. 🚨 Will Angela's coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue. Buy Now on Amazon [The Scrum Master Toolbox Podcast Recommends] About Oluyomi Emmanuel Oluyomi is a Scrum Master, Agile Coach, and Product Lead with over seven years of experience helping teams work better and deliver meaningful digital products. Having worked across energy, consumer platforms, and fintech, he is passionate about building high-performing teams, creating clarity, and turning Agile principles into real business and customer value. You can link with Oluyomi Emmanuel on LinkedIn .

Episode page

More from Scrum Master Toolbox Podcast: Agile storytelling from the trenches

Oluyomi Emmanuel, a Scrum Master with seven years of experience across fintech, energy, and consumer platforms, discusses how to measure Scrum Master success through 'constructive independence'—the team's growing ability to notice, discuss, and solve problems independently. Rather than traditional metrics, Emmanuel…

Worth it if you're a Scrum Master or Agile coach seeking to reframe success metrics beyond velocity or burndown, or if you want practical retrospective formats and daily reflection practices.

Oluyomi Emmanuel, an agile coach with seven years of experience across fintech, energy, and consumer platforms, discusses a real organizational challenge: creating end-to-end visibility across multiple value streams without adding administrative burden. The episode centers on a case study where Oluyomi's client faced…

Worth it if you're a scrum master, agile coach, or product leader struggling with fragmented work visibility, competing priorities, or unclear ownership across teams or value streams.

Ad-heavy

Oluyomi Emmanuel, a Scrum Master and Agile Coach with seven years of experience, discusses a common dysfunction in supposedly agile teams: the shift from individual task ownership to collective work ownership. He describes a pattern where teams appear collaborative during ceremonies but revert to siloed behavior…

Worth it if you're a Scrum Master or agile coach struggling with siloed team behavior or looking for practical ways to shift team language and ownership.

Oluyomi Emmanuel, a Scrum Master with seven years of experience across fintech, energy, and consumer platforms, shares a cautionary case study about how team trust can deteriorate before a Scrum Master intervenes. The episode centers on a newly formed eight-person software team where tension emerged between a tech…

Worth it if you're a Scrum Master or Agile coach looking for a cautionary tale about early intervention in team conflict, or someone managing newly formed technical teams.

/10