Team coaching isn’t training, and it isn’t team building — and the difference shows up the following week
Team training transfers specific skills to team members on the assumption that the gap is one of knowledge. Team building creates shared experiences that improve surface-level communication and trust — useful, but it doesn’t address the deeper dynamic. Team coaching, by contrast, approaches the team as a living entity with its own patterns, roles, and hidden drivers; it doesn’t look at individuals’ skills but at how the whole system functions. The difference a leader feels directly: team building ends, and the old dynamics return within a week; team coaching changes the patterns because it works at the level of the system, not the surface.
Confusing the three is common in organizations for three reasons: their superficial similarity in format — they’re all “group sessions” from the point of view of whoever prepares the budget — sometimes-comparable pricing, and the absence of an objective standard that helps HR staff distinguish between the three before contracting. The result is that many teams get matched with the wrong tool, so their problem recurs every few months under the cover of “new training,” while the team itself grows resistant to any further intervention because it links every new program to the last one’s failure.
The voices you don’t hear in your meetings
The Deep Democracy model rests on the principle that a team’s marginalized voices — the silence, the unnamed weight, the objection that gets swallowed — carry more important information than the voices that speak loudest. In a Saudi team that spans multiple nationalities, levels, and generations, this principle runs into a real obstacle: social and organizational hierarchy silences lower-ranked expatriate nationalities, lower job levels, and the younger generation — and these are often the ones holding the most accurate diagnosis of what’s actually happening. Applying this principle doesn’t mean forcing the silent to speak; that intervention makes things worse, not better. It means designing an environment where unheard voices can safely emerge, through short individual interviews before the group session and questions directed at the team rather than at individuals. Gathering patterns, not names, from these interviews, then presenting them in the session as “what I heard in my conversations,” brings the silent voices in without exposing whoever said them.
Hidden roles and ghosts no one sees — but that drive your team
Inside every team there are informal roles: someone who balances things out, someone who redirects anger, someone who carries the whole team’s anxiety without ever announcing it, someone who keeps hope alive, someone who keeps raising what everyone else wants to avoid. These roles genuinely serve the team, and surfacing them in a session allows them to be discussed as a system, not as individuals. Proper disclosure happens when the roles are presented in the language of the system, not by pointing to a specific person: “It seems this team always needs a voice that keeps caution present — who’s carrying that role?” Naming the role without naming the person is the difference between disclosure and exposure.
Beyond individual roles, every team carries an institutional history that keeps shaping the present without anyone being consciously aware of it. A “ghost role” is a role that still shapes the team’s dynamic without its original holder being present — the manager who left three years ago and whom the team still acts as though is in the room, or the hard decision made a decade ago that still shapes reactions today. A “time spirit” is broader still: the spirit of the team’s founding, or the spirit of a crisis it went through in a particular year, continuing to drive present behavior without anyone naming it. Dealing with these ghosts doesn’t mean invoking them dramatically — it means naming them calmly: “I notice this team always returns to a particular style in difficult moments — when did this style begin?”
The gap between what your team wishes for and how it actually behaves
Every team carries a “higher dream” — the picture it wishes for itself in a moment of openness — and a “lower dream,” which is how it actually behaves on its hard days. The gap between the two is exactly the working space of team coaching. Two simple questions reveal it: “What does this team look like on its best days?” for the higher dream, and “What usually happens when the team is under pressure?” for the lower dream. The value of these two questions is that they show the gap in a picture the team sees for itself, not one imposed by someone else — and that produces a shared acknowledgment of the problem before work on solving it even begins.
Fourteen markers of team health — and two of them are particularly contested here
The Team Diagnostic Assessment™ framework classifies team health across fourteen markers: seven under “positivity” — trust, respect, optimism, belonging, getting things done, shared values, fun — and seven under “productivity” — embracing differences, sustained dialogue, shared responsibility, constructive conflict management, role clarity, self-management, continuous learning. A healthy team isn’t marked by the positivity indicators alone, but by their balance with productivity. The “constructive conflict management” marker is the most contested in many environments that regard disagreement as a problem rather than a sign of health, and “team self-management” often conflicts with cultures built around centralized decision-making.
When you know sessions have stopped producing transformation
Three practical signals are worth pausing on: when the team’s leader shifts from steward of the process to an obstacle to it; when the conflict inside the team stems from an organizational decision that hasn’t yet been announced; and when the session becomes a refuge for members to talk without any commitment to actual change.
Four steps to start this week
Before your next session, ask each member individually: “Describe the team at its best moment with you.” Gather the shared themes, not the names. Notice who consistently stays silent in your meetings. Rate your team honestly against the fourteen markers, and name its two weakest ones plainly. If the same pattern keeps recurring despite repeated individual training, the problem is at the level of the system, not the individuals.
After more than 1,500 hours of executive and team coaching with leadership teams in Riyadh, and a career spanning 16 years in institutional leadership, the clearest pattern is that teams who ask for an early diagnosis save themselves months of recurring friction.
Request a scoping call to diagnose your team before any intervention.
Sources
CRR Global: the Organization and Relationship Systems Coaching (ORSC) framework and the Team Diagnostic Assessment™ (TDA) tool. — Mindell, A.: Process Work theory and the origins of the Deep Democracy model. — Lewis, M.: development of Deep Democracy applications in organizational and community contexts. — International Coaching Federation (ICF): ethical practice standards and contracting boundaries in team coaching.