If I move too quickly, I may relieve the very pressure the team needs to learn from.

I was recently coaching a leadership team in Brussels. They had said they wanted to talk about trust. Within minutes, they were discussing reporting lines, missed updates, and meeting cadence.

The conversation was intelligent. It was also moving away from the work.

My first task was not to interrupt. It was to notice the drift.

Later, I was told (not very subtly) that I had moved too slowly. That remark unsettled me, because it touched one of the hardest balances in team coaching: when to intervene, and when to wait.

I used to think team coaching was mostly about helping a group have a better conversation. I still believe that. But the longer I work with teams, the more I see that the real work often begins before I say anything. It begins in how I enter the room. How I manage my body, my urgency, my wish to help, and my assumptions about what should happen next.

A team is never having only one conversation. There is the conversation on the table, and there is the conversation underneath it. There is the stated agenda, and there is the real concern that may or may not be ready to surface. There are roles people have learned to play: the responsible one, the challenger, the peacemaker, the silent observer, the person everyone looks at before deciding whether it is safe to speak.

Early in my work, I felt pressure to do something with all of that. Ask the right question. Name the dynamic. Move the group forward. Make the session valuable.

Over time, I discovered that presence often begins with resisting that pressure.

In team coaching, my body is part of the work. If I lean too far in, I can become over-involved. I start carrying responsibility that belongs to the team. I want them to move faster, speak more honestly, become braver. But if I pull too far back, I become an observer instead of a presence. The room may feel watched, but not held.

The balance is delicate. I need enough distance to see the system, and enough care for the team to feel that I am with them.

Sometimes that means a small physical adjustment. Feet on the floor. Breath lower in the body. Shoulders softer. Sitting back just enough to widen my view. Not disengaging. Just becoming more available.

One of the most useful discoveries has been noticing what happens inside me during the work.

A team may trigger irritation in me. Or urgency. Or boredom. Or the desire to protect one person from another. Sometimes a thought appears: This is going nowhere. Or: They are avoiding the real issue. Or: I need to intervene now.

Earlier, I might have treated those reactions as noise. Now I try to treat them as information.

Something shows up. I notice it. I let it breathe. I do not need to use it immediately. I do not need to turn every sensation into a question. Sometimes the thought fades. Sometimes it connects to something happening in the room. Sometimes it tells me more about myself than about the team.

The coach’s inner world can be a useful instrument, but only if it is not driving the session unconsciously.

I also remind myself that things can wait. Silence can wait. Tension can wait. The point I want to make can wait. The question I am tempted to ask can wait.

This is not passivity. It is discipline.

Teams often need more time than the coach wants to give them. The first answer is rarely the whole answer. The first disagreement is rarely the real disagreement. The first silence is often not emptiness, but the beginning of contact with something less rehearsed.

If I move too quickly, I may relieve the very pressure the team needs to learn from.

That is one of the paradoxes of the work. The coach is there to support movement, but not every movement is progress. Sometimes the most useful move is a pause. Sometimes it is a timeout. Sometimes it is simply naming that the team has drifted.

“I notice we started with trust, and now we are discussing reporting lines. How are these connected?”

A question like that does not accuse the team. It brings the team back to itself.

This is where process matters. Not as a rigid structure, but as a way of protecting the client’s agenda. Teams are intelligent. They can produce a lot of words. They can move quickly into operational detail, familiar debates, or safe abstractions. The conversation may sound productive and still avoid the work they came to do.

So I have become more curious about direction.

Where are we now? What are we working on? Is this still serving the purpose we named? What changed in the room? Who entered the conversation, and who disappeared from it?

In those moments, I feel as if I am watching several screens at once.

I am watching the formal process: the goal, the time, the agreement, the shape of the session. But I am also watching the relational field: who speaks, who withdraws, who interrupts, who softens, who looks away, who seems to carry permission for others.

I am watching the energy in the room: when it becomes alive, when it flattens, when humor opens something, and when humor protects the team from going further.

I am also watching the practical reality: the room, the screens, the sound, the fatigue, the seating, the break that should have happened earlier. Logistics are not separate from the work. They influence what the team is able to access.

And I am watching myself. What am I feeling? What am I assuming? What am I wanting to happen?

That has changed how I understand the coach’s authority.

I do not believe the team coach is in the room because he knows what is right. Often I do not know. And when I think I know, I try to be careful. The team lives inside a context I only partially understand. What looks like avoidance may be caution. What looks like resistance may be wisdom. What looks like agreement may be fear.

The most powerful moments in team coaching are rarely the moments when I say something brilliant. They are the moments when the team begins to see itself. When someone says, “We do this all the time.” When a quieter voice enters and the room changes. When the group notices that it talks about trust while rewarding caution. When a leader realizes that silence in the room is not agreement.

In those moments, the coach does not need to become bigger. The team does.

After years of working with leaders and teams, I keep returning to this: team coaching is not only about helping people speak more honestly. It is about helping a team become more present to itself.

When that happens, the conversation changes. The team starts to notice what it was producing without awareness. It sees how it creates trust, distance, confusion, protection, or courage. It becomes less dependent on the coach and more responsible for the room it creates.

And when a team becomes more responsible for the room it creates, the work changes too. Meetings become less performative. Decisions become cleaner. Avoidance becomes harder to hide. People begin to say what they previously said in the hallway after the meeting. The team does not become perfect, but it becomes more able to notice itself before old patterns take over.

And perhaps that is the deeper purpose of the work. Not to make the coach indispensable but to help the team see enough, feel enough, and choose more consciously together.

‍