Applied Team Formation Diagnosis: A Case Walkthrough for Team Coaches

Picture a leadership team you are about to coach: a technology company with six executives – a CEO who was the company’s original CTO, a CFO, a CTO, a CMO, a VP of Operations, and a VP of People. The CEO has brought you in because the leadership team “isn’t aligned on strategy” and “the same arguments keep happening.” You have your first observation session in two days. You have the team roster. You have the IMPRINT framework. Where do you start?

This is the work of applied formation diagnosis – and it begins before you enter the room. The previous four chapters each taught a single lens: bilateral collision patterns, the specific collisions that surface most often, the formation center of gravity that determines which voices a team structurally amplifies, and the coach’s own formation bias. This chapter puts all three lenses together in a single case walkthrough. The same team threads through every section. Each layer adds something the previous one could not see.

A Team Walks into a Room

Two days before the observation session. The roster is on your desk. Six names, six functional backgrounds – and already, the IMPRINT framework gives you somewhere to start that generic intake questions do not.

Step 1: Map the formations. Six leaders, six functional backgrounds. But the count is deceptive. The CEO’s formation is not “CEO.” There is no CEO formation – only the formation the person carried into the role. This CEO was the company’s CTO before stepping up. Their formation is technology – speed, iteration, meritocratic debate, systems thinking as a default lens. That origin matters because the CEO’s formation shapes the entire team’s operating culture in ways a CEO from a finance or marketing background would not. The other five carry their functional formations more visibly: a CFO shaped by precision and quantified justification, a CTO anchored to building and systems architecture, a CMO oriented toward narrative and resonance, a VP of Operations trained in stability and process optimization, and a VP of People grounded in relational intelligence and people advocacy.

Step 2: Identify the likely collision pairs. With this team composition, several high-impact collisions are structurally built in. CFO and CMO: precision versus narrative – the most common collision in leadership teams. CTO and VP of Operations: iteration versus stability. CMO and VP of Operations: visible versus invisible value. But the less obvious dynamic may be the most consequential: the CEO and CTO share a technology formation. Same professional lens, different roles. The CEO may unconsciously privilege the CTO’s perspective – not because they agree on everything, but because the CTO’s reasoning style, evidence standards, and trust currency match their own. That affinity is structural, not personal.

Step 3: Predict the center of gravity. A CEO with a technology formation likely creates a technology-dominant team culture: speed over deliberation, iteration over stability, data-driven meritocratic debate as the decision-making standard. The team probably moves fast. “Ship it and learn” is likely the implicit standard. In that environment, the CFO’s insistence on financial rigor may read as caution rather than due diligence. The VP of People’s advocacy for retention and wellbeing may get deferred as secondary to velocity. The VP of Operations’ concerns about process stability may be dismissed as resistance to iteration. These voices are not silenced. They are structurally discounted – and the team may not notice.

This is all before you enter the room. It is formation-informed preparation – the coach’s private awareness layer. Not a prediction to confirm, but a hypothesis to test. The observation session will show you what actually happens. The preparation gives you something to watch for.

What the First Session Reveals

The observation session. You are in the room, watching the team work through a strategic planning discussion. Three lenses are running simultaneously.

Through the collision lens. The CFO and CMO do collide – the pattern you predicted. But the more interesting dynamic is the one you almost missed in your preparation: the CEO-CFO collision. The CEO keeps reframing the CFO’s financial concerns as “not thinking big enough.” Watch the language carefully. “Not thinking big enough” is a technology formation’s read of a finance formation’s caution. The CEO is not being dismissive on purpose. They are applying the evaluative standard their career installed: scale thinking, possibility orientation, tolerance for ambiguity. The CFO’s precision – the very quality that earned every promotion in their career – is being experienced as constraint. And the CFO has learned to back down. Three times in the session, the CFO raises a concern, watches it get reframed as small thinking, and softens the position. The financial perspective is being suppressed, not expressed. That dynamic would take months of generic team coaching to surface without the collision lens.

Through the center of gravity lens. The technology formation dominates, as predicted – but the specifics are more nuanced than the prediction suggested. Meetings move fast. Topics shift before they resolve. The implicit standard is action over deliberation. The CTO and CEO operate in a shared shorthand that the rest of the team does not fully access. When the VP of People raises retention concerns for the third time, the CEO responds: “We’ll address that after the launch.” When the VP of Operations flags a capacity constraint, the CTO offers a technical workaround that eliminates the concern without addressing it. The voices operating from different formations are not being told to be quiet. They are being structurally outpaced – the meeting tempo itself is calibrated to the dominant formation’s speed.

Through the coach bias lens. And now the hardest lens – the one you turn on yourself. If your own background is people-oriented (coaching, psychology, organizational development), you may notice something about your own internal experience. The VP of People is the easiest person in the room to connect with. Their language feels like your language. Their concerns feel like your concerns. The CTO, by contrast, feels impenetrable – efficient, terse, solution-oriented in a way that leaves no space for exploration. The CEO’s directness feels abrasive. The CFO’s deference feels like a coaching opportunity you want to pursue immediately.

That gravitational pull – toward the VP of People and away from the CTO – is your own formation at work. If you follow it unchecked, you will spend disproportionate energy engaging the people-formation leader while unconsciously treating the technology-formation leaders as resistant rather than differently formed. The bias lens does not eliminate the pull. It makes it visible so you can correct for it.

