"The Coaching Conversation Nobody Wants to Have"

Part 1 of 2 — The Power Problem. Part 2: The Conversation Itself.

There is a conversation that every Scrum Master, Agile Coach, and team lead eventually faces. A manager’s behaviour is visibly undermining the team. The sprint review becomes a performance review. The daily standup turns into a reporting line. Decisions made by the team in the sprint planning are quietly overridden by Monday morning. Everyone in the team sees it. Nobody says anything. And the person who is nominally responsible for the team’s effectiveness – the Scrum Master – is expected to do something about it.

The problem is not that the conversation is uncomfortable. The problem is structural. And until you understand the structure, all the advice about “how to have difficult conversations” is solving the wrong problem.

---

The Hook: The Most Dangerous Sentence in Agile Coaching

“Someone needs to tell the manager.”

I have heard this sentence in every organisation I have worked in. It usually comes from a senior team member, sometimes from a Product Owner, occasionally from HR. It is always said with a resigned tone that implies everyone already knows who “someone” needs to be. It is the Scrum Master. And everyone in the room – including the Scrum Master – knows that the consequences of that conversation are entirely theirs to carry.

This is not a communication skills problem. It is a power problem. And organisations that treat it as a communication skills problem produce Scrum Masters who attend difficult conversations training, go back to their teams, say the difficult thing to the manager, and then spend the next six months managing the fallout.

---

The Reality: Why the Conversation Is Structurally Loaded

The Authority Gap

The Scrum Master has no formal authority over anyone in the organisation. The Scrum Guide describes the role as a servant leader – someone who influences through expertise, relationship, and coaching rather than through position or power. This is a deliberate and theoretically sound design choice. It is also, in practice, a significant vulnerability when the person whose behaviour needs to change outranks you organisationally.

A manager at the middle or senior level typically controls the Scrum Master’s contract, day rate, or performance review. They have access to stakeholders the Scrum Master does not. They have been in the organisation longer, understand its politics better, and have relationships with the people who make structural decisions. When a Scrum Master tells a manager that their behaviour is undermining the team, they are not two professionals having a peer conversation. They are engaging across a significant power differential – and the power differential does not disappear because the Scrum Guide says everyone should be a servant leader.

The Accountability Vacuum

The second structural problem is accountability. In a well-functioning Agile environment, the organisation’s leadership is accountable for creating conditions in which Agile can succeed. This means protecting team autonomy, acting on impediments, and modelling the behaviours the transformation requires. Most organisations have not set this accountability up clearly. There is no formal mechanism by which a manager who consistently undermines team self-organisation is held responsible for the consequences.

In this vacuum, the accountability drifts to the person closest to the problem. The Scrum Master becomes the de facto owner of a situation they did not create and cannot structurally resolve. They are expected to coach upward – to influence a manager’s behaviour through relationship and skill alone – without formal backing, without escalation paths, and without protection if the conversation goes badly.

What the Theory Assumes	What Reality Looks Like
Managers understand Agile values	Many managers received one-day Agile training and continued operating as before
Organisations support upward feedback	Most organisations punish the person who delivers it, not the behaviour that warranted it
Scrum Masters have coaching authority	Scrum Masters are often mid-level contractors with no formal standing to challenge management
Difficult conversations lead to change	Without structural consequences, they lead to awareness at best and resentment at worst

The Isolation Dynamic

The third structural problem is what I call the isolation dynamic. When a manager’s behaviour is undermining a team, the team members are rarely in a position to say so directly. They work for that manager, depend on them for performance reviews, and operate in an environment where the manager’s behaviour is itself evidence of what is and is not safe to say. So the team watches. They note the pattern. They mention it quietly to the Scrum Master. And then they wait to see what happens.

This creates a specific trap: the Scrum Master enters the conversation carrying the team’s unexpressed concerns, with no formal mandate to do so, and no protection if the manager responds defensively. If the conversation goes well, the team’s situation improves and the Scrum Master gets quiet credit. If it goes badly, the Scrum Master carries the consequences alone – while the team, understandably, maintains plausible deniability.

I have seen this dynamic play out in financial services, pharmaceutical, and manufacturing environments. It is not a personality issue. It is a structural feature of organisations that have adopted the language of Agile without redesigning the authority structures that Agile actually requires.

---

The Checksum: What the Scrum Guide Says – and What It Cannot Fix

The Scrum Guide is clear that the Scrum Master serves the organisation by “leading, training, and coaching the organisation in its Scrum adoption” and by “causing the removal of impediments to the Scrum Team’s progress.” A manager who consistently overrides team decisions, micromanages sprint execution, or uses Scrum events as control mechanisms is, by definition, an impediment to the team’s progress.

But “causing the removal” is not the same as personally confronting. It implies escalation – taking the impediment to the level of the organisation where it can actually be resolved. In practice, most Scrum Masters interpret this as their responsibility to have a direct conversation with the person whose behaviour is the problem, rather than as an instruction to escalate structurally to the leadership level that has the authority to address it.

This is a critical misreading. The conversation with the manager is sometimes necessary. It is rarely sufficient. And approaching it as sufficient – as though skilled communication alone can resolve a structural authority problem – is the error that puts Scrum Masters in the most vulnerable position.

