Team Coaching
The people are fine. The system isn’t.
Coaching for leadership teams as a working system, with the whole team in the room and a parallel thread for the leader. Measured in how the work moves.
Why team building doesn’t work.
Talented people, a leader who cares, clear enough roles, and something that keeps not working: decisions stall, conversations cycle without resolution, a professional distance grows between people who should be operating as a unit. None of that is a talent problem. The patterns live in the relationship system between the people, and changing them is different work.
Most team interventions assume that if you improve the individuals, the team improves. So you run the communication workshop, book the offsite, introduce a feedback framework. People find it valuable and leave with intentions. Two weeks later, the same patterns are back, because the patterns were never in the individuals. They live in the system: its history, its ways of managing tension, its unwritten role assignments. A team where one person always absorbs the anxiety doesn’t need that person to change. It needs the system to change.
The patterns were never in the individuals to begin with. They’re in the system.
The reframe this practice runs on
Coaching the system.
This practice runs on Organization and Relationship Systems Coaching, the discipline behind the ORSCC credential. Engagements are led by Bryan, who holds it. Four working principles shape every engagement.
The client is the system.
In systems coaching the team itself is the client: the relationships between the people rather than the people one at a time. That changes what we pay attention to, what we name, and what we leave alone.
Roles belong to the system.
Every team generates roles: the voice of caution, the energizer, the one who holds the tension so no one else has to. These are functions the system needs filled, and someone will fill them. We help the team work with its roles instead of against the people carrying them.
Conflict carries information.
When a team keeps having the same argument, or keeps avoiding the argument it needs, that’s a signal about what the system protects and what it hasn’t found a way to say. Our job is to help the team have that conversation, at a pace it can survive.
The team has a voice of its own.
A working system knows things no single member could articulate alone. Part of the work is helping the team hear itself: what the quieter voices are carrying, what the current patterns are preventing. The coaching creates the conditions for that intelligence to surface.
What an engagement looks like.
Every engagement starts with observation. Before we design anything, we need to see how this particular system operates, where it functions well, and where the real constraint lives.
Observe and diagnose. Enter without an agenda.
Interviews with team members individually and together, observation of the team in its own meetings, and attention to the dynamics being carefully avoided. This is where we find the pattern underneath the presenting problem.
Design the arc. A sequence built for this system.
From the diagnosis, a coaching sequence specific to this team: regular whole-team sessions, a parallel thread with the leader, and defined moments to practice new patterns inside real work.
Work live dynamics. In the room, in the moment.
We work with what’s in the room: what the team is doing in the moment rather than what it reports about itself. When a pattern surfaces, we name it and work it in real time. Teams find this the most uncomfortable part of the engagement, and the most useful.
Sustain and close. Capacity that holds without us.
Toward the close, the work shifts to the team’s ability to notice and work with its own system. The final phase is an explicit handoff: a clearer view of its own patterns and a working language for navigating them.
The leader is part of the system.
Often the part with the most influence over its patterns. Every engagement includes a parallel coaching thread for the team leader: individual sessions on how their presence and habits shape the system around them, so the leader models what the team is being asked to practice.
A team cannot develop faster than its leader is willing to.
Why the leader thread is non-negotiable
The shape of an engagement.
Depending on what the diagnosis reveals. The minimum productive arc for systems-level change runs longer than most teams expect, and we say so at the start.
Typically monthly, with more frequency in the early phase, plus individual touchpoints and the parallel leader thread.
Specific observations to make and small practices to run inside the team’s own working rhythm: patterns are easier to notice once you know what to look for.
Who this is for.
Teams in the middle of real change: a leader who just inherited the room, a restructure that redrew everyone’s lanes, a merger that put two cultures at one table. High-performing teams that have hit a ceiling they can’t diagnose from inside. Teams where friction is getting in the way of the work, or where the surface is so smooth the real conversation has stopped. The one prerequisite is willingness to look at how the team operates, including the leader. If what’s wanted is a facilitator to run a few sessions and declare success, we’re the wrong firm.
A new leader inheriting an established team.
A restructure or post-merger integration.
A capable team at a ceiling it can’t name from inside.
Friction that’s getting in the way of the work.
A surface so smooth the real conversation has stopped.
Show us the team. We’ll tell you what we see.
Most engagements start with a diagnostic conversation. We’ll listen for the system patterns underneath the presenting problem and tell you whether team coaching is the right intervention, or whether something else would move faster. The call is with Bryan.