The people are fine.
The system isn’t.
Talented people. A leader who cares. Clear enough roles. And something that keeps not working: decisions that stall, conversations that cycle without resolution, a professional distance between people who should be operating as a unit. This isn’t a talent problem and it isn’t a communication problem. It’s a relationship system problem. And it requires a different kind of work.
Why team building doesn’t work.
Most team interventions are designed around a faulty assumption: that if you improve the individuals on the team, the team will improve. So you run a communication workshop. You book an offsite. You introduce a framework for giving feedback. People find it valuable. They leave with intentions. Two weeks later, the same patterns are back. The patterns were never in the individuals to begin with. They’re in the system.
A team is a relationship system. It has its own dynamics, its own history, its own ways of managing tension and distributing roles. Those patterns operate below the level of individual behavior, which is why individual-level interventions don’t touch them. A team where one person always absorbs the anxiety doesn’t need that person to change. It needs the system to change. That’s a different problem. It requires different work.
The patterns were never in the individuals to begin with. They’re in the system. The reframe this practice runs on
Coaching the system, not the individuals.
Bryan holds the ORSCC credential (Organization and Relationship Systems Coaching Certified), one of the most rigorous designations in the field for working with teams as systems. What that means in practice isn’t a methodology. It’s a fundamentally different orientation to what a team actually is and where the work actually lives.
The system is the client. Not the individuals in it.
In a conventional coaching or facilitation engagement, the coach works with each person and hopes the team benefits. In systems coaching, the team itself is the client: the relationship between the people, not the people themselves.
That distinction changes everything: what we pay attention to, what we name, what we work with, and what we leave alone.
Roles belong to the system, not the person.
Every team generates roles: the voice of caution, the energizer, the one who holds the tension so no one else has to. These aren’t personality traits. They’re functions the system needs fulfilled, and they will be played by someone regardless of who steps into them first.
Working at the system level means understanding which roles the team is generating and why, and helping the team work with them rather than against the people carrying them.
Conflict carries information.
Most team interventions try to reduce conflict. Systems coaching works with what conflict is carrying. When a team keeps having the same argument, or keeps not having the argument it actually needs to have, that’s a signal about what the system values, what it’s protecting, and what it hasn’t yet found a way to say.
The most important conversation in a team is usually the one that isn’t happening. Our job is to help it happen safely.
The team has a voice beyond the sum of its members.
There’s an intelligence in a well-functioning relationship system that no individual member could produce alone. Part of the work is helping the team hear itself: what it already knows collectively but hasn’t articulated, what the quieter voices in the room are carrying that the louder ones are drowning out, what the system is trying to do that its current patterns are preventing.
That intelligence is already there. The coaching creates the conditions for it to surface.
What a team coaching engagement actually looks like.
Every engagement starts with observation. Not assumption. Before we design anything, we need to understand how this particular system is actually operating, where it’s functioning well, and where the real constraint lives.
Observe & Diagnose
Enter without an agenda.
Interviews with team members individually and as a group, observation of how the team actually operates in its own meetings and working sessions, and assessment of the dynamics that are visible, and the ones being carefully avoided. This is where we find the real pattern underneath the presenting problem.
Design the Coaching Arc
A sequence built for this system.
From the diagnosis, we build a coaching sequence specific to this team’s system. Not a generic team-health curriculum. The arc includes regular team coaching sessions, a parallel thread with the team leader, and defined moments for the team to practice new patterns in real work rather than constructed exercises.
Work Live Dynamics
In the room, in the moment.
Team coaching sessions are live working sessions, not workshops. We work with what’s actually in the room: what the team is doing in the moment, not what it’s reporting about itself. When a pattern surfaces in the session, we name it and work with it in real time. This is the part most teams find uncomfortable and most useful.
Sustain & Close
Capacity that holds without us in the room.
Toward the close of the engagement, the work shifts to sustainability: building the team’s capacity to notice and work with its own system without a coach in the room. The final phase includes an explicit handoff: the team should leave with a clearer view of its own patterns and a working language for navigating them without us.
The team leader isn’t a bystander.
The team leader is part of the system, often the part with the most influence over its patterns. In every team coaching engagement, the leader receives a parallel coaching thread: individual sessions focused on how their own patterns, behaviors, and presence shape the system around them. This isn’t about fixing the leader. It’s about helping the leader model what the team is being asked to practice.
A team cannot develop faster than its leader is willing to. Why this thread is non-negotiable
The shape of an engagement.
Four to nine months.
Depending on the team’s situation and what the diagnosis reveals. The minimum productive arc for real systems-level change is longer than most teams expect. We’re direct about that at the start.
Whole-team working sessions.
Typically monthly, with more frequency in the early phase, plus individual touchpoints and the parallel leader coaching thread. Sessions are working sessions with the whole team in the room, not training deliveries.
Structured attention between sessions.
Teams are given specific observations to make and small practices to try inside their own working rhythms. Not homework, but structured attention to patterns that are easier to notice once you know what to look for.
The teams we work with.
Leadership teams navigating significant change: a new leader, a restructure, a mandate that requires genuinely different ways of operating together. High-performing teams that have hit a ceiling they can’t diagnose from inside the system. Teams where the interpersonal friction is getting in the way of the work, or where the professional surface is so smooth that the real conversation has stopped happening entirely.
We work with teams that are willing to look honestly at how they operate, including the leader. That willingness is the only prerequisite. Everything else can be worked with.
We don’t take every engagement. If a team is looking for a facilitator to run a few sessions and declare success, we’re not the right fit. If it’s willing to do real work on its own system, we can help.
A new leader inheriting an established team.
A team navigating a restructure or post-merger integration.
A capable team that’s hit a ceiling it can’t name from inside.
Interpersonal friction that’s getting in the way of the work.
A surface so smooth the real conversation has stopped happening.
Show us the team.
We’ll tell you what we see.
Most engagements start with a diagnostic conversation. We’ll ask what’s actually happening underneath the presenting problem, listen for the system patterns, and tell you honestly whether team coaching is the right intervention — or whether something else would move faster.