“Coaching upward is not about having the right words. It is about having the right conditions. Without conditions that make change structurally possible, the most skilful coaching conversation produces insight in the room and nothing outside it.” Markus – agile-checksum.com

The Three Structural Preconditions for the Conversation to Work

Before the conversation with the manager happens, three structural questions need honest answers:

1. Is there organisational backing for what you are about to say?

Not just implicit approval – explicit backing. Does someone above the manager in the organisational hierarchy know this conversation is happening? Do they support it? Have they communicated, clearly and directly, that the behaviour in question is inconsistent with the organisation’s stated approach? If the answer is no, you are having the conversation without a structural safety net.

2. Are the consequences of the behaviour documented and specific?

The conversation is much stronger – and much less personal – when it is anchored in specific, observable outcomes. Not “your approach makes the team uncomfortable” but “in the last three sprints, four team decisions made during sprint planning were overridden before Wednesday. Here is the list.” Specific, documented impact is harder to dismiss as perception or sensitivity. It also shifts the conversation from interpersonal to operational.

3. Is there an escalation path if the conversation does not produce change?

If the manager acknowledges the feedback, agrees to change, and then continues the same behaviour the following sprint – what happens next? If the answer is “nothing, because there is no mechanism for holding a manager accountable for how they interact with Scrum teams” – then the conversation is a release valve, not a structural intervention. Understanding this before you walk into the room is essential for managing your own expectations and the team’s.

---

Real-World Examples: The Structure in Action

The Manager Who Meant Well

A department head in a mid-size logistics company genuinely believed he was supporting his Scrum teams. He attended every sprint review. He asked questions about progress. He sent follow-up emails to individual team members after sprint planning to check they were clear on priorities. He saw these behaviours as engagement. His team experienced them as surveillance.

The Scrum Master raised this with him directly. The conversation was respectful and professionally handled. The manager listened, acknowledged the feedback, and described his intention to step back and give the team more space. Two weeks later, the follow-up emails resumed. He had not changed; he had temporarily adjusted a behaviour while the feedback was fresh, and then reverted when the pressure to deliver information upward reasserted itself.

The pattern continued for four months. Not because the Scrum Master had the wrong conversation. But because the manager’s behaviour was being driven by pressure from above – pressure to have visibility and control of delivery timelines – and that pressure had not changed. No conversation with the manager could fix what was being caused by his own manager’s demands. The impediment was one level higher than where the conversation was happening.

The Transformation That Got the Structure Right

In a pharmaceutical organisation I worked with, the Head of IT and the programme director had a documented agreement: any escalated people-level impediment reported through a Scrum Master would be acknowledged in writing within five working days and resolved or actively progressed within one sprint. This agreement was not aspirational. It was in the transformation governance document.

When a Scrum Master in that environment identified a manager whose behaviour was creating a pattern of team dysfunction, they documented three specific incidents, raised them formally through the agreed escalation path, and within two weeks the manager had a direct conversation with their own line manager about the expectations associated with managing Agile teams. The behaviour changed. Not perfectly, not immediately, but structurally and durably.

The Scrum Master in this case was not braver or more skilled than their peers in other organisations. They were operating in an environment where the structural preconditions made the conversation possible.

---

The Takeaway: Fix the Structure Before You Fix the Conversation

The coaching conversation with a manager whose behaviour is undermining the team is sometimes necessary. It is almost never a first step. Before that conversation happens, the structural conditions that make it viable need to be in place – or explicitly acknowledged as absent.

If the structure is in place: document the impact, secure the backing, and have the conversation with clear escalation in view. Part 2 of this series will walk through how.

If the structure is absent: your first conversation is not with the manager. It is with the people in the organisation who have the authority and responsibility to put that structure in place. Going to them with a specific, documented impediment – rather than a general complaint about management culture – is the intervention most likely to produce lasting change.

The team needs the Scrum Master to be effective over time. That requires protecting your own standing, not spending it in conversations that the organisation has not yet set up to succeed.

Run the checksum on your situation before the conversation:

1. Can you name three specific, observable behaviours by this manager that have produced measurable negative team outcomes – with dates and examples?
2. Does anyone above this manager in the organisation know this conversation is necessary – and do they support it?
3. If this conversation produces no change, what is the next step – and who is responsible for taking it?

If you cannot answer all three questions clearly, you are not ready for the conversation. You are ready for the structural work that needs to happen first.

---

Part 2 of this series – “How to Actually Have the Conversation” – will cover preparation, framing, and what to do when it goes wrong. [Coming next week.]

---

Glossary Terms Used in This Article

• Scrum Master – The Scrum accountability responsible for establishing Scrum and serving the team and organisation.
• Scrum Guide – The official reference document defining Scrum, maintained by its co-creators Ken Schwaber and Jeff Sutherland.
• Sprint – A fixed time-box of 1–4 weeks in which a Scrum team delivers a potentially releasable increment.
• Sprint Planning – A Scrum event in which the team plans the work to be performed in the upcoming Sprint.
• Psychological Safety – The shared belief that it is safe to take interpersonal risks within a team.
• Impediment – Anything that prevents a Scrum team from progressing as effectively as possible.
• Agile Transformation – The process by which an organisation attempts to adopt Agile values and practices at scale.