You Became the Team's Pattern: What Enactment Tells You About Stuck Agile Teams

The thing no one says out loud

The moment is always small. A question answered before the team can attempt it. A silence filled before it has a chance to become thought.

A Scrum Master — eighteen months into her engagement with a fintech product squad — is running a sprint review. The team is perpetually behind and perpetually deferential. A developer is working through an explanation of a technical trade-off. He is finding his words slowly. The SM adds detail to his explanation. He continues. She adds more. The third time, he stops mid-sentence and glances at her. She finishes the explanation herself. He nods. The stakeholder's follow-up question is addressed to the SM.

Walking out, she tells herself she was being helpful. The developer was struggling. The stakeholder needed an answer. She had the words. It seemed like the obvious move.

What she has not noticed is that this was the seventh time in eight sessions that she supplied an answer the team was working toward. She has not noticed because it never felt like a decision. It felt like helping. The difference, it turns out, matters enormously.

Coaching culture does not prepare practitioners for this moment. It prepares them to watch teams — to hold questions, to resist rescue, to stay in the observational position. What it does not prepare them for is the discovery that the pull toward rescue may not be theirs. The SM did not decide to rescue the developer. Something in the system arranged for her to arrive at that moment with exactly the words needed, and she produced them.

The team got what it always gets: someone to speak when the silence becomes uncomfortable.

This is not a story about a coaching mistake. It is a story about data. The most precise diagnostic information available to that SM was sitting in what she had just done — and she had been treating it as noise for eight sessions.

What enactment actually is

Reflective practice teaches coaches to track their emotional responses to teams — frustration, boredom, anxiety, over-investment — as potentially useful field data rather than personal noise. This is a useful discipline. The coach who notices they are bored in a team that describes itself as highly engaged has learned something about what the team is not saying.

But the principle stops there in most training. The emotional reaction is named; the behavioural one is not. What is harder to teach — and harder to face — is that the reaction does not stay in the realm of feeling. It extends into action. The coach who notices they are frustrated is still, at that point, observing the field from some distance. The coach who notices they have started doing something they did not decide to do has moved inside it.

In relational practice, the coach is never simply an observer of the system they are working with. They enter the field. The field enters them. Co-creative Transactional Analysis names this explicitly through the concept of the participant-observer (Van Beekum, 2012): the coach is not a technician operating from outside the system. They are inside it. The team's dynamics act on the coach as much as the coach's interventions act on the team.

When the coach notices that their reaction — the compulsion to speak, the unusual quiet, the exhaustion after a session — carries information about the team rather than only about themselves, they are working with what relational practitioners call countertransference as field data. The feeling is not interference. It is report.

Enactment is what happens when that movement crosses from feeling into behaviour. The coach stops choosing what they do and starts performing the team's script. Van Beekum (2012) describes the coach as a "signifier of transformation": a container whose disruptions — moments when the coach does something unexpected, unplanned, or out of role — carry information about what the team needs to transform. The plain translation: the coach who starts acting like the team is not losing their footing. They are, briefly, the team's most honest report on itself.

Enactment is not a coaching failure. It is a sign that the coach got close enough to be recruited.

The obvious objection is worth taking seriously. Perhaps the SM really was being helpful. Perhaps the developer really was struggling and the intervention was appropriate. A single act of filling a silence is a coaching judgment call. What marks enactment is not the act but the pattern: the compulsion, the frequency, and — most precisely — the team's response. When the team stops attempting the thing the coach keeps supplying, the coach has crossed from being helpful to being necessary. The team no longer needs to solve the problem. It has arranged for the problem to be managed on its behalf.

Enactment is not resolved by trying harder to stay neutral. Neutrality is not available — the coach is already inside the system. The task is not distance. It is recognition.

Five enactments agile coaches actually experience

These are not personality types. They are field positions the team recruits coaches into. Any coach can be pulled into any of them, depending on the team's structure and what the moment makes available. The pattern belongs to the system. The coach is the one who makes it visible.

