Agile coaching is sometimes described as "helping people see reality through Agile and Lean perspectives." That is a reasonable starting point, but it understates the challenge. Helping people change their paradigms, habits, and roles requires an understanding of human nature that no framework guide contains.

Most Agile coaches are well-versed in frameworks. The ones who produce durable transformation are also well-versed in psychodynamics. These are different skills, and developing only one of them leaves significant capability on the table.

The coaching stance

At the core of effective agile coaching is a systemic coaching stance: genuine curiosity, non-judgment, and the discipline to help people explore their own situation rather than presenting solutions. A coach in this mode steers and coordinates — pursuing jointly defined objectives — while simultaneously providing the kind of neutrality that allows the coachee to find answers they own rather than answers they were handed.

This is harder than it sounds. The temptation to demonstrate expertise — to explain, advise, and direct — is strong, especially for people who have spent years developing deep knowledge of frameworks and transformation approaches. The discipline of holding back, of asking rather than telling, of treating your observations as hypotheses rather than diagnoses, is something that has to be actively practised.

The four additional stances

Pure coaching is the default — but an effective Agile coach also needs to move fluidly between four other stances depending on what the situation calls for.

Teaching is appropriate when the coachee lacks knowledge. You explain a concept, verify their understanding, and then return to coaching mode: how will they apply this in their context? Teaching without returning to coaching mode tends to produce dependence rather than capability.

Mentoring serves a coachee with limited experience. You share your own experiences and anecdotes, demonstrate an approach, and then invite them to connect it to their situation. The goal is their gaining personal experience, not internalising your story.

Advising is appropriate when your expertise is genuinely relevant. The key discipline here is offering advice as options with trade-offs rather than as directives — because you do not fully know the coachee's context, however much you know about the domain. "In my experience, these two approaches tend to produce different outcomes for these reasons" is advice. "You should do X" is instruction, which undermines ownership.

Facilitating is the fourth stance — creating the conditions for a team or group to reach shared understanding or make decisions. The facilitator provides structure, ensures everyone's voice contributes, and maintains the kind of productive neutrality that prevents the most vocal participant from dominating.

Why understanding human dynamics matters more than most coaches realise

Ralph Stacey, the organisational theorist, described organisational dynamics as the consequence of the interplay of personal intentions among members — not of the plans and strategies devised by managers or coaches. This is worth sitting with. The behaviour you observe in an organisation is not primarily caused by its processes. It is caused by what individuals want, fear, believe, and are trying to protect.

David Rock's SCARF model identifies five key dimensions that activate either a threat or reward response in people: Status, Certainty, Autonomy, Relatedness, and Fairness. Of these, Status deserves particular attention for coaches, because it is the one most frequently triggered by the coaching relationship itself. Asking someone to examine their practice, acknowledge what they do not know, or change how they work all have the potential to threaten status. The way you deliver the coaching determines whether people experience it as a threat to be resisted or a resource to be drawn on.

Applying humble inquiry — the recognition that despite your experience you do not fully understand the coachee's context, and that their sense of status matters — is what turns potentially resistant encounters into collaborative ones. It gives you a partner rather than an opponent.

The balance that matters

An effective Agile coach must know the frameworks well enough to teach them, mentor practitioners through them, and advise on their application. They must also understand human nature well enough to navigate the dynamics that determine whether any of that knowledge actually takes root in the organisation.

Neither half of this is optional. Our ICP-ACC programme develops both, which is why we designed it the way we did.