Coaching Product Owners from Isolation to Collaboration | Sara Di Gregorio

Summary

Podcast Summary:

Scrum Master Toolbox Podcast: Coaching Product Owners from Isolation to Collaboration
Guest: Sara Di Gregorio
Host: Vasco Duarte
Release Date: November 21, 2025

---

Overview

In this episode, Vasco Duarte is joined by agile coach Sara Di Gregorio to explore common anti-patterns and best practices in product owner behavior. The discussion centers around the journey from isolationist habits—where product owners work solo and limit collaboration with their teams—to building rich, ongoing partnerships. Sara shares actionable coaching approaches and concrete techniques, with a focus on fostering productive dialogue and empowering team innovation.

---

Key Discussion Points & Insights

1. Product Owner Anti-Pattern: Working in Isolation

• Main Issue:
  Product owners sometimes assume they know everything relevant to the product, working alone on detailed user stories and involving the team only at the execution stage.
• Sara’s Insight:
  • “The most harmful product owner anti-pattern is when they believe that they don't need to interact with the team…they assume they know everything and the team has only to execute what they ask for.” (Sara, 01:38)
  • This approach stifles creativity, reduces buy-in, and ignores the value the team can add from both a technical and user perspective.

2. The Importance of Collaboration

• Host’s Perspective (Vasco):
  • Product and business innovation stem from the product owner, but technical innovation must come from the team.
  • “Product owners can come up with product and business innovation, but only the team can come up with the technical side of innovation…they can bring that into the conversation.” (Vasco, 03:29)

3. Coaching Strategy: User Story Mapping

• User Story Mapping as a Tool:
  • Sara introduces user story mapping workshops as a core exercise to break the isolation of product owners.
  • She emphasizes creating a space for dialogue:
    • “We create a moment where the product owner explains what they want to deliver…and then the team asks a lot of questions to understand, 'Why do you want this?'” (Sara, 04:13)
  • This approach encourages the product owner to reflect on their needs and perspectives as the team brings in both technical insight and user empathy.
  • It promotes shared understanding and quick identification of dependencies and alternative approaches.
• Impact Observed:
  • “With the user story mapping at the beginning of each development, it's helping a lot the team to understand the big picture…and the product owner to reflect on what she's asking.” (Sara, 05:54)

4. Notable Practice: Continuous Feedback and Availability

• Traits of Great Product Owners:
  • Sara recounts her experience working with exemplary product owners who:
    • Build strong, collaborative relationships with the Scrum team.
    • Exchange feedback continuously, not just during formal events.
    • Prioritize open and ongoing communication—the “muscle we have to train every day.” (Sara, 09:40)
    • Are readily available for clarifying questions, often attending stand-ups as observers and being approachable for quick problem-solving discussions.
  • “They don't attend Scrum events only as attendees, but as engaged contributors.” (Sara, 08:57)
  • Encourage transparency by actively participating in retrospectives and fostering shared ownership of the product.

5. Communication as a Core Skill

• Host’s Summary:
  • Effective product owners naturally leverage communication skills for team alignment and shared purpose.
  • “They don't come in with the idea that they know everything... they're collaborating. They use this, as you said, communication skills, which is so important.” (Host, 10:05)

---

Memorable Quotes

• Sara Di Gregorio:

  • “We have to create space for dialogue…we have to make them understand how important is to collaborate and cooperate with the team.” (02:04)
  • “Developers are not only developers…but are users of this product, for example, so they can give their point of view.” (05:00)
  • “They [great product owners] are not only the business part, but they are into the team.” (09:02)

• Vasco Duarte:

  • “Product owners can come up with product and business innovation, but only the team can come up with the technical side of innovation.” (03:29)

---

Timestamps for Key Segments

• 01:38 – Sara describes the product owner anti-pattern of working in isolation
• 03:29 – Host and Sara discuss why involving the team is critical for innovation
• 04:13 – User story mapping as a practical tool to enhance collaboration
• 07:26 – Sara shares the qualities and practices of excellent product owners
• 08:55 – Importance of availability, engagement, and communication
• 10:05 – Host summarizes the essence of great product owner behavior

---

Original Language & Tone

The conversation is practical, encouraging, and focused on real-world coaching. Both Vasco and Sara use accessible, conversational language peppered with concrete examples and gentle guidance on improvement. Sara’s tone is empathetic and collaborative, echoing her core message about building relationships and mutual understanding.

---

Further Information

• Connect with Sara Di Gregorio:
  • Sara’s LinkedIn (As referenced at 10:43)
• Reference:
  • User Story Mapping by Jeff Patton blog post (Host, 06:40)

---

This episode is ideal for Scrum Masters, Agile coaches, product owners, and anyone looking to bridge communication gaps and unlock the potential of team collaboration in Agile environments.

Transcript

[Vasco]

Hey there Agile adventurer, just a quick question.

[Host]

What if for the price of a.

[Vasco]

Fancy coffee or half a pizza, you could unlock over 700 hours of the best agile content on the planet? That's audio, video, E courses, books, presentations, all that you can think of. But you can also join live calls with world class practitioners and hang out in a flame war free and AI slop clean slack with the sharpest minds in the game. Oh, and yes, you get direct access to me, Vasko, your Scrum Master Toolbox podcast. No, this is not a drill. It's this Scrum Master Toolbox membership. And it's your unfair advantage in the agile world. So if you want to know more, go check out scrummastertoolbox.org membership. That's scrummastertoolbox.org Membership. And check out all the goodies we have for you. Do it now. But if you're not doing it now, let's listen to the podcast.

[Host]

Hello everybody. Welcome to our TGIF and Product Owner episode this Week with Sara DiGregorio. Hey Sara, welcome back. That is lovely way to greet everybody. Happy Friday everybody. And we're talking about product owners of course, great product owners. We're going to explore all about that. But before do share with us potentially the worst product or anti pattern you've witnessed in your career.

[Sara Di Gregorio]

Well, I think that the anti pattern, the most harmful product owner anti pattern is when they believe that they don't need to interact with the team because sometimes they feel very comfortable in their subject so they assume they know everything and the team has only to execute what they ask for. In this mindset I think that the product owner might write detailed user stories alone, keep interesting discussions with developers and work with developers only when they think it's important to include them. But for me this is the opposite. For me we have to work in opposite way. So if I encounter this situation, for me the first step is to create space for the dialogue. To be honest, I think that we can start a training with the product owner. So we have to make them understand how important is to collaborate and cooperate with the team and then make them automatically including the team because they have to understand how impacting is. Include the team during their conversation from the beginning of the feature study.

[Host]

What I what I often talk about with proctors when it comes to that specific idea of helping them understand why it's important to involve the team is this idea that product owners can come up with product and business innovation, but only the team can come up with the technical side of innovation. Because they understand the technology limitations and possibilities and they can bring that into the conversation. And product owners typically can't because they're not looking at the code every day. They're not looking and dealing with what technology can do. But that's my approach.

[Vasco]

What's your approach?

[Host]

To try to show the benefit to the product owners of including the team in the conversation early on, when thinking about features or designing features.

[Sara Di Gregorio]

Yes, I experiment the user story mapping. And first of all, I had a workshop with them, so with the team and the product owner to explain what the user story mapping is. And then we are using it. So we create a moment where the product owner explains from his point of view, from her point of view, what they want to deliver. So what they would like to see in the product. And then the team ask a lot of questions to understand, why do you want this? Not only, okay, so I will do it. No, for me, it was very important to give attention to why uproductone want this feature, want this on the product. What I understood is that the product owner, with this exercise understood that they can also change their mindset talking with the developers. It doesn't mean that the developers said, okay, no, we cannot do this. No, the developers are normally not only developers, but are users of this product, for example, so they can give their point of view. From a technical point of view, it's like, okay, but if we do in this way, we can be faster and then you can try your product faster and give us a feedback. But also because they can, as a user, give their opinion and make the product owner reflecting. So what I saw is that with the user story mapping at the beginning of each development, it's helping a lot the team to understand the big picture of what the the product owner is asking for them and the product owner to reflect on what she's asking. So I think that this is the right approach to solve this problem.

[Host]

I think. I really love user story mapping in general. But as you were just saying, it creates dialogue, right? It doesn't start from the perspective that somebody has all the answers. It starts from the perspective that we're creating the narrative. Right? Like that's why it's called user story. There's a narrative. We're creating the narrative together. So definitely a shout out to Jeff Patton for the user story mapping promotion that he did way back when. I'll put the link in the show notes to the original blog post, which I think is a great blog post to read even today. But now we turn our attention to great Product owners, Sarah, because there's many of them out there. So shout out to them as well. But share with us potentially the best product owner you've ever worked with. How did they work?

[Sara Di Gregorio]

Okay. I'm very lucky I think because I'm working with product owners that in my opinion are a very great example to follow. So in this moment of my working life, I am really very happy. I think that one of the key strength is the ability to build a strong collaborative relationship with the Scrum team. We constantly exchange feedback so we don't wait for the Sprint review with the shared goal and improving both our collaborating and the way of working. So from a practical point of view, we involve the team as I said before in the user story mapping. So after the analysis phases, the analysis phase and for what I saw this creates an open discussion around upcoming topics, helps the team surface potential dependencies. So and I think it's very, very, very important. Another important skill that they demonstrate to have is the availability. So they always have. They always are ready to answer questions from the team to clarify details. We always find a moment during the day to to be present with the team. For example, they are observer in the daily standup. So there. So if the team needs so can we have a five minutes talking later. And for me it's very important to give this availability. So it's very important so that they don't attend to the Scrum events only as attendees, but as engaged contributors. I see how they open encourage the open dialogue, for example, also during the retrospective they help a lot because they are interested in working with the team. So they are not only the business part, but they are into the team. They are very interested. And I think that this communication, this five episode, I always come to the communication because I think it's as that we have to train every day and helps a lot to bring clarification.

[Host]

And great product owners kind of naturally have that ability to communicate. They don't come in with the idea that they know everything. They don't come in with the idea that they must do everything alone, even if they don't do it, if they don't know about it. But they come in with the idea that we're doing this together, they're collaborating. They use this, as you said, communication skills, which is so important.

[Vasco]

Thank you for sharing all of these.

[Host]

Stories with us this week, Sara. It's been a pleasure to have you as a guest here on the podcast. We're getting close to the end though. But before we go, where can people find out more about you and the work that you're doing.

[Sara Di Gregorio]

Well, you can find something on LinkedIn. Sara Di Gregorio I'm not very social, so I don't post a lot of things, but when I see something that it's very important for me, I try to repost because I always think that it's important to give the opportunity to the important post on the social to be written by everyone.

[Host]

Yeah, absolutely. So we'll put the link to sara's page on LinkedIn, so be sure to check out her post stream and why not ask a few follow up questions. I'm sure there's a lot we can all learn from each other as a community. Sara, it's been a pleasure. Thank you very much for being here and for being so generous with your time and your knowledge.

[Sara Di Gregorio]

The pleasure is mine. So thank you very much to you for giving me this opportunity. It was very nice, so thank you very much.

[Vasco]

All right, I hope you liked this episode, but before you hit next episode, here's the deal. This podcast is powered by people like you. The members who wanted more than just inspiration. They wanted real tools and real connection to people who are practicing agile. Every day we're talking access to over 700 hours of agile Gold, CTO level strategy talks, Summit keynotes, live workshops, E courses, Deep Dive interviews, books, and if you're into no Estimates, we got the pioneers of no Estimates in those Deep Dive interviews as well. Agile Business Intelligence, creating product visions, coaching your product owner courses, you name it. You'll get invites to monthly live Q&As with agile pioneers and practitioners, plus a private Slack community which is free of all of that AI slop you see everywhere. And of course without the flame wars, it's a community of practitioners that want to learn and thrive together. The best place to connect with community and learn together. So if this podcast has helped you before, imagine what you will get from this podcast membership. So head on over to scrummastertoolbox.org membership and join the community that's shaping the future of Agile. We have so much for you. So check out all the [e-mail] membership because listening is great, it's important, but doing it together, that's next level. I'll see you in the community.

[Host]

Slack.

[Outro Voice]

We really hope you liked our show. And if you did, why not rate this podcast on Stitcher or itunes? Share this podcast and let other Scrum masters know about this valuable resource for their work. Remember that sharing is caring.

[Sara Di Gregorio]

Sam.