The exit from enactment is not willpower. It is not a stronger commitment to neutrality or a more disciplined reflective practice. It is a sequence of three moves, each of which requires something different from the coach — and none of which can be done in the session in which the enactment is happening.

Van Beekum (2015) calls this the politics of revelation rather than salvation. The coach who silently fixes stays in salvation mode — they manage the system's pain on behalf of the system. The coach who names the pattern, however imperfectly, creates the conditions for something different: the team becomes able to see what it has been doing, which is the first requirement for doing something else.

None of these moves is a technique. Each is a discipline — which means the skill being developed is attention and tolerance for uncertainty, not a more sophisticated protocol. A coach who can hold a compulsion without acting on it for thirty seconds has more to offer the team than one who can articulate a perfect return.

The discipline that makes this possible

Most of what is described in the three moves cannot be done alone. The coach inside an enactment does not have a clean view of their own behaviour. That is the nature of recruitment — it happens below the threshold of real-time awareness. What the coach needs is a container outside the system.

Supervision provides that container. Not peer coaching — peer coaching can reproduce the enactment, with two coaches caught in the same dynamic, each validating the other's reading of it. Supervision with someone who is not inside the client system provides the one thing the coach cannot generate alone: a partial view from outside.

A supervision group of four Agile coaches is working a case. The presenting coach describes the Urgency Absorber pattern — working longer hours than the team, preparing materials the team never asked for, carrying what the team refuses to carry. Twenty minutes into the discussion, the group is in a low-level argument about whose case should take priority. Whose situation is most urgent. Who most needs the group's time. The supervisor notices the group has started replicating the same urgency dynamic the case is describing. She names it. The group falls quiet. One coach says: That is exactly what happens in my team every sprint planning.

This is parallel process: the dynamic in the original system reappears in the container built to examine it. It is not a coincidence. It is information. The team's pattern has travelled through the coach and into the supervision room. Supervision that can notice this replication and name it gives the coach something reflection alone cannot provide.

The research landscape for Agile coaching confirms that supervision is widely advocated and rarely practiced. Most coaches working with the level of relational complexity described in this article have no structural container for it. The patterns go unnamed. They become habits. The Urgency Absorber becomes the coach's professional identity rather than a diagnostic they can examine and set down.

Supervision is not therapy. It is a professional practice structure — the same structure that clinical and organisational practitioners in adjacent fields treat as non-negotiable. A coach who works with teams over extended engagements without it is working without the professional infrastructure the work requires.

What the shift looks like

Enactment worked with successfully looks like the team doing something they were previously waiting for the coach to do. The coach will feel slightly redundant. That is the correct signal. It means the role the team had assigned to the coach is no longer filled, and the team is learning to fill it themselves.

Three markers indicate the work is landing:

The goal is not to be a coach who is never recruited. Recruitment is a feature of close engagement, not a failure of it. The goal is to be a coach who notices when they have been recruited — and who has the structure, the vocabulary, and the tolerance to work with what they find. Enactment is not resolved. It is worked with. The difference is everything.

The transmission

The SM who kept finishing the developer's sentences was not making a coaching error. She was receiving a transmission. The team had found, over eighteen months, the most efficient way to stay safe: produce someone who would speak for them. She fit the role precisely. She was helpful, present, articulate, and invested. The team had done its work well.

The question this article is asking is whether the coach can turn that transmission into a conversation. Whether the information carried in the enactment — who the team needs, what it cannot yet do for itself, what kind of absence it is protecting — can be brought back into the room as something the team examines rather than repeats.

The next article in this series looks at the current beneath the team — the undertow that predates the current sprint and recruits coaches before they have had a chance to orient. If enactment is the coach's experience of the system from inside it, the undertow is the system's history pressing into the present. That article is The Current Beneath the Sprint.

You will be recruited. The question is whether you notice before the team does.