The Three Leaders in the Room: Why Coaching the Wrong Person Changes Nothing
Every team has three distinct leadership structures operating simultaneously. The Scrum Master is accountable on paper. Someone else makes the real decisions under pressure. And a third person — often invisible — shapes what the team permits itself to do. Coaching only one of the three is the most common structural error in Agile team coaching.
The coach who didn't know who she was talking to
Six months. A talented Scrum Master. Retrospectives improving. Sprint planning more collaborative. The coaching work is going well — the manager says so, the metrics suggest it, the SM's growing confidence confirms it.
Then comes a sprint review at a fintech delivery team. The CTO asks, casually, why the team changed their deployment approach mid-quarter. The SM gives a careful, technically accurate, well-structured explanation. No one reacts. A senior developer — J, who has been quiet for most of the review — adds four words: "We were getting bottlenecked." The CTO nods once. The discussion moves forward.
In the cab back to the office, the coach replays six months of sessions. Every decision that actually changed something — J had weighed in on it. Every time the team had been asked to move in a new direction and hadn't — J had said nothing. Every retro action item that died in the sprint — J had neither endorsed nor opposed it.
The coach had been working with the SM for six months. J had been running the team.
This is not a story about a bad coaching engagement. The SM grew considerably. The facilitation improved. What the coach missed was structural: the team had three distinct sources of leadership operating simultaneously, and the coaching had engaged with only one of them.
What Berne saw that the org chart doesn't show
Every team has someone who is answerable to the organisation for what happens. They're on the reporting line. They write the escalation email. They're named in the retrospective when things go wrong. This is the person the org chart is designed to find. But this person is not necessarily the person who decided what happened.
And every team has someone — sometimes the same person, usually not — who the group turns to when the room goes quiet and a decision needs to be made under real pressure. Not the most senior person. Not the most technically skilled. The person the team has collectively assigned the role of actual anchor. Their presence changes what is possible in the room. Their absence creates a different kind of meeting.
In 1963, Eric Berne described three distinct types of leadership operating in any group or organisation. They can be embodied by one person, by two, or by three different people simultaneously — and they are almost never all visible on the org chart.
The responsible leader is the front person: accountable to higher authority, visible in the structure, answerable if things go wrong. In Agile teams, this is almost always the Scrum Master or team lead. They hold the formal mandate.
The effective leader is the person who makes the actual decisions. Whose proposals get followed under stress. Whose questions get answered before anyone else's. Who determines direction in practice, regardless of title. Berne's diagnostic was sharp: "If the leader plays the role of king but someone else plays the ace, the first is not truly the leader but a sub-leader or delegate." The practical test for effective leadership is simple — whose decisions, under pressure, remain unreversed by anyone present?
The psychological leader lives in the private structure of the team — in the members' mental pictures of the group and their place in it. This person may hold no formal role. They may rarely speak. What they do is set the group's permission level: what can be said here, what risks can be taken, what kind of difficulty the group can tolerate before it closes down. They shape the team's collective psychology whether or not anyone, including themselves, is aware of it.
Berne was clear that all three types are always present — in every group, in every organisation. The question is never whether they exist, but whether they are held by one person or distributed across several, and whether the people responsible for coaching the team have found them all.
When a coach's entire engagement is with the responsible leader while the effective leader makes all substantive decisions and the psychological leader shapes what the team permits itself to do, the coaching work produces real development in one person and no traction in the system. Which is the most common outcome in Agile team coaching. It is rarely noticed for what it is.
Reading the room for all three
Each leadership type has specific observable signs. The coach who knows what to look for can begin to identify all three within the first two or three sessions — not with certainty, but with enough hypothesis to adjust their approach.
The responsible leader — easier to find than to read accurately
The responsible leader is usually the person who opened the calendar invite. They're running the agenda. They speak first and last. They are also the person most likely to perform confidence they don't have — to protect the team from uncomfortable truths, to smooth over tensions before the coach can see them, and to carry the organisation's anxiety on behalf of the group. Their visible authority is real. But it comes with a specific kind of pressure that often makes them the least candid person in the room.
A coach who reads the responsible leader as the most authoritative person in the team is reading the public structure accurately and the private structure not at all. The responsible leader's mandate comes from above. Their actual influence within the team may be partial, conditional, or increasingly nominal as the team matures.
The effective leader — revealed by stress and silence
The effective leader doesn't show up in a well-facilitated team discussion where all voices are equally invited and the format ensures participation. They show up when something is uncertain, when a decision needs to be made under pressure, when the structured process breaks down and the team has to rely on its private structure rather than the public one.
Two observable signs: first, whose questions get answered before anyone else's? In most teams, some people's contributions change the direction of a conversation and others' don't — not because of content quality but because of the group's implicit hierarchy. Second, when a decision is made that everyone accepts without apparent coercion, who spoke last before the room moved on?
One diagnostic approach that works reliably across team types: ask the same open question to different people in the same meeting and watch how the room responds. The effective leader's answer will shift the direction of the conversation. Others' answers will be acknowledged and set aside. This distinction is almost always visible if you're watching the room rather than the content.
The psychological leader — the most consequential and the least visible
The psychological leader's influence operates through the group's private structure. This is not about what they say or what they decide. It is about the group's collective permission field — the unspoken answer to the question what is it safe to do and be here? When the psychological leader is anxious, the team becomes cautious. When they are engaged, the team opens up. When they go quiet in a retrospective, the retrospective empties out, not because anyone is being deliberately withholding but because something in the permission field has shifted.
Their influence is therefore felt rather than seen. Team members will not be able to tell you they are deferring to this person. They will tell you the decision "just made sense" or that "everyone agreed." Berne observed that the psychological leader can often be identified only through methods that attend to the group's emotional and relational field rather than its observable content — which in practice means: notice whose state the room tracks without knowing it does.
The effective leader is visible if you watch the right moments. The psychological leader requires a different quality of attention — less focused on what is being said, more attuned to what changes in the room when different people speak. There is a person whose mood the room adjusts to. That person is not necessarily the most senior, the most vocal, or the most technically skilled. They are the person the team has collectively organised its permission field around.
The most destabilising configuration — and the most common in mature Agile teams — is a responsible leader who believes they are also the effective leader (because they were, before the team's dynamics shifted), and a psychological leader who has no idea they hold the role. Neither person is acting in bad faith. Both are running the team's private structure in ways that the public structure makes invisible.
Five moves for coaching at the right level
Identifying all three leaders changes what the coach does next. The interventions appropriate for each type are different. A single coaching approach applied exclusively to the responsible leader cannot reach the effective or psychological leader — not because the responsible leader is unimportant, but because the system runs on all three simultaneously.
Map before you contract
The first three sessions with a new team should be diagnostic before they are prescriptive. Before agreeing to work with the SM on facilitation skills, the coach needs to know whether the SM is also the effective leader or whether that role belongs elsewhere. Coaching the responsible leader on process when the effective leader is making all substantive decisions is not wrong — it is incomplete in a way that will produce incomplete results. The diagnostic move is simple: observe who the team defers to under uncertainty. Introduce a mild ambiguity — a question with no obvious answer — and watch the room solve it. Who speaks? Who is looked at? Whose answer ends the conversation?
Contract separately with the effective leader
If the effective leader is not the responsible leader, they need their own coaching relationship. Not the same conversations passed through the SM as a relay. Not a briefing. A direct engagement. Most effective leaders in Agile teams are never directly approached by coaches. They are approached by the SM with coaching-influenced proposals. The effective leader considers the proposal, weighs it against their own read of the situation, and either lets it land or allows it to quietly disappear. This is not resistance. It is the effective leader doing their job in the absence of a direct coaching relationship.
The contracting question is not "Will you support the coaching work?" — that is a management question that positions the coaching as something the effective leader supervises rather than participates in. The relational question is: "What is it that the team most needs to be able to do that it can't do now, from where you sit?" This question treats the effective leader as a participant in the coaching work rather than a gatekeeper for it.
Work with the psychological leader's state, not their opinion
The psychological leader's influence runs through the group's permission field. Coaching them on their stated opinions — what they think should change, what their feedback is, what their assessment of the sprint was — will not shift the underlying dynamic. What the coach can work with is their state: their level of engagement in the room, their relationship to uncertainty, the moments when they go quiet and what the team does when they do.
In sessions where the psychological leader seems withdrawn or flat, the coach's instinct is often to redirect attention elsewhere — to keep the energy in the room up, to ensure participation. The more effective move is to name what you notice without forcing it: "Something feels different in the room today. Is there something present that we haven't quite got to yet?" This is not therapy. It is an invitation to the group to bring its private structure into the working space rather than running it beneath the surface of the meeting.
Don't triangulate — connect directly
When the coach learns that the effective leader has reservations about the coaching work, the instinct is to go through the SM: "Can you talk to J about this?" This recreates the triangulation pattern the coaching is often trying to disrupt elsewhere in the system. The coach who has identified the effective leader and knows they have reservations must contact them directly. The relational work happens between coach and effective leader, not through an intermediary. A conversation routed through the SM is a message. A direct conversation is a relationship.
Name the structure, eventually
The team's three-leader structure is almost always invisible to the team itself. The responsible leader knows they are accountable. They may or may not know that the effective leadership has shifted to someone else. The psychological leader almost certainly doesn't know they hold the role. The coach who has mapped this structure has information the team doesn't have about its own operation.
At the right moment — which is rarely in the first six months, and which requires genuine trust to have been established across all three types — naming this structure explicitly with the team is one of the most unlocking moves available. Not to assign blame. Not to redistribute formal authority. But because a team that can see its own leadership structure can begin to work with it deliberately rather than be run by it unconsciously. The team that knows J is its effective leader can stop routing every real decision through a process designed for a team where the SM holds that role.
A product delivery team at a logistics company. The SM — eight months into the role, skilled, growing in confidence — had been told by her manager that the coaching work was going well. The coach asked her a direct question: "Who does the team actually follow when things get uncertain?"
She sat with it for a moment. Then: "Probably K."
K was a senior developer. No special title. No formal authority. Present in most meetings but rarely vocal. When K spoke in a retrospective, the conversation changed direction. When K was absent, decisions got deferred until the next session.
The SM and the coach spent the next session not designing a better retrospective format but mapping the team's actual decision-making pattern. It was the first time the SM had looked at the team as a system rather than as a facilitation challenge. Three months later, she described it as the moment the coaching work "actually started."
The map is not the territory. But a coach without a map is working in the dark.
The psychological leader as the hardest case
The psychological leader is the most consequential of the three types and the most resistant to direct coaching. They didn't ask for the role. They often don't know they hold it. The tools that work with responsible and effective leaders — direct conversation, explicit contracting, agreed development goals — frequently don't reach the psychological leader, because their influence operates beneath the level of the explicit.
Berne wrote that the psychological leader can be identified by "psychiatric methods" — a phrase that, translated into coaching practice, means attending to the group's emotional field rather than its stated positions. The effective leader is visible if you watch the right moments. The psychological leader requires a different quality of attention: not what is being decided, but what changes in the room when different people speak. Not the content of the conversation, but the permission field it is operating within.
A further complication: the psychological leader role is not permanently assigned. As a team's dynamics shift — as people leave, as crises occur, as trust patterns change — the person carrying the psychological leadership function can shift too. The coach who identified the psychological leader six months ago may be working with outdated information. The role may have moved.
A coach working with a software consultancy team, six months in. Retrospectives consistently produced action items that were sensible on paper and quietly ignored in practice. The coach had been working with this as a commitment problem — clearer owners, tighter due dates, more explicit accountability.
In one session, a usually quiet data scientist — M — said, midway through the retrospective: "I don't think we actually believe we have time to do any of this."
The room went still. Not the managed stillness of a well-run ceremony. Something heavier. Then people began saying things they hadn't said before — about workload, about what they had been protecting each other from naming, about what they had quietly stopped believing was possible. The retrospective ran fifty minutes over. Four of the six action items from that session were completed before the sprint ended. It was the highest completion rate in four months.
M had not been identified as a leader of any kind. But when they spoke from the team's actual private structure, the room moved. That is the psychological leader: the person whose statement of the private truth changes what the group permits itself to acknowledge.
The coach's response was not to intervene. It was to hold the space and let what was in the room stay in the room long enough to become usable.
The coaching moves appropriate for the psychological leader are different in kind from those used with the other two types. Direct approaches — asking them to lead, inviting them to take on more visible authority, coaching them on their stated positions — typically produce the opposite of what is intended. The role runs beneath volition. Coaching at the level of explicit choice doesn't reach it.
What does work: protecting the conditions that allow the psychological leader to speak. Not filling their silences. Directing questions toward the private structure rather than the surface content — "What's the thing that's present in the room but hasn't quite been said?" — in ways that give the psychological leader permission to name it without requiring them to. Noticing when they are unusually withdrawn and naming it to the group as a field observation rather than a personal question.
And staying curious about who the psychological leader actually is at any given point in the engagement. The person who carried the role in month two may not be carrying it in month nine. The team's private structure is not static. Neither are the people who hold its most important functions.
Why reading leadership is a relational act
Reading the three leadership types is not a management consulting skill imported into Agile coaching. It is not a political analysis of who holds organisational power. It is the prerequisite for any genuine relational work with a team — because you cannot build a relationship with a system whose actual structure you haven't seen.
Genuine coaching contact — the kind that produces change rather than only improvement — requires the coach to meet the system as it is, not as the org chart suggests it should be. The responsible leader's formal authority is real but partial. The effective leader's decision-making capacity is real and often unrecognised by the organisation. The psychological leader's influence on the group's permission field is real and almost always invisible until the coach has developed the capacity to look for it.
A coach who engages only with the responsible leader is having a real relationship with a partial picture. That partial picture produces partial interventions — skilled, often well-received, genuinely useful in isolation. But insufficient to the depth of what the team needs, because the depth of what the team needs includes the structures the coach isn't yet seeing.
"The private structure determines the outcome."
Eric Berne, The Structure and Dynamics of Organizations and Groups (1963)
Reading the leadership structure is also, in itself, a relational gesture. The coach who maps all three types is demonstrating a quality of attention to the team — a willingness to see the system as it actually operates rather than as the role titles suggest. Teams notice this, even when it is never made explicit. The coach who is clearly attending to the real dynamics of the room earns a different kind of trust than the coach who is attending to the formal structure.
This series continues with the second invisible layer the coach must read: the unwritten rulebook that every team carries — what Berne called the group canon — which determines which of the coach's interventions will be allowed to land and which will be quietly discarded, regardless of their quality, because the team's culture does not yet have permission to receive them.
The org chart shows you who is accountable. It tells you almost nothing about who the team actually follows, or why.
Continue Exploring
Go deeper into the work
The Book
The Art of Creating Self-Organizing Teams
The full framework behind this article — contracting, team dynamics, and practical coaching tools for every stage of the journey.
Companion Toolkit
Resistance Radar & Resilience Scorecard
Practical tools for mapping resistance patterns and measuring whether interventions increased capacity — not just compliance.
TA for Agile
Co-creative TA in Agile Contexts
Ego states, psychological contracts, group imago, and the relational concepts that underpin this article — applied to real teams.