How to Say "This Is a System Problem" to the Product Owner Without Triggering Defensiveness
How to move the conversation from blame to ownership and action.
I’ve been on both sides of this conversation.
I’ve been the person trying to diplomatically explain that the whole system is broken. And I’ve been the person hearing that feedback, mentally preparing my defence before the other person finishes their sentence.
Believe me… neither side is fun.
As a Scrum Master, you have the exact same problem.
You are expected to “diagnose” but criticized for your “diagnosis.”
Stories are not ready. Sprint work spills over. Priorities change mid-sprint. Developers wait for answers that don’t come. Stakeholders bypass the Product Owner entirely.
From where you are sitting, the diagnosis of the above problems is obvious:
The system around product decision-making is broken.
But the moment you say “this is a systems problem” out loud, you risk damaging your relationship with the Product Owner if you’re not careful in your delivery.
So, how do we fix the delivery?
Let’s find out.
Got an urgent question?
Get a quick answer by joining the subscriber chat below.