Each lens reveals something the others cannot see. The collision lens shows the CEO-CFO suppression. The center of gravity lens shows the technology dominance pattern. The bias lens shows the coach’s own distortion. Together, they produce a formation read that generic “team alignment” work would take months to approximate.

From Diagnosis to Intervention

What changes with a three-layer formation read? The session design shifts. Instead of generic alignment exercises – “let’s clarify our shared goals” or “how can we communicate more effectively?” – the coach designs interventions that surface the specific structural dynamics the team cannot see from inside.

Two interventions that the formation read makes possible:

• An epistemic diversity exercise. Each leader describes what “good decision-making” looks like in their function – what evidence they trust, what process they follow, what standard they hold themselves to. The technology leaders will describe speed and iteration. The CFO will describe quantified justification and risk modeling. The VP of People will describe consultation and impact assessment. The exercise surfaces what the team’s center of gravity suppresses: the epistemic diversity that the team needs but the dominant formation’s tempo does not accommodate.
• A trust currency exercise. Each leader names what earns credibility in their professional world – the thing they must demonstrate to be taken seriously. This makes visible the different currencies the team is unconsciously ranking. In a technology-dominant team, building-and-shipping is the currency that counts. Precision (CFO), relational insight (VP People), and process reliability (VP Ops) are present but structurally undervalued. Naming the hierarchy does not eliminate it, but it makes the team’s default a conscious choice rather than an invisible structure.

Questions the coach prepares – each tied to a specific dynamic the formation read surfaced:

• For the team: “Whose definition of ‘moving fast’ is this team using? Is that a choice, or is it the default that came with the room?”
• For the CEO (in a private conversation): “You and the CTO share a technology formation. What does that make easier in the room? What does it make harder to hear?”
• For the CFO: “I notice you raise a concern and then soften it before the room responds. What would happen if you held the concern longer?”
• For the VP of People: “When you raise retention, the team defers it. What do you think is being protected by deferring?”

Each question surfaces a structural pattern without pathologizing any formation. The team question names the center of gravity without blaming the CEO. The CEO question names the shared-formation dynamic without accusing them of favoritism. The CFO question names the suppression pattern without positioning the CFO as a victim. The VP of People question names the deferral pattern without positioning them as the team’s conscience.

This is where ICF Competency 6 (Listens Actively) and Competency 7 (Evokes Awareness) become specific in team coaching. Active listening in a multi-formation room is multi-track – the coach is simultaneously tracking bilateral dynamics between pairs, systemic patterns in the team’s operating culture, and their own gravitational pulls toward familiar formations. Evoking awareness in a team means surfacing a structural dynamic the team cannot see from inside it. “The same argument keeps happening because the room is structured to hear certain voices more easily than others – and that structure is invisible to everyone in it.” That observation, grounded in a three-layer formation read, is qualitatively different from “I notice some tension between you two.”

The Five-Step Team Formation Protocol

What the case walkthrough demonstrated can be condensed into a preparation protocol for any team coaching engagement. These five steps are what the coach does before the session – the private awareness work that shapes everything that follows.

1. Map the formations in the room. Who is present? What are their functional backgrounds – not just current titles, but origin formations? A CEO who started in operations carries a different formation than a CEO who started in marketing, and that origin shapes the team’s culture in ways the current title does not reveal.

2. Identify the collision pairs. Which bilateral collision patterns are likely to activate? Which are highest-impact given this team’s composition and current challenges? A team navigating a product launch will activate different collisions than a team navigating a restructuring.

3. Read the center of gravity. Which formation’s standards dominate the team’s defaults – its definition of “rigorous,” its definition of “fast,” its definition of “strategic”? Which voices are structurally marginalized? Not silenced, but operating against the current of the dominant formation’s preferences.

4. Check your own formation bias. Which formations in this room will you find easiest to engage with? Which will you be tempted to misread as resistant or disengaged? What is your self-correction question – the question that interrupts your own formation pull when it activates?

5. Prepare formation-informed questions. At least one question per identified dynamic – a question that surfaces the structural pattern without pathologizing any formation. Questions that name what the team has not named: defaults, hierarchies of credibility, temporal misalignments, suppression patterns.

The protocol is preparation, not a session agenda. The coach does not walk into the room and execute a five-step assessment in front of the team. They walk in having done the assessment – and that preparation shapes every question they ask, every observation they make, and every dynamic they notice. The team never hears about formations, collision patterns, or centers of gravity. They experience a coach whose questions are unusually precise, whose observations surface what the team had not yet articulated, and whose presence holds space for voices the team’s structure was built to discount.

Not every technology company has a technology-dominant culture. Not every CFO suppresses their perspective in a fast-moving room. The protocol asks the coach to observe, not to assume. The preparation creates hypotheses. The session tests them.

The five-step protocol mirrors the individual coaching preparation structure that Chapter 30 develops for one-on-one engagements – mapping formation, predicting stress patterns, checking bias, and preparing questions. The team version adds Steps 2 and 3 because the multi-formation room creates collision dynamics and systemic amplification patterns that do not exist in a one-on-one setting. For the ICF-credentialed team coaching training that builds these capabilities in practice, see Tandem’s ACTC certification program.

The formation read you build before the session is not the end of the diagnostic work. It is the beginning of a coaching engagement where your private awareness – collision patterns, center of gravity, your own bias – informs every moment of presence. What the team experiences is not a framework. It is a coach who seems to hear what nobody else has named.