A practitioner’s guide · ICF team coaching · 48 methods · 113 situations

The Team Coaching Field Guide

A practical map of the moves a team coach can make and the situations that call for them — built around the ICF Team Coaching Competencies and the Advanced Certification in Team Coaching (ACTC). What to notice in a room full of people, what to ask the team as a whole, what to avoid, and how to turn a good session into a team that keeps coaching itself.

6families
48methods
113situations
69frameworks in the library
10situation groups
8ICF competencies mapped
33diagrams
The client is the team, not the loudest person in it, not the leader, and not the sponsor. Coach the space between people. Follow the energy in the room, describe what you see, and let the team make the meaning.

Start here

Team coaching is coaching in which the client is a whole team. The coach partners with the team, as one entity, to help it see its own dynamics, relationships and patterns, and to choose how it wants to work towards its common purpose. The coach doesn’t supply the answers, and doesn’t work through the team members one by one. Instead, they shape a space in which the team can think, disagree, decide and learn together.

This guide collects 48 team coaching methods, 113 situations and a Knowledge Library of 69 frameworks that come up again and again when coaching teams. It is a companion to the one-to-one Coaching Methods Field Guide and keeps the same structure, so you can move between the two. Everything has been rewritten from the team’s point of view, and mapped to the ICF Team Coaching Competencies that underpin the ACTC.

The central idea is the same as in individual coaching, with one twist. First notice what is happening between people in the room, then choose the move that fits it. In team coaching, the “what is happening” is usually about process — who speaks, who decides, what is avoided — rather than about content.

What you’ll find

  • Who the client is: the team, the leader, the sponsor and the wider system
  • The ICF competencies with every team addition and the methods that express it
  • 6 families that follow the arc of a team session
  • 48 methods, each in ten parts plus three worked problems
  • 113 situations in 10 groups, each on a full card
  • Team models, diagrams and an interactive team health check
  • Where to start: a Team Maturity × Method map and quick picker
  • A Between Sessions Toolkit and a Coach Presence Lab
  • A Knowledge Library of 69 frameworks from the ACTC curriculum, with a study path and progress tracker

Three ways to use this guide

To learn

Read “Who is the client?”, the ICF map and “The spine of a team session” first. Then learn the ten starter methods below, trying one or two in real sessions before adding more. Use the self-assessment to track progress.

Before a session

Think about the team you’re about to meet. Find the situation that sounds most like them in the Situation Atlas and read its card. Check your contract and the leader’s role. Pick one process observation you’ll watch for.

After a session

Look up the methods you used. Read “Where it gets stuck”, “Coach mistakes” and “Team traps”. Use the supervision prompts — ACTC requires coaching supervision, and these make good material for it.

Ten methods to learn first

  1. 1 Contract with the Three ClientsAgree outcomes with the team, the leader and the sponsor before the first session
  2. 5 Check-in RoundsHear every voice early, before the loudest voice sets the tone
  3. 7 Contract the Session LiveAgree what this group wants from this session, and whose agenda it really is
  4. 9 Process Observation in Real TimeName what is happening between people, here and now
  5. 13 Name the UndiscussableMake it safe to say what everyone knows but nobody says
  6. 15 Liberating StructuresUse simple, ready-made structures that include every voice and reduce the coach’s talking
  7. 25 Build Psychological SafetyMake it safe to speak up, admit mistakes and ask for help
  8. 27 Make Conflict ProductiveTurn avoided or destructive conflict into useful debate about ideas
  9. 32 Coach the Leader in the RoomWork with the leader’s dual role — inside the team and above it
  10. 40 Team Experiments and CommitmentsTurn insight into a small, owned experiment the whole team can see

How to read a page

A method page

Starts with the core move, the ICF competencies it expresses and a quick card (when to reach for it, the move, a watch-out and four questions). Then ten parts: what it is, the team’s context, the coach’s options, how it works, where it gets stuck and how to move forward, questions, situations it fits, coach mistakes and team traps — plus three worked problems and where it comes from.

A situation card

Shows what is happening and the recommended move at a glance. Open it for what you’ll see in the room, what members might say, what’s underneath, questions to ask the team, what to avoid, examples, a sample exchange, signs it’s working, a look-alike and the methods that handle it.

Codes

Methods are numbered 1 to 48. Situations use S-codes: S4.2 is situation 2 in group 4 (Conflict and trust). Coloured chips ICF 4 show the ICF competency a method expresses. In sample exchanges, C is the coach, L the team leader, M a team member and S the sponsor.

Key terms

Team coaching
ICF’s definition: partnering in a co-creative and reflective process with a team on its dynamics and relationships, in a way that inspires the team to maximise its abilities and potential in order to reach its common purpose and shared goals.
Team as client
In team coaching the client is the team as a single entity made up of multiple individuals — not the leader, not the sponsor and not each member separately.
Team leader
The person with formal authority for the team. Usually a member of the team-as-client and also a distinct stakeholder with their own needs.
Sponsor
The person or function that commissions and often pays for the coaching — for example the leader’s manager, HR or a business-unit head.
Stakeholders
Everyone who depends on, or is affected by, the team’s work: customers, other teams, the board, regulators, communities.
Multi-stakeholder contract
The explicit agreement between coach, team, leader and sponsor about purpose, roles, confidentiality, reporting, process and review.
Working agreements
The team’s own behavioural norms for how it will work in sessions (and often beyond them), including what happens when an agreement is broken.
Process vs content
Content is what the team is talking about. Process is how it is talking: who speaks, who decides, what is avoided. Team coaches work mostly on process.
Psychological safety
A shared belief that the team is safe for interpersonal risk-taking — speaking up, admitting mistakes, asking for help (Amy Edmondson).
Co-coaching
Two (or more) coaches working with the same team, agreed with the team and sponsor. Allows one coach to observe while the other leads.
Team development modalities
Team coaching, team building, team training, team consulting, team mentoring and team facilitation. ICF expects team coaches to keep these distinct and to move between them only by agreement.
Supervision
Regular reflective practice with a qualified supervisor. Required for the ICF Advanced Certification in Team Coaching (ACTC).
A note on scope. This is a guide for professional team coaching. It is not a manual for therapy, mediation of formal grievances, investigations or performance management. If a member is at risk, discloses harassment or describes a clinical problem, safety and the right formal process come first. Always follow the ICF Code of Ethics, your contract and any organisational policies that apply.

Who is the client? The team as one entity

The single biggest shift from one-to-one coaching is the nature of the client. ICF is explicit: in team coaching, the client is the team as a single entity comprising multiple individuals. Yet the team never arrives alone. It has a leader who sits both inside and above it, a sponsor who commissions the work, and stakeholders whose needs are the reason the team exists.

Who is the client in team coachingWider system: customers · other teams · board · communityThe team= the client, as one entityTeamleaderinside the team and above itSponsor /organisationStake-holdersCoach(+ co-coach, if agreed)contracts with all three,coaches the team as one

Coach the whole, not the parts

Questions go to the team (“What do we notice?”), observations describe the team’s pattern, and progress is measured at team level. Individual issues are noticed as part of the system, not coached one by one in front of others.

Hold the leader’s dual role

Agree in advance how the leader will show up — when to speak, how to receive challenge, what they own. Never become the leader’s instrument, and never protect the team from its leader.

Keep the system in view

A team’s value is created for others. Bring stakeholders’ voices into the room, and close the loop with them, so the team’s development serves the organisation and not just the team’s comfort.

Team coaching is not the only way to develop a team

ICF’s first team competency asks coaches to keep team coaching distinct from team building, training, consulting, mentoring and facilitation — and to use more directive modes only when the team genuinely needs them, openly and by agreement. The map below is a simplification, but it helps when a sponsor asks “What exactly will you do?”

Team coaching compared with other team development modalitiesWho supplies the answers? →Expert / practitionerThe team itselfFocus →Task / skillsTeam as a systemTrainingTeaches a skillor contentConsultingDiagnoses andadvisesMentoringSharesexperienceTeam buildingBonding, sharedexperienceFacilitationRuns theprocess; teamowns contentTeam coachingCo-creative,reflective,systemicTeam coaches may step into other modes —openly, briefly and by agreement

One-to-one coaching and team coaching compared

DimensionOne-to-one coachingTeam coaching
Who is the client?One personThe team as a single entity, with a leader inside it and a sponsor and stakeholders around it
ContractingUsually two-way (sometimes three with a sponsor)Multi-party: sponsor, leader, members, co-coaches — and renewed every session
What the coach listens toThe client’s words, feelings, beliefsEach voice, plus the relationships between voices, the energy of the whole and patterns over time
Where the work happensInside one person’s thinkingBetween people, live, in the room — the team’s process is visible as it happens
ConfidentialityBetween coach and clientLayered: what stays in one-to-one interviews, what stays in the team, what goes to the sponsor
Coach’s presenceAttuned to one personMoving in and out of the dialogue; often with a co-coach; staying multi-partial
Typical risksRescuing, advisingColluding with the leader or a subgroup, becoming the facilitator or expert, scapegoating
Success looks likeThe client acts differentlyThe team works differently together and keeps coaching itself after the coach leaves

The ICF Team Coaching Competencies

ICF’s team model does not invent new competencies. It keeps the eight Core Competencies and adds team-specific sub-competencies to each one. Click a segment to jump to it. Every method in this guide is tagged with the competencies it most clearly expresses, so you can study the model through practice.

ICF competencies with team coaching additions1Demonstratesethicalpractice2Embodies acoachingmindset3Establishesand maintainsagreements4Cultivatestrust andsafety5Maintainspresence6Listensactively7Evokesawareness8Facilitatesclient growthThe teamas one client8 competenciesFoundationCompetencies 1–2Co-creating the relationshipCompetencies 3–5Communicating effectivelyCompetencies 6–7Cultivating learning and growthCompetencies 8No new competencies for team coaching —ICF adds team-specific sub-competenciesto each of the eight core ones.
1
Foundation

Demonstrates ethical practice

Team coaching adds
  • Coaches the team as one client entity.
  • Keeps team coaching distinct from team building, training, consulting, mentoring and facilitation.
  • Builds the competence needed for any blend of modalities offered.
  • Uses more directive modalities only when the team needs them to reach its goals.
  • Stays trustworthy, transparent and clear when holding more than one role.
Methods in this guide that express it 4
2
Foundation

Embodies a coaching mindset

Team coaching adds
  • Uses coaching supervision for support, development and accountability.
  • Stays objective and aware of team dynamics and patterns.
Methods in this guide that express it 5
3
Co-creating the relationship

Establishes and maintains agreements

Team coaching adds
  • Explains what team coaching is and is not, and how it differs from other modalities.
  • Creates agreements with all relevant parties — leader, members, stakeholders, co-coaches — on relationship, process, plans, modalities and goals.
  • Agrees with the team leader how ownership of the process is shared between coach, leader and team.
Methods in this guide that express it 13
4
Co-creating the relationship

Cultivates trust and safety

Team coaching adds
  • Creates a safe space for open, honest interaction between members.
  • Helps the team see itself as one entity with a common identity.
  • Encourages members to voice individual and collective feelings, concerns, hopes and suggestions.
  • Encourages participation and contribution from every member.
  • Works with the team to create, maintain and reflect on its rules and norms.
  • Promotes effective communication within the team.
  • Works with the team to identify and resolve internal conflict.
Methods in this guide that express it 19
5
Co-creating the relationship

Maintains presence

Team coaching adds
  • Uses the full range of sensory and perceptual abilities.
  • Uses a co-coach when the team and sponsors agree and it helps presence.
  • Invites members to pause and reflect on how they interact.
  • Moves in and out of the team dialogue as appropriate.
Methods in this guide that express it 7
6
Communicating effectively

Listens actively

Team coaching adds
  • Notices how each member’s view relates to others’ views and to the team dialogue.
  • Notices how each member affects the team’s energy, engagement and focus.
  • Notices verbal and non-verbal patterns that signal alliances, conflicts or growth.
  • Models confident, effective collaboration with co-coaches or other experts.
  • Encourages the team to own its dialogue.
Methods in this guide that express it 11

The team additions above are paraphrased for learning. Always check the current wording in ICF’s own Team Coaching Competencies document.

The ACTC at a glance

The ICF Advanced Certification in Team Coaching (ACTC) is a specialisation that sits on top of an existing ICF credential. It is built on the Team Coaching Competencies, the Core Competencies and the ICF Code of Ethics. ICF describes team coaching as helping teams navigate complex group dynamics, improve collaboration, foster shared accountability, align on common goals and sustain change over time.

Eligibility

  • An ICF credential (ACC, PCC or MCC) in good standing
  • 60+ hours of team coaching education
  • 5 team coaching engagements in the past 5 years
  • 5 hours of coaching supervision with an eligible supervisor
  • A passing score on the ICF Team Coaching Certification Exam

Application paths

General team coaching education60 hours from any programme; 48 of them applying the Team Coaching or Core Competencies in team contexts
ICF-accredited programmeCertificate from an ICF Advanced Accredited Team Coaching (AATC) programme
Prior learning through experience10 team engagements, 10 supervision hours and at least 30 education hours

Good to know

  • Engagements must include real-time (synchronous) sessions in which participants set the agenda; training, consulting or team building count only if real team coaching sessions are included.
  • Two engagements need signed verification letters (from a team member, leader, sponsor representative or third-party coaching body), including dates, hours and team size.
  • Applications can be audited: keep records and client consent for contact details.
  • Mentor coaching is optional; coaching supervision is required. The ACTC is an add-on to an existing ICF credential, not a replacement.
Requirements change. Fees, hours and paths are set by ICF and updated from time to time. Check the official ACTC page before you apply. How this guide helps: the Knowledge Library maps the 12 knowledge areas most ACTC programmes teach, with a study path; the methods give you a shared vocabulary for your 60 hours of education, the situation cards make good supervision material, and the engagement section mirrors what verification letters ask you to evidence (dates, hours, team size, real-time sessions where the team sets the agenda).

The session arc: six families

The 48 methods sit inside six families. The grouping tells you when in a team session, or in an engagement, each tool belongs. Each family is triggered by one diagnostic question about the team. Click a family to jump to it.

The six families along the arc of a team coaching sessionContractMethods 1–7Contract and ConveneIs everyone clear whatthis team is here to dotogether, and who theclient is?SurfaceMethods 8–15Surface the SystemDoes the team see its ownpatterns, or only itsstories about them?ShiftMethods 16–24Shift the Team FrameIs the team locked intoone meaning of itssituation?ConnectMethods 25–32Trust, Conflict and VoiceCan the team say truethings to each other andstay a team?ChooseMethods 33–39Future and DecisionsDoes the team share apicture of where it isgoing and how it decides?CommitMethods 40–48Land, Learn and SustainHas enough opened that itmust become something theteam does?
More on choosing and sequencing methods with a team

In a room of seven people, a dozen possible directions open up every minute. One member raises a concern, another sighs, the leader leans forward, someone on the screen goes quiet. Follow the content and you may miss the pattern; follow one person and you lose the team. This guide is meant to make that split-second judgment easier to see, name and practise.

Sequencing matters even more with teams than with individuals. Contract before anything, because a team working on an agenda it doesn’t own will perform rather than think. Surface before you shift: a reframe offered before the team has seen its own pattern lands as the coach’s opinion. Build enough safety before you invite conflict, because conflict without safety injures people. Agree a direction before you assign actions, or the actions will be fought over later. And always land — a team that leaves without one owned experiment will start next session from the same place.

The families also map loosely onto an engagement. Early sessions lean on Contract and Surface; the middle on Shift, Trust and Choose; the later sessions on Land and on handing the coaching role back to the team. But any session can need any family: a rupture in month six needs Trust methods, whatever the plan says.

The spine of a team session

Every entry in this guide sits somewhere on the same underlying sequence — the shape a well-run team coaching session tends to take, whether it lasts ninety minutes or a full day. Contract agrees the team’s own question. Surface makes visible how the team actually works. Shift loosens the frame the team is stuck in. Connect lets members say true things to each other. Choose turns shared understanding into shared direction. Commit turns insight into something the team will do differently by the next session.

With teams, stages are rarely announced, and different members may be at different stages at once. Two people are ready to commit while three are still surfacing. Reading where the team is — not where its most vocal member is — is the core skill.

01

Contract

Whose agenda is this, and what does the team want from today? Test it with every voice, not only the leader’s.

Skipping it: The team performs for the sponsor or the leader instead of working on its own question.
02

Surface

Make the team’s data, patterns and history visible. Describe behaviour; let the team make the meaning.

Skipping it: The team discusses its stories about itself, not its actual patterns.
03

Shift

Zoom out to the system, find both/and, uncover hidden commitments. New meaning creates new options.

Skipping it: The team chooses between the same two positions it walked in with.
04

Connect

Let members say true things to each other: safety, conflict about ideas, minority voice, repair.

Skipping it: Agreement in the room, disagreement in the corridor.
05

Choose

Agree a shared direction, who decides what and how much support there really is.

Skipping it: Decisions are reopened next week because they were never truly made.
06

Commit

One or two owned experiments, a way to know they happened, and a place in the team’s routines.

Skipping it: A great session with nothing built to carry it into Monday.

How to use this in a live team session

Notice how the team is talking, not just what it is talking about: who speaks first, who speaks most, who looks at whom, where the energy rises and drops, what makes the room go quiet. That noticing is the diagnostic step. Then decide whether to stay in the content or to step briefly into process — “Can I share what I’m noticing about how we’re talking?” Choose one family that fits what you see, and offer one question to the whole team.

Then wait — longer than with an individual. Teams need time to decide who will answer, and the first answer is often the safest one. If nothing opens, don’t ask a cleverer question at the same level: change level, from content to process, to climate, to assumptions, to identity and purpose, to the wider system. A stuck team conversation is very often the right question aimed at the wrong level.

If nothing opens, change level, not wording · explained below
1Content
2Process
3Climate
4Assumptions
5Identity & purpose
6Wider system
Then land at Experiment: what will the team try?
Noticethe pattern, not only the topic
Nameit neutrally, with permission
Chooseone method family
Askthe whole team
Waitfor the system to answer
Shiftlevel if stuck

Changing level: six levels of a team conversation

The same issue can be discussed at six levels. When a team conversation stalls, the problem is usually the level, not the question. The example follows one leadership team that says, “We keep missing deadlines.” Most sessions should end with the team choosing an experiment, whichever level unlocked it.

1

Content

What we are discussing

The topic itself: the project, the numbers, the decision.

Ask“What exactly is happening with the deadlines?”
Team“Three of the last five releases slipped.”
Go here whenThe team has not yet described the issue concretely, or members are clearly describing different problems.
2

Process

How we are talking

The pattern of interaction: who speaks, who decides, what happens to ideas.

Ask“What do you notice about how we discuss deadlines?”
Team“Whoever raises a risk gets told to be positive.”
Go here whenThe content is going in circles and the same people play the same roles.
3

Climate

How it feels to be here

The collective emotion: tension, fear, fatigue, excitement.

Ask“What’s the mood in the team when a deadline is at risk?”
Team“Dread. Everyone hopes someone else will say it.”
Go here whenThe process is clear, but there is energy (or flatness) that nobody names.
4

Assumptions

What we believe must be true

The norms and beliefs underneath behaviour.

Ask“What do we assume would happen if we said a date was unrealistic?”
Team“That we’d look weak in front of the board.”
Go here whenThe feeling is named but locked in place by an unspoken rule.
5

Identity and purpose

Who we are and why we exist

How the issue connects to the team’s sense of itself and its reason for being.

Ask“What kind of team do we want to be when promises are at stake?”
Team“The one people trust because we tell the truth early.”
Go here whenAssumptions are visible but the team needs a reason bigger than comfort to change them.
6

Wider system

What around us keeps this going

Stakeholders, structures, incentives and other teams.

Ask“How does the way deadlines are set upstream shape this?”
Team“Sales commits dates before we’re asked.”
Go here whenThe team is ready to act but the pattern is held in place outside the room.

Team models every team coach should know

Methods are moves; models are maps. The ICF team competencies note that team coaches need a broader knowledge base than one-to-one coaches. These five maps are the ones most often used to make sense of a team. Hold them lightly: they are lenses for curiosity, not boxes for teams.

1

Hawkins: five disciplines of systemic team coaching

Peter Hawkins argues that high-performing teams master five disciplines: understanding what they are commissioned to deliver, clarifying their own purpose and roles, co-creating how they work together, connecting with stakeholders, and core learning at the centre. Many teams only work on co-creating — their relationships — and wonder why nothing changes outside.

2

Wageman and Hackman: six conditions

Research on senior leadership teams found that most of a team’s effectiveness comes from its design conditions, and only a smaller part from coaching. The practical lesson: test the essentials (see Method 2) before investing heavily in coaching, and coach at the right moments — beginnings, midpoints and ends.

Six conditions for team effectivenessSix conditions for team effectiveness (Wageman, Hackman et al.)Real teamBounded, interdependent, stableCompelling directionClear, challenging, consequential purposeRight peopleSkills and size the task needsESSENTIALS — without these, coaching has little to work onSolid structureTask design, norms, sizeSupportive contextRewards, information, resourcesCompetent coachingWell-timed help for the teamENABLERS — they accelerate a team that already has the essentials
3

Tuckman: stages of team development

Bruce Tuckman’s forming–storming–norming–performing (with adjourning added later) is the most widely known team model. Real teams loop back — a new member or a reorganisation can return a performing team to storming. Use it to normalise the stage the team is in, not to rush it.

Stages of team developmentTeam effectivenessFormingWorking agreements,purpose, user manualsStormingProductive conflict,repair, rolesNormingDecision rights,feedback, rhythmsPerformingPeer accountability,stakeholder loopsAdjourningHarvest learning, endwellTuckman’s stages — and where the coach’s emphasis usually sits
4

Edmondson: psychological safety and accountability

Safety is not the same as comfort. Amy Edmondson shows that teams learn best when psychological safety and standards are both high. Low safety with high demands produces anxiety and hidden mistakes; high safety with low demands produces a pleasant comfort zone. See Method 25.

Psychological safety and accountability (after Edmondson)Psychological safety →Standards / accountability →Anxiety zoneHigh demands, low safety: peopleperform and hide mistakesLearning zoneHigh demands, high safety: candour,learning, performanceApathy zoneLow demands, low safety: peopledisengageComfort zoneLow demands, high safety: pleasant,unstretched
5

Kantor: four acts in every conversation

David Kantor’s structural dynamics gives teams a simple shared language for their conversations. Healthy teams use all four acts flexibly; stuck teams overuse one or two. See Method 10.

Kantor four-player modelFour acts in every team conversation (Kantor)Moveproposes a directionFollowsupports and buildsOpposechallenges, correctsBystandcomments on the processStuck patterns:• move–oppose loop• move–follow (no oppose)• nobody bystands

Other useful lenses include Lencioni’s five dysfunctions (absence of trust, fear of conflict, lack of commitment, avoidance of accountability, inattention to results) — popular and easy to remember, though based on practice rather than research — Clutterbuck’s PERILL model, Beckhard’s GRPI, the Drexler-Sibbet model, Katzenbach and Smith’s distinction between working groups and real teams, and Bion’s basic assumptions — all explained in the Knowledge Library. The “How it works” sections in this guide mix research, theory and craft wisdom; treat them as working explanations to test in your own practice.

More team lenses many coaches use

Beyond the core five, four more lenses come up again and again in ACTC programmes and in practice. Each has a fuller card in the Knowledge Library.

6

Lencioni’s five dysfunctions — a quick team check

The pyramid is easy for teams to use as a shared language: build trust before inviting conflict, commitment before expecting accountability. Score the ten statements from 1 (rarely true) to 5 (almost always true), alone or with the team. The pyramid colours by level. This is an informal conversation starter, not the published Five Behaviors assessment.

TrustMembers admit mistakes and weaknesses to each other.
TrustMembers ask each other for help without hesitating.
ConflictOur meetings include open, passionate debate about important issues.
ConflictDisagreements are raised in the room, not afterwards.
CommitmentWhen we leave a meeting, everyone knows what was decided.
CommitmentWe back decisions even when we argued against them.
AccountabilityMembers point out each other’s unhelpful behaviour.
AccountabilityWe hold each other to commitments — it isn’t only the leader’s job.
ResultsWe put team results ahead of individual or department goals.
ResultsWe review our collective results regularly and act on them.
7

Clutterbuck’s PERILL: the team as a complex system

Six influences — Purpose and motivation, External systems and processes, Relationships, Internal systems and processes, Learning, Leadership — all interact. A “relationship problem” may be rooted in unclear purpose or clumsy processes. Use it to trace connections before you intervene. 6 · Purpose and Stakeholder Expectations 35 · Clarify Decision Rights 44 · Redesign the Team Rhythm

Clutterbuck PERILL modelPurpose &motivationExternal systems& processesRelationshipsInternal systems& processesLearningLeadershipTeam as acomplex systemEvery influence affects every other:the presenting problem is rarely the root.
8

Belbin: a lighter team-roles lens

Nine roles in three clusters. Ask which roles the team overuses, which are missing, and who could consciously cover a gap. Discuss roles as behaviours, not boxes; you don’t need the full instrument to use the lens. 39 · Role Negotiation (Give and Get) 26 · Personal Histories and User Manuals

Belbin roles in three clustersThinkingPlantMonitorEvaluatorSpecialistActionShaperImplementerCompleterFinisherPeopleCoordinatorTeamworkerResourceInvestigator
9

Gersick: punctuated equilibrium

A useful counter to linear stage thinking. Project teams often lock into an approach early, keep it for the first half of their time, then change sharply around the midpoint. Schedule a coaching session near the midpoint — it is the team’s natural window for rethinking. 43 · After-Action Review / Retrospective 7 · Contract the Session Live

Punctuated equilibriumPhase 1: inertiamidpoint transitionPhase 2: new approachfinal pushprogress
10

Team of teams and fluid teaming

Many teams are now nodes in a network: squads, programmes, task forces with changing membership. Stanley McChrystal’s “team of teams” describes networks that combine shared consciousness (everyone sees the whole) with empowered execution (teams act locally within shared intent). Amy Edmondson’s “teaming” describes how people build trust and shared understanding fast when membership keeps changing. Coach the network: shared purpose, explicit interfaces, liaison roles and cross-team learning. 3 · Teaming for Fluid Teams 16 · Zoom to the Ecosystem (Stakeholder Chairs) 15 · Liberating Structures S8.10 Team of teams / cross-team coordination S8.14 Fluid membership: the team keeps changing

Command structure versus team of teamsCommand structureTeam of teamsefficient, but slow to adapt;problems sit between silosshared purpose + liaison links (dashed) + local autonomy

Team Maturity × Method Map: where do I start with this team?

Coaches constantly ask where to begin. Two tools help. The quick picker uses three conditions that predict most of what a team needs — safety, clarity and accountability. The matrix shows which methods tend to be highest-leverage at each stage of team development. Both are starting points for your judgment, not prescriptions: the team in front of you always wins.

Psychological safety
Clarity of purpose, roles and decisions
Mutual accountability

Highest-leverage methods by stage

StageContract and ConveneSurface the SystemShift the Team FrameTrust, Conflict and VoiceFuture and DecisionsLand, Learn and Sustain
FormingOrientation, politeness, dependence on the leader1 · Contract with the Three Clients3 · Teaming for Fluid Teams4 · Co-create Working Agreements5 · Check-in Rounds11 · Team Timeline / Journey Line20 · Appreciative Inquiry: What Is Working26 · Personal Histories and User Manuals25 · Build Psychological Safety6 · Purpose and Stakeholder Expectations33 · Shared Preferred Future40 · Team Experiments and Commitments
StormingTension, testing, competition for influence7 · Contract the Session Live9 · Process Observation in Real Time10 · Map Interaction Patterns13 · Name the Undiscussable17 · Polarity Map for Teams19 · From Drama to Empowerment22 · Walk Down the Ladder of Inference27 · Make Conflict Productive31 · Repair a Rupture in the Room28 · Hear the Minority Voice32 · Coach the Leader in the Room35 · Clarify Decision Rights39 · Role Negotiation (Give and Get)43 · After-Action Review / Retrospective
NormingAgreements, roles, growing trust4 · Co-create Working Agreements8 · Diagnostic and Data Feedback15 · Liberating Structures23 · Clean Language for Teams29 · Team Feedback Rounds30 · Feedforward and Start / Stop / Continue36 · Gradients of Agreement37 · Consent-Based Decision Making38 · Prioritize and Stop Doing44 · Redesign the Team Rhythm41 · Peer Accountability and Peer Coaching45 · Team Rituals and Ceremonies
PerformingOwnership, candour, delivery; risk of comfort6 · Purpose and Stakeholder Expectations14 · Collective Shadow12 · Sculpt the Team (Constellations)16 · Zoom to the Ecosystem (Stakeholder Chairs)24 · Theory U and Presencing Practices30 · Feedforward and Start / Stop / Continue34 · Team Pre-Mortem33 · Shared Preferred Future46 · Harvest Team Learning47 · Close the Loop with Stakeholders42 · Action Learning Sets for Intact Teams
Transition / adjourningChange of members, leader or task; endings3 · Teaming for Fluid Teams1 · Contract with the Three Clients11 · Team Timeline / Journey Line18 · Team Immunity to Change31 · Repair a Rupture in the Room33 · Shared Preferred Future48 · Fade the Coach and End Well45 · Team Rituals and Ceremonies46 · Harvest Team Learning

Stages follow Tuckman, with “transition” added because real teams loop back whenever members, leaders or tasks change. See also Team models and S8.14 Fluid membership: the team keeps changing.

A team session, start to finish

Priya leads a product leadership team of seven. She asked for this session saying “people aren’t delivering — we need accountability.” Follow the session stage by stage. On the right you can see what the coach noticed, which situation it matched, the level the conversation was working at and the method used.

ConversationWhat the coach noticed · situation · level · method used
Contract
Leader

Thanks for coming. As I said in the invite, today is about accountability — people aren’t delivering.

Coach

Thank you, Priya. Before we dive in, I’d like to hear from everyone. In one sentence: what would make today worth your time?

The leader’s framing arrives first and names a problem located in “people”. The coach thanks her and opens the contract to every voice before accepting it.

Member

Honestly? Knowing what our actual priorities are.

Member

Same. I’ve got six “top priorities”.

Member

Fewer meetings would help.

Coach

I’m hearing “priorities” from four of you and “accountability” from Priya. Could they be connected? Which shall we work on?

The round shows a different centre of gravity. The coach names both agendas without choosing between them and hands the choice to the team.

Surface
Member

Can I say something? When we agree priorities here, they change by Wednesday.

Leader

Well, that’s because the market changes.

Coach

Can I share something I’m noticing? In the last ten minutes, three people raised changes after meetings, and each time the conversation moved to why it was necessary. What do you notice?

A process pattern: concerns are explained away before they’re explored. The coach describes behaviour, not motive, and asks the team.

Member

(pause) We don’t really push back. On Priya, or on each other.

Coach

What makes it hard to push back here?

Member

The last person who did got moved off the account.

Silence, then a member names the undiscussable. The level shifts from process to climate and assumptions.

Connect
Leader

(quietly) I didn’t know that was how it landed.

Coach

Priya, what’s it like to hear that?

Leader

Hard. And useful. I want people to push back — I clearly haven’t made that safe.

The leader’s response will decide whether the team takes more risks. The coach slows down and gives her space to respond, not defend.

Shift
Coach

What would you each assume would happen if you said “that priority is unrealistic” in this meeting?

Member

That I’d be seen as not a team player.

Coach

And is that still true, given what Priya just said?

The coach makes the shared assumption explicit so the team can test it rather than obey it.

S2.6 Collective cynicismLevel: Assumptions
Choose
Member

Could we agree that priorities can only change in this meeting, not by email?

Coach

Let’s check real support. Fist to five?

Coach

Mostly fours and fives, one two. Anil, what would move you up?

Member

A rule for genuine emergencies.

The team has energy for a structural fix. The coach tests the level of agreement and gives the minority a voice before deciding.

Commit
Coach

What will you try before we meet again, and who will own it?

Leader

I’ll ask “what am I missing?” before I respond to any concern.

Member

I’ll run the priorities list, and flag any change made outside this meeting.

Coach

How will we know in four weeks if it worked?

Two experiments, each with an owner, one of them the leader’s own behaviour. The original “accountability” problem is now being addressed through structure and safety.

S6.7 Nobody owns actionsLevel: Experiment

What to take from it

  • The leader’s opening agenda was respected but not adopted; the team’s round reshaped it.
  • The turning point was a process observation, not a clever question about content.
  • The most important move was giving the leader space to respond well to an undiscussable.
  • “Accountability” was solved through decision structure and safety — not by holding individuals to account.

Anatomy of every method

Every method follows the same template, so you always know where to look. Each method page has a coloured strip linking to its own parts.

Anatomy of each methodEvery one of the methodsUnderstand it1What it really is2The team’s context3The coach’s options4How it works, deeplyWhen it stalls5Where it gets stuck6How to move it forwardUse it7Questions for the team8Situations from the fieldAvoid the traps9Coach mistakes10Team traps+ a quick card, ICF tags, three worked problems, origins and your own notes
Family 1 of 6 · Methods 1–7 · Start of an engagement or a session

Contract and Convene

Is everyone clear what this team is here to do together, and who the client is?

The Contract and Convene family sets up the conditions for everything else. In individual coaching, contracting is a conversation between two people. In team coaching it is a negotiation across at least three parties — the team, its leader and the sponsoring organisation — and it has to be repeated at the start of every session, because a team’s agenda is never one person’s agenda.

These methods turn a gathering of individuals into a coaching client: they test whether the group really is a team, agree who owns what, give every voice a place early and tie the work to a purpose larger than the room. Nothing gets “solved” here. The point is that when the team starts working, it is working on its own question, in a space it trusts.

1
Contract and Convene family

Contract with the Three Clients

Core move: Agree outcomes with the team, the leader and the sponsor before the first session
5 options10 questions16 situations

1What it really is

In team coaching the client is the team as a single entity, but the team never arrives alone. There is almost always a leader who sits both inside and above the team, and a sponsor (often the leader’s boss, HR or a business unit head) who funds the work and expects something from it. Multi-stakeholder contracting makes those three relationships explicit before any coaching begins. It agrees what the work is for, who owns which part of it, what is confidential, how progress will be reviewed and what team coaching is and is not. It is the foundation every later method stands on.

4How it works, deeply

Contracting with multiple parties works because it converts invisible loyalties into visible agreements. Every team member silently asks, “Whose side is the coach on?” If the answer is unclear, members protect themselves: they speak carefully, perform for the leader and save honesty for the corridor. A visible three-way agreement answers that question with a structure rather than a promise. It also gives the coach something to return to when pressure arrives — when the sponsor asks “who is the problem?”, the coach can point to the agreement rather than improvise a boundary under stress. Peter Hawkins calls this the commissioning discipline: the team needs to know who it serves and what they need, before it can coach itself toward it.

Quick card

Reach for it when
Start of any engagement; when the sponsor, the leader and the team want different things; when confidentiality is unclear
The move
Name the three clients out loud and build one agreement all three can see
Watch
An agreement made only with the sponsor turns the coach into the organisation’s instrument, and the team will feel it in the first ten minutes.
Four questions that often open it
  1. What does the organisation need from this team that it isn’t getting yet?
  2. What would make this coaching worth the team’s time, not just the sponsor’s?
  3. What will be shared outside this room, and what stays here?
  4. How will we all know, in six months, that this was useful?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Sponsor-driven — the request came from above (“fix the leadership team”) and the team has not yet chosen the work for itself.
  • Leader-shaped — the leader has a clear view of what is wrong, usually involving other people, and wants an ally.
  • Fragmented expectations — interviews reveal that the sponsor wants alignment, the leader wants accountability and members want relief from overload.
  • Burnt by past “interventions” — the team has had away-days, assessments and consultants; they expect another one.
  • Unclear boundaries — nobody has said what the coach will report, to whom, or whether individuals will be assessed.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Three-way meeting — bring sponsor, leader and coach together before the team launch to agree purpose, success measures and reporting.
2Team ratification — present the draft agreement to the whole team and change it with them, so it becomes theirs.
3Reporting contract — agree that only themes and team-level progress leave the room, never individual attributions.
4Explain the modality — describe how coaching differs from training, facilitation and consulting, and when (with permission) the coach may step into another mode.
5Review points — schedule mid-point and end reviews with all three clients now, not when trouble arrives.

5Where it gets stuck

The sponsor wants individual assessments disguised as team coaching. The leader quietly expects the coach to “deal with” one member. The team agrees to everything in the launch meeting and believes none of it. Confidentiality is promised loosely and broken accidentally in the first sponsor update.

6How to move it forward

Make the uncomfortable clauses explicit: “I will not report on individuals. I will report on themes and on our agreed measures.” Test the agreement against a realistic scenario (“If the sponsor asks me who is resisting, I will say…”). Ask the team what would make the agreement trustworthy for them, and write their conditions into it. If the sponsor will not accept team-level reporting, the honest move may be to decline or re-scope the work.

7Questions to ask the team

Core questions
  • What is this team uniquely responsible for delivering?
  • What does success look like from the sponsor’s chair, the leader’s chair and the team’s chair?
  • What are you hoping I will do — and what are you hoping I won’t do?
  • What would make it unsafe for members to speak honestly here?
  • How will we review this agreement as we go?
Going further
  • If this engagement failed quietly, how would it fail?
  • Who else has a stake in this team’s success and is not in this conversation?
  • Where do your hopes for this work differ from the sponsor’s?
  • What have previous team interventions taught you to expect?
  • What would you need to hear from me to believe confidentiality is real?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S1.1Sent by the sponsorThe team attends because someone above asked; low ownership of the agenda
What is happening The team attends because someone above asked; low ownership of the agendaCoach move Name the three clients; find the team’s own stake in the work
In the room
Arms folded, polite questions about “what HR wants”. Members look at the leader to see how seriously to take this. Energy is dutiful, not curious.
What’s underneath
An assigned engagement feels like a judgment. Members protect themselves until they know whose side the coach is on and whether anything they say will travel upward. Ownership cannot be demanded; it is found when the team locates something it wants from the work.
Avoid here
Defending the sponsor. Launching into diagnostics before the contract is clear. Pretending the request came from the team.
Example
Operations leadership team. The COO commissions coaching after two missed targets. The team opens with sarcasm. The coach shares the sponsor’s brief word for word and asks what they would change. They rewrite the objectives around cross-shift hand-offs — the issue they had been raising for a year.
Full situation card: questions, examples, sample exchange
Filed under methods176
S1.2The leader’s agenda dressed as the team’sThe leader frames the topic; members nod but energy is elsewhere
What is happening The leader frames the topic; members nod but energy is elsewhereCoach move Test the agenda with the whole team before working on it
In the room
The leader introduces “our priorities”. Members look at the table. When asked directly, they agree quickly and briefly. Later, side remarks reveal different concerns.
What’s underneath
In hierarchical teams, the leader’s framing becomes the team’s by default. Members don’t contest it because the cost feels high. If the coach accepts the framing, the coaching becomes the leader’s instrument.
Avoid here
Accepting the agenda without testing it. Asking “do you agree?” in front of the leader (invites a yes). Exposing the leader publicly.
Example
Marketing team. The leader brings “accountability” as the topic. An anonymous card round shows most members want to discuss unclear priorities. The leader accepts. Accountability issues turn out to be a symptom of the priority problem.
Full situation card: questions, examples, sample exchange
Filed under methods7321
S1.4Wants the coach to fix one personThe team or leader frames the problem as one member
What is happening The team or leader frames the problem as one memberCoach move Contract for team patterns; widen from person to system
In the room
Members glance at one colleague (often absent or quiet). Stories all point to the same person. The leader says in private, “If X changed, we’d be fine.”
What’s underneath
Scapegoating simplifies complexity. The team avoids its own contribution by locating the problem in one person. Even when the person’s behaviour is a real issue, the system usually sustains it.
Avoid here
Agreeing to “fix” anyone. Running a session that becomes a group attack. Ignoring genuine performance issues that the leader needs to manage.
Example
Sales team. Members blamed one colleague for losing a big account. A timeline showed three handoffs failed before that colleague was involved. The team redesigned handoffs.
Full situation card: questions, examples, sample exchange
Filed under methods1219
S1.8Cynical about coaching (“been here before”)The team has had away-days and consultants; expects another one
What is happening The team has had away-days and consultants; expects another oneCoach move Make past experience into design input; promise less, deliver more
In the room
Eye-rolls. Jokes about “trust falls”. A senior member checks emails ostentatiously.
What’s underneath
Cynicism is often disappointed hope. Past interventions created energy that the organisation didn’t sustain. Members protect themselves from another disappointment.
Avoid here
Defending coaching. Overpromising. Treating cynics as obstacles.
Example
Public sector team. The coach asked for a list of what made past interventions useless. It became the “we won’t do” list. Cynicism dropped.
Full situation card: questions, examples, sample exchange
Filed under methods1420
S4.10Disclosure of bullying or harassment in sessionA member raises a serious allegation in the room
What is happening A member raises a serious allegation in the roomCoach move Pause; protect the individual; follow ethical and organisational procedures
In the room
Shock, silence, discomfort. The person may be upset.
What’s underneath
Allegations of bullying or harassment are not team coaching topics; they require formal processes. The coach’s duty is to the person’s safety and the organisation’s procedures.
Avoid here
Investigating in the room. Dismissing. Promising confidentiality you can’t keep.
Example
Hospital team. Coach paused the session, spoke to the member privately, and supported a referral to HR.
Full situation card: questions, examples, sample exchange
Filed under methods31132
S7.2Leader absent or abdicatingThe leader delegates coaching and doesn’t engage
What is happening The leader delegates coaching and doesn’t engageCoach move Recontract; clarify leader’s role
In the room
The leader sends apologies; the team has no authority to decide; members ask “why are we doing this if she’s not here?”
What’s underneath
Leader absence signals low priority and blocks decisions. It may also mean the leader sees the team as the problem and coaching as something done to it.
Avoid here
Coaching around the leader.
Example
Leadership team. The coach recontracted with the leader and sponsor; the leader committed to attending half of each session.
Full situation card: questions, examples, sample exchange
Filed under methods13235
S7.3Leader wants the coach as allyThe leader tries to align the coach with their view
What is happening The leader tries to align the coach with their viewCoach move Hold the contract; coach the leader
In the room
Private calls from the leader, phrases like “between us”, “you see what I mean”. In sessions, the leader looks at the coach for agreement.
What’s underneath
Leaders may seek an ally against the team, especially if they feel isolated. Collusion feels like rapport while it is happening.
Avoid here
Collusion.
Example
CEO. The coach declined to deliver a message and helped the CEO rehearse saying it himself.
Full situation card: questions, examples, sample exchange
Filed under methods132
S7.7Leader asks coach about individualsThe leader asks for information about members
What is happening The leader asks for information about membersCoach move Hold confidentiality; redirect
In the room
A private request, often framed as concern: “Who is resisting?” or “What did X say about me?”
What’s underneath
Leaders may want information to manage people or protect themselves. Sharing it would break the team’s trust and the contract.
Avoid here
Sharing.
Example
Department head. The coach redirected to what the leader was observing; the leader raised it directly in the next session.
Full situation card: questions, examples, sample exchange
Filed under methods132
S7.9Leader leaves mid-engagementThe leader exits during coaching
What is happening The leader exits during coachingCoach move Recontract; timeline; transition
In the room
Uncertainty, loss, questions about the coaching’s future and who now owns the contract.
What’s underneath
Leader departure changes the system and the contract. The team may grieve, worry or feel relief.
Avoid here
Continuing as if nothing changed.
Example
Leadership team. Recontracted with the new leader after a farewell session for the old one.
Full situation card: questions, examples, sample exchange
Filed under methods11148
S10.1Sponsor asks for a report on individualsThe sponsor wants information about team members
What is happening The sponsor wants information about team membersCoach move Hold contract; offer team-level reporting
In the room
Private request.
What’s underneath
Sponsors may misuse coaching for assessment.
Avoid here
Sharing individual data.
Example
CFO sponsor. Accepted monthly theme reports co-written with the team.
Full situation card: questions, examples, sample exchange
Filed under methods147
S10.2Member asks for private coaching mid-engagementA member wants individual coaching from the team coach
What is happening A member wants individual coaching from the team coachCoach move Clarify roles; refer if needed
In the room
Private request.
What’s underneath
Dual roles create confidentiality and fairness issues.
Avoid here
Agreeing without contract.
Example
Member. Referred to another coach for individual work.
Full situation card: questions, examples, sample exchange
Filed under methods14
S10.5Co-coach disagreementCo-coaches disagree on approach
What is happening Co-coaches disagree on approachCoach move Contracting between coaches; review
In the room
Visible tension between coaches.
What’s underneath
Co-coach dynamics affect the team.
Avoid here
Arguing in front of the team.
Example
Co-coaches. Agreed roles and a signal for time-outs.
Full situation card: questions, examples, sample exchange
Filed under methods143
S10.6Team wants training, not coachingThe team asks for content
What is happening The team asks for contentCoach move Clarify modalities; contract
In the room
Requests for models, tools, slides.
What’s underneath
Teams may need training. The coach must distinguish modalities.
Avoid here
Switching modes without contracting.
Example
Team. Agreed a short training input followed by coaching.
Full situation card: questions, examples, sample exchange
Filed under methods17
S10.8Scope creepThe engagement expands without agreement
What is happening The engagement expands without agreementCoach move Recontract
In the room
New requests.
What’s underneath
Scope creep dilutes the work.
Avoid here
Saying yes to everything.
Example
Engagement. Recontracted with the sponsor.
Full situation card: questions, examples, sample exchange
Filed under methods17
S10.12Interview data tempting to useThe coach knows individual information from interviews
What is happening The coach knows individual information from interviewsCoach move Hold confidentiality; feed back only themes
In the room
Coach holds private knowledge.
What’s underneath
Individual data is confidential.
Avoid here
Hints.
Example
Coach. Kept themes anonymous.
Full situation card: questions, examples, sample exchange
Filed under methods81
S7.11The sponsor or a senior stakeholder is in the roomA powerful person attends; the team performs; real issues disappear
What is happening A powerful person attends; the team performs; real issues disappearCoach move Contract the visitor’s role in advance; make the power visible and the purpose clear
In the room
Polished answers, careful language, members watching the visitor. The leader is more formal than usual. The visitor asks questions that sound like assessment.
What’s underneath
When the sponsor or a senior stakeholder joins, the team’s attention shifts from learning to impression management. The “real client” of the commissioning relationship is present, and confidentiality feels at risk. The visitor may not realise their impact. Handled well, their presence can be a powerful “connecting” moment.
Avoid here
Letting the visitor turn the session into a review. Pretending the power isn’t there. Breaking confidentiality agreements by discussing previous sessions.
Example
Leadership team. The CEO joined for 40 minutes with a clear brief: share strategy, then listen. Members asked candid questions; the CEO later said it was the most useful hour of her month.
Full situation card: questions, examples, sample exchange
Filed under methods13297

9Coach mistakes & watch-outs

  • Contracting only with the person who pays.
  • Promising total confidentiality and then being unable to keep it.
  • Letting the leader pre-diagnose the problem and adopting their story.
  • Treating contracting as a single meeting rather than a living agreement.
  • Skipping the explanation of what team coaching is, so the team expects a trainer.

10Team traps

  • Agreeing to everything to get the session over with.
  • The leader nominating “the problem member” during contracting.
  • Sponsor asking for a “quick confidential chat” about individuals.

Three worked problems

1

The CFO who wanted a report. The sponsor asks for a monthly note on “who is engaging”. The coach proposes instead a monthly theme summary co-written with the team, plus three team-level measures. The sponsor accepts after seeing a sample; the team reads the first summary before it goes out, and trust rises noticeably at session two.

2

The leader with a target. In the pre-meeting the leader says, “Honestly, it’s Ravi.” The coach acknowledges the concern, then asks how the leader would want the team to work if Ravi were not the explanation. The agreement is written around team patterns; Ravi’s behaviour later shows up as one strand of a wider pattern of avoided disagreement.

3

The team that had seen it all. Members roll their eyes at the launch. The coach invites them to list what made past interventions useless; the list becomes the “what we won’t do” section of the agreement. Cynicism becomes design input.

Where it comes from

Multi-party contracting comes from organisational consulting and transactional analysis (Fanita English’s “three-cornered contract”) and is central to Peter Hawkins’ systemic team coaching (CID-CLEAR model) and to ICF Team Coaching Competency 3.

My notes

2
Contract and Convene family

Test for Team-ness

Core move: Check whether the group really needs to work as a team before coaching it as one
4 options10 questions4 situations

1What it really is

Many “teams” are really groups of individuals who report to the same person. Richard Hackman and Ruth Wageman found that real teams need a shared purpose, clear boundaries (members know who is on the team), interdependence on a collective task, and some stability of membership. Testing for team-ness means helping the group discover which of these exist. Sometimes the answer reshapes the whole engagement: the group may need to become a team on a few collective tasks while remaining a working group on everything else. That is a healthy outcome, not a failure.

4How it works, deeply

Teams are expensive. They take meeting time, negotiation and trust, and they pay off only when the work genuinely needs combined judgment. When the work does not need it, team-building creates cynicism because members experience it as theatre. Testing for team-ness respects members’ intelligence: it treats the question “should we be a team?” as real. Paradoxically, groups that go through this honestly often discover a small number of genuinely collective tasks, and their commitment to those few is far stronger than to a vague ideal of “collaboration”.

Quick card

Reach for it when
The group reports to one leader but members rarely depend on each other; “teamwork” is the stated goal but nobody can say what the team does together
The move
Ask what the group must deliver together that no member can deliver alone, and coach from there
Watch
Coaching a working group as if it were a team creates frustrating sessions about “collaboration” with no shared work to collaborate on.
Four questions that often open it
  1. What can only this group do, together, that none of you could do alone?
  2. Where does your work genuinely depend on each other?
  3. If this group never met again, what would suffer?
  4. Who is in this team — and is everyone sure?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Hub-and-spoke — each member works one-to-one with the leader; meetings are sequential status reports.
  • Blurred boundary — people disagree about who is “really” on the team; some attend sometimes.
  • Collaboration slogan — the leader wants more teamwork but cannot name a joint deliverable.
  • Two teams in one — a core group of three decides; the others feel like an audience.
  • Senior team trap — functional heads represent their departments rather than leading the enterprise together.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Collective task inventory — list outputs that need two or more members, then pick the ones that truly need all of them.
2Boundary drawing — ask each member to write who they believe is on the team; compare the lists.
3Team / group split — agree which work the team will do together and which it will leave to individuals or subgroups.
4Enterprise hat — invite senior members to speak from the role of “leader of the whole” rather than “head of my function”.

5Where it gets stuck

The leader is attached to the word “team” and hears the question as criticism. Members agree they are not interdependent and then stop engaging. The group lists collective tasks that are really the leader’s tasks delegated in pieces.

6How to move it forward

Frame it as design, not judgment: “Let’s decide where being a team pays off for you.” Push for specificity — a collective task has a shared output and a shared consequence. If there is little, contract for a few high-value joint tasks and a lighter way of working on the rest.

7Questions to ask the team

Core questions
  • What is the work that needs all of you?
  • Who is on this team, and who decides that?
  • When did you last make a decision together that none of you could have made alone?
  • Which of your current meetings need everyone in them?
  • What would you lose by working as individuals?
Going further
  • Where do you represent your function, and where do you lead the whole?
  • What do your stakeholders believe this team is for?
  • Which of your goals would fail if one of you succeeded and another did not?
  • If you designed this team from scratch, who would be in it?
  • What would being “more of a team” actually cost you each week?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S1.7A group, not a teamMembers report to the same leader but rarely depend on each other
What is happening Members report to the same leader but rarely depend on each otherCoach move Test for team-ness; find the few genuinely collective tasks
In the room
Meetings are a round of updates. Members multitask. Questions about “collaboration” produce blank looks.
What’s underneath
Teamwork has costs. If the work doesn’t need interdependence, team coaching on collaboration feels like theatre. The real question is where interdependence would add value.
Avoid here
Running trust-building for a group with no shared task. Making the leader feel judged.
Example
Regional managers. They found two genuinely shared decisions and focused coaching there. Meetings halved.
Full situation card: questions, examples, sample exchange
Filed under methods26
S5.1No shared purposeMembers can’t say why the team exists
What is happening Members can’t say why the team existsCoach move Explore stakeholders and purpose; create a shared statement
In the room
Different answers to “what is this team for?” Confusion and some embarrassment.
What’s underneath
Without purpose, members default to individual goals and politics.
Avoid here
Writing the purpose for the team.
Example
IT leadership. Stakeholder interviews clarified purpose.
Full situation card: questions, examples, sample exchange
Filed under methods6332
S5.5Individual goals beat team goalsIncentives reward individuals; collaboration suffers
What is happening Incentives reward individuals; collaboration suffersCoach move Clarify collective goals; manage the individual/team polarity
In the room
Members protect their own targets; reluctance to help others.
What’s underneath
Incentive structures shape behaviour. Teams can’t collaborate if every reward is individual.
Avoid here
Lecturing about teamwork.
Example
Sales team. Proposed a shared target component; the sponsor agreed.
Full situation card: questions, examples, sample exchange
Filed under methods2176
S8.10Team of teams / cross-team coordinationSeveral teams must deliver together; nobody owns the whole
What is happening Several teams must deliver together; nobody owns the wholeCoach move Coach the system of teams: shared purpose, explicit interfaces, liaison roles and regular cross-team learning
In the room
Representatives defend their own team’s priorities. Coordination meetings are long and report-heavy. Problems appear at the boundaries between teams. Each team blames the others; the programme lead is overwhelmed.
What’s underneath
In a team of teams, the critical work happens between teams. Each team is optimised for itself, and the system is optimised for nobody. Stanley McChrystal’s “team of teams” idea is that the network needs shared consciousness (everyone sees the whole picture) and empowered execution (teams decide locally within shared intent). Fluid membership and dual loyalties make it harder. The client may be the whole network, not one team.
Avoid here
Coaching each team separately and hoping the system improves. More status meetings. Ignoring the different incentives of each team.
Example
Programme team. An ecosystem map and interface agreements cut escalations.
Full situation card: questions, examples, sample exchange
Filed under methods16315392

9Coach mistakes & watch-outs

  • Assuming the label “team” proves there is a team.
  • Running trust exercises for a group with no shared work.
  • Making the leader feel judged for having a working group.
  • Abandoning the engagement instead of re-scoping it.

10Team traps

  • “We’re already a great team” as a way to avoid examining interdependence.
  • Members discovering they are a group and using it as permission to disengage.
  • Inventing collective tasks to please the coach.

Three worked problems

1

The regional heads. Seven country managers meet monthly for status updates. Asked what only they can do together, they name two things: allocating shared marketing budget and handling cross-border key accounts. Coaching focuses on those two decisions; status updates move to a shared document. Meetings drop from three hours to ninety minutes and energy rises.

2

Who is on the team?. Members write the team list individually. Lists range from five to eleven names. The disagreement itself becomes the first coaching topic and leads to a core team of six plus a wider leadership forum.

3

The enterprise hat. A senior team argues about budgets as department heads. The coach asks members to swap seats and speak as “the CEO of the whole organisation”. The tone changes: two members propose cutting their own budgets.

Where it comes from

Richard Hackman’s work on real teams and enabling conditions, Ruth Wageman’s research on senior leadership teams, and Katzenbach and Smith’s distinction between working groups and teams.

My notes

3
Contract and Convene family

Teaming for Fluid Teams

Core move: Build enough trust, shared purpose and a shared picture of the work — fast — when the team won’t stay together long
4 options10 questions6 situations

1What it really is

Amy Edmondson uses the word teaming for teamwork on the fly: people who may never have worked together have to coordinate, learn and deliver, often while also belonging to other teams. Many modern teams are like this — project teams, incident teams, matrix squads, cross-functional task forces. Teaming routines replace the slow build-up of a stable team with a short, deliberate launch: a shared purpose, a picture of who knows what (a “transactive memory”), explicit roles, working agreements in minutes, and built-in learning loops. The coach helps the team design these routines so that the next team can reuse them.

4How it works, deeply

Edmondson’s research in hospitals, construction and product development shows that fluid teams succeed when they combine psychological safety with “situational humility”: everyone accepts that the work is uncertain and that they need each other’s knowledge. Rapid trust (sometimes called swift trust) is built not from shared history but from role clarity, competence signals and early reliability. A shared mental model — who does what, how decisions are made, what the plan is — reduces coordination errors. The coach’s contribution is to make these elements explicit and repeatable, so teaming becomes an organisational capability rather than luck.

Quick card

Reach for it when
Project or task-force teams; members join and leave often; people belong to several teams at once; the team must perform within days, not months
The move
Replace slow team-building with fast “teaming” routines: a short launch, explicit roles, quick ways to learn and a clear way to hand over
Watch
Stable-team methods (long trust-building, months of norming) don’t fit fluid teams. Don’t apologise for speed — design for it.
Four questions that often open it
  1. What do we need to know about each other in the first hour?
  2. What does “done” look like for this team, and when do we disband?
  3. Who knows what — and who needs to know it?
  4. How will we learn quickly while we work?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Constantly changing membership — people rotate in and out of squads every few weeks.
  • Many teams at once — members split their time between three or four teams and feel they belong nowhere.
  • Urgent launch — a task force must deliver in weeks, with no time for a “forming” phase.
  • Cross-boundary team — members bring different professional languages, incentives and bosses.
  • Hand-off fatigue — knowledge is lost every time people leave.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Fast launch — a 60–90 minute kick-off covering purpose, outcome, roles, decision rights, norms and “who knows what”.
2Expertise map — each person states what they know, what they don’t, and what they need from others.
3Learning loops — very short after-action reviews built into the work (daily or weekly).
4Join-and-leave protocol — a standard welcome briefing and a hand-over checklist for people leaving.

5Where it gets stuck

The team skips the launch because “we’re too busy”. Members bring loyalty to their home teams and treat the project as secondary. The launch is done once and never refreshed as people change. Knowledge leaves with each departing member.

6How to move it forward

Keep the launch short and practical, and show the time it saves. Refresh it whenever more than a third of the members have changed. Make the join-and-leave protocol someone’s role. Connect the project to each member’s home-team goals so the dual loyalty is discussed, not hidden.

7Questions to ask the team

Core questions
  • What is this team here to deliver, by when?
  • What does each of us bring, and what do we need?
  • Who decides what?
  • How will we know early if we’re off track?
  • What happens when someone joins or leaves?
Going further
  • Which home-team pressures will compete with this work?
  • What would a newcomer need to know on day one?
  • What do we not yet know that could hurt us?
  • How will we capture what we learn for the next team?
  • When will this team end, and how will we close it well?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S1.9Newly formed teamMembers are new to each other and to the task
What is happening Members are new to each other and to the taskCoach move Build working agreements, purpose and relationships early
In the room
Polite introductions, careful words. People explain their backgrounds. Questions about roles are tentative.
What’s underneath
Tuckman’s “forming” stage: members look for belonging and clarity. Early norms shape the team for years. This is a window of maximum influence.
Avoid here
Rushing into task without relationships. Assuming norms will form well by themselves.
Example
Startup leadership. Spent the first session on user manuals and working agreements. Six months later, they still referred to them.
Full situation card: questions, examples, sample exchange
Filed under methods42663
S8.4Rapid growth / many new membersThe team is growing fast; culture is diluting
What is happening The team is growing fast; culture is dilutingCoach move Explicit norms; onboarding rituals; rhythms
In the room
Many new faces; old-timers nostalgic; confusion about how things work.
What’s underneath
Growth stretches informal norms. What worked when small no longer works.
Avoid here
Nostalgia. Ignoring newcomers.
Example
Startup. Wrote team agreements and an onboarding guide; new joiners got up to speed faster.
Full situation card: questions, examples, sample exchange
Filed under methods426443
S8.10Team of teams / cross-team coordinationSeveral teams must deliver together; nobody owns the whole
What is happening Several teams must deliver together; nobody owns the wholeCoach move Coach the system of teams: shared purpose, explicit interfaces, liaison roles and regular cross-team learning
In the room
Representatives defend their own team’s priorities. Coordination meetings are long and report-heavy. Problems appear at the boundaries between teams. Each team blames the others; the programme lead is overwhelmed.
What’s underneath
In a team of teams, the critical work happens between teams. Each team is optimised for itself, and the system is optimised for nobody. Stanley McChrystal’s “team of teams” idea is that the network needs shared consciousness (everyone sees the whole picture) and empowered execution (teams decide locally within shared intent). Fluid membership and dual loyalties make it harder. The client may be the whole network, not one team.
Avoid here
Coaching each team separately and hoping the system improves. More status meetings. Ignoring the different incentives of each team.
Example
Programme team. An ecosystem map and interface agreements cut escalations.
Full situation card: questions, examples, sample exchange
Filed under methods16315392
S6.12Knowledge loss and key-person dependencyCritical knowledge lives in a few heads; departures cause crises
What is happening Critical knowledge lives in a few heads; departures cause crisesCoach move Make knowledge flow a team responsibility: map dependencies, pair, document and hand over by design
In the room
Anxious jokes about “if she wins the lottery”. Work stalls during holidays. New members take months to become productive. Old decisions can’t be explained.
What’s underneath
Key-person dependency is a systemic risk, not an individual failing. It grows when the team is overloaded, when expertise is rewarded more than sharing, and when membership changes often. It links to fluid teaming and hero culture.
Avoid here
Asking experts to “document everything” on top of their work. Blaming those who leave. Treating it as an IT problem only.
Example
Engineering team. Built a dependency map; three critical systems had one expert. Pairing rotations and a monthly “teach-back” cut the risk in a quarter.
Full situation card: questions, examples, sample exchange
Filed under methods3423944
S8.13A purely virtual teamMembers have never (or rarely) met; all work happens online
What is happening Members have never (or rarely) met; all work happens onlineCoach move Design connection, communication and rituals deliberately — nothing happens by accident online
In the room
Cameras off, chat-heavy, quick transactional meetings. People know each other’s work but not each other. Silence is hard to read. Time zones mean someone is always tired.
What’s underneath
Purely virtual teams differ from hybrid teams: there is no office core, but there is also no informal glue. Trust must be built deliberately, through reliability, responsiveness and some personal connection. Misunderstandings escalate in text. Belonging depends on rituals and norms designed for the medium.
Avoid here
Copying office practices online. Long video sessions. Assuming silence means agreement.
Example
Global consulting team. Introduced a weekly 15-minute “no work talk” call and rotating meeting times. Engagement scores rose.
Full situation card: questions, examples, sample exchange
Filed under methods345415
S8.14Fluid membership: the team keeps changingPeople join and leave constantly; the team never settles
What is happening People join and leave constantly; the team never settlesCoach move Shift from building a stable team to building teaming routines that survive turnover
In the room
New faces every month. Old-timers tired of re-explaining. Newcomers unsure how things work. Norms quietly erode.
What’s underneath
Stable-team models assume membership that lasts. Many teams are now fluid. Without explicit routines, every change resets trust and shared understanding. The answer is not to stop the change but to make joining, working and leaving routine and quick.
Avoid here
Long trust-building processes. Blaming newcomers for not knowing. Treating turnover as temporary when it’s structural.
Example
Agile squads. A one-page team passport and a 60-minute re-launch every quarter. New joiners were productive in days.
Full situation card: questions, examples, sample exchange
Filed under methods3454

9Coach mistakes & watch-outs

  • Running long trust-building exercises for a two-month project.
  • Assuming fluid teams need no coaching.
  • Ignoring members’ other team commitments.
  • Launching once and never re-launching.

10Team traps

  • Treating the project as less important than the “real job”.
  • Waiting for trust instead of building it through reliability.
  • Hoarding knowledge as personal value.

Three worked problems

1

The incident team. A hospital forms incident teams at short notice. The coach helps design a five-minute huddle: names and roles, the goal, the top risk, and “speak up if you see something”. Staff report fewer coordination errors.

2

The rotating squad. Members of a product squad change every six weeks. The team creates a one-page “squad passport” (purpose, current priorities, norms, who knows what). New joiners say they feel productive in days, not weeks.

3

The task force. A cross-functional task force has eight weeks. A 90-minute launch clarifies decision rights and dual loyalties. Weekly 20-minute learning reviews keep it on track.

Where it comes from

Amy Edmondson’s “Teaming” (2012) and research on fluid teams; research on swift trust (Debra Meyerson, Karl Weick and Roderick Kramer) and transactive memory (Daniel Wegner). Related: Stanley McChrystal’s “Team of Teams”.

My notes

4
Contract and Convene family

Co-create Working Agreements

Core move: Let the team write the rules of its own coaching space
4 options10 questions19 situations

1What it really is

Working agreements are the team’s own norms for how it will behave in coaching sessions and, often, beyond them. Co-creating them is not a warm-up exercise. It is the first real piece of collective work the team does with the coach, and it shows in miniature how the team negotiates, who speaks, who defers and what stays unsaid. Good agreements are behavioural, few in number, owned by the team and revisited. They also cover how the team will respond when an agreement is broken, because norms are tested at the moment of breach.

4How it works, deeply

Norms already exist in every team; they are just unwritten. Making them explicit transfers power from the habitual to the chosen. When members write their own agreements, they also give each other permission to name breaches, which is the real goal — the coach should not be the only guardian of the space. Working agreements also give the coach a non-personal way to intervene: “We agreed to finish each other’s points before replying. Shall we try that again?” is very different from “Stop interrupting her.”

Quick card

Reach for it when
First session; after a breach of trust; when new members join; when the same unhelpful behaviour repeats
The move
Ask the team what it needs from each other to do its best thinking here, then make those needs specific and visible
Watch
Generic rules (“respect”, “be open”) cost nothing to agree and protect nothing. Push until each agreement describes a behaviour you could see.
Four questions that often open it
  1. What do you need from each other to think well together today?
  2. What does “respect” look like here when we disagree?
  3. What should happen when someone breaks an agreement?
  4. How will we know if these agreements are working?

2The team’s context

A team needing this method usually shows up in one of these states:

  • New or newly formed team — no shared history of norms; members guess at the rules.
  • Post-incident — a leak, a public humiliation or a blow-up has left people wary.
  • Polite to the point of uselessness — everyone agrees with everything in public.
  • Mixed cultures — members bring very different assumptions about interruption, hierarchy and directness.
  • Hybrid or remote — unspoken rules about cameras, chat and side messages create unequal participation.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Silent-first generation — everyone writes needs individually before any discussion, so the loudest voices do not set the norms.
2Behavioural translation — turn each abstract value into “we will…” and “we won’t…” statements.
3Breach protocol — agree what anyone (not just the coach) can say when a norm is broken.
4Regular review — open each session by asking which agreement is under strain.

5Where it gets stuck

The team produces a list of virtues in ten minutes and moves on. The leader drafts the rules. Agreements are written and never referred to again. Somebody breaks an agreement and nobody, including the coach, says anything.

6How to move it forward

Slow the process down and test each rule with a scenario. Ask who would find each agreement hardest to keep, and why. In the next session, open with a quick review. When the first breach happens, use it — the team learns more from one handled breach than from ten pages of rules.

7Questions to ask the team

Core questions
  • What do you need from this group to say what you really think?
  • What has made meetings unsafe or unproductive in the past?
  • How should we handle disagreement here?
  • What is confidential, and what can you share outside?
  • What will we do when someone breaks one of these?
Going further
  • Which agreement would be hardest for you personally to keep?
  • What unwritten rule already runs this team?
  • What would a new member notice first about how you behave?
  • How should we treat people who are absent?
  • Which of these do you want to carry beyond our sessions?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S1.8Cynical about coaching (“been here before”)The team has had away-days and consultants; expects another one
What is happening The team has had away-days and consultants; expects another oneCoach move Make past experience into design input; promise less, deliver more
In the room
Eye-rolls. Jokes about “trust falls”. A senior member checks emails ostentatiously.
What’s underneath
Cynicism is often disappointed hope. Past interventions created energy that the organisation didn’t sustain. Members protect themselves from another disappointment.
Avoid here
Defending coaching. Overpromising. Treating cynics as obstacles.
Example
Public sector team. The coach asked for a list of what made past interventions useless. It became the “we won’t do” list. Cynicism dropped.
Full situation card: questions, examples, sample exchange
Filed under methods1420
S1.9Newly formed teamMembers are new to each other and to the task
What is happening Members are new to each other and to the taskCoach move Build working agreements, purpose and relationships early
In the room
Polite introductions, careful words. People explain their backgrounds. Questions about roles are tentative.
What’s underneath
Tuckman’s “forming” stage: members look for belonging and clarity. Early norms shape the team for years. This is a window of maximum influence.
Avoid here
Rushing into task without relationships. Assuming norms will form well by themselves.
Example
Startup leadership. Spent the first session on user manuals and working agreements. Six months later, they still referred to them.
Full situation card: questions, examples, sample exchange
Filed under methods42663
S2.1Low trustMembers protect themselves; candour is rare
What is happening Members protect themselves; candour is rareCoach move Build safety in small steps; start with understanding each other
In the room
Careful wording, guarded body language. People check each other’s reactions. Information is shared selectively.
What’s underneath
Low trust may come from past betrayal, competition, unclear intentions or a punishing culture. Trust grows from repeated experiences of vulnerability met with respect.
Avoid here
Forcing vulnerability. Trust-falls. Asking for honesty without protecting it.
Example
Sales leadership. Started with personal histories. Members heard each other’s backgrounds. Three sessions later, they shared performance worries.
Full situation card: questions, examples, sample exchange
Filed under methods25264
S3.3The meeting after the meetingReal conversations happen outside sessions
What is happening Real conversations happen outside sessionsCoach move Bring the corridor conversation into the room
In the room
Agreement in sessions, complaints afterwards. Decisions are undermined.
What’s underneath
The team lacks safety or norms for disagreement in the room. Outside conversations carry the real content.
Avoid here
Accusing people of gossip. Ignoring the pattern.
Example
Executive team. Anonymous cards captured corridor talk. Real issues surfaced.
Full situation card: questions, examples, sample exchange
Filed under methods13436
S3.5Interrupting and talking overMembers cut each other off
What is happening Members cut each other offCoach move Use agreements and process observation
In the room
Overlapping voices, raised volume, unfinished sentences.
What’s underneath
Interrupting may reflect enthusiasm, dominance, cultural norms or not listening. It reduces thinking quality.
Avoid here
Policing individuals. Ignoring it.
Example
Sales team. Agreed to let people finish; the coach used a talking object.
Full situation card: questions, examples, sample exchange
Filed under methods4910
S3.11Remote members invisibleHybrid meetings favour those in the room
What is happening Hybrid meetings favour those in the roomCoach move Agree hybrid norms; equalise participation
In the room
In-room members talk to each other; remote members struggle to join; side conversations.
What’s underneath
Hybrid meetings create unequal access. Remote members lose influence and belonging.
Avoid here
Treating remote members as an afterthought.
Example
Global team. Everyone joined from laptops; remote members spoke more.
Full situation card: questions, examples, sample exchange
Filed under methods4544
S4.4Disagreement turns personalA task disagreement becomes an attack on a person
What is happening A task disagreement becomes an attack on a personCoach move Pause; separate the idea from the person; restore norms
In the room
Tone sharpens, “you” statements, references to character.
What’s underneath
Task conflict turns into relationship conflict when people feel threatened or disrespected.
Avoid here
Ignoring personal attacks.
Example
Strategy team. Coach paused and reminded the team of its agreement; members rephrased.
Full situation card: questions, examples, sample exchange
Filed under methods27314
S4.5Trust breach / leakSomething said in confidence was shared outside
What is happening Something said in confidence was shared outsideCoach move Revisit agreements; repair; rebuild confidentiality
In the room
Shock, anger, suspicion. Members are careful and silent.
What’s underneath
A leak damages the safety of the whole team. Without repair, members will withdraw.
Avoid here
Witch hunts. Ignoring the breach.
Example
Leadership team. Revisited confidentiality agreements; the person responsible apologised.
Full situation card: questions, examples, sample exchange
Filed under methods43125
S4.7Cross-cultural misunderstandingDifferent cultural norms lead to misinterpretations
What is happening Different cultural norms lead to misinterpretationsCoach move Explore cultural assumptions; build shared norms
In the room
Confusion, frustration, members feeling disrespected without knowing why.
What’s underneath
Cultures differ in directness, hierarchy, time and conflict. Behaviours are often misread through one’s own cultural lens.
Avoid here
Stereotyping. Ignoring culture.
Example
Global team. User manuals revealed different norms; the team created communication guidelines.
Full situation card: questions, examples, sample exchange
Filed under methods26224
S4.8Venting about an absent colleagueThe team criticises someone who isn’t present
What is happening The team criticises someone who isn’t presentCoach move Refer to agreements; refocus on the team’s part
In the room
Stories about the absent person; agreement; laughter.
What’s underneath
Venting can release frustration but undermines trust: members wonder what is said about them when they are absent.
Avoid here
Joining. Shaming.
Example
Sales team. Agreed not to discuss absent members without them.
Full situation card: questions, examples, sample exchange
Filed under methods4219
S8.2Hybrid frictionHybrid working creates unequal access and misunderstandings
What is happening Hybrid working creates unequal access and misunderstandingsCoach move Agree hybrid norms; redesign rhythms; map the team in space
In the room
Office group and remote group; separate chats; remote members feel second-class.
What’s underneath
Hybrid creates proximity bias and different experiences of the same team.
Avoid here
Choosing a side (office vs remote).
Example
Consultancy team. Agreed decisions only in shared channels; in-office days aligned.
Full situation card: questions, examples, sample exchange
Filed under methods44412
S8.3Multicultural teamMembers from different cultures bring different norms
What is happening Members from different cultures bring different normsCoach move Surface norms; build shared agreements; treat difference as resource
In the room
Different speaking styles, silence norms, attitudes to hierarchy and time.
What’s underneath
Cultural differences in communication, hierarchy and conflict (Erin Meyer’s culture map) shape team dynamics. Differences can be strengths if they are discussed.
Avoid here
Stereotypes. Assuming one culture is the norm.
Example
Global IT team. Mapped members on directness and hierarchy scales and agreed norms.
Full situation card: questions, examples, sample exchange
Filed under methods26224
S8.4Rapid growth / many new membersThe team is growing fast; culture is diluting
What is happening The team is growing fast; culture is dilutingCoach move Explicit norms; onboarding rituals; rhythms
In the room
Many new faces; old-timers nostalgic; confusion about how things work.
What’s underneath
Growth stretches informal norms. What worked when small no longer works.
Avoid here
Nostalgia. Ignoring newcomers.
Example
Startup. Wrote team agreements and an onboarding guide; new joiners got up to speed faster.
Full situation card: questions, examples, sample exchange
Filed under methods426443
S10.2Member asks for private coaching mid-engagementA member wants individual coaching from the team coach
What is happening A member wants individual coaching from the team coachCoach move Clarify roles; refer if needed
In the room
Private request.
What’s underneath
Dual roles create confidentiality and fairness issues.
Avoid here
Agreeing without contract.
Example
Member. Referred to another coach for individual work.
Full situation card: questions, examples, sample exchange
Filed under methods14
S10.7Member discloses personal crisisA member shares a personal difficulty
What is happening A member shares a personal difficultyCoach move Support; refer; manage team impact
In the room
Emotion; silence.
What’s underneath
Personal crises affect the team; but team coaching is not therapy.
Avoid here
Therapy in the team.
Example
Member. Referred to the employee assistance programme.
Full situation card: questions, examples, sample exchange
Filed under methods314
S10.11Cameras off on videoRemote members turn off cameras
What is happening Remote members turn off camerasCoach move Norms; check-in; rhythms
In the room
Black screens.
What’s underneath
Cameras off may reflect fatigue or disengagement.
Avoid here
Forcing cameras.
Example
Team. Cameras on for check-in only.
Full situation card: questions, examples, sample exchange
Filed under methods4544
S8.11Generational or neurodiversity frictionDifferent ways of thinking, communicating and working cause misunderstanding
What is happening Different ways of thinking, communicating and working cause misunderstandingCoach move Make differences in style explicit and design working norms that let different minds contribute
In the room
Frustration about “how they communicate”. Some members find meetings overwhelming; others find written channels cold. Jokes about generations. Some people mask or withdraw.
What’s underneath
Differences in generation, neurotype and working style are often read as attitude problems (“disrespectful”, “slow”, “difficult”). Many standard team practices — fast open discussion, open-plan noise, unstructured brainstorming — favour some minds over others. Inclusion means designing for difference, not asking people to adapt to one norm. Disclosure of neurodivergence is personal and voluntary.
Avoid here
Stereotyping generations. Asking anyone to disclose a diagnosis. Treating one communication style as “professional” and others as wrong.
Example
Product team. User manuals revealed that two members needed agendas in advance and written follow-ups. The team adopted “agenda 24 hours ahead, decisions in writing” — and everyone benefited.
Full situation card: questions, examples, sample exchange
Filed under methods2642328
S8.13A purely virtual teamMembers have never (or rarely) met; all work happens online
What is happening Members have never (or rarely) met; all work happens onlineCoach move Design connection, communication and rituals deliberately — nothing happens by accident online
In the room
Cameras off, chat-heavy, quick transactional meetings. People know each other’s work but not each other. Silence is hard to read. Time zones mean someone is always tired.
What’s underneath
Purely virtual teams differ from hybrid teams: there is no office core, but there is also no informal glue. Trust must be built deliberately, through reliability, responsiveness and some personal connection. Misunderstandings escalate in text. Belonging depends on rituals and norms designed for the medium.
Avoid here
Copying office practices online. Long video sessions. Assuming silence means agreement.
Example
Global consulting team. Introduced a weekly 15-minute “no work talk” call and rotating meeting times. Engagement scores rose.
Full situation card: questions, examples, sample exchange
Filed under methods345415
S8.14Fluid membership: the team keeps changingPeople join and leave constantly; the team never settles
What is happening People join and leave constantly; the team never settlesCoach move Shift from building a stable team to building teaming routines that survive turnover
In the room
New faces every month. Old-timers tired of re-explaining. Newcomers unsure how things work. Norms quietly erode.
What’s underneath
Stable-team models assume membership that lasts. Many teams are now fluid. Without explicit routines, every change resets trust and shared understanding. The answer is not to stop the change but to make joining, working and leaving routine and quick.
Avoid here
Long trust-building processes. Blaming newcomers for not knowing. Treating turnover as temporary when it’s structural.
Example
Agile squads. A one-page team passport and a 60-minute re-launch every quarter. New joiners were productive in days.
Full situation card: questions, examples, sample exchange
Filed under methods3454

9Coach mistakes & watch-outs

  • Supplying the rules yourself to save time.
  • Accepting abstract words without making them behavioural.
  • Never revisiting the agreements.
  • Being the only person who enforces them.

10Team traps

  • Agreeing to norms that members privately know they won’t keep.
  • Using an agreement as a weapon against a colleague.
  • Spending the whole session on rules to avoid the real topic.

Three worked problems

1

“Respect” made visible. A team lists “respect”. The coach asks what disrespect looked like last month. Members name eye-rolling, laptops open and re-making decisions after the meeting. The final agreements are about those three behaviours.

2

The first breach. In session three, two members start a side chat. A member — not the coach — points to the agreement on the wall. The coach later names this as a turning point: the team is now holding its own space.

3

Remote rules. A hybrid team agrees that if one person is remote, everyone joins from their own laptop. Participation from remote members doubles within two sessions.

Where it comes from

Group work traditions in organisational development, Roger Schwarz’s ground rules in “The Skilled Facilitator”, and team charter practice in team effectiveness research. Part of ICF Team Coaching Competency 4 (co-creating team rules and norms).

My notes

5
Contract and Convene family

Check-in Rounds

Core move: Hear every voice early, before the loudest voice sets the tone
4 options10 questions17 situations

1What it really is

A check-in round invites each member to speak once, briefly, before discussion begins. It gives every voice a place in the room early — research on group dynamics shows that people who speak in the first minutes are more likely to contribute later. It also gives the coach data: the mood of the team, hidden preoccupations, energy levels, and who is holding something back. Nancy Kline’s “Time to Think” approach adds that people think better when they know they will not be interrupted.

4How it works, deeply

The check-in works on three levels. Practically, it moves people from where they were to where they are. Relationally, it says that every person’s presence matters. Systemically, it reveals the field — the emotional climate of the team — which is often more important than any single topic. A coach who listens to the whole round as one piece of data (“most people mentioned tiredness”) can contract the session much more accurately than one who starts with the agenda.

Quick card

Reach for it when
Opening of every session; after a break; when the energy changes; when a few members dominate
The move
Ask one simple question that every member answers in turn, briefly and without discussion
Watch
A check-in that turns into a debate or a status update loses its power. Keep it short and protect the no-response rule.
Four questions that often open it
  1. What are you bringing into the room today?
  2. In one word, how are you arriving?
  3. What has your attention right now that might distract you?
  4. What do you need from this session?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Arriving from chaos — members come in from back-to-back meetings with their heads elsewhere.
  • Unequal airtime — two or three people dominate every discussion.
  • Hidden weather — something has happened (a resignation, a rumour) that nobody has named.
  • Cultural or rank deference — junior or newer members wait to be invited.
  • Remote fatigue — cameras off, energy low, chat silent.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1One-word round — fast and light; good for large teams or tight time.
2Question round — a reflective prompt connected to the work, answered in a sentence or two.
3Scale round — each member gives a number (e.g. energy 1–10) and one sentence.
4Pass allowed — explicitly allow anyone to pass, which paradoxically increases honesty.

5Where it gets stuck

The round becomes a series of status updates. People respond to each other and the round turns into a discussion. The leader speaks first and everyone echoes them. Members give polite, empty answers.

6How to move it forward

Model a short, real answer yourself if appropriate. Ask the leader to go last. Collect the themes out loud at the end of the round (“I heard tired, curious and two people mentioned the restructure”) and ask what the team makes of them before deciding the focus.

7Questions to ask the team

Core questions
  • What’s one thing you need to set down before we begin?
  • What’s on your mind about this team today?
  • What would make this time well spent for you?
  • On a scale of 1–10, how much energy do you have for this?
  • What are you curious about today?
Going further
  • What’s something going well that the team might not know about?
  • What’s one thing you haven’t said in our meetings recently?
  • What are you hoping nobody brings up today?
  • If the team had a weather report today, what would it be?
  • What have you noticed about us since last time?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S1.3Polite, flat and “fine”Everyone is pleasant; nothing real is said; energy is low
What is happening Everyone is pleasant; nothing real is said; energy is lowCoach move Name the pattern lightly; use anonymous or individual ways to surface the real material
In the room
Smiles, agreement, short answers. Nobody disagrees. The conversation feels like a corporate brochure. Time passes slowly.
What’s underneath
Pseudo-harmony (what Scott Peck called pseudo-community) protects the team from conflict and exposure. It is often a sign of low safety, not high trust. The real conversations happen elsewhere.
Avoid here
Pushing hard for “honesty” before any safety exists. Accepting “fine” as the full picture. Moralising about politeness.
Example
Finance team. Interviews revealed tensions, but the first session was all smiles. The coach shared the interview themes anonymously. Silence, then a member said, “Yes, that’s true.” The real work started.
Full situation card: questions, examples, sample exchange
Filed under methods513815
S1.6Firefighting / crisis modeUrgent operational issues hijack every session
What is happening Urgent operational issues hijack every sessionCoach move Acknowledge the crisis; separate what needs solving now from what the crisis reveals about the team
In the room
Phones buzz. Members arrive late, leave early. Every topic becomes today’s fire. The tone is tense and fast.
What’s underneath
Some teams live in permanent crisis because the crisis protects them from strategic or relational work. Others are genuinely overwhelmed. The coach needs to tell the difference without dismissing the urgency.
Avoid here
Ignoring a real emergency. Turning the session into operational problem-solving. Lecturing about firefighting.
Example
IT operations. A major outage hit on session day. The coach rescheduled. The next session started with “what did the outage teach you about the team?”
Full situation card: questions, examples, sample exchange
Filed under methods7385
S2.2Fear after layoffs or restructuringMembers are anxious about their jobs; survivor guilt; silence
What is happening Members are anxious about their jobs; survivor guilt; silenceCoach move Acknowledge the fear; make space for what happened before moving on
In the room
Quiet. People look tired. Questions about future plans are met with “who knows”. Some members are overly busy.
What’s underneath
Layoffs create grief, fear and survivor guilt. The team may withdraw, avoid risk and protect itself. Ignoring the emotional impact makes any coaching superficial.
Avoid here
Jumping to vision or performance. Pretending things are normal. Making promises about job security.
Example
Tech team. After 20% cuts, the first session was a check-in and timeline. Members talked about colleagues who left. The next session moved to priorities with more energy.
Full situation card: questions, examples, sample exchange
Filed under methods25511
S2.3Exhausted / burnoutMembers are depleted; coaching feels like another demand
What is happening Members are depleted; coaching feels like another demandCoach move Make load visible; decide what to stop; protect energy
In the room
Yawns, slumped posture, cameras off. People arrive late from back-to-back meetings. Reactions are slow.
What’s underneath
Burnout is a team and system issue, not only individual. Coaching that adds demands will fail. Reducing load is the intervention.
Avoid here
Asking for more commitments. Resilience lectures. Ignoring systemic causes.
Example
Nursing team. Used the session to list all recurring tasks and stopped three.
Full situation card: questions, examples, sample exchange
Filed under methods38544
S2.4Grief after a lossA colleague has died, left suddenly or been seriously ill
What is happening A colleague has died, left suddenly or been seriously illCoach move Pause the agenda; create space to acknowledge the loss
In the room
Silence, tearfulness, avoidance. Some members want to “get on with work”; others can’t.
What’s underneath
Teams grieve collectively. Unacknowledged grief shows up as irritability, withdrawal or loss of purpose. People grieve differently; the team needs room for differences.
Avoid here
Rushing to tasks. Forcing emotional sharing. Acting as a therapist.
Example
Research team. A colleague died. The session became a remembrance; the team decided to name a project after her.
Full situation card: questions, examples, sample exchange
Filed under methods5113145
S2.7Anger at the organisationThe team is angry about decisions made above
What is happening The team is angry about decisions made aboveCoach move Acknowledge the anger; separate venting from influence; connect to the system
In the room
Raised voices, strong language, members agreeing loudly. Energy is high but directed outward.
What’s underneath
Anger signals perceived injustice. It contains energy that can be redirected toward influence. But staying in anger creates a victim-persecutor dynamic.
Avoid here
Defending the organisation. Shutting down anger. Letting the whole session become venting.
Example
Engineering team. Angry about a reorganisation. Ten minutes venting, then mapped what they could influence. Wrote a joint proposal.
Full situation card: questions, examples, sample exchange
Filed under methods16195
S2.10Disengaged / going through the motionsMembers show up physically but not mentally
What is happening Members show up physically but not mentallyCoach move Reconnect to purpose and to what each person cares about
In the room
Cameras off, multitasking, minimal participation, no questions.
What’s underneath
Disengagement often means the work has lost meaning, or members feel unheard. It may also signal burnout or plans to leave.
Avoid here
Lecturing about engagement. Assuming laziness.
Example
Admin team. Purpose exploration revealed members felt invisible to stakeholders. Stakeholder feedback restored meaning.
Full situation card: questions, examples, sample exchange
Filed under methods653345
S3.1One or two voices dominateA few members do most of the talking
What is happening A few members do most of the talkingCoach move Structure participation; make the pattern visible
In the room
Two people speak; others nod or look at phones. Ideas from quieter members are lost.
What’s underneath
Dominance may come from rank, extroversion, expertise or anxiety. Quieter members may feel unheard or unsafe. The team loses diverse input.
Avoid here
Shaming dominant members. Calling on quiet members suddenly.
Example
Strategy team. Coach shared airtime count; dominant members agreed to speak second.
Full situation card: questions, examples, sample exchange
Filed under methods591015
S3.2Silent membersSome members rarely speak
What is happening Some members rarely speakCoach move Use structure and invitation; understand the silence
In the room
The same people silent each session. They may look engaged or withdrawn.
What’s underneath
Silence can mean thinking, disagreement, cultural norms, low safety, or disengagement. Don’t assume.
Avoid here
Putting people on the spot. Assuming silence means agreement.
Example
Multicultural team. Writing first and rounds increased contributions.
Full situation card: questions, examples, sample exchange
Filed under methods5282515
S3.8Joking to deflectHumour shuts down serious discussion
What is happening Humour shuts down serious discussionCoach move Notice the pattern lightly; invite what’s under the joke
In the room
Laughs at key moments; tension released before issues are explored.
What’s underneath
Humour is a healthy team resource, but also a defence. Jokes at critical moments avoid discomfort.
Avoid here
Banning humour. Shaming jokers.
Example
Sales team. Coach noted jokes appeared whenever targets were discussed; the team talked about pressure.
Full situation card: questions, examples, sample exchange
Filed under methods9135
S3.10Advice-giving instead of thinkingMembers jump to solutions for each other
What is happening Members jump to solutions for each otherCoach move Slow down; ask questions; use structured thinking
In the room
Someone shares a problem; others immediately suggest fixes.
What’s underneath
Advice-giving is quick and well-meant but can block thinking and ownership.
Avoid here
Lecturing about coaching. Shutting down all suggestions.
Example
Leadership team. Practised “questions only” rounds; quality of thinking improved.
Full situation card: questions, examples, sample exchange
Filed under methods954142
S3.11Remote members invisibleHybrid meetings favour those in the room
What is happening Hybrid meetings favour those in the roomCoach move Agree hybrid norms; equalise participation
In the room
In-room members talk to each other; remote members struggle to join; side conversations.
What’s underneath
Hybrid meetings create unequal access. Remote members lose influence and belonging.
Avoid here
Treating remote members as an afterthought.
Example
Global team. Everyone joined from laptops; remote members spoke more.
Full situation card: questions, examples, sample exchange
Filed under methods4544
S7.1Leader dominatesThe leader talks most; the team defers
What is happening The leader talks most; the team defersCoach move Contract leader role; structure participation; observe
In the room
The leader speaks first and longest. Members nod, glance at the leader before answering, and rarely contradict.
What’s underneath
Leader dominance limits team thinking, even when the leader wants input. Members read status signals and edit themselves.
Avoid here
Undermining the leader publicly.
Example
CEO team. The CEO agreed to speak last; debate quality rose noticeably within two sessions.
Full situation card: questions, examples, sample exchange
Filed under methods3259
S8.5Key member leavingAn important member is leaving
What is happening An important member is leavingCoach move Acknowledge; redistribute roles; capture knowledge
In the room
Sadness, worry, role gaps.
What’s underneath
Losing a key member affects roles, relationships and identity.
Avoid here
Ignoring the loss.
Example
Product team. A farewell round and role negotiation covered the gap.
Full situation card: questions, examples, sample exchange
Filed under methods5391145
S8.6External crisisA sudden external event threatens the team
What is happening A sudden external event threatens the teamCoach move Contract the session around the crisis; plan; support
In the room
High stress, urgency, focus on immediate response.
What’s underneath
Crises demand rapid response but also reveal team strengths and weaknesses.
Avoid here
Forcing reflection during the acute phase.
Example
Pandemic response. Short weekly check-ins and pre-mortems helped the team act fast.
Full situation card: questions, examples, sample exchange
Filed under methods7345
S10.10Coach’s own anxiety in the groupThe coach feels overwhelmed by the group
What is happening The coach feels overwhelmed by the groupCoach move Self-regulation; supervision; process
In the room
Coach notices racing thoughts, over-talking.
What’s underneath
Groups amplify anxiety.
Avoid here
Over-controlling.
Example
Coach. Paused, breathed, asked the team what they noticed.
Full situation card: questions, examples, sample exchange
Filed under methods95
S10.11Cameras off on videoRemote members turn off cameras
What is happening Remote members turn off camerasCoach move Norms; check-in; rhythms
In the room
Black screens.
What’s underneath
Cameras off may reflect fatigue or disengagement.
Avoid here
Forcing cameras.
Example
Team. Cameras on for check-in only.
Full situation card: questions, examples, sample exchange
Filed under methods4544

9Coach mistakes & watch-outs

  • Commenting on each person’s check-in.
  • Letting the leader go first by default.
  • Skipping the round when time is short — exactly when it is most useful.
  • Ignoring the pattern in the round and going straight to the agenda.

10Team traps

  • Using the check-in to give a speech.
  • Saying “fine” every time.
  • Using humour to avoid anything real.

Three worked problems

1

The unnamed resignation. In the round, four of seven members say “distracted”. The coach reflects the pattern and asks what is behind it. A respected colleague resigned yesterday. The planned session on priorities becomes a session on what the loss means for the team — and priorities are reshaped in the last half hour.

2

Leader last. A leader always opened discussions. The coach asks her to check in last. For the first time, two quieter members speak about workload before hearing her view.

3

Remote round. On a video call, the coach uses a name-by-name round with cameras on for just the round. Chat participation for the rest of the session triples.

Where it comes from

Group and therapeutic traditions, Nancy Kline’s “Thinking Environment”, and facilitation practice (Liberating Structures). Supports ICF Team Coaching Competency 4 (encouraging contribution from all members).

My notes

6
Contract and Convene family

Purpose and Stakeholder Expectations

Core move: Ask why the team exists and who it serves before asking how it should behave
4 options10 questions14 situations

1What it really is

Teams exist to create value for others — customers, the wider organisation, communities. Peter Hawkins’ systemic team coaching starts not with relationships but with commissioning: what the team has been asked to deliver, and by whom. This method helps the team identify its stakeholders, understand their expectations, and co-create a purpose that serves them. It shifts the conversation from “how do we get on better?” to “what are we here to achieve together?”, which often resolves relationship problems more effectively than working on them directly.

4How it works, deeply

Purpose is the gravity that holds a team together. Without it, members fall back on their own goals and on politics. With it, conflicts become debates about how best to serve someone, which is easier to resolve than debates about who is right. Looking outward also reduces defensiveness: it is easier to hear “our stakeholders find us slow” than “you are slow”. And because stakeholders are external, the team can unite around them instead of dividing around each other.

Quick card

Reach for it when
The team is busy but unclear about why; members argue about priorities; stakeholders are unhappy; a new leader or strategy arrives
The move
Look outward first: who needs what from this team, and what is the team uniquely here to create?
Watch
Purpose statements written only from inside the team often describe what members enjoy, not what the organisation needs.
Four questions that often open it
  1. Who are this team’s most important stakeholders?
  2. What do they need from you that only you can provide?
  3. What would be lost if this team disappeared tomorrow?
  4. How would your stakeholders describe your purpose?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Busy without direction — high activity, low sense of contribution.
  • Inward-looking — all conversation is about internal frustrations; customers are rarely mentioned.
  • Mixed signals — different stakeholders want different things and the team is trying to satisfy everyone.
  • Inherited purpose — the mission statement was written years ago and nobody uses it.
  • New strategy — the organisation’s direction has changed and the team has not caught up.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Stakeholder map — draw everyone who has a stake in the team, their needs and their current satisfaction.
2Stakeholder interviews — members interview stakeholders and bring back their voices.
3Purpose drafting — each member writes the team’s purpose in one sentence; the team compares and blends.
4Future-back test — ask what stakeholders would say about the team in two years if it fulfilled its purpose.

5Where it gets stuck

The team produces a generic purpose statement that could describe any team. Members say they already know their stakeholders but cannot describe their needs. Stakeholder input is collected and then ignored. The leader’s purpose is adopted without debate.

6How to move it forward

Ask for evidence: what have stakeholders actually said? Invite a stakeholder into a session, or role-play their chair. Test the purpose statement: would it help the team say no to something? If not, it is not yet a purpose.

7Questions to ask the team

Core questions
  • Who depends on this team?
  • What do they need from you?
  • What do they get today, and what are they missing?
  • What can only this team do?
  • How does your purpose connect to the organisation’s strategy?
Going further
  • Which stakeholder would be hardest to satisfy, and why?
  • What would your customers say if they sat in on this meeting?
  • What will matter about this team in five years?
  • Which purpose would you be proud to tell your family about?
  • What would your purpose lead you to stop doing?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S1.1Sent by the sponsorThe team attends because someone above asked; low ownership of the agenda
What is happening The team attends because someone above asked; low ownership of the agendaCoach move Name the three clients; find the team’s own stake in the work
In the room
Arms folded, polite questions about “what HR wants”. Members look at the leader to see how seriously to take this. Energy is dutiful, not curious.
What’s underneath
An assigned engagement feels like a judgment. Members protect themselves until they know whose side the coach is on and whether anything they say will travel upward. Ownership cannot be demanded; it is found when the team locates something it wants from the work.
Avoid here
Defending the sponsor. Launching into diagnostics before the contract is clear. Pretending the request came from the team.
Example
Operations leadership team. The COO commissions coaching after two missed targets. The team opens with sarcasm. The coach shares the sponsor’s brief word for word and asks what they would change. They rewrite the objectives around cross-shift hand-offs — the issue they had been raising for a year.
Full situation card: questions, examples, sample exchange
Filed under methods176
S1.7A group, not a teamMembers report to the same leader but rarely depend on each other
What is happening Members report to the same leader but rarely depend on each otherCoach move Test for team-ness; find the few genuinely collective tasks
In the room
Meetings are a round of updates. Members multitask. Questions about “collaboration” produce blank looks.
What’s underneath
Teamwork has costs. If the work doesn’t need interdependence, team coaching on collaboration feels like theatre. The real question is where interdependence would add value.
Avoid here
Running trust-building for a group with no shared task. Making the leader feel judged.
Example
Regional managers. They found two genuinely shared decisions and focused coaching there. Meetings halved.
Full situation card: questions, examples, sample exchange
Filed under methods26
S1.9Newly formed teamMembers are new to each other and to the task
What is happening Members are new to each other and to the taskCoach move Build working agreements, purpose and relationships early
In the room
Polite introductions, careful words. People explain their backgrounds. Questions about roles are tentative.
What’s underneath
Tuckman’s “forming” stage: members look for belonging and clarity. Early norms shape the team for years. This is a window of maximum influence.
Avoid here
Rushing into task without relationships. Assuming norms will form well by themselves.
Example
Startup leadership. Spent the first session on user manuals and working agreements. Six months later, they still referred to them.
Full situation card: questions, examples, sample exchange
Filed under methods42663
S2.10Disengaged / going through the motionsMembers show up physically but not mentally
What is happening Members show up physically but not mentallyCoach move Reconnect to purpose and to what each person cares about
In the room
Cameras off, multitasking, minimal participation, no questions.
What’s underneath
Disengagement often means the work has lost meaning, or members feel unheard. It may also signal burnout or plans to leave.
Avoid here
Lecturing about engagement. Assuming laziness.
Example
Admin team. Purpose exploration revealed members felt invisible to stakeholders. Stakeholder feedback restored meaning.
Full situation card: questions, examples, sample exchange
Filed under methods653345
S5.1No shared purposeMembers can’t say why the team exists
What is happening Members can’t say why the team existsCoach move Explore stakeholders and purpose; create a shared statement
In the room
Different answers to “what is this team for?” Confusion and some embarrassment.
What’s underneath
Without purpose, members default to individual goals and politics.
Avoid here
Writing the purpose for the team.
Example
IT leadership. Stakeholder interviews clarified purpose.
Full situation card: questions, examples, sample exchange
Filed under methods6332
S5.2Competing prioritiesMembers pull in different directions
What is happening Members pull in different directionsCoach move Make priorities visible; decide together; manage polarities
In the room
Arguments about what matters most; members defend their areas.
What’s underneath
Competing priorities often reflect unclear strategy or misaligned incentives.
Avoid here
Deciding for the team.
Example
Product team. Portfolio wall led to stopping two projects.
Full situation card: questions, examples, sample exchange
Filed under methods38176
S5.3Goals imposed from aboveTargets set without team input; low ownership
What is happening Targets set without team input; low ownershipCoach move Explore what the team can own; test assumptions; connect to stakeholders
In the room
Frustration, cynicism, low commitment.
What’s underneath
Imposed goals reduce autonomy and motivation. The team may resist or comply without commitment.
Avoid here
Defending the targets.
Example
Sales team. Team immunity map revealed assumption that pushing back was pointless; they tested it.
Full situation card: questions, examples, sample exchange
Filed under methods18616
S5.4Strategy unclearThe team doesn’t understand the organisation’s direction
What is happening The team doesn’t understand the organisation’s directionCoach move Clarify what is known; connect to stakeholders; build preferred future
In the room
Questions, confusion, speculation.
What’s underneath
Unclear strategy makes team prioritisation hard. The team may need to seek clarity or create its own direction.
Avoid here
Inventing strategy for the organisation.
Example
Regional team. Invited the strategy director to a session.
Full situation card: questions, examples, sample exchange
Filed under methods6163324
S5.5Individual goals beat team goalsIncentives reward individuals; collaboration suffers
What is happening Incentives reward individuals; collaboration suffersCoach move Clarify collective goals; manage the individual/team polarity
In the room
Members protect their own targets; reluctance to help others.
What’s underneath
Incentive structures shape behaviour. Teams can’t collaborate if every reward is individual.
Avoid here
Lecturing about teamwork.
Example
Sales team. Proposed a shared target component; the sponsor agreed.
Full situation card: questions, examples, sample exchange
Filed under methods2176
S5.6Disagree on what success meansMembers use different definitions of success
What is happening Members use different definitions of successCoach move Build a shared preferred future; use data
In the room
Arguments about outcomes; “we’re doing well” vs “we’re failing”.
What’s underneath
Without a shared definition of success, teams pull in different directions.
Avoid here
Choosing one definition.
Example
Software team. Defined success as reliable releases and customer satisfaction.
Full situation card: questions, examples, sample exchange
Filed under methods338623
S5.8Purpose drift after successAfter achieving goals, the team loses direction
What is happening After achieving goals, the team loses directionCoach move Revisit purpose; harvest learning; set new goals
In the room
Low energy, uncertainty, “what now?”
What’s underneath
Achievement can create a vacuum. Teams need a new purpose or a renewed one.
Avoid here
Rushing to new goals without reflection.
Example
Project team. Harvested learning and set a new purpose.
Full situation card: questions, examples, sample exchange
Filed under methods61146
S5.9Purpose conflicts with valuesMembers feel the team’s goals clash with their values
What is happening Members feel the team’s goals clash with their valuesCoach move Hear the minority voice; explore values and purpose
In the room
Moral language, discomfort, some members withdraw.
What’s underneath
Values conflicts are deep and can lead to disengagement or departure.
Avoid here
Dismissing concerns.
Example
Pharma team. Concern about marketing practices was escalated.
Full situation card: questions, examples, sample exchange
Filed under methods28617
S8.7Stakeholders unhappyStakeholders complain about the team
What is happening Stakeholders complain about the teamCoach move Zoom to stakeholders; close the loop; revisit purpose
In the room
Defensiveness; stories about unreasonable stakeholders.
What’s underneath
Stakeholder dissatisfaction is valuable data, even when partly unfair.
Avoid here
Dismissing complaints.
Example
IT team. Stakeholder interviews led to a new intake process.
Full situation card: questions, examples, sample exchange
Filed under methods16476
S5.10A good team that wants to become greatNo crisis, solid results — the team wants to raise its game
What is happening No crisis, solid results — the team wants to raise its gameCoach move Start from strengths, find the next level of value for stakeholders, and stretch with small, ambitious experiments
In the room
Relaxed, confident, curious. Members are proud of results and a little bored. They ask, “What’s next for us?”
What’s underneath
High-performing teams risk the comfort zone and the plateau. The challenge is not repair but stretch: more value for stakeholders, more learning, more distributed leadership. Problem-focused methods can feel wrong here; appreciative and future-focused methods fit better.
Avoid here
Inventing problems so the coaching has something to fix. Generic team-building. Complacent celebration with no stretch.
Example
Finance leadership team. Strong internally, weak at “connecting”. Stakeholder interviews revealed an appetite for strategic advice. The team redefined its purpose and doubled its strategic work.
Full situation card: questions, examples, sample exchange
Filed under methods863046

9Coach mistakes & watch-outs

  • Starting with internal relationships when the real issue is unclear purpose.
  • Wordsmithing a statement instead of exploring meaning.
  • Letting purpose remain abstract and untested.
  • Treating stakeholders as an audience rather than as part of the team’s system.

10Team traps

  • Defining purpose as what the team likes doing.
  • Blaming stakeholders for unreasonable demands.
  • Agreeing a purpose and changing nothing.

Three worked problems

1

The IT team that served itself. Asked who their stakeholders are, an IT leadership team names other IT teams first. Interviews with business units reveal frustration with slow response. The team rewrites its purpose around “making it easy for the business to move fast” and redesigns its intake process.

2

One sentence each. Eight members write the purpose in one sentence. Answers range from “keep the lights on” to “transform customer experience”. The gap becomes the real conversation and leads to an explicit two-part purpose.

3

The empty chair stakeholder. The coach places an empty chair for “the customer”. Members speak from it. The tone changes from defending the team to hearing what the customer experiences.

Where it comes from

Peter Hawkins’ five disciplines of systemic team coaching (commissioning, clarifying, co-creating, connecting, core learning) and stakeholder-centred approaches to team effectiveness.

My notes

7
Contract and Convene family

Contract the Session Live

Core move: Agree what this group wants from this session, and whose agenda it really is
4 options10 questions9 situations

1What it really is

Engagement contracting sets the overall direction. Session contracting agrees the focus of today. In team coaching this is harder than in individual coaching, because several people bring different topics and different senses of urgency. Live contracting means proposing a focus, testing it with the whole team, and agreeing a visible outcome for the session. It also means being willing to re-contract mid-session when the room’s energy clearly moves somewhere else.

4How it works, deeply

Contracting the session is also a diagnostic act. How the team chooses its topic shows how it makes decisions, who has influence, and what it avoids. The coach does not need to control the choice; they need to make the choosing visible. When the team owns the agenda, members are more willing to engage, because they are working on their problem rather than performing for someone else’s.

Quick card

Reach for it when
Start of each session; when the agenda is too full; when energy shifts mid-session; when the leader’s agenda dominates
The move
Ask what the team needs from today, check it is a team topic, and re-contract when the energy moves
Watch
A session agenda set entirely by the leader or the sponsor turns coaching into a meeting the coach happens to facilitate.
Four questions that often open it
  1. What does this team most need from today?
  2. Is this a team issue or an issue for some of you?
  3. What would make this session worth your time?
  4. How will we know we’ve got there?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Agenda overload — members arrive with eight topics and ninety minutes.
  • Leader’s list — the agenda arrives pre-written by the leader.
  • Silent disagreement — some members nod at the topic but look disengaged.
  • Emerging issue — a new tension appears mid-session and the planned topic loses energy.
  • Repeat topic — the team keeps choosing the same comfortable topic.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Topic harvest and vote — list topics, then use dot-voting to choose.
2Team-level test — ask whether each topic needs the whole team or a subgroup.
3Outcome framing — agree what “done” looks like for today: a decision, an insight, a draft, a commitment.
4Mid-point check — ask halfway whether the focus still serves the team.

5Where it gets stuck

Every topic is “urgent”. The team cannot choose and asks the coach to decide. The chosen topic belongs to two people while the rest watch. The team picks the safe topic to avoid the real one.

6How to move it forward

Name the process: “It looks hard to choose. What does that tell us?” Use a structure — dot voting, a 2×2 of impact and urgency. If a topic belongs to a subgroup, park it for them. If you sense avoidance, ask “Which topic are we not choosing, and why?”

7Questions to ask the team

Core questions
  • What does the team need to make progress on today?
  • Which of these needs all of you?
  • What outcome would make this time useful?
  • What would you be disappointed not to cover?
  • Where is the energy right now?
Going further
  • Which topic are we avoiding?
  • If we only had twenty minutes, what would you work on?
  • Whose agenda is this?
  • What has changed since we agreed the plan?
  • Is this still the right conversation?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S1.1Sent by the sponsorThe team attends because someone above asked; low ownership of the agenda
What is happening The team attends because someone above asked; low ownership of the agendaCoach move Name the three clients; find the team’s own stake in the work
In the room
Arms folded, polite questions about “what HR wants”. Members look at the leader to see how seriously to take this. Energy is dutiful, not curious.
What’s underneath
An assigned engagement feels like a judgment. Members protect themselves until they know whose side the coach is on and whether anything they say will travel upward. Ownership cannot be demanded; it is found when the team locates something it wants from the work.
Avoid here
Defending the sponsor. Launching into diagnostics before the contract is clear. Pretending the request came from the team.
Example
Operations leadership team. The COO commissions coaching after two missed targets. The team opens with sarcasm. The coach shares the sponsor’s brief word for word and asks what they would change. They rewrite the objectives around cross-shift hand-offs — the issue they had been raising for a year.
Full situation card: questions, examples, sample exchange
Filed under methods176
S1.2The leader’s agenda dressed as the team’sThe leader frames the topic; members nod but energy is elsewhere
What is happening The leader frames the topic; members nod but energy is elsewhereCoach move Test the agenda with the whole team before working on it
In the room
The leader introduces “our priorities”. Members look at the table. When asked directly, they agree quickly and briefly. Later, side remarks reveal different concerns.
What’s underneath
In hierarchical teams, the leader’s framing becomes the team’s by default. Members don’t contest it because the cost feels high. If the coach accepts the framing, the coaching becomes the leader’s instrument.
Avoid here
Accepting the agenda without testing it. Asking “do you agree?” in front of the leader (invites a yes). Exposing the leader publicly.
Example
Marketing team. The leader brings “accountability” as the topic. An anonymous card round shows most members want to discuss unclear priorities. The leader accepts. Accountability issues turn out to be a symptom of the priority problem.
Full situation card: questions, examples, sample exchange
Filed under methods7321
S1.5Too many topics at onceThe team arrives with a long list; everything feels urgent
What is happening The team arrives with a long list; everything feels urgentCoach move Harvest, prioritise, and test which topics need the whole team
In the room
Flip chart fills quickly. Members talk over each other to add items. The leader looks anxious about time.
What’s underneath
An overloaded agenda can be a sign of overload in the work, or a way to avoid depth. Covering everything means engaging with nothing.
Avoid here
Trying to cover everything. Choosing for the team. Letting the leader decide alone.
Example
Product leadership. Twelve topics. Dot voting gave two clear priorities; four topics belonged to subgroups. The session achieved a real decision for the first time in months.
Full situation card: questions, examples, sample exchange
Filed under methods738
S1.6Firefighting / crisis modeUrgent operational issues hijack every session
What is happening Urgent operational issues hijack every sessionCoach move Acknowledge the crisis; separate what needs solving now from what the crisis reveals about the team
In the room
Phones buzz. Members arrive late, leave early. Every topic becomes today’s fire. The tone is tense and fast.
What’s underneath
Some teams live in permanent crisis because the crisis protects them from strategic or relational work. Others are genuinely overwhelmed. The coach needs to tell the difference without dismissing the urgency.
Avoid here
Ignoring a real emergency. Turning the session into operational problem-solving. Lecturing about firefighting.
Example
IT operations. A major outage hit on session day. The coach rescheduled. The next session started with “what did the outage teach you about the team?”
Full situation card: questions, examples, sample exchange
Filed under methods7385
S8.6External crisisA sudden external event threatens the team
What is happening A sudden external event threatens the teamCoach move Contract the session around the crisis; plan; support
In the room
High stress, urgency, focus on immediate response.
What’s underneath
Crises demand rapid response but also reveal team strengths and weaknesses.
Avoid here
Forcing reflection during the acute phase.
Example
Pandemic response. Short weekly check-ins and pre-mortems helped the team act fast.
Full situation card: questions, examples, sample exchange
Filed under methods7345
S10.3Coach pulled into expert roleThe team wants the coach to give answers
What is happening The team wants the coach to give answersCoach move Return ownership; process observation; fade the coach
In the room
“What do you think?” “What would you do?”
What’s underneath
Teams may want answers to avoid responsibility.
Avoid here
Becoming the consultant without contracting.
Example
Leadership team. The coach offered a model with permission, then returned to coaching.
Full situation card: questions, examples, sample exchange
Filed under methods9748
S10.6Team wants training, not coachingThe team asks for content
What is happening The team asks for contentCoach move Clarify modalities; contract
In the room
Requests for models, tools, slides.
What’s underneath
Teams may need training. The coach must distinguish modalities.
Avoid here
Switching modes without contracting.
Example
Team. Agreed a short training input followed by coaching.
Full situation card: questions, examples, sample exchange
Filed under methods17
S10.8Scope creepThe engagement expands without agreement
What is happening The engagement expands without agreementCoach move Recontract
In the room
New requests.
What’s underneath
Scope creep dilutes the work.
Avoid here
Saying yes to everything.
Example
Engagement. Recontracted with the sponsor.
Full situation card: questions, examples, sample exchange
Filed under methods17
S7.11The sponsor or a senior stakeholder is in the roomA powerful person attends; the team performs; real issues disappear
What is happening A powerful person attends; the team performs; real issues disappearCoach move Contract the visitor’s role in advance; make the power visible and the purpose clear
In the room
Polished answers, careful language, members watching the visitor. The leader is more formal than usual. The visitor asks questions that sound like assessment.
What’s underneath
When the sponsor or a senior stakeholder joins, the team’s attention shifts from learning to impression management. The “real client” of the commissioning relationship is present, and confidentiality feels at risk. The visitor may not realise their impact. Handled well, their presence can be a powerful “connecting” moment.
Avoid here
Letting the visitor turn the session into a review. Pretending the power isn’t there. Breaking confidentiality agreements by discussing previous sessions.
Example
Leadership team. The CEO joined for 40 minutes with a clear brief: share strategy, then listen. Members asked candid questions; the CEO later said it was the most useful hour of her month.
Full situation card: questions, examples, sample exchange
Filed under methods13297

9Coach mistakes & watch-outs

  • Accepting the leader’s agenda without testing it with the team.
  • Letting the topic be too big for the time.
  • Never re-contracting even when the energy has clearly moved.
  • Choosing the topic yourself because the team is slow.

10Team traps

  • Choosing the comfortable topic.
  • Insisting that every individual topic gets airtime.
  • Making the coach decide, then disowning the choice.

Three worked problems

1

Eight topics, one session. A leadership team lists eight topics. Dot voting gives two clear winners. One turns out to involve only three members and is passed to them. The team spends the session on cross-functional hand-offs and leaves with one agreed change.

2

The shift. Halfway through a planning session, a member mentions a rumour of a merger. The room changes. The coach names the shift and asks whether to continue planning or explore the rumour. The team chooses fifteen minutes on the rumour, then returns to planning with renewed focus.

3

The leader’s list. The leader arrives with a written agenda. The coach thanks her and asks the team what they would add or remove. The final agenda keeps two of her items and adds one the team had never raised in her presence.

Where it comes from

Session contracting is fundamental to coaching practice; adapted to groups through facilitation practice and ICF Team Coaching Competency 3 (agreements with all relevant parties).

My notes

Family 2 of 6 · Methods 8–15 · When the real issue is how the team works

Surface the System

Does the team see its own patterns, or only its stories about them?

Teams are usually experts on their content and strangers to their own process. The Surface the System family makes the invisible visible: the data about the team, the patterns of who speaks and who doesn’t, the history members carry, the spatial truth of who is close and who is outside, and the topics everyone knows about and nobody names.

The coach’s stance here is that of a mirror, not a judge. Observations describe behaviour; the team supplies the meaning. When a team sees a pattern for itself, it owns the change; when a coach announces it, the team defends against it.

8
Surface the System family

Diagnostic and Data Feedback

Core move: Show the team its own data and let it make the meaning
4 options10 questions7 situations

1What it really is

Diagnostic feedback uses structured data — one-to-one interviews, team effectiveness surveys, stakeholder interviews, or psychometric profiles — to give the team a picture of itself it cannot get from inside. The coach collects the data, groups it into themes without attributing comments to individuals, and presents it in a way that invites the team to interpret it. The point is not the data itself; it is the conversation the data makes possible. Ownership comes from the team making meaning, not from the coach delivering conclusions.

4How it works, deeply

People tend to defend against opinions and engage with evidence, especially evidence they helped produce. Anonymised themes reduce the personal risk of honesty. Comparing internal and external views challenges the team’s self-image without the coach having to say it. And because the team interprets the data, the conclusions are theirs. Coaches must be careful: too much data overwhelms, and a beautifully produced report can become the coach’s performance rather than the team’s mirror.

Quick card

Reach for it when
Early in an engagement; when perceptions differ widely; when the team says “we’re fine” but outcomes say otherwise; mid-point review
The move
Gather data from members and stakeholders, feed back themes without attribution, and ask the team what it sees
Watch
Data presented as a verdict invites defence. Data presented as a mirror invites curiosity.
Four questions that often open it
  1. What stands out to you in this data?
  2. What surprises you?
  3. What is confirmed that you already suspected?
  4. What would you want to understand better?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Divergent views — members see the team very differently but have never compared notes.
  • Blind spots — the team scores itself highly, stakeholders do not.
  • New engagement — the coach needs a baseline and the team needs a shared starting picture.
  • Stuck conversation — the team keeps debating opinions; data could ground it.
  • Review moment — measuring progress since the start.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Pre-engagement interviews — thirty to forty-five minutes with each member, asking the same questions, themed and anonymised.
2Team effectiveness survey — a validated instrument comparing perceptions across dimensions.
3Stakeholder voice — interview or survey people who work with the team.
4Data walk — post themes on walls; members walk, read and annotate silently before discussion.

5Where it gets stuck

The team attacks the method (“the survey is flawed”). Members try to identify who said what. The leader takes the data personally. The team accepts the data and moves straight to solutions without understanding it.

6How to move it forward

Expect defence and normalise it. Redirect from “who said it” to “what might be true about it”. Slow down: ask what the data means before what to do about it. If the leader is defensive, prepare them privately beforehand so the team session does not become about the leader’s reaction.

7Questions to ask the team

Core questions
  • What do you notice first?
  • Where do you agree with the data, and where not?
  • What story does this tell about the team?
  • If an outsider read this, what would they conclude?
  • What do you want to explore further?
Going further
  • What would it mean if this were accurate?
  • Which theme are we most tempted to ignore?
  • Where is there a gap between how we see ourselves and how others see us?
  • What is this data not showing?
  • What would we need to change for next year’s data to be different?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S1.3Polite, flat and “fine”Everyone is pleasant; nothing real is said; energy is low
What is happening Everyone is pleasant; nothing real is said; energy is lowCoach move Name the pattern lightly; use anonymous or individual ways to surface the real material
In the room
Smiles, agreement, short answers. Nobody disagrees. The conversation feels like a corporate brochure. Time passes slowly.
What’s underneath
Pseudo-harmony (what Scott Peck called pseudo-community) protects the team from conflict and exposure. It is often a sign of low safety, not high trust. The real conversations happen elsewhere.
Avoid here
Pushing hard for “honesty” before any safety exists. Accepting “fine” as the full picture. Moralising about politeness.
Example
Finance team. Interviews revealed tensions, but the first session was all smiles. The coach shared the interview themes anonymously. Silence, then a member said, “Yes, that’s true.” The real work started.
Full situation card: questions, examples, sample exchange
Filed under methods513815
S2.8Overconfidence / euphoriaAfter success, the team feels invincible and ignores risks
What is happening After success, the team feels invincible and ignores risksCoach move Celebrate, then test with pre-mortem and outside views
In the room
High energy, jokes, quick agreement on ambitious plans. Risks are waved away.
What’s underneath
Success can lead to overconfidence and groupthink. Teams under-examine their assumptions when they feel successful.
Avoid here
Killing the celebration. Lecturing about risk.
Example
Startup. After funding, a pre-mortem revealed hiring risks. The team planned hiring carefully.
Full situation card: questions, examples, sample exchange
Filed under methods34816
S5.6Disagree on what success meansMembers use different definitions of success
What is happening Members use different definitions of successCoach move Build a shared preferred future; use data
In the room
Arguments about outcomes; “we’re doing well” vs “we’re failing”.
What’s underneath
Without a shared definition of success, teams pull in different directions.
Avoid here
Choosing one definition.
Example
Software team. Defined success as reliable releases and customer satisfaction.
Full situation card: questions, examples, sample exchange
Filed under methods338623
S7.6Leader defensive under feedbackThe leader reacts badly to team feedback
What is happening The leader reacts badly to team feedbackCoach move Prepare the leader; model curiosity; safety
In the room
The leader explains, defends or corrects when feedback arrives; the team goes quiet and withdraws.
What’s underneath
Defensiveness under feedback quickly reduces team safety. Leaders often feel exposed in front of their own team.
Avoid here
Exposing the leader.
Example
Executive team. The leader prepared privately with the coach and responded with curiosity in the session.
Full situation card: questions, examples, sample exchange
Filed under methods32825
S7.8Leader is the issue no one namesThe team’s problem centres on the leader’s behaviour
What is happening The team’s problem centres on the leader’s behaviourCoach move Anonymous data; leader preparation; name the undiscussable
In the room
Indirect comments, careful silences, members exchanging looks when the leader speaks.
What’s underneath
Teams avoid naming leadership issues because of power. The undiscussable often drains energy from every other topic.
Avoid here
Exposing without preparation.
Example
CEO. Anonymous data feedback revealed a leadership issue; the coach prepared the CEO, who responded well.
Full situation card: questions, examples, sample exchange
Filed under methods13328
S10.12Interview data tempting to useThe coach knows individual information from interviews
What is happening The coach knows individual information from interviewsCoach move Hold confidentiality; feed back only themes
In the room
Coach holds private knowledge.
What’s underneath
Individual data is confidential.
Avoid here
Hints.
Example
Coach. Kept themes anonymous.
Full situation card: questions, examples, sample exchange
Filed under methods81
S5.10A good team that wants to become greatNo crisis, solid results — the team wants to raise its game
What is happening No crisis, solid results — the team wants to raise its gameCoach move Start from strengths, find the next level of value for stakeholders, and stretch with small, ambitious experiments
In the room
Relaxed, confident, curious. Members are proud of results and a little bored. They ask, “What’s next for us?”
What’s underneath
High-performing teams risk the comfort zone and the plateau. The challenge is not repair but stretch: more value for stakeholders, more learning, more distributed leadership. Problem-focused methods can feel wrong here; appreciative and future-focused methods fit better.
Avoid here
Inventing problems so the coaching has something to fix. Generic team-building. Complacent celebration with no stretch.
Example
Finance leadership team. Strong internally, weak at “connecting”. Stakeholder interviews revealed an appetite for strategic advice. The team redefined its purpose and doubled its strategic work.
Full situation card: questions, examples, sample exchange
Filed under methods863046

9Coach mistakes & watch-outs

  • Presenting conclusions instead of themes.
  • Including identifiable quotes.
  • Overloading with data.
  • Skipping the leader preparation conversation.

10Team traps

  • Attacking the instrument.
  • Hunting for authors.
  • Selecting only the flattering data.

Three worked problems

1

The 5.8 vs 3.2 team. A leadership team rates its strategic alignment at 5.8 of 7; its direct reports rate it 3.2. The coach shows the gap without comment. After a long silence, the CFO says, “We think we agree because we never discuss it.”

2

Interview themes. Twelve interviews produce five themes. The coach posts them on the wall and asks members to put a dot on the one that most needs attention. Unexpectedly, the most-dotted theme is “we don’t celebrate”. The team explores why.

3

Defensive leader. The coach meets the leader before the feedback session. He reads the data and is upset. They discuss how he wants to respond in front of the team. In the session, he says, “Some of this is hard to read, and I want to understand it.” The team relaxes.

Where it comes from

Survey feedback in organisational development (Kurt Lewin, Floyd Mann), team effectiveness instruments (e.g. Team Diagnostic Survey by Wageman and Hackman), and systemic team coaching inquiry phases.

My notes

9
Surface the System family

Process Observation in Real Time

Core move: Name what is happening between people, here and now
4 options10 questions13 situations

1What it really is

Process observation means attending to how the team talks rather than what it says. Edgar Schein called it process consultation: helping the group see its own patterns of communication, decision-making and influence as they happen. The coach steps briefly out of the content and offers a neutral description of observable behaviour, then invites the team to reflect. This is one of the most powerful and distinctive team coaching moves, because the pattern visible in the coaching room is usually the same pattern that limits the team everywhere else.

4How it works, deeply

Teams are usually unconscious of their process because they are absorbed in content. Making the process visible creates choice. It also gives the team a new competence — noticing its own patterns — which is one of the main ways team coaching builds lasting capability. The ICF team competencies describe this as inviting members to pause and reflect on how they interact. Done well, process observation is a gift; done badly, it is surveillance.

Quick card

Reach for it when
The team is caught in a pattern while discussing a topic; the way they talk is the real problem; the content is going in circles
The move
Pause the content and describe, neutrally, what you see the team doing — then ask what they notice
Watch
An observation that sounds like a judgment (“you’re avoiding this”) will be defended. An observation that describes behaviour (“three people have started sentences and stopped”) can be explored.
Four questions that often open it
  1. Can I share something I’m noticing about how we’re talking right now?
  2. What do you notice about how this conversation is going?
  3. What’s happening in the room?
  4. How does this compare to how you talk in your regular meetings?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Repeating loops — the same argument is happening again.
  • Unequal participation — a few dominate, others fall silent.
  • Surface politeness — everyone agrees, energy is flat.
  • Escalation — voices rise, people interrupt.
  • Leader dependency — the team waits for the leader to decide.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Describe behaviour — “In the last ten minutes, every proposal was followed by a question about risk.”
2Ask the team first — “Pause. What do you notice about this conversation?”
3Count — airtime, interruptions, questions vs statements; share numbers.
4Fishbowl — some members observe others discussing, then share what they saw.

5Where it gets stuck

Members hear observations as criticism. The team talks about the observation in the same pattern (e.g. debating it). The coach makes too many observations and becomes the centre of attention. The observation is accurate but too early, before trust is built.

6How to move it forward

Ask permission first. Use plain behavioural language. Offer one observation and wait. Turn it into a question for the team. Over time, hand the role to members: “Who’d like to be our process observer for the next twenty minutes?”

7Questions to ask the team

Core questions
  • What’s happening in this conversation right now?
  • What do you notice about who is speaking and who isn’t?
  • What pattern are we in?
  • Is this how you usually discuss things like this?
  • What would you like to do differently in the next ten minutes?
Going further
  • What does this pattern protect us from?
  • What happens in your regular meetings at this point?
  • Who would be most likely to break this pattern?
  • If we filmed this conversation, what would the replay show?
  • What’s the cost of this pattern to the team’s work?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S1.4Wants the coach to fix one personThe team or leader frames the problem as one member
What is happening The team or leader frames the problem as one memberCoach move Contract for team patterns; widen from person to system
In the room
Members glance at one colleague (often absent or quiet). Stories all point to the same person. The leader says in private, “If X changed, we’d be fine.”
What’s underneath
Scapegoating simplifies complexity. The team avoids its own contribution by locating the problem in one person. Even when the person’s behaviour is a real issue, the system usually sustains it.
Avoid here
Agreeing to “fix” anyone. Running a session that becomes a group attack. Ignoring genuine performance issues that the leader needs to manage.
Example
Sales team. Members blamed one colleague for losing a big account. A timeline showed three handoffs failed before that colleague was involved. The team redesigned handoffs.
Full situation card: questions, examples, sample exchange
Filed under methods1219
S2.11Tension you could cutSomething unnamed is creating tension in the room
What is happening Something unnamed is creating tension in the roomCoach move Name the tension neutrally; ask permission to explore
In the room
Short answers, avoidance of eye contact, stiff posture, long silences.
What’s underneath
Tension often signals an undiscussable or recent incident. Ignoring it makes the session feel false.
Avoid here
Ignoring it. Forcing it into the open.
Example
Leadership team. Coach named the tension; a member shared that a decision had been made without them.
Full situation card: questions, examples, sample exchange
Filed under methods13931
S3.1One or two voices dominateA few members do most of the talking
What is happening A few members do most of the talkingCoach move Structure participation; make the pattern visible
In the room
Two people speak; others nod or look at phones. Ideas from quieter members are lost.
What’s underneath
Dominance may come from rank, extroversion, expertise or anxiety. Quieter members may feel unheard or unsafe. The team loses diverse input.
Avoid here
Shaming dominant members. Calling on quiet members suddenly.
Example
Strategy team. Coach shared airtime count; dominant members agreed to speak second.
Full situation card: questions, examples, sample exchange
Filed under methods591015
S3.5Interrupting and talking overMembers cut each other off
What is happening Members cut each other offCoach move Use agreements and process observation
In the room
Overlapping voices, raised volume, unfinished sentences.
What’s underneath
Interrupting may reflect enthusiasm, dominance, cultural norms or not listening. It reduces thinking quality.
Avoid here
Policing individuals. Ignoring it.
Example
Sales team. Agreed to let people finish; the coach used a talking object.
Full situation card: questions, examples, sample exchange
Filed under methods4910
S3.8Joking to deflectHumour shuts down serious discussion
What is happening Humour shuts down serious discussionCoach move Notice the pattern lightly; invite what’s under the joke
In the room
Laughs at key moments; tension released before issues are explored.
What’s underneath
Humour is a healthy team resource, but also a defence. Jokes at critical moments avoid discomfort.
Avoid here
Banning humour. Shaming jokers.
Example
Sales team. Coach noted jokes appeared whenever targets were discussed; the team talked about pressure.
Full situation card: questions, examples, sample exchange
Filed under methods9135
S3.9The same debate on loopThe team repeats the same argument without resolution
What is happening The team repeats the same argument without resolutionCoach move Map the pattern or polarity; change the structure of the conversation
In the room
Familiar arguments, same people, same positions. Frustration and fatigue.
What’s underneath
Repeated debates often indicate a polarity (both sides needed), a missing decision process, or a pattern of conversational moves.
Avoid here
Joining the debate. Forcing a decision.
Example
Product team. Speed vs quality polarity map ended a year-long debate.
Full situation card: questions, examples, sample exchange
Filed under methods1710923
S3.10Advice-giving instead of thinkingMembers jump to solutions for each other
What is happening Members jump to solutions for each otherCoach move Slow down; ask questions; use structured thinking
In the room
Someone shares a problem; others immediately suggest fixes.
What’s underneath
Advice-giving is quick and well-meant but can block thinking and ownership.
Avoid here
Lecturing about coaching. Shutting down all suggestions.
Example
Leadership team. Practised “questions only” rounds; quality of thinking improved.
Full situation card: questions, examples, sample exchange
Filed under methods954142
S4.8Venting about an absent colleagueThe team criticises someone who isn’t present
What is happening The team criticises someone who isn’t presentCoach move Refer to agreements; refocus on the team’s part
In the room
Stories about the absent person; agreement; laughter.
What’s underneath
Venting can release frustration but undermines trust: members wonder what is said about them when they are absent.
Avoid here
Joining. Shaming.
Example
Sales team. Agreed not to discuss absent members without them.
Full situation card: questions, examples, sample exchange
Filed under methods4219
S7.1Leader dominatesThe leader talks most; the team defers
What is happening The leader talks most; the team defersCoach move Contract leader role; structure participation; observe
In the room
The leader speaks first and longest. Members nod, glance at the leader before answering, and rarely contradict.
What’s underneath
Leader dominance limits team thinking, even when the leader wants input. Members read status signals and edit themselves.
Avoid here
Undermining the leader publicly.
Example
CEO team. The CEO agreed to speak last; debate quality rose noticeably within two sessions.
Full situation card: questions, examples, sample exchange
Filed under methods3259
S10.3Coach pulled into expert roleThe team wants the coach to give answers
What is happening The team wants the coach to give answersCoach move Return ownership; process observation; fade the coach
In the room
“What do you think?” “What would you do?”
What’s underneath
Teams may want answers to avoid responsibility.
Avoid here
Becoming the consultant without contracting.
Example
Leadership team. The coach offered a model with permission, then returned to coaching.
Full situation card: questions, examples, sample exchange
Filed under methods9748
S10.4Coach colluding with a subgroupThe coach aligns with one faction
What is happening The coach aligns with one factionCoach move Self-awareness; supervision; observation
In the room
The coach notices favouring some members.
What’s underneath
Coaches can unconsciously side with members they like.
Avoid here
Ignoring it.
Example
Coach. Noticed alignment with a subgroup and took it to supervision.
Full situation card: questions, examples, sample exchange
Filed under methods928
S10.10Coach’s own anxiety in the groupThe coach feels overwhelmed by the group
What is happening The coach feels overwhelmed by the groupCoach move Self-regulation; supervision; process
In the room
Coach notices racing thoughts, over-talking.
What’s underneath
Groups amplify anxiety.
Avoid here
Over-controlling.
Example
Coach. Paused, breathed, asked the team what they noticed.
Full situation card: questions, examples, sample exchange
Filed under methods95
S7.11The sponsor or a senior stakeholder is in the roomA powerful person attends; the team performs; real issues disappear
What is happening A powerful person attends; the team performs; real issues disappearCoach move Contract the visitor’s role in advance; make the power visible and the purpose clear
In the room
Polished answers, careful language, members watching the visitor. The leader is more formal than usual. The visitor asks questions that sound like assessment.
What’s underneath
When the sponsor or a senior stakeholder joins, the team’s attention shifts from learning to impression management. The “real client” of the commissioning relationship is present, and confidentiality feels at risk. The visitor may not realise their impact. Handled well, their presence can be a powerful “connecting” moment.
Avoid here
Letting the visitor turn the session into a review. Pretending the power isn’t there. Breaking confidentiality agreements by discussing previous sessions.
Example
Leadership team. The CEO joined for 40 minutes with a clear brief: share strategy, then listen. Members asked candid questions; the CEO later said it was the most useful hour of her month.
Full situation card: questions, examples, sample exchange
Filed under methods13297

9Coach mistakes & watch-outs

  • Interpreting instead of describing.
  • Interrupting too often.
  • Making observations that single out one person in front of everyone.
  • Never handing the role to the team.

10Team traps

  • Arguing with the observation.
  • Turning the observation into a new topic to avoid the original one.
  • Agreeing instantly and then resuming the same pattern.

Three worked problems

1

The risk reflex. A team keeps responding to new ideas with risks. The coach counts: seven ideas, seven risk responses, zero builds. She shares the count. A member says, “That’s every meeting.” The team agrees a rule: two builds before any risk.

2

Silence in the corner. Three members have not spoken for twenty minutes. The coach notes it neutrally and asks if the team wants to hear from people who haven’t spoken yet. One of them has a crucial objection.

3

Rotating observer. By session four, members take turns as process observer. Their observations become sharper than the coach’s, and the team starts using the practice in its regular meetings.

Where it comes from

Edgar Schein’s process consultation, Kurt Lewin’s T-groups and the group relations tradition (Tavistock). Explicitly part of ICF Team Coaching Competencies 5 and 6.

My notes

10
Surface the System family

Map Interaction Patterns

Core move: Make the team’s conversational moves visible: who moves, follows, opposes, bystands
4 options10 questions6 situations

1What it really is

David Kantor’s structural dynamics describes four basic speech acts: move (proposes a direction), follow (supports a direction), oppose (challenges a direction) and bystand (offers a perspective on what is happening). Healthy teams use all four flexibly. Stuck teams overuse some and lack others — e.g. lots of moves and opposes with no follows (endless debate), or moves and follows with no opposes (groupthink). Mapping these patterns gives the team a shared language for its conversations and a practical lever for changing them.

4How it works, deeply

Teams often believe their problem is a person (“he always blocks”), but it is usually a pattern (“nobody follows his challenges with anything useful”). Mapping moves shifts attention from personality to structure. It also legitimises opposition — essential for good decisions — and bystanding, which is how teams start to coach themselves. Kantor’s work shows these patterns are stable over time and highly predictive of team outcomes.

Quick card

Reach for it when
The team gets stuck in the same type of conversation; some roles are missing (no one opposes, or everyone opposes); one person always plays the same role
The move
Teach a simple map of conversational acts, then help the team see which acts it overuses and which it lacks
Watch
A model can become a box. Use it to describe moves in a conversation, not to label people.
Four questions that often open it
  1. Which moves are we making a lot of today?
  2. Which move is missing?
  3. Who could make that missing move?
  4. What happens to proposals in this team?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Endless debate — move-oppose, move-oppose, no resolution.
  • Groupthink — everything followed, nothing opposed.
  • Courteous compliance — the leader moves, everyone follows.
  • Covert opposition — opposition happens outside the room.
  • Missing bystander — nobody steps back to comment on the process.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Teach and practise — introduce the four acts and run a short conversation where members label their own moves.
2Live tally — the coach or a member tallies moves during a real discussion.
3Missing-move invitation — ask someone to make the missing move.
4Role rotation — members deliberately play an unfamiliar role for ten minutes.

5Where it gets stuck

Members label each other as “opposers” and the map becomes a weapon. The team understands the model but does not change its behaviour. The exercise feels artificial.

6How to move it forward

Keep it light and practical. Use it on a real topic, not a role play. Ask the team to agree one experiment, e.g. “Every proposal gets one follow and one oppose before decision.” Review at the next session.

7Questions to ask the team

Core questions
  • What happens to an idea in this team?
  • Who usually proposes? Who usually challenges?
  • What move would help us right now?
  • What does it feel like when nobody opposes?
  • Who is bystanding today?
Going further
  • What does the leader’s move invite from the rest?
  • When was opposition last useful here?
  • What would happen if you followed someone you normally oppose?
  • What move do you find hardest?
  • How do these patterns play out with other teams?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S3.1One or two voices dominateA few members do most of the talking
What is happening A few members do most of the talkingCoach move Structure participation; make the pattern visible
In the room
Two people speak; others nod or look at phones. Ideas from quieter members are lost.
What’s underneath
Dominance may come from rank, extroversion, expertise or anxiety. Quieter members may feel unheard or unsafe. The team loses diverse input.
Avoid here
Shaming dominant members. Calling on quiet members suddenly.
Example
Strategy team. Coach shared airtime count; dominant members agreed to speak second.
Full situation card: questions, examples, sample exchange
Filed under methods591015
S3.4GroupthinkThe team agrees quickly; dissent is absent
What is happening The team agrees quickly; dissent is absentCoach move Legitimise dissent; use pre-mortems and red teams
In the room
Fast agreement, nodding, nobody challenges. Ideas aren’t tested.
What’s underneath
Groupthink (Irving Janis) happens with high cohesion and pressure for consensus. The team avoids conflict and misses risks.
Avoid here
Accepting quick agreement. Appointing the same devil’s advocate.
Example
Board. A pre-mortem revealed concerns about an acquisition.
Full situation card: questions, examples, sample exchange
Filed under methods34271024
S3.5Interrupting and talking overMembers cut each other off
What is happening Members cut each other offCoach move Use agreements and process observation
In the room
Overlapping voices, raised volume, unfinished sentences.
What’s underneath
Interrupting may reflect enthusiasm, dominance, cultural norms or not listening. It reduces thinking quality.
Avoid here
Policing individuals. Ignoring it.
Example
Sales team. Agreed to let people finish; the coach used a talking object.
Full situation card: questions, examples, sample exchange
Filed under methods4910
S3.9The same debate on loopThe team repeats the same argument without resolution
What is happening The team repeats the same argument without resolutionCoach move Map the pattern or polarity; change the structure of the conversation
In the room
Familiar arguments, same people, same positions. Frustration and fatigue.
What’s underneath
Repeated debates often indicate a polarity (both sides needed), a missing decision process, or a pattern of conversational moves.
Avoid here
Joining the debate. Forcing a decision.
Example
Product team. Speed vs quality polarity map ended a year-long debate.
Full situation card: questions, examples, sample exchange
Filed under methods1710923
S6.10Handoffs keep failingWork stalls at interfaces
What is happening Work stalls at interfacesCoach move Role negotiation; AAR; interaction patterns
In the room
Complaints that work arrives late, incomplete or without context; blame bouncing between functions.
What’s underneath
Handoffs fail when expectations about timing, quality and information are not explicit. Each side sees only its own pressures.
Avoid here
Blame.
Example
Sales–delivery handoff. Role negotiation produced a one-page handoff checklist; rework fell.
Full situation card: questions, examples, sample exchange
Filed under methods39431015
S7.5Team defers to leaderMembers wait for the leader’s opinion
What is happening Members wait for the leader’s opinionCoach move Leader speaks last; interaction patterns; decision rights
In the room
Members glance at the leader before answering, use phrases like “whatever you think”, and wait for direction.
What’s underneath
Deference reflects hierarchy, cultural norms or a lack of safety. Sometimes it is learned: the leader has overruled people in the past.
Avoid here
Blaming the team.
Example
CEO team. A member was asked to make an “oppose” move as an experiment; the CEO thanked him and debate opened.
Full situation card: questions, examples, sample exchange
Filed under methods321036

9Coach mistakes & watch-outs

  • Labelling people instead of moves.
  • Treating opposition as bad.
  • Teaching the model without applying it.
  • Using it once and dropping it.

10Team traps

  • “I’m just a natural opposer.”
  • Using the language to score points.
  • Stopping all challenge out of fear of being labelled.

Three worked problems

1

Debate club. A product team argues every point. The tally shows 14 moves, 18 opposes, 2 follows. Members laugh. They agree to add one follow before any oppose. Discussions become shorter and decisions stickier.

2

The silent yes. A leadership team follows every CEO move. The coach asks someone to oppose the next one, explicitly as an experiment. The CFO does. The CEO thanks him; the conversation deepens.

3

The bystander. A quiet member takes the bystander role for twenty minutes. Her comment — “We keep solving the symptom” — redirects the session.

Where it comes from

David Kantor’s “Reading the Room” and structural dynamics; related to William Isaacs’ dialogue work.

My notes

11
Surface the System family

Team Timeline / Journey Line

Core move: Walk the team’s history together to see where today’s patterns come from
4 options10 questions9 situations

1What it really is

The timeline method invites members to place key events — launches, crises, departures, successes, reorganisations — on a shared line, often with emotional highs and lows marked above and below. Each member adds their own experiences, so the team sees that people lived the same events differently. Newer members learn the history; older members discover how others experienced it. The final step is reflection: which patterns repeat, what strengths the team has shown, and what unfinished business it still carries.

4How it works, deeply

Teams are shaped by their history, but rarely discuss it. Unspoken history creates unspoken rules (“we never challenge finance, since 2019”). Making history visible turns those rules into choices. Shared history also builds belonging: hearing how others lived the same events increases empathy and reduces assumptions. For merged teams, honouring both histories is often essential before a new shared identity can form.

Quick card

Reach for it when
New leader or new members; merged teams; the team carries old wounds; the team does not understand why it behaves as it does
The move
Build a shared timeline of key events, highs and lows, then ask what the history teaches about today
Watch
A timeline can turn into nostalgia or blame. Keep the focus on meaning and learning, not on who was right.
Four questions that often open it
  1. What are the key moments in this team’s history?
  2. When was this team at its best?
  3. What happened that we still carry?
  4. What does our history tell us about today?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Merged team — two histories that have never been told to each other.
  • New members — newcomers do not understand old sensitivities.
  • Old wounds — a past failure, layoff or conflict still shapes behaviour.
  • Lost identity — the team has forgotten what it is good at.
  • Anniversary or milestone — a natural moment to look back.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Wall timeline — a long sheet with years or quarters; members post events and emotions.
2Highs and lows curve — each member draws their personal energy line; the team overlays them.
3Chapter titles — the team names chapters of its history.
4Legacy question — what from the past to keep, and what to leave behind.

5Where it gets stuck

Long-standing members dominate the story. The discussion becomes complaints about past leadership. People who were not there feel excluded. The team enjoys the reflection but does not connect it to the present.

6How to move it forward

Invite newcomers to ask questions rather than tell stories. Ask “what did we learn?” about every low point. End with a forward question: “Given this history, what do we want the next chapter to be called?”

7Questions to ask the team

Core questions
  • What were the defining moments of this team?
  • When did you feel proudest?
  • What was hardest?
  • What patterns do you notice across the timeline?
  • What do we want to carry forward?
Going further
  • What happened before you joined that you’ve been told about?
  • Which event still shapes how we behave?
  • What did we learn at the low points?
  • What story do other teams tell about us?
  • What’s the title of the chapter we’re in now?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S1.10Merged team (“us and them”)Two former teams now one; old identities persist
What is happening Two former teams now one; old identities persistCoach move Honour both histories, then build a shared story and purpose
In the room
Members sit with their old team. Language like “we used to” and “their way”. Jokes with an edge.
What’s underneath
Mergers cause loss — of identity, status, ways of working. Unacknowledged loss turns into resistance. A new identity forms only after old ones are respected.
Avoid here
Forcing a new identity too quickly. Ignoring grief. Taking sides.
Example
Bank merger. Two teams drew their timelines and shared them. They found common experiences. A shared purpose emerged.
Full situation card: questions, examples, sample exchange
Filed under methods11262045
S2.2Fear after layoffs or restructuringMembers are anxious about their jobs; survivor guilt; silence
What is happening Members are anxious about their jobs; survivor guilt; silenceCoach move Acknowledge the fear; make space for what happened before moving on
In the room
Quiet. People look tired. Questions about future plans are met with “who knows”. Some members are overly busy.
What’s underneath
Layoffs create grief, fear and survivor guilt. The team may withdraw, avoid risk and protect itself. Ignoring the emotional impact makes any coaching superficial.
Avoid here
Jumping to vision or performance. Pretending things are normal. Making promises about job security.
Example
Tech team. After 20% cuts, the first session was a check-in and timeline. Members talked about colleagues who left. The next session moved to priorities with more energy.
Full situation card: questions, examples, sample exchange
Filed under methods25511
S2.4Grief after a lossA colleague has died, left suddenly or been seriously ill
What is happening A colleague has died, left suddenly or been seriously illCoach move Pause the agenda; create space to acknowledge the loss
In the room
Silence, tearfulness, avoidance. Some members want to “get on with work”; others can’t.
What’s underneath
Teams grieve collectively. Unacknowledged grief shows up as irritability, withdrawal or loss of purpose. People grieve differently; the team needs room for differences.
Avoid here
Rushing to tasks. Forcing emotional sharing. Acting as a therapist.
Example
Research team. A colleague died. The session became a remembrance; the team decided to name a project after her.
Full situation card: questions, examples, sample exchange
Filed under methods5113145
S4.6Old history resurfacesPast conflicts shape current interactions
What is happening Past conflicts shape current interactionsCoach move Map the history; acknowledge; decide what to carry forward
In the room
References to “last time”, “remember when”. Tension when certain topics come up.
What’s underneath
Unresolved history continues to influence the present. Teams need to acknowledge it before moving on.
Avoid here
Re-fighting the past. Dismissing it.
Example
Marketing team. Timeline revealed an old conflict; acknowledgement allowed a fresh start.
Full situation card: questions, examples, sample exchange
Filed under methods113122
S5.8Purpose drift after successAfter achieving goals, the team loses direction
What is happening After achieving goals, the team loses directionCoach move Revisit purpose; harvest learning; set new goals
In the room
Low energy, uncertainty, “what now?”
What’s underneath
Achievement can create a vacuum. Teams need a new purpose or a renewed one.
Avoid here
Rushing to new goals without reflection.
Example
Project team. Harvested learning and set a new purpose.
Full situation card: questions, examples, sample exchange
Filed under methods61146
S7.4New leader inherits teamA new leader takes over an existing team
What is happening A new leader takes over an existing teamCoach move Timeline; personal histories; leader role contracting
In the room
Members compare the new leader with the old one, test boundaries, and hold back. The new leader tries to make a quick impact.
What’s underneath
Transitions create anxiety and loyalty conflicts. Members wonder what will change; the leader wonders whom to trust.
Avoid here
Comparing leaders.
Example
Finance team. A new-leader assimilation session let the team ask questions anonymously; the leader answered them openly.
Full situation card: questions, examples, sample exchange
Filed under methods11263245
S7.9Leader leaves mid-engagementThe leader exits during coaching
What is happening The leader exits during coachingCoach move Recontract; timeline; transition
In the room
Uncertainty, loss, questions about the coaching’s future and who now owns the contract.
What’s underneath
Leader departure changes the system and the contract. The team may grieve, worry or feel relief.
Avoid here
Continuing as if nothing changed.
Example
Leadership team. Recontracted with the new leader after a farewell session for the old one.
Full situation card: questions, examples, sample exchange
Filed under methods11148
S8.1Reorganisation or mergerStructural change disrupts roles, identity and relationships
What is happening Structural change disrupts roles, identity and relationshipsCoach move Honour the past; build a shared future; manage the tensions of change
In the room
Questions about new structures, anxious jokes, people counting who is “in” and “out”.
What’s underneath
Reorganisation triggers loss and uncertainty. Teams move through endings, a neutral zone and new beginnings (William Bridges). Coaching that skips the ending creates resistance.
Avoid here
Selling the change. Treating resistance as a problem to overcome.
Example
Bank integration. The team mapped what was ending, what continued and what was new; anxiety fell.
Full situation card: questions, examples, sample exchange
Filed under methods113317
S8.5Key member leavingAn important member is leaving
What is happening An important member is leavingCoach move Acknowledge; redistribute roles; capture knowledge
In the room
Sadness, worry, role gaps.
What’s underneath
Losing a key member affects roles, relationships and identity.
Avoid here
Ignoring the loss.
Example
Product team. A farewell round and role negotiation covered the gap.
Full situation card: questions, examples, sample exchange
Filed under methods5391145

9Coach mistakes & watch-outs

  • Letting the timeline become a blame session.
  • Not giving space to different experiences of the same event.
  • Skipping the reflection step.
  • Spending too long on the past.

10Team traps

  • Nostalgia for a golden age.
  • Re-fighting old battles.
  • Dismissing history as irrelevant.

Three worked problems

1

The merged teams. Two teams merged a year ago and still talk about “them”. Each draws its own timeline, then they join them. Members discover both teams went through layoffs the same year. A shared story starts to form around resilience.

2

The 2019 incident. A team never challenges the sales department. The timeline reveals a 2019 conflict that ended with a colleague being moved. Naming it allows the team to decide whether the old rule still makes sense.

3

Chapter titles. The team names its chapters: “Startup chaos”, “The big win”, “Lost in the matrix”. Asked to name the next chapter, they choose “Finding our voice again” — which becomes the coaching theme.

Where it comes from

Narrative approaches, appreciative inquiry and organisational development practice; journey lines are widely used in team coaching and facilitation.

Theory behind it · Knowledge Library9Bridges’ Transitions model

My notes

12
Surface the System family

Sculpt the Team (Constellations)

Core move: Put the team’s relationships into space so members can see what words hide
4 options10 questions2 situations

1What it really is

Team sculpting (and systemic constellations) uses physical space to represent relationships. Members position themselves — or objects on a table — according to a question, such as “How close do you feel to the team’s purpose?” or “Where are you in relation to the leader?” Then the coach invites each person to describe what they see and feel from their position. This bypasses rehearsed arguments and reveals patterns quickly: subgroups, outsiders, distance from the leader, missing stakeholders.

4How it works, deeply

The body and space hold information that language organises away. When people stand in a spatial map, they notice things they could not say: “I didn’t realise I was standing outside the circle.” Constellation approaches (developed by Bert Hellinger and adapted for organisations by John Whittington and others) assume that systems have an order and that stepping into a position gives access to it. Even without that philosophy, spatial mapping is a powerful way to make the invisible visible.

Quick card

Reach for it when
Words are not working; relationships are complex; the team cannot see its own structure; stakeholders or other teams are part of the problem
The move
Ask members to place themselves (or objects) in the room to represent relationships, then explore what the positions reveal
Watch
Spatial work can feel exposing. Offer it as an experiment, explain it clearly, and let people choose objects instead of their bodies.
Four questions that often open it
  1. If you stood where you feel you are in this team, where would you be?
  2. What do you notice from your position?
  3. What would you change in this picture?
  4. Who or what is missing from this map?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Hidden structures — informal alliances or exclusions nobody names.
  • Overthought conflicts — the team has talked the issue to death.
  • Systemic complexity — multiple teams, stakeholders and leaders are involved.
  • Remote team — members are physically scattered and the picture is unclear.
  • Identity questions — members unsure where they belong.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Live sculpture — members stand in the room based on a question.
2Table constellation — objects (coins, figures) on a table or virtual whiteboard.
3Stakeholder positions — empty chairs or markers for stakeholders, customers, other teams.
4Move to preferred — members move to where they would like to be and describe what changes.

5Where it gets stuck

Members are self-conscious and position themselves politely. The leader orchestrates the sculpture. The exercise produces a striking picture that nobody wants to discuss. People feel exposed by what is revealed.

6How to move it forward

Start with objects rather than bodies. Use a low-stakes question first. Debrief one position at a time. Ask “what is the next small move that would make this picture better?” rather than discussing the whole picture.

7Questions to ask the team

Core questions
  • What do you notice from where you are?
  • What is it like to be in this position?
  • Who do you see clearly? Who is out of sight?
  • What surprises you about this picture?
  • What small move would help?
Going further
  • What would the customer see if they stood here?
  • Who is missing from this picture?
  • Where is the leader in relation to the team, and what does that create?
  • What changes when you move one step?
  • How long has the picture looked like this?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S3.6Subgroups and factionsThe team splits into camps
What is happening The team splits into campsCoach move Make the factions visible; explore their positions and needs
In the room
Members sit together by camp; alliances in voting; side glances.
What’s underneath
Factions form around location, function, history or values. They may be protecting legitimate interests.
Avoid here
Taking sides. Ignoring factions.
Example
Global team. Sculpting revealed a split between HQ and regions.
Full situation card: questions, examples, sample exchange
Filed under methods121728
S8.2Hybrid frictionHybrid working creates unequal access and misunderstandings
What is happening Hybrid working creates unequal access and misunderstandingsCoach move Agree hybrid norms; redesign rhythms; map the team in space
In the room
Office group and remote group; separate chats; remote members feel second-class.
What’s underneath
Hybrid creates proximity bias and different experiences of the same team.
Avoid here
Choosing a side (office vs remote).
Example
Consultancy team. Agreed decisions only in shared channels; in-office days aligned.
Full situation card: questions, examples, sample exchange
Filed under methods44412

9Coach mistakes & watch-outs

  • Over-interpreting the positions.
  • Pushing people to move physically when they are uncomfortable.
  • Running it without enough trust.
  • Leaving revealing pictures unprocessed.

10Team traps

  • Performing the “correct” position.
  • Making the exercise about one person.
  • Laughing it off to avoid the discomfort.

Three worked problems

1

The outer ring. Asked to stand according to closeness to the team’s decisions, three members stand near the leader and four in an outer ring. The outer ring describe how they learn of decisions afterwards. The team redesigns how decisions are communicated.

2

The missing customer. In a table constellation, nobody places the customer. When the coach adds a figure for the customer, it ends up far from everyone. The team spends the session on what that means.

3

Remote sculpt. A virtual team uses a whiteboard with avatars. Two members put themselves at the edge. Their story — time zones and late-night calls — leads to a new meeting rotation.

Where it comes from

Family therapy sculpting (Virginia Satir), systemic constellations (Bert Hellinger), organisational constellations (John Whittington, Gunthard Weber) and psychodrama.

My notes

13
Surface the System family

Name the Undiscussable

Core move: Make it safe to say what everyone knows but nobody says
4 options10 questions6 situations

1What it really is

Every team has undiscussables — topics too risky to raise in the room: the leader’s behaviour, a colleague’s performance, a failed strategy, a political conflict. Chris Argyris showed that undiscussables are often protected by a second undiscussable: the fact that they are undiscussable. This method makes it possible to name them through anonymous cards, structured prompts or the coach’s observation, and then to explore both the topic and why it was unsayable.

4How it works, deeply

Undiscussables drain energy and trust. Teams spend effort maintaining the silence and managing each other around it. Naming one releases that energy, but only if the team can handle what is said. The coach’s role is to hold the space: acknowledge courage, slow down defensive reactions, focus on the pattern rather than blame, and help the team decide what to do next. Often the most important learning is not the content but discovering that the team can survive saying it.

Quick card

Reach for it when
There is an obvious tension nobody names; conversations stall at the same point; side conversations carry the real content; the team is polite and stuck
The move
Create a safe, often anonymous, way to surface the unsaid, then work with it as a team pattern
Watch
Naming the undiscussable without enough safety can harm individuals. Name patterns and topics, not people, and make sure the team can hold what emerges.
Four questions that often open it
  1. What are we not talking about?
  2. What would someone say in the corridor that they wouldn’t say here?
  3. What is everyone thinking but nobody is saying?
  4. What makes it hard to say?

2The team’s context

A team needing this method usually shows up in one of these states:

  • The meeting after the meeting — real discussions happen in corridors and chats.
  • Everyone avoids one topic — the team keeps changing the subject.
  • Obvious tension — two members clearly disagree but act friendly.
  • Leader blind spot — the team is managing the leader’s behaviour.
  • Fear — recent events (layoffs, punishment of dissent) have taught silence.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Anonymous cards — members write one thing that isn’t being said; the coach reads them out.
2Corridor question — “What would people say about this meeting in the corridor?”
3Name the pattern — the coach says “I notice we change topic whenever X comes up.”
4Left-hand column — each member writes what they thought but didn’t say in a recent conversation.

5Where it gets stuck

Nobody writes anything real. The named issue is too hot and the team retreats. One person feels exposed or targeted. The team names the issue but treats it as already solved.

6How to move it forward

Build safety first. Start with lighter undiscussables. Acknowledge the courage it took. Ask the team what it needs to work on this safely. Keep the focus on what the team will do, not on assigning blame.

7Questions to ask the team

Core questions
  • What’s the conversation we keep avoiding?
  • What makes it hard to talk about here?
  • What would happen if we did talk about it?
  • What do we lose by keeping it unsaid?
  • What would help us discuss it safely?
Going further
  • How long has this been undiscussable?
  • Who benefits from the silence?
  • What would a new member notice that we no longer see?
  • What do people tell their partners about this team?
  • What’s the smallest step towards talking about this?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S1.3Polite, flat and “fine”Everyone is pleasant; nothing real is said; energy is low
What is happening Everyone is pleasant; nothing real is said; energy is lowCoach move Name the pattern lightly; use anonymous or individual ways to surface the real material
In the room
Smiles, agreement, short answers. Nobody disagrees. The conversation feels like a corporate brochure. Time passes slowly.
What’s underneath
Pseudo-harmony (what Scott Peck called pseudo-community) protects the team from conflict and exposure. It is often a sign of low safety, not high trust. The real conversations happen elsewhere.
Avoid here
Pushing hard for “honesty” before any safety exists. Accepting “fine” as the full picture. Moralising about politeness.
Example
Finance team. Interviews revealed tensions, but the first session was all smiles. The coach shared the interview themes anonymously. Silence, then a member said, “Yes, that’s true.” The real work started.
Full situation card: questions, examples, sample exchange
Filed under methods513815
S2.11Tension you could cutSomething unnamed is creating tension in the room
What is happening Something unnamed is creating tension in the roomCoach move Name the tension neutrally; ask permission to explore
In the room
Short answers, avoidance of eye contact, stiff posture, long silences.
What’s underneath
Tension often signals an undiscussable or recent incident. Ignoring it makes the session feel false.
Avoid here
Ignoring it. Forcing it into the open.
Example
Leadership team. Coach named the tension; a member shared that a decision had been made without them.
Full situation card: questions, examples, sample exchange
Filed under methods13931
S3.3The meeting after the meetingReal conversations happen outside sessions
What is happening Real conversations happen outside sessionsCoach move Bring the corridor conversation into the room
In the room
Agreement in sessions, complaints afterwards. Decisions are undermined.
What’s underneath
The team lacks safety or norms for disagreement in the room. Outside conversations carry the real content.
Avoid here
Accusing people of gossip. Ignoring the pattern.
Example
Executive team. Anonymous cards captured corridor talk. Real issues surfaced.
Full situation card: questions, examples, sample exchange
Filed under methods13436
S3.8Joking to deflectHumour shuts down serious discussion
What is happening Humour shuts down serious discussionCoach move Notice the pattern lightly; invite what’s under the joke
In the room
Laughs at key moments; tension released before issues are explored.
What’s underneath
Humour is a healthy team resource, but also a defence. Jokes at critical moments avoid discomfort.
Avoid here
Banning humour. Shaming jokers.
Example
Sales team. Coach noted jokes appeared whenever targets were discussed; the team talked about pressure.
Full situation card: questions, examples, sample exchange
Filed under methods9135
S4.2Covert conflict / passive aggressionConflict shows up as sarcasm, delays, missed deadlines
What is happening Conflict shows up as sarcasm, delays, missed deadlinesCoach move Name the pattern; make it discussable; explore underlying conflict
In the room
Polite words, sharp undertones. “Forgotten” tasks. Eye-rolls.
What’s underneath
Passive aggression occurs when open conflict feels unsafe. The conflict leaks out indirectly.
Avoid here
Accusing individuals. Ignoring the pattern.
Example
Marketing team. Left-hand column revealed unspoken criticism; the team discussed it openly.
Full situation card: questions, examples, sample exchange
Filed under methods13272214
S7.8Leader is the issue no one namesThe team’s problem centres on the leader’s behaviour
What is happening The team’s problem centres on the leader’s behaviourCoach move Anonymous data; leader preparation; name the undiscussable
In the room
Indirect comments, careful silences, members exchanging looks when the leader speaks.
What’s underneath
Teams avoid naming leadership issues because of power. The undiscussable often drains energy from every other topic.
Avoid here
Exposing without preparation.
Example
CEO. Anonymous data feedback revealed a leadership issue; the coach prepared the CEO, who responded well.
Full situation card: questions, examples, sample exchange
Filed under methods13328

9Coach mistakes & watch-outs

  • Forcing disclosure too early.
  • Allowing the named issue to become an attack on one person.
  • Naming it and then moving on as if done.
  • The coach naming the elephant for the team when the team could name it.

10Team traps

  • Collective denial (“there’s nothing we aren’t saying”).
  • Venting once and returning to silence.
  • Using the safe space to settle scores.

Three worked problems

1

The cards. Eight anonymous cards include five that mention “the reorganisation nobody explained”. The leader hears this for the first time and shares what she knows. The team agrees questions to escalate.

2

The CEO’s phone. The undiscussable is the CEO checking his phone during presentations. A card mentions it. He laughs, then asks what it costs. The team agrees phones-down meetings — including him.

3

Left-hand column. Members write what they thought in last week’s budget meeting. The pattern: everyone thought the plan was unrealistic and nobody said so. The team revisits the plan.

Where it comes from

Chris Argyris’ work on undiscussables and defensive routines, Argyris and Schön’s left-hand column, and the group relations tradition.

My notes

14
Surface the System family

Collective Shadow

Core move: Gently notice what the team habitually leaves out, pushes away or puts onto others
4 options10 questions5 situations

1What it really is

In Jungian language, the shadow is what a person or group disowns: qualities that don’t fit the self-image. Teams have shadows too. A team that prides itself on being “caring” may exclude toughness; a team that sees itself as “rigorous” may disown playfulness or speed; a team that calls itself “collaborative” may be unable to decide. Disowned qualities often get projected — onto another team (“they’re so political”) or onto one member who ends up carrying them. A light version of shadow work helps the team notice its exclusions and consider whether to reclaim a little of what it has pushed away.

4How it works, deeply

Groups maintain identity by drawing boundaries: “we are like this, not like that”. What sits outside the boundary doesn’t disappear; it appears elsewhere — in the person who keeps raising it, in the team the group loves to criticise, or in the problems that keep recurring. Naming the shadow reduces projection (and so interteam conflict), frees the member who carries it, and gives the team access to a missing resource. Arnold Mindell’s process work describes a related idea: “edges” where a group stops itself from going further. The coach’s stance is curious and non-interpretive: offer questions, let the team find its own meaning.

Quick card

Reach for it when
The team strongly defines itself by what it is not; it projects a quality onto another team or one member; the same blind spot keeps returning
The move
Ask what the team is proud of never being — and what it might lose by never being it
Watch
This is a reflective coaching move, not therapy. Keep it light, collective and work-related, and never single out a person as the carrier of the team’s shadow.
Four questions that often open it
  1. What kind of team would we hate to be?
  2. What do we criticise most in other teams?
  3. What quality is “not allowed” here?
  4. What might that quality offer us?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Strong self-image — the team defines itself by a few virtues and is proud of them.
  • Projection onto others — another department is described in very harsh terms.
  • Identified carrier — one member is seen as “the difficult one” who voices what others won’t.
  • Recurring blind spot — the same kind of mistake keeps happening.
  • Overdone strength — the team’s best quality has become its limit.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Virtue and vice — list the team’s proudest qualities, then ask what each one excludes.
2The team we’d hate to be — describe it in detail, then ask what useful thing that team might have.
3Projection check — when the team criticises others harshly, ask where a little of that quality might be useful here.
4Voice of the excluded — invite someone to speak, as an experiment, for the quality the team avoids.

5Where it gets stuck

The team experiences the conversation as criticism of its values. Members name individuals rather than qualities. The exercise becomes abstract or psychological. Nothing changes because the team agrees the shadow exists but doesn’t want it.

6How to move it forward

Frame it as balance, not correction: “We’re not giving up caring; we’re adding some directness.” Keep it concrete — one meeting, one behaviour. If someone is carrying the shadow, thank them and redistribute the role.

7Questions to ask the team

Core questions
  • What are we most proud of being?
  • What does that make it hard for us to be?
  • Which team or person annoys us most, and why?
  • When has the quality we avoid actually been useful?
  • What small dose of it might help us now?
Going further
  • What would our critics say we can’t see?
  • Who in the team says what others won’t — and what is it like to be them?
  • What kind of conversation never happens here?
  • What would we have to give up to change?
  • How would a new member describe our blind spot?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S1.11Talks only about other teamsEvery problem is located outside the team
What is happening Every problem is located outside the teamCoach move Zoom to the ecosystem, then explore the team’s part
In the room
Stories about head office, sales, IT, the board. Energy rises when complaining. Silence when asked about the team’s own role.
What’s underneath
External blame protects the team from looking at itself — and often contains real truth. The team may also feel powerless. The coach needs to validate the system issues while finding the team’s sphere of influence.
Avoid here
Dismissing the complaints. Joining the blame. Lecturing about ownership.
Example
Customer service. Blamed product for bugs. Empty chair for product revealed they never shared customer data with product. They started a monthly data share.
Full situation card: questions, examples, sample exchange
Filed under methods16192214
S3.7A scapegoatOne person carries blame for team problems
What is happening One person carries blame for team problemsCoach move Externalize the problem; explore the team pattern
In the room
Members look at one person when problems arise; jokes at their expense.
What’s underneath
Scapegoating protects the team from looking at itself. The scapegoat often carries something the team avoids.
Avoid here
Group attacks. Ignoring the scapegoat’s hurt.
Example
Project team. Externalizing “the delay monster” shifted blame.
Full situation card: questions, examples, sample exchange
Filed under methods21192214
S4.2Covert conflict / passive aggressionConflict shows up as sarcasm, delays, missed deadlines
What is happening Conflict shows up as sarcasm, delays, missed deadlinesCoach move Name the pattern; make it discussable; explore underlying conflict
In the room
Polite words, sharp undertones. “Forgotten” tasks. Eye-rolls.
What’s underneath
Passive aggression occurs when open conflict feels unsafe. The conflict leaks out indirectly.
Avoid here
Accusing individuals. Ignoring the pattern.
Example
Marketing team. Left-hand column revealed unspoken criticism; the team discussed it openly.
Full situation card: questions, examples, sample exchange
Filed under methods13272214
S4.11The team that is “too nice”Warm relationships, low challenge — and quietly declining performance
What is happening Warm relationships, low challenge — and quietly declining performanceCoach move Name the cost of harmony; make challenge a form of care
In the room
Lots of appreciation, few questions. Problems are softened into “small things”. Underperformance is worked around rather than discussed. People leave meetings smiling and nothing changes.
What’s underneath
Excessive harmony is a comfort zone (high safety, low standards). It protects relationships at the cost of results — and, over time, of the relationships themselves, because unspoken frustration builds. The team often has a shared value (“we’re caring”) that has become a shadow: directness is not allowed.
Avoid here
Shaming the team for being kind. Jumping straight to hard-hitting feedback. Treating it only as conflict avoidance — the performance cost must be visible.
Example
Charity leadership team. Scored very high on safety, low on accountability. The coach showed the learning-zone model; members placed themselves in the comfort zone. They agreed “kind and clear” norms.
Full situation card: questions, examples, sample exchange
Filed under methods27143025
S6.11A star performer or hero cultureOne person carries critical work; others defer, or resent; the system depends on a hero
What is happening One person carries critical work; others defer, or resent; the system depends on a heroCoach move Make the pattern systemic rather than personal; spread capability and recognition
In the room
The star answers first and is thanked most. Others wait for them, or roll their eyes. The star works late and looks tired. The leader praises the star in public.
What’s underneath
Hero culture is co-created: the organisation rewards heroics, the hero gains identity and status, and others gain relief from responsibility. It creates fragility (key-person risk), burnout and unequal growth. The hero may also be carrying the team’s shadow — the competence or decisiveness others don’t own.
Avoid here
Attacking or diminishing the star. Ignoring the burnout risk. Treating it as only the star’s behaviour.
Example
Sales team. The top performer closed half the deals. The team redesigned key accounts into pairs; overall sales rose and the star worked fewer weekends.
Full situation card: questions, examples, sample exchange
Filed under methods14413929

9Coach mistakes & watch-outs

  • Interpreting the team’s unconscious for it.
  • Turning it into therapy or personal disclosure.
  • Naming a person as the shadow carrier in public.
  • Pushing the team to embrace qualities it rightly rejects.

10Team traps

  • Agreeing intellectually, changing nothing.
  • Using shadow language to attack others (“that’s your shadow”).
  • Treating the exercise as a joke.

Three worked problems

1

The caring team. A support team prides itself on kindness. Asked what kindness excludes, members say “saying no” and “holding people to deadlines”. They agree one experiment: clear deadlines with kind explanations. Burnout drops.

2

“They’re so political”. A technical team criticises the commercial team as political. The coach asks where a little “political” skill — building support before meetings — might help. The team realises its proposals fail because it never pre-socialises them.

3

The difficult one. One member is labelled “negative” for raising risks. The team sees that she carries its unspoken caution. It creates a rotating “risk voice” role; she relaxes and the team owns its caution.

Where it comes from

Carl Jung’s concept of the shadow; group relations and projection in organisations; Arnold Mindell’s process work (edges, roles and “ghost roles”); Robert Bly’s writing on the shadow. Used lightly in team coaching, without clinical interpretation.

My notes

15
Surface the System family

Liberating Structures

Core move: Use simple, ready-made structures that include every voice and reduce the coach’s talking
4 options10 questions9 situations

1What it really is

Liberating Structures, developed by Henri Lipmanowicz and Keith McCandless, are 33 simple “microstructures” that change how a group interacts — how space is arranged, who participates, how groups are configured, how time is used and how the invitation is framed. They make it easy for every member to contribute and reduce the facilitator’s role. For team coaches, a handful are especially useful: 1-2-4-All (think alone, then pairs, then fours, then whole group), Troika Consulting (peer coaching in threes), What I Need From You (functions state their core needs to each other), 15% Solutions (what you can do now with the freedom you already have), TRIZ (list what would guarantee the worst outcome, then stop doing it), Wicked Questions (name the paradoxes in a strategy) and Impromptu Networking (fast pair conversations to connect a large group).

4How it works, deeply

Conventional meeting formats — presentations, open discussion, managed discussion — systematically favour confident, senior and fast-thinking people. Liberating Structures change the conditions so that everyone thinks first, talks in small groups where it feels safer, and contributes to the whole. This is psychological safety built into the format rather than requested. The structures also distribute ownership: the team generates and selects, so it owns the result. For the coach, they lower the risk of becoming the centre of the session — which supports ICF’s emphasis on the team owning its dialogue.

Quick card

Reach for it when
A few voices dominate; the team wants quick, practical progress; large teams or teams of teams; you want the team, not the coach, to do the work
The move
Choose one microstructure that fits the purpose, give a clear invitation, time it tightly, and let the structure do the facilitating
Watch
Structures support coaching; they don’t replace it. Debrief what the structure revealed, or it becomes an energising exercise with no learning.
Four questions that often open it
  1. What would we gain if everyone thought alone first?
  2. What could you do tomorrow without anyone’s permission?
  3. What do you need from each other to succeed?
  4. What could we stop doing that would make things better?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Dominant voices — the same three people speak; the rest wait.
  • Big or mixed groups — teams of teams or extended leadership forums.
  • Slow, coach-centred sessions — the team relies on the coach to drive.
  • Stuck in permission — the team believes it can’t act until someone else changes.
  • Hidden needs between roles — functions frustrate each other without asking clearly.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

11-2-4-All — for any question where you want everyone’s ideas, not the loudest.
2Troika Consulting — for building peer coaching and quick help on individual challenges.
3What I Need From You — for role and interface tension; each function names up to two core needs, others reply yes, no, or “I’ll try”.
415% Solutions or TRIZ — for teams waiting for permission or overloaded with work that should stop.

5Where it gets stuck

The team experiences the structure as a gimmick. Timing drifts and the energy fades. Results are generated but not used. The coach uses too many structures in one session.

6How to move it forward

Explain the purpose in one sentence. Keep strict, visible timing. Always end with a short debrief: “What did we notice? What do we do with this?” Use one or two structures per session, and repeat favourites until the team runs them itself.

7Questions to ask the team

Core questions
  • What does each of us think, before we hear the others?
  • What ideas came up in more than one group?
  • What do you need from each other — specifically?
  • What is within our 15% — what can we do now?
  • What did this structure help us see?
Going further
  • What would guarantee the worst outcome here — and which of those are we doing?
  • What paradox are we living with?
  • Who would never have spoken in an open discussion?
  • Which structure should the team keep using without the coach?
  • How could we use this in our regular meetings?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S1.3Polite, flat and “fine”Everyone is pleasant; nothing real is said; energy is low
What is happening Everyone is pleasant; nothing real is said; energy is lowCoach move Name the pattern lightly; use anonymous or individual ways to surface the real material
In the room
Smiles, agreement, short answers. Nobody disagrees. The conversation feels like a corporate brochure. Time passes slowly.
What’s underneath
Pseudo-harmony (what Scott Peck called pseudo-community) protects the team from conflict and exposure. It is often a sign of low safety, not high trust. The real conversations happen elsewhere.
Avoid here
Pushing hard for “honesty” before any safety exists. Accepting “fine” as the full picture. Moralising about politeness.
Example
Finance team. Interviews revealed tensions, but the first session was all smiles. The coach shared the interview themes anonymously. Silence, then a member said, “Yes, that’s true.” The real work started.
Full situation card: questions, examples, sample exchange
Filed under methods513815
S3.1One or two voices dominateA few members do most of the talking
What is happening A few members do most of the talkingCoach move Structure participation; make the pattern visible
In the room
Two people speak; others nod or look at phones. Ideas from quieter members are lost.
What’s underneath
Dominance may come from rank, extroversion, expertise or anxiety. Quieter members may feel unheard or unsafe. The team loses diverse input.
Avoid here
Shaming dominant members. Calling on quiet members suddenly.
Example
Strategy team. Coach shared airtime count; dominant members agreed to speak second.
Full situation card: questions, examples, sample exchange
Filed under methods591015
S3.2Silent membersSome members rarely speak
What is happening Some members rarely speakCoach move Use structure and invitation; understand the silence
In the room
The same people silent each session. They may look engaged or withdrawn.
What’s underneath
Silence can mean thinking, disagreement, cultural norms, low safety, or disengagement. Don’t assume.
Avoid here
Putting people on the spot. Assuming silence means agreement.
Example
Multicultural team. Writing first and rounds increased contributions.
Full situation card: questions, examples, sample exchange
Filed under methods5282515
S4.9Silo war with another teamConflict between this team and another
What is happening Conflict between this team and anotherCoach move Zoom to the ecosystem; negotiate the interface
In the room
Strong language about the other team; history of disputes.
What’s underneath
Interteam conflicts often reflect structural issues, competing goals or poor interfaces. Each team sees itself as the victim.
Avoid here
Joining blame. Ignoring structural causes.
Example
Sales and operations. Joint role negotiation produced handoff agreements.
Full situation card: questions, examples, sample exchange
Filed under methods16391915
S6.10Handoffs keep failingWork stalls at interfaces
What is happening Work stalls at interfacesCoach move Role negotiation; AAR; interaction patterns
In the room
Complaints that work arrives late, incomplete or without context; blame bouncing between functions.
What’s underneath
Handoffs fail when expectations about timing, quality and information are not explicit. Each side sees only its own pressures.
Avoid here
Blame.
Example
Sales–delivery handoff. Role negotiation produced a one-page handoff checklist; rework fell.
Full situation card: questions, examples, sample exchange
Filed under methods39431015
S8.10Team of teams / cross-team coordinationSeveral teams must deliver together; nobody owns the whole
What is happening Several teams must deliver together; nobody owns the wholeCoach move Coach the system of teams: shared purpose, explicit interfaces, liaison roles and regular cross-team learning
In the room
Representatives defend their own team’s priorities. Coordination meetings are long and report-heavy. Problems appear at the boundaries between teams. Each team blames the others; the programme lead is overwhelmed.
What’s underneath
In a team of teams, the critical work happens between teams. Each team is optimised for itself, and the system is optimised for nobody. Stanley McChrystal’s “team of teams” idea is that the network needs shared consciousness (everyone sees the whole picture) and empowered execution (teams decide locally within shared intent). Fluid membership and dual loyalties make it harder. The client may be the whole network, not one team.
Avoid here
Coaching each team separately and hoping the system improves. More status meetings. Ignoring the different incentives of each team.
Example
Programme team. An ecosystem map and interface agreements cut escalations.
Full situation card: questions, examples, sample exchange
Filed under methods16315392
S9.6Waiting for permissionThe team waits for approval to act
What is happening The team waits for approval to actCoach move Drama to empowerment; decision rights; test assumptions
In the room
“We’d need approval”.
What’s underneath
Waiting may reflect real constraints or learned helplessness.
Avoid here
Encouraging rule-breaking.
Example
Public sector team. Discovered it had more authority than assumed.
Full situation card: questions, examples, sample exchange
Filed under methods19351815
S3.12Innovation or creative stucknessThe team needs new ideas but keeps producing variations of old ones
What is happening The team needs new ideas but keeps producing variations of old onesCoach move Change the quality of attention: sense the system freshly, include every voice, then prototype small
In the room
Brainstorms produce the usual suspects. Ideas are judged within seconds. Energy is dutiful. Members say “we tried that” more than “what if”.
What’s underneath
Creative stuckness is rarely a lack of talent. It usually comes from downloading old patterns, premature judgment, fear of looking foolish, or being too far from the people who experience the problem. It is different from conflict or groupthink: the team agrees — on the old answer.
Avoid here
Another open brainstorm with the same people and the same format. Judging ideas as they emerge. Asking for “blue-sky” ideas without contact with reality.
Example
Retail product team. Three brainstorms produced nothing new. A half-day sensing journey in stores revealed staff workarounds that became the new product idea.
Full situation card: questions, examples, sample exchange
Filed under methods241520
S8.13A purely virtual teamMembers have never (or rarely) met; all work happens online
What is happening Members have never (or rarely) met; all work happens onlineCoach move Design connection, communication and rituals deliberately — nothing happens by accident online
In the room
Cameras off, chat-heavy, quick transactional meetings. People know each other’s work but not each other. Silence is hard to read. Time zones mean someone is always tired.
What’s underneath
Purely virtual teams differ from hybrid teams: there is no office core, but there is also no informal glue. Trust must be built deliberately, through reliability, responsiveness and some personal connection. Misunderstandings escalate in text. Belonging depends on rituals and norms designed for the medium.
Avoid here
Copying office practices online. Long video sessions. Assuming silence means agreement.
Example
Global consulting team. Introduced a weekly 15-minute “no work talk” call and rotating meeting times. Engagement scores rose.
Full situation card: questions, examples, sample exchange
Filed under methods345415

9Coach mistakes & watch-outs

  • Running structures without a clear purpose.
  • Letting timing slip.
  • Skipping the debrief.
  • Overloading the session with structures.

10Team traps

  • Treating it as a game.
  • Dominant members taking over the small groups.
  • Generating ideas and never acting on them.

Three worked problems

1

1-2-4-All on priorities. Two senior members usually decide priorities. With 1-2-4-All, quieter members propose a priority nobody had raised: fixing onboarding. It becomes the team’s top goal.

2

What I Need From You. Sales, product and operations each state two needs. Sales asks for realistic dates; operations asks for earlier notice of big deals. Most requests get a clear yes, two get a “no, because…”, which ends months of silent resentment.

3

TRIZ. Asked what would guarantee terrible meetings, the team lists ten behaviours — and laughs when it recognises seven. It stops three of them immediately.

Where it comes from

Henri Lipmanowicz and Keith McCandless, “The Surprising Power of Liberating Structures” (2013) and liberatingstructures.com. Builds on complexity science, positive deviance and participatory facilitation.

My notes

Family 3 of 6 · Methods 16–24 · When the story the team tells keeps it stuck

Shift the Team Frame

Is the team locked into one meaning of its situation?

Teams develop shared stories about themselves and the world around them: “head office never listens”, “we’re a dysfunctional team”, “speed and quality are at war”. These stories organise behaviour. The Shift the Team Frame family helps the team step outside its current meaning: by zooming out to the wider system, turning either/or fights into both/and polarities, uncovering hidden commitments, leaving the drama triangle, studying its best moments, externalizing the problem and separating data from inference.

Shifting the frame does not mean arguing the team out of its view. The facts stay the same; what changes is the meaning the team makes of them — and with it, the options that become visible.

16
Shift the Team Frame family

Zoom to the Ecosystem (Stakeholder Chairs)

Core move: Bring the voices outside the room into the room
4 options10 questions11 situations

1What it really is

Teams are part of larger systems: organisations, customers, suppliers, regulators, communities. Many team problems are actually system problems — or are only solvable at the system level. Zooming out means helping the team see itself from the outside, often by literally placing empty chairs for stakeholders and asking members to sit in them and speak from that perspective. This method breaks inward-looking conversations and shifts the team from blaming the system to understanding its role in it.

4How it works, deeply

Systemic team coaching argues that a team’s value is created in its connections, not just in its internal functioning. When members speak from another chair, they often discover that their story about the other is incomplete. The empty chair also offers distance: it is easier to say “from the customer’s chair, this looks slow” than “we are slow”. Moving between chairs builds the team’s capacity to hold multiple perspectives at once — a key capability of mature teams.

Quick card

Reach for it when
The team blames other teams or the organisation; the team is inward-looking; a decision affects people who are not present
The move
Place empty chairs for key stakeholders and invite members to speak from them
Watch
Speaking for stakeholders can become guessing. Use it to open curiosity, then check with the real stakeholders.
Four questions that often open it
  1. What would our customers say about this conversation?
  2. How does this look from the other team’s side?
  3. Who is affected by this decision and not here?
  4. What does the wider system need from us?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Us vs them — “The problem is the sales team / head office / regulators.”
  • Inward spiral — weeks of discussion about internal relationships.
  • Hidden stakeholders — a decision affects people nobody has thought about.
  • Silo competition — the team optimises for itself at the cost of the organisation.
  • Disconnected from strategy — the team does not see how its work fits.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Empty chairs — chairs for stakeholders; members sit and speak in role.
2Stakeholder map — draw the system and the flows between parts.
3Future stakeholder — speak from the chair of a future customer or future team member.
4Invite a guest — bring a real stakeholder into a session.

5Where it gets stuck

Members caricature the stakeholder. The exercise becomes theatrical. The team gains insight but does not change its relationship with the stakeholder. Members refuse to sit in the chair of a group they resent.

6How to move it forward

Ask members to speak as if they wanted to be fair to the stakeholder. Follow with real data — interview the stakeholder. Agree one action to strengthen the relationship.

7Questions to ask the team

Core questions
  • Who are we leaving out of this conversation?
  • What would they say if they were here?
  • How do we look from their side?
  • What do they need from us?
  • What do we need from them?
Going further
  • What is our part in this problem?
  • What would change if we treated them as partners?
  • What do we know about their pressures?
  • What would the organisation as a whole want here?
  • How would we explain this decision to them?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S1.11Talks only about other teamsEvery problem is located outside the team
What is happening Every problem is located outside the teamCoach move Zoom to the ecosystem, then explore the team’s part
In the room
Stories about head office, sales, IT, the board. Energy rises when complaining. Silence when asked about the team’s own role.
What’s underneath
External blame protects the team from looking at itself — and often contains real truth. The team may also feel powerless. The coach needs to validate the system issues while finding the team’s sphere of influence.
Avoid here
Dismissing the complaints. Joining the blame. Lecturing about ownership.
Example
Customer service. Blamed product for bugs. Empty chair for product revealed they never shared customer data with product. They started a monthly data share.
Full situation card: questions, examples, sample exchange
Filed under methods16192214
S2.7Anger at the organisationThe team is angry about decisions made above
What is happening The team is angry about decisions made aboveCoach move Acknowledge the anger; separate venting from influence; connect to the system
In the room
Raised voices, strong language, members agreeing loudly. Energy is high but directed outward.
What’s underneath
Anger signals perceived injustice. It contains energy that can be redirected toward influence. But staying in anger creates a victim-persecutor dynamic.
Avoid here
Defending the organisation. Shutting down anger. Letting the whole session become venting.
Example
Engineering team. Angry about a reorganisation. Ten minutes venting, then mapped what they could influence. Wrote a joint proposal.
Full situation card: questions, examples, sample exchange
Filed under methods16195
S2.8Overconfidence / euphoriaAfter success, the team feels invincible and ignores risks
What is happening After success, the team feels invincible and ignores risksCoach move Celebrate, then test with pre-mortem and outside views
In the room
High energy, jokes, quick agreement on ambitious plans. Risks are waved away.
What’s underneath
Success can lead to overconfidence and groupthink. Teams under-examine their assumptions when they feel successful.
Avoid here
Killing the celebration. Lecturing about risk.
Example
Startup. After funding, a pre-mortem revealed hiring risks. The team planned hiring carefully.
Full situation card: questions, examples, sample exchange
Filed under methods34816
S4.9Silo war with another teamConflict between this team and another
What is happening Conflict between this team and anotherCoach move Zoom to the ecosystem; negotiate the interface
In the room
Strong language about the other team; history of disputes.
What’s underneath
Interteam conflicts often reflect structural issues, competing goals or poor interfaces. Each team sees itself as the victim.
Avoid here
Joining blame. Ignoring structural causes.
Example
Sales and operations. Joint role negotiation produced handoff agreements.
Full situation card: questions, examples, sample exchange
Filed under methods16391915
S5.3Goals imposed from aboveTargets set without team input; low ownership
What is happening Targets set without team input; low ownershipCoach move Explore what the team can own; test assumptions; connect to stakeholders
In the room
Frustration, cynicism, low commitment.
What’s underneath
Imposed goals reduce autonomy and motivation. The team may resist or comply without commitment.
Avoid here
Defending the targets.
Example
Sales team. Team immunity map revealed assumption that pushing back was pointless; they tested it.
Full situation card: questions, examples, sample exchange
Filed under methods18616
S5.4Strategy unclearThe team doesn’t understand the organisation’s direction
What is happening The team doesn’t understand the organisation’s directionCoach move Clarify what is known; connect to stakeholders; build preferred future
In the room
Questions, confusion, speculation.
What’s underneath
Unclear strategy makes team prioritisation hard. The team may need to seek clarity or create its own direction.
Avoid here
Inventing strategy for the organisation.
Example
Regional team. Invited the strategy director to a session.
Full situation card: questions, examples, sample exchange
Filed under methods6163324
S6.2Turf warsMembers compete for territory and authority
What is happening Members compete for territory and authorityCoach move Negotiate roles; zoom to the ecosystem; clarify decisions
In the room
Possessive language (“my clients”, “my project”), copying the boss on emails, defensive body language when another member’s name is mentioned.
What’s underneath
Turf wars usually reflect unclear roles, scarce resources or incentives that reward individual territory. They can also protect status and identity during uncertainty.
Avoid here
Taking sides.
Example
Marketing and sales leads. Both claimed ownership of the key-account campaigns. Role negotiation produced a shared-ownership agreement with clear decision rights.
Full situation card: questions, examples, sample exchange
Filed under methods391635
S6.9Matrix / dual reporting tensionMembers serve two bosses; conflicting demands
What is happening Members serve two bosses; conflicting demandsCoach move Negotiate roles; manage polarities; map the system
In the room
Members hesitate before committing (“I need to check with my other boss”), conflicting deadlines, frustration about divided loyalties.
What’s underneath
Matrix structures create competing loyalties and conflicting priorities. Members can feel they belong nowhere and are judged by everyone.
Avoid here
Choosing for the member.
Example
Global product team. Role negotiation with both functional and project leads produced a shared priority list.
Full situation card: questions, examples, sample exchange
Filed under methods391716
S8.7Stakeholders unhappyStakeholders complain about the team
What is happening Stakeholders complain about the teamCoach move Zoom to stakeholders; close the loop; revisit purpose
In the room
Defensiveness; stories about unreasonable stakeholders.
What’s underneath
Stakeholder dissatisfaction is valuable data, even when partly unfair.
Avoid here
Dismissing complaints.
Example
IT team. Stakeholder interviews led to a new intake process.
Full situation card: questions, examples, sample exchange
Filed under methods16476
S8.8Resource cutsBudget or staff reduced; same expectations
What is happening Budget or staff reduced; same expectationsCoach move Prioritise; test assumptions; engage stakeholders
In the room
Frustration, overload, resentment.
What’s underneath
Cuts force trade-offs. Without explicit prioritisation, teams burn out.
Avoid here
Accepting impossible expectations.
Example
Public sector. A stop list was agreed with the sponsor.
Full situation card: questions, examples, sample exchange
Filed under methods381816
S8.10Team of teams / cross-team coordinationSeveral teams must deliver together; nobody owns the whole
What is happening Several teams must deliver together; nobody owns the wholeCoach move Coach the system of teams: shared purpose, explicit interfaces, liaison roles and regular cross-team learning
In the room
Representatives defend their own team’s priorities. Coordination meetings are long and report-heavy. Problems appear at the boundaries between teams. Each team blames the others; the programme lead is overwhelmed.
What’s underneath
In a team of teams, the critical work happens between teams. Each team is optimised for itself, and the system is optimised for nobody. Stanley McChrystal’s “team of teams” idea is that the network needs shared consciousness (everyone sees the whole picture) and empowered execution (teams decide locally within shared intent). Fluid membership and dual loyalties make it harder. The client may be the whole network, not one team.
Avoid here
Coaching each team separately and hoping the system improves. More status meetings. Ignoring the different incentives of each team.
Example
Programme team. An ecosystem map and interface agreements cut escalations.
Full situation card: questions, examples, sample exchange
Filed under methods16315392

9Coach mistakes & watch-outs

  • Letting the chair become a parody.
  • Forgetting to return members to their own seats and debrief.
  • Ignoring real stakeholder data.
  • Using the exercise to make the team feel guilty.

10Team traps

  • Speaking from the chair to confirm existing beliefs.
  • Avoiding the chair of a resented group.
  • Insight without action.

Three worked problems

1

The sales chair. An operations team blames sales for over-promising. A member sits in the sales chair and describes quarterly targets and customer threats. The team realises it never explains its capacity limits. They create a monthly capacity briefing for sales.

2

The customer’s chair. A product team designs a feature. The coach places an empty chair for the customer. Speaking from it, a member says, “I don’t want this; I want the old one to work.” The roadmap shifts.

3

Head office. The team resents head office. The coach asks what head office would say they need. The team discovers it has never asked. They invite a head office representative to the next session.

Where it comes from

Peter Hawkins’ systemic team coaching (the “connecting” discipline), Gestalt empty-chair work, and systems thinking (Peter Senge).

My notes

17
Shift the Team Frame family

Polarity Map for Teams

Core move: Turn either/or arguments into both/and management
4 options10 questions10 situations

1What it really is

Many team arguments are not problems with a right answer but polarities — pairs of interdependent values both needed over time: centralise and decentralise, speed and quality, stability and change, individual and team, short term and long term. Barry Johnson’s polarity map shows the upsides and downsides of each pole, a shared higher purpose, and early warning signs of overdoing one side. Mapping a polarity turns a win-lose debate into a shared management task.

4How it works, deeply

Polarity mapping works because it honours both sides. People defending one pole usually see its upside and the other pole’s downside. When they see the whole map, the conversation changes from “you are wrong” to “we need both of what we each care about”. It also prevents the pendulum effect, where the team over-corrects and then over-corrects again. Teams learn that some tensions are permanent and need ongoing management, not victory.

Quick card

Reach for it when
The team keeps arguing between two good options; the argument returns every few months; both sides are partly right
The move
Map the upsides and downsides of each pole, then agree how to get the best of both
Watch
Not every disagreement is a polarity. If one option is simply better, decide; polarity mapping is for tensions that will never be solved once and for all.
Four questions that often open it
  1. Is this a problem to solve or a tension to manage?
  2. What’s good about each side?
  3. What happens if we overdo one side?
  4. What signs would tell us we’re leaning too far?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Recurring debates — the same argument returns after each “decision”.
  • Factions — subgroups form around each pole.
  • Pendulum swings — the team goes from one extreme to the other.
  • Leadership changes — a new leader “corrects” the previous one’s emphasis.
  • Values conflict — both sides believe they defend something important.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Four-quadrant map — upsides and downsides of each pole.
2Higher purpose and deeper fear — what both poles serve, and what happens if the team fails to manage them.
3Early warnings — measurable signs of overdoing each pole.
4Action steps — how to get the upside of each pole.

5Where it gets stuck

The team insists one side must win. The map is drawn but no warning signs are agreed. The tension is actually a problem with a solution, and polarity mapping delays a necessary decision.

6How to move it forward

Test the polarity: “Over time, do we need both?” Ask each faction to fill in the upsides of the other side. Focus on the early warning signs and agree who will watch them.

7Questions to ask the team

Core questions
  • What are the benefits of each side?
  • What happens if we only focus on one?
  • What larger purpose do both serve?
  • What would warn us we’re over-doing one side?
  • What actions give us the best of both?
Going further
  • When has the pendulum swung before?
  • What do you fear will happen if the other side wins?
  • What does the other side see that you might be missing?
  • How will we know we’re balancing well?
  • Who should watch the warning signs?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S2.5Anxiety about changeUpcoming change creates worry and speculation
What is happening Upcoming change creates worry and speculationCoach move Separate known from unknown; build a shared preferred future; manage polarities
In the room
Rumours, “what if” questions, catastrophising. Some members very vocal, others withdrawn.
What’s underneath
Uncertainty is harder than bad news. Anxiety often fills the vacuum with worst-case stories. Teams need to separate what they know, what they don’t, and what they can influence.
Avoid here
False reassurance. Spending the session on rumours. Dismissing anxiety.
Example
Finance shared services. Sorted rumours into known, unknown and influence. Sent questions to the sponsor. Anxiety dropped.
Full situation card: questions, examples, sample exchange
Filed under methods331725
S3.6Subgroups and factionsThe team splits into camps
What is happening The team splits into campsCoach move Make the factions visible; explore their positions and needs
In the room
Members sit together by camp; alliances in voting; side glances.
What’s underneath
Factions form around location, function, history or values. They may be protecting legitimate interests.
Avoid here
Taking sides. Ignoring factions.
Example
Global team. Sculpting revealed a split between HQ and regions.
Full situation card: questions, examples, sample exchange
Filed under methods121728
S3.9The same debate on loopThe team repeats the same argument without resolution
What is happening The team repeats the same argument without resolutionCoach move Map the pattern or polarity; change the structure of the conversation
In the room
Familiar arguments, same people, same positions. Frustration and fatigue.
What’s underneath
Repeated debates often indicate a polarity (both sides needed), a missing decision process, or a pattern of conversational moves.
Avoid here
Joining the debate. Forcing a decision.
Example
Product team. Speed vs quality polarity map ended a year-long debate.
Full situation card: questions, examples, sample exchange
Filed under methods1710923
S5.2Competing prioritiesMembers pull in different directions
What is happening Members pull in different directionsCoach move Make priorities visible; decide together; manage polarities
In the room
Arguments about what matters most; members defend their areas.
What’s underneath
Competing priorities often reflect unclear strategy or misaligned incentives.
Avoid here
Deciding for the team.
Example
Product team. Portfolio wall led to stopping two projects.
Full situation card: questions, examples, sample exchange
Filed under methods38176
S5.5Individual goals beat team goalsIncentives reward individuals; collaboration suffers
What is happening Incentives reward individuals; collaboration suffersCoach move Clarify collective goals; manage the individual/team polarity
In the room
Members protect their own targets; reluctance to help others.
What’s underneath
Incentive structures shape behaviour. Teams can’t collaborate if every reward is individual.
Avoid here
Lecturing about teamwork.
Example
Sales team. Proposed a shared target component; the sponsor agreed.
Full situation card: questions, examples, sample exchange
Filed under methods2176
S5.7Short-termism / always urgentThe team focuses only on immediate issues
What is happening The team focuses only on immediate issuesCoach move Manage the short/long polarity; protect strategic time
In the room
Discussion of this week’s issues; no space for strategy.
What’s underneath
Short-termism may reflect pressure, incentives or anxiety.
Avoid here
Ignoring real urgency.
Example
Retail team. Agreed a monthly strategy session.
Full situation card: questions, examples, sample exchange
Filed under methods173844
S5.9Purpose conflicts with valuesMembers feel the team’s goals clash with their values
What is happening Members feel the team’s goals clash with their valuesCoach move Hear the minority voice; explore values and purpose
In the room
Moral language, discomfort, some members withdraw.
What’s underneath
Values conflicts are deep and can lead to disengagement or departure.
Avoid here
Dismissing concerns.
Example
Pharma team. Concern about marketing practices was escalated.
Full situation card: questions, examples, sample exchange
Filed under methods28617
S6.9Matrix / dual reporting tensionMembers serve two bosses; conflicting demands
What is happening Members serve two bosses; conflicting demandsCoach move Negotiate roles; manage polarities; map the system
In the room
Members hesitate before committing (“I need to check with my other boss”), conflicting deadlines, frustration about divided loyalties.
What’s underneath
Matrix structures create competing loyalties and conflicting priorities. Members can feel they belong nowhere and are judged by everyone.
Avoid here
Choosing for the member.
Example
Global product team. Role negotiation with both functional and project leads produced a shared priority list.
Full situation card: questions, examples, sample exchange
Filed under methods391716
S8.1Reorganisation or mergerStructural change disrupts roles, identity and relationships
What is happening Structural change disrupts roles, identity and relationshipsCoach move Honour the past; build a shared future; manage the tensions of change
In the room
Questions about new structures, anxious jokes, people counting who is “in” and “out”.
What’s underneath
Reorganisation triggers loss and uncertainty. Teams move through endings, a neutral zone and new beginnings (William Bridges). Coaching that skips the ending creates resistance.
Avoid here
Selling the change. Treating resistance as a problem to overcome.
Example
Bank integration. The team mapped what was ending, what continued and what was new; anxiety fell.
Full situation card: questions, examples, sample exchange
Filed under methods113317
S8.12AI or new tool adoption changes how the team worksNew AI or digital tools change roles, decisions and expertise
What is happening New AI or digital tools change roles, decisions and expertiseCoach move Treat adoption as a team change: explore hopes and fears, agree principles, and run small experiments with review
In the room
Excitement from some, anxiety from others. Unspoken worries about jobs and expertise. Inconsistent use: some members use AI for everything, others not at all. Confusion about who is accountable for AI-assisted work.
What’s underneath
New tools change more than tasks: they change status (whose expertise matters), decision rights (who checks what), trust and quality standards. If these are not discussed, teams split into enthusiasts and resisters, and risks go unmanaged. It is a classic polarity — speed and innovation versus quality and safety.
Avoid here
Taking sides between enthusiasts and sceptics. Ignoring job-security fears. Letting adoption happen individually without team agreements.
Example
Marketing team. Polarity mapping of speed vs quality led to principles: AI drafts, humans decide and check facts. Anxiety eased; output rose.
Full situation card: questions, examples, sample exchange
Filed under methods24374017

9Coach mistakes & watch-outs

  • Treating every disagreement as a polarity.
  • Drawing the map without action steps.
  • Taking sides.
  • Using it to postpone a decision that needs making.

10Team traps

  • Defending one pole as “the right way”.
  • Agreeing to the map but still fighting.
  • Seeing the other pole’s downside only.

Three worked problems

1

Speed vs quality. A software team fights over release speed. The map shows the upsides of speed (learning, customer feedback) and of quality (reliability, trust). Warning signs: more than two rollbacks a month (too much speed), or releases slipping twice (too much quality). Both factions agree to watch them.

2

Central vs local. A regional team swings between central control and local freedom with each new leader. Mapping shows the swing. The team agrees a few central standards and local freedom for everything else.

3

Team vs individual. High performers resent team goals. The map shows the need for both individual excellence and collaboration. Bonuses are redesigned with a team component.

Where it comes from

Barry Johnson’s polarity management; related to paradox theory in organisations (Wendy Smith and Marianne Lewis).

Theory behind it · Knowledge Library9Polarity Management

My notes

18
Shift the Team Frame family

Team Immunity to Change

Core move: Find the hidden commitments that keep the team from doing what it says it wants
4 options10 questions6 situations

1What it really is

Robert Kegan and Lisa Lahey’s immunity to change map explains why people and teams fail to change even when they want to. The team identifies its improvement goal, lists the behaviours that work against it, discovers the hidden competing commitments these behaviours serve (often protecting against a fear), and uncovers the big assumptions that keep the system in place. The team then designs small tests of those assumptions. This turns resistance from a weakness to blame into intelligence to explore.

4How it works, deeply

The method works because it respects the logic of resistance. The behaviours that block change are usually protecting something valuable — harmony, status, safety. Simply pushing harder triggers stronger protection. By naming the competing commitment (“we are committed to never being blamed for a failure”) and the assumption behind it (“if we fail, leadership will punish us”), the team can test whether the assumption is still true. Changing assumptions changes behaviour more lastingly than willpower.

Quick card

Reach for it when
The team commits to change and doesn’t follow through; good intentions repeatedly fail; the team seems to resist its own goals
The move
Map the team’s goal, what it does instead, the hidden commitments behind those behaviours, and the big assumptions underneath
Watch
The team will want to fix the behaviours immediately. The power of this method is in understanding the competing commitment first.
Four questions that often open it
  1. What do we say we want to change?
  2. What do we do instead?
  3. What are we worried would happen if we did the opposite?
  4. What are we assuming that keeps us safe?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Broken promises — the team agrees changes that never happen.
  • Collective resistance — everyone wants change but nothing moves.
  • Overcommitment — the team keeps taking on more despite saying it wants focus.
  • Avoided conflict — the team says it wants honest debate but always backs down.
  • Change fatigue — repeated failures have produced cynicism.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Full four-column map — goal, behaviours, competing commitments, big assumptions.
2Worry box — ask what members fear if they did the opposite.
3Assumption test — design a safe, small experiment to test one big assumption.
4Individual within team — members map their own immunity to the team goal.

5Where it gets stuck

The team rushes to solutions. Competing commitments are stated superficially (“we are committed to being busy”). The big assumption is too frightening to test. Members map other people’s immunity instead of their own.

6How to move it forward

Slow down at the worry box. Ask, “If we really did the opposite, what would scare us?” Keep the test small and safe. Celebrate data from the test, whatever it shows.

7Questions to ask the team

Core questions
  • What is our improvement goal?
  • What do we do or not do that works against it?
  • If we did the opposite, what would worry us?
  • What are we committed to protecting?
  • What are we assuming must be true?
Going further
  • How long have we held this assumption?
  • Where did it come from?
  • When has it not been true?
  • What small, safe test could we run?
  • What would we learn if the test went badly?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S2.6Collective cynicismThe team believes nothing will improve
What is happening The team believes nothing will improveCoach move Find exceptions; test assumptions; start very small
In the room
Sarcasm, shrugging, “seen it all before”. Ideas are dismissed quickly.
What’s underneath
Cynicism protects against disappointment. It often contains valid criticism. Shifting it requires evidence, not persuasion.
Avoid here
Arguing against the cynicism. Positivity pushing. Ignoring legitimate grievances.
Example
Factory supervisors. Mapped immunity to change; assumption was “management will ignore us”. Tested it with one proposal — approved. Cynicism softened.
Full situation card: questions, examples, sample exchange
Filed under methods201840
S5.3Goals imposed from aboveTargets set without team input; low ownership
What is happening Targets set without team input; low ownershipCoach move Explore what the team can own; test assumptions; connect to stakeholders
In the room
Frustration, cynicism, low commitment.
What’s underneath
Imposed goals reduce autonomy and motivation. The team may resist or comply without commitment.
Avoid here
Defending the targets.
Example
Sales team. Team immunity map revealed assumption that pushing back was pointless; they tested it.
Full situation card: questions, examples, sample exchange
Filed under methods18616
S8.8Resource cutsBudget or staff reduced; same expectations
What is happening Budget or staff reduced; same expectationsCoach move Prioritise; test assumptions; engage stakeholders
In the room
Frustration, overload, resentment.
What’s underneath
Cuts force trade-offs. Without explicit prioritisation, teams burn out.
Avoid here
Accepting impossible expectations.
Example
Public sector. A stop list was agreed with the sponsor.
Full situation card: questions, examples, sample exchange
Filed under methods381816
S8.9Change fatigueRepeated changes exhaust the team
What is happening Repeated changes exhaust the teamCoach move Test assumptions; appreciate stability; prioritise
In the room
Weariness, cynicism, low energy.
What’s underneath
Change fatigue reduces engagement and capacity.
Avoid here
Adding more change.
Example
Bank. Appreciative inquiry on how the team had coped with past change rebuilt confidence.
Full situation card: questions, examples, sample exchange
Filed under methods182038
S9.4Reverting under pressureNew behaviours disappear when stress rises
What is happening New behaviours disappear when stress risesCoach move Immunity to change; rhythm; peer support
In the room
The team describes going back to old habits.
What’s underneath
Old habits feel safer under stress.
Avoid here
Blame.
Example
Sales team. An immunity map revealed the assumption that only speed mattered under pressure.
Full situation card: questions, examples, sample exchange
Filed under methods184441
S9.6Waiting for permissionThe team waits for approval to act
What is happening The team waits for approval to actCoach move Drama to empowerment; decision rights; test assumptions
In the room
“We’d need approval”.
What’s underneath
Waiting may reflect real constraints or learned helplessness.
Avoid here
Encouraging rule-breaking.
Example
Public sector team. Discovered it had more authority than assumed.
Full situation card: questions, examples, sample exchange
Filed under methods19351815

9Coach mistakes & watch-outs

  • Moving to action plans too early.
  • Accepting surface-level commitments.
  • Designing tests that are too big.
  • Judging the competing commitments.

10Team traps

  • Using the map to justify not changing.
  • Blaming the organisation entirely.
  • Pretending to have no fears.

Three worked problems

1

The team that never says no. Goal: focus on three priorities. Behaviour: accepting every request. Worry: being seen as unhelpful. Assumption: “If we say no, we’ll lose influence with the board.” Test: decline one low-value request with a clear explanation. Result: the board accepts and even thanks them.

2

Avoiding debate. Goal: more honest debate. Behaviour: agreeing in meetings. Commitment: protecting relationships. Assumption: “Disagreement damages relationships.” Test: structured debates with clear rules. Relationships improve.

3

The leader’s immunity. The leader maps her own immunity to delegating. Assumption: “If I don’t check everything, I’ll be exposed.” Her honesty encourages the team to map theirs.

Where it comes from

Robert Kegan and Lisa Lahey’s “Immunity to Change” and their work on adult development and collective immunity.

My notes

19
Shift the Team Frame family

From Drama to Empowerment

Core move: Help the team step out of victim, persecutor and rescuer roles
4 options10 questions5 situations

1What it really is

Stephen Karpman’s drama triangle describes three roles people take in conflict: victim (“poor us”), persecutor (“it’s your fault”) and rescuer (“let me fix it for you”). Teams can get stuck in these roles with each other and with other teams. David Emerald’s The Empowerment Dynamic (TED*) offers alternatives: creator (instead of victim), challenger (instead of persecutor) and coach (instead of rescuer). This method helps teams see the roles they play and choose more empowering ones.

4How it works, deeply

The drama triangle is self-reinforcing: each role invites the others. Victims invite rescuers and persecutors; rescuers keep victims dependent; persecutors create victims. Teams stuck in drama spend energy on roles rather than results. Naming the triangle gives members a shared, non-blaming language. Shifting roles (from victim to creator) changes the team’s relationship to the problem — from “it’s happening to us” to “what do we want to create?”

Quick card

Reach for it when
Blame flows between members or teams; someone is always rescued; the team describes itself as helpless; conflicts follow a repeated script
The move
Map the roles the team is playing, then explore the empowering alternatives (creator, challenger, coach)
Watch
Never label a person as “the persecutor”. The roles are positions people move between, often within minutes.
Four questions that often open it
  1. Who are we blaming, and who are we rescuing?
  2. Where do we feel powerless?
  3. What would a creator do here?
  4. What would helpful challenge look like?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Blame culture — every problem has a culprit.
  • Learned helplessness — “Nothing we do matters here.”
  • Chronic rescuing — one member always covers for others.
  • Interteam drama — the team is a victim of another team (persecutor).
  • Leader as rescuer — the leader steps in, the team steps back.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Map the triangle — draw it and place recent events or interactions on it.
2Role shift — ask what a creator, challenger or coach would do.
3Own your corner — members name which role they most often take.
4Interteam version — map the triangle between this team and others.

5Where it gets stuck

Members use the triangle to accuse each other. The team agrees with the model but stays in victim mode about the organisation. The rescuer refuses to stop rescuing because it feels like abandoning colleagues.

6How to move it forward

Ask everyone to name their own most frequent role first. Use it on a specific recent event. Practise the empowering alternative in a role-play of a real conversation.

7Questions to ask the team

Core questions
  • What role are we playing right now?
  • Who are we waiting for to fix this?
  • What do we want to create instead?
  • What would helpful challenge sound like?
  • How could we support without rescuing?
Going further
  • What do we gain from the victim role?
  • Who in the team rescues most often, and what does it cost them?
  • What would the other team say about us?
  • Where do we have more power than we admit?
  • What is one creator move for this week?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S1.11Talks only about other teamsEvery problem is located outside the team
What is happening Every problem is located outside the teamCoach move Zoom to the ecosystem, then explore the team’s part
In the room
Stories about head office, sales, IT, the board. Energy rises when complaining. Silence when asked about the team’s own role.
What’s underneath
External blame protects the team from looking at itself — and often contains real truth. The team may also feel powerless. The coach needs to validate the system issues while finding the team’s sphere of influence.
Avoid here
Dismissing the complaints. Joining the blame. Lecturing about ownership.
Example
Customer service. Blamed product for bugs. Empty chair for product revealed they never shared customer data with product. They started a monthly data share.
Full situation card: questions, examples, sample exchange
Filed under methods16192214
S2.7Anger at the organisationThe team is angry about decisions made above
What is happening The team is angry about decisions made aboveCoach move Acknowledge the anger; separate venting from influence; connect to the system
In the room
Raised voices, strong language, members agreeing loudly. Energy is high but directed outward.
What’s underneath
Anger signals perceived injustice. It contains energy that can be redirected toward influence. But staying in anger creates a victim-persecutor dynamic.
Avoid here
Defending the organisation. Shutting down anger. Letting the whole session become venting.
Example
Engineering team. Angry about a reorganisation. Ten minutes venting, then mapped what they could influence. Wrote a joint proposal.
Full situation card: questions, examples, sample exchange
Filed under methods16195
S3.7A scapegoatOne person carries blame for team problems
What is happening One person carries blame for team problemsCoach move Externalize the problem; explore the team pattern
In the room
Members look at one person when problems arise; jokes at their expense.
What’s underneath
Scapegoating protects the team from looking at itself. The scapegoat often carries something the team avoids.
Avoid here
Group attacks. Ignoring the scapegoat’s hurt.
Example
Project team. Externalizing “the delay monster” shifted blame.
Full situation card: questions, examples, sample exchange
Filed under methods21192214
S4.9Silo war with another teamConflict between this team and another
What is happening Conflict between this team and anotherCoach move Zoom to the ecosystem; negotiate the interface
In the room
Strong language about the other team; history of disputes.
What’s underneath
Interteam conflicts often reflect structural issues, competing goals or poor interfaces. Each team sees itself as the victim.
Avoid here
Joining blame. Ignoring structural causes.
Example
Sales and operations. Joint role negotiation produced handoff agreements.
Full situation card: questions, examples, sample exchange
Filed under methods16391915
S9.6Waiting for permissionThe team waits for approval to act
What is happening The team waits for approval to actCoach move Drama to empowerment; decision rights; test assumptions
In the room
“We’d need approval”.
What’s underneath
Waiting may reflect real constraints or learned helplessness.
Avoid here
Encouraging rule-breaking.
Example
Public sector team. Discovered it had more authority than assumed.
Full situation card: questions, examples, sample exchange
Filed under methods19351815

9Coach mistakes & watch-outs

  • Labelling individuals.
  • Moralising about drama.
  • Ignoring real power imbalances — sometimes the team really is constrained.
  • Rescuing the team yourself.

10Team traps

  • Accusing others of being persecutors.
  • Using the triangle to deepen victimhood (“we’re victims of the drama”).
  • Refusing to stop rescuing.

Three worked problems

1

The victim team. A support team says, “Development always throws bugs over the wall.” Mapping shows the team in victim, development as persecutor and the manager as rescuer. Asked what a creator would do, the team proposes joint bug triage. Development agrees.

2

The rescuer. A senior member always works late fixing others’ mistakes. She names herself as rescuer. The team agrees that she will coach rather than fix — and that members will ask for help earlier.

3

Leader exits rescuer. The leader realises she steps in whenever discussions get hard. She agrees to stay quiet for a whole session. The team solves a difficult issue without her.

Where it comes from

Stephen Karpman’s drama triangle (transactional analysis) and David Emerald’s The Empowerment Dynamic.

My notes

20
Shift the Team Frame family

Appreciative Inquiry: What Is Working

Core move: Build on the team’s best moments rather than diagnosing its worst
4 options10 questions7 situations

1What it really is

David Cooperrider’s appreciative inquiry starts from the belief that teams move in the direction of what they study. Instead of analysing problems, the team explores its peak experiences and strengths. The 4-D cycle — discovery (what works), dream (what could be), design (what should be), destiny (what will be) — turns strengths into deliberate practice. In team coaching, short appreciative interviews in pairs often change the energy of a whole session.

4How it works, deeply

Problem-focused conversation often produces defensiveness and depletion. Strength-focused conversation produces energy and generative ideas. Neuroscience and positive psychology support the idea that people think more broadly when they feel positive (Barbara Fredrickson’s broaden-and-build theory). Appreciative inquiry also reveals real capabilities — practices that already work — which are easier to spread than new practices imported from outside.

Quick card

Reach for it when
Morale is low; the team is stuck in problem talk; the team has forgotten its strengths; after a long period of criticism
The move
Ask the team to tell stories of its best moments, identify what made them possible, and design more of that
Watch
Appreciative inquiry is not ignoring problems. If the team feels its real difficulties are dismissed, it will disengage.
Four questions that often open it
  1. When has this team been at its best?
  2. What made that possible?
  3. What do we want more of?
  4. What would it look like if that happened every week?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Problem saturation — the team only talks about what is wrong.
  • Low morale — after layoffs, failures or criticism.
  • Forgotten strengths — the team underestimates itself.
  • New team — wants to build on members’ best team experiences.
  • Change resistance — positive framing opens possibilities.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Paired interviews — members interview each other about their best team experience.
2Positive core — the team lists strengths that appear across stories.
3Dream statement — a provocative statement of what the team wants to become.
4Design principles — practical agreements to make the dream real.

5Where it gets stuck

The team feels the exercise is “fluffy” or naive. Strengths are described vaguely. The team generates a beautiful dream with no practical next step. Members who are unhappy feel silenced.

6How to move it forward

Acknowledge problems first, then ask permission to look at what works. Push for specific examples. Connect strengths to current challenges: “How could this strength help with the problem we discussed?”

7Questions to ask the team

Core questions
  • Tell us about a time this team worked brilliantly.
  • What made it possible?
  • What did each of you contribute?
  • What strengths keep appearing?
  • How can we use them now?
Going further
  • What do we do well that we take for granted?
  • What would our best day look like next year?
  • What do stakeholders appreciate about us?
  • What small thing would bring more of our best?
  • Which strength could help with our hardest problem?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S1.8Cynical about coaching (“been here before”)The team has had away-days and consultants; expects another one
What is happening The team has had away-days and consultants; expects another oneCoach move Make past experience into design input; promise less, deliver more
In the room
Eye-rolls. Jokes about “trust falls”. A senior member checks emails ostentatiously.
What’s underneath
Cynicism is often disappointed hope. Past interventions created energy that the organisation didn’t sustain. Members protect themselves from another disappointment.
Avoid here
Defending coaching. Overpromising. Treating cynics as obstacles.
Example
Public sector team. The coach asked for a list of what made past interventions useless. It became the “we won’t do” list. Cynicism dropped.
Full situation card: questions, examples, sample exchange
Filed under methods1420
S1.10Merged team (“us and them”)Two former teams now one; old identities persist
What is happening Two former teams now one; old identities persistCoach move Honour both histories, then build a shared story and purpose
In the room
Members sit with their old team. Language like “we used to” and “their way”. Jokes with an edge.
What’s underneath
Mergers cause loss — of identity, status, ways of working. Unacknowledged loss turns into resistance. A new identity forms only after old ones are respected.
Avoid here
Forcing a new identity too quickly. Ignoring grief. Taking sides.
Example
Bank merger. Two teams drew their timelines and shared them. They found common experiences. A shared purpose emerged.
Full situation card: questions, examples, sample exchange
Filed under methods11262045
S2.6Collective cynicismThe team believes nothing will improve
What is happening The team believes nothing will improveCoach move Find exceptions; test assumptions; start very small
In the room
Sarcasm, shrugging, “seen it all before”. Ideas are dismissed quickly.
What’s underneath
Cynicism protects against disappointment. It often contains valid criticism. Shifting it requires evidence, not persuasion.
Avoid here
Arguing against the cynicism. Positivity pushing. Ignoring legitimate grievances.
Example
Factory supervisors. Mapped immunity to change; assumption was “management will ignore us”. Tested it with one proposal — approved. Cynicism softened.
Full situation card: questions, examples, sample exchange
Filed under methods201840
S2.9Shame after a public failureThe team failed visibly and members feel embarrassed
What is happening The team failed visibly and members feel embarrassedCoach move Make learning safe; separate identity from event; review without blame
In the room
Avoidance of the topic, defensive explanations, self-criticism or blame.
What’s underneath
Shame makes teams hide and defend. Learning requires turning shame into curiosity. Blame and withdrawal are both shame responses.
Avoid here
Rushing past the failure. Blaming. Over-reassuring.
Example
Launch failure. After-action review with no blame; team found process gaps. Confidence recovered.
Full situation card: questions, examples, sample exchange
Filed under methods432120
S8.9Change fatigueRepeated changes exhaust the team
What is happening Repeated changes exhaust the teamCoach move Test assumptions; appreciate stability; prioritise
In the room
Weariness, cynicism, low energy.
What’s underneath
Change fatigue reduces engagement and capacity.
Avoid here
Adding more change.
Example
Bank. Appreciative inquiry on how the team had coped with past change rebuilt confidence.
Full situation card: questions, examples, sample exchange
Filed under methods182038
S9.5Experiment fails and team gives upA failed experiment leads to abandonment
What is happening A failed experiment leads to abandonmentCoach move AAR; reframe failure as learning; adapt
In the room
Disappointment; “told you so”.
What’s underneath
Teams often confuse failure of an experiment with failure of the goal.
Avoid here
Forcing the same experiment.
Example
Product team. Adjusted a daily stand-up to weekly after the daily version failed.
Full situation card: questions, examples, sample exchange
Filed under methods434020
S3.12Innovation or creative stucknessThe team needs new ideas but keeps producing variations of old ones
What is happening The team needs new ideas but keeps producing variations of old onesCoach move Change the quality of attention: sense the system freshly, include every voice, then prototype small
In the room
Brainstorms produce the usual suspects. Ideas are judged within seconds. Energy is dutiful. Members say “we tried that” more than “what if”.
What’s underneath
Creative stuckness is rarely a lack of talent. It usually comes from downloading old patterns, premature judgment, fear of looking foolish, or being too far from the people who experience the problem. It is different from conflict or groupthink: the team agrees — on the old answer.
Avoid here
Another open brainstorm with the same people and the same format. Judging ideas as they emerge. Asking for “blue-sky” ideas without contact with reality.
Example
Retail product team. Three brainstorms produced nothing new. A half-day sensing journey in stores revealed staff workarounds that became the new product idea.
Full situation card: questions, examples, sample exchange
Filed under methods241520

9Coach mistakes & watch-outs

  • Using it to avoid conflict.
  • Accepting generalities.
  • Forcing positivity.
  • Skipping the design step.

10Team traps

  • Cynicism (“this is just positive thinking”).
  • Nostalgia without action.
  • Using strengths to justify not changing.

Three worked problems

1

The criticised team. After an audit, a finance team is demoralised. Paired interviews about their best quarter reveal tight collaboration and early warning. The team designs a weekly 15-minute risk huddle based on that success.

2

Merger strengths. Two merged teams interview each other about what they were proud of before the merger. The positive core combines both. Resistance to the merger softens.

3

Problem first. A team rejects appreciative inquiry as naive. The coach spends twenty minutes acknowledging problems, then asks, “When was this less true?” The team engages.

Where it comes from

David Cooperrider and Suresh Srivastva’s appreciative inquiry; solution-focused practice (Steve de Shazer, Insoo Kim Berg); positive psychology.

Theory behind it · Knowledge Library2CliftonStrengths team reports8Appreciative Inquiry

My notes

21
Shift the Team Frame family

Externalize the Team Problem

Core move: Turn a blamed person or vague malaise into a shared opponent
4 options10 questions4 situations

1What it really is

Narrative therapy (Michael White and David Epston) teaches that “the person is not the problem; the problem is the problem.” In teams, externalizing the problem means turning a pattern — silos, firefighting, last-minute panic — into something with a name and character, separate from any person. The team then explores how this “character” works, what tricks it uses, and when the team has resisted it. This reduces blame, increases collective ownership and makes the problem feel smaller and more manageable.

4How it works, deeply

Externalizing changes the team’s relationship with the problem. When the problem is “in” a person or the team, it threatens identity and creates defence. When it is “outside”, the team can unite against it. Names also make the problem visible and easier to discuss: “Panic Mode is back” is easier to say than “we’re panicking again”. Unique outcomes show the team that it already has resources to resist.

Quick card

Reach for it when
The team blames individuals for a systemic issue; the problem feels too big; the team uses labels (“we’re dysfunctional”)
The move
Give the problem a name and a character, then explore how it operates and how the team can resist it
Watch
Externalizing can feel playful. Keep it respectful, and don’t use it to avoid individual accountability where that matters.
Four questions that often open it
  1. If this problem had a name, what would it be?
  2. When is it strongest?
  3. What does it make us do?
  4. When have we defeated it?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Blame on individuals — “If only Sam communicated better.”
  • Global labels — “We’re just a dysfunctional team.”
  • Overwhelm — the problem feels huge and vague.
  • Shame — after a failure, members feel the team is broken.
  • Interteam tension — another team is blamed.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Name the problem — the team agrees a name (“The Silo Monster”, “Panic Mode”).
2Interview the problem — ask how it gets the team, when it is strongest, what it feeds on.
3Find unique outcomes — times the team defeated it.
4Team strategies — design ways to resist the problem.

5Where it gets stuck

The name becomes a joke and nobody takes it seriously. The team externalizes a problem that is really one person’s behaviour. Members use the name to blame others (“your Panic Mode”).

6How to move it forward

Ask the team to describe the problem’s tactics seriously. Focus on unique outcomes. If individual accountability is needed, address it separately and respectfully.

7Questions to ask the team

Core questions
  • What shall we call this problem?
  • How does it affect our work?
  • When is it strongest? When weakest?
  • When have we beaten it?
  • What helps us resist it?
Going further
  • What does it want us to believe about ourselves?
  • Who is most vulnerable to it?
  • What would it hate us to do?
  • What would our stakeholders notice if we defeated it?
  • How will we know when it’s trying to return?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S1.4Wants the coach to fix one personThe team or leader frames the problem as one member
What is happening The team or leader frames the problem as one memberCoach move Contract for team patterns; widen from person to system
In the room
Members glance at one colleague (often absent or quiet). Stories all point to the same person. The leader says in private, “If X changed, we’d be fine.”
What’s underneath
Scapegoating simplifies complexity. The team avoids its own contribution by locating the problem in one person. Even when the person’s behaviour is a real issue, the system usually sustains it.
Avoid here
Agreeing to “fix” anyone. Running a session that becomes a group attack. Ignoring genuine performance issues that the leader needs to manage.
Example
Sales team. Members blamed one colleague for losing a big account. A timeline showed three handoffs failed before that colleague was involved. The team redesigned handoffs.
Full situation card: questions, examples, sample exchange
Filed under methods1219
S2.9Shame after a public failureThe team failed visibly and members feel embarrassed
What is happening The team failed visibly and members feel embarrassedCoach move Make learning safe; separate identity from event; review without blame
In the room
Avoidance of the topic, defensive explanations, self-criticism or blame.
What’s underneath
Shame makes teams hide and defend. Learning requires turning shame into curiosity. Blame and withdrawal are both shame responses.
Avoid here
Rushing past the failure. Blaming. Over-reassuring.
Example
Launch failure. After-action review with no blame; team found process gaps. Confidence recovered.
Full situation card: questions, examples, sample exchange
Filed under methods432120
S3.7A scapegoatOne person carries blame for team problems
What is happening One person carries blame for team problemsCoach move Externalize the problem; explore the team pattern
In the room
Members look at one person when problems arise; jokes at their expense.
What’s underneath
Scapegoating protects the team from looking at itself. The scapegoat often carries something the team avoids.
Avoid here
Group attacks. Ignoring the scapegoat’s hurt.
Example
Project team. Externalizing “the delay monster” shifted blame.
Full situation card: questions, examples, sample exchange
Filed under methods21192214
S4.8Venting about an absent colleagueThe team criticises someone who isn’t present
What is happening The team criticises someone who isn’t presentCoach move Refer to agreements; refocus on the team’s part
In the room
Stories about the absent person; agreement; laughter.
What’s underneath
Venting can release frustration but undermines trust: members wonder what is said about them when they are absent.
Avoid here
Joining. Shaming.
Example
Sales team. Agreed not to discuss absent members without them.
Full situation card: questions, examples, sample exchange
Filed under methods4219

9Coach mistakes & watch-outs

  • Treating it as a game.
  • Externalizing real individual issues.
  • Not finding unique outcomes.
  • Naming the problem for the team.

10Team traps

  • Using the name to deflect responsibility.
  • Laughing it off.
  • Saying “the monster made us do it”.

Three worked problems

1

The Silo Monster. A team blames one member for not sharing information. The coach invites them to name the problem: “The Silo Monster”. They explore its tactics: busy schedules, separate tools, fear of judgment. Unique outcome: last month’s launch, when everyone used one shared channel. The team re-introduces it.

2

Panic Mode. A project team names its last-minute rushes “Panic Mode”. They find it is strongest when deadlines are set externally without consultation. They agree to negotiate deadlines earlier.

3

We’re dysfunctional. A team calls itself dysfunctional. The coach asks what “Dysfunction” makes them do. They list three behaviours; two are easy to change.

Where it comes from

Narrative therapy (Michael White and David Epston); adapted for organisations and teams by narrative practitioners.

Theory behind it · Knowledge Library4Lewin’s equation B = f(P, E)

My notes

22
Shift the Team Frame family

Walk Down the Ladder of Inference

Core move: Separate what happened from the story the team tells about it
4 options10 questions6 situations

1What it really is

Chris Argyris’ ladder of inference describes how people move quickly from observable data to selected data, interpretations, assumptions, conclusions, beliefs and actions — usually without noticing the steps. Teams build shared ladders: “Finance always blocks us” may rest on two experiences years ago. Walking down the ladder means making the reasoning visible, separating data from interpretation, and exploring alternatives. It is a core tool for reducing conflict based on misunderstanding.

4How it works, deeply

The ladder works because it slows down automatic thinking. Most conflict is not about data but about interpretations. When people see their own reasoning as a series of steps, they can hold their conclusions more lightly. Peter Senge’s work on mental models shows that teams which surface and test assumptions learn faster. It also builds a culture where “What’s your data?” is a normal, non-hostile question.

Quick card

Reach for it when
Members jump to conclusions about each other; conflicts rest on assumptions; the team treats interpretations as facts
The move
Help the team trace a conclusion back to the observable data, and test the steps in between
Watch
Don’t use the ladder to prove someone wrong. Use it to make reasoning visible so the team can test it together.
Four questions that often open it
  1. What did we actually see or hear?
  2. What did we add to that?
  3. What other interpretations are possible?
  4. How could we test our conclusion?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Misread intentions — “She didn’t reply because she doesn’t care.”
  • Team myths — shared beliefs about other teams based on old events.
  • Polarised camps — each side has its own ladder.
  • Leader assumptions — the leader concludes the team is not committed.
  • Feedback conflicts — feedback is based on interpretation, not behaviour.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Draw the ladder — the coach draws it and places one conclusion on it.
2Data first — ask “What would a camera have recorded?”
3Alternative ladders — generate at least three other interpretations.
4Test publicly — agree how to check the assumption with the person or group.

5Where it gets stuck

The team debates which interpretation is right. People feel their judgments are being dismissed. The data is genuinely ambiguous and no test is possible.

6How to move it forward

Acknowledge that interpretations are natural. Focus on testing, not winning. Agree what data would change minds.

7Questions to ask the team

Core questions
  • What exactly happened?
  • What did you notice, and what might you have missed?
  • What did you conclude, and how?
  • What else could explain it?
  • How could we find out?
Going further
  • What beliefs make this conclusion feel obvious?
  • When did this belief start?
  • What would the other person say about this ladder?
  • What actions has this belief led us to?
  • What happens if we’re wrong?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S1.11Talks only about other teamsEvery problem is located outside the team
What is happening Every problem is located outside the teamCoach move Zoom to the ecosystem, then explore the team’s part
In the room
Stories about head office, sales, IT, the board. Energy rises when complaining. Silence when asked about the team’s own role.
What’s underneath
External blame protects the team from looking at itself — and often contains real truth. The team may also feel powerless. The coach needs to validate the system issues while finding the team’s sphere of influence.
Avoid here
Dismissing the complaints. Joining the blame. Lecturing about ownership.
Example
Customer service. Blamed product for bugs. Empty chair for product revealed they never shared customer data with product. They started a monthly data share.
Full situation card: questions, examples, sample exchange
Filed under methods16192214
S3.7A scapegoatOne person carries blame for team problems
What is happening One person carries blame for team problemsCoach move Externalize the problem; explore the team pattern
In the room
Members look at one person when problems arise; jokes at their expense.
What’s underneath
Scapegoating protects the team from looking at itself. The scapegoat often carries something the team avoids.
Avoid here
Group attacks. Ignoring the scapegoat’s hurt.
Example
Project team. Externalizing “the delay monster” shifted blame.
Full situation card: questions, examples, sample exchange
Filed under methods21192214
S4.2Covert conflict / passive aggressionConflict shows up as sarcasm, delays, missed deadlines
What is happening Conflict shows up as sarcasm, delays, missed deadlinesCoach move Name the pattern; make it discussable; explore underlying conflict
In the room
Polite words, sharp undertones. “Forgotten” tasks. Eye-rolls.
What’s underneath
Passive aggression occurs when open conflict feels unsafe. The conflict leaks out indirectly.
Avoid here
Accusing individuals. Ignoring the pattern.
Example
Marketing team. Left-hand column revealed unspoken criticism; the team discussed it openly.
Full situation card: questions, examples, sample exchange
Filed under methods13272214
S4.6Old history resurfacesPast conflicts shape current interactions
What is happening Past conflicts shape current interactionsCoach move Map the history; acknowledge; decide what to carry forward
In the room
References to “last time”, “remember when”. Tension when certain topics come up.
What’s underneath
Unresolved history continues to influence the present. Teams need to acknowledge it before moving on.
Avoid here
Re-fighting the past. Dismissing it.
Example
Marketing team. Timeline revealed an old conflict; acknowledgement allowed a fresh start.
Full situation card: questions, examples, sample exchange
Filed under methods113122
S4.7Cross-cultural misunderstandingDifferent cultural norms lead to misinterpretations
What is happening Different cultural norms lead to misinterpretationsCoach move Explore cultural assumptions; build shared norms
In the room
Confusion, frustration, members feeling disrespected without knowing why.
What’s underneath
Cultures differ in directness, hierarchy, time and conflict. Behaviours are often misread through one’s own cultural lens.
Avoid here
Stereotyping. Ignoring culture.
Example
Global team. User manuals revealed different norms; the team created communication guidelines.
Full situation card: questions, examples, sample exchange
Filed under methods26224
S8.3Multicultural teamMembers from different cultures bring different norms
What is happening Members from different cultures bring different normsCoach move Surface norms; build shared agreements; treat difference as resource
In the room
Different speaking styles, silence norms, attitudes to hierarchy and time.
What’s underneath
Cultural differences in communication, hierarchy and conflict (Erin Meyer’s culture map) shape team dynamics. Differences can be strengths if they are discussed.
Avoid here
Stereotypes. Assuming one culture is the norm.
Example
Global IT team. Mapped members on directness and hierarchy scales and agreed norms.
Full situation card: questions, examples, sample exchange
Filed under methods26224

9Coach mistakes & watch-outs

  • Lecturing about assumptions.
  • Using the ladder to win arguments.
  • Never testing interpretations.
  • Applying it only to others.

10Team traps

  • Insisting “I know what I saw.”
  • Treating every interpretation as equally valid.
  • Agreeing intellectually but not changing.

Three worked problems

1

The unanswered email. A member says a colleague ignored her email “because she doesn’t respect my work.” Walking down the ladder shows the data: one unanswered email, sent during the colleague’s leave. The team agrees to check assumptions before concluding.

2

Finance blocks us. The team believes finance always blocks proposals. Data: two rejections in three years; five approvals. The belief changes.

3

The leader’s ladder. The leader concludes the team is not committed because people leave at 5pm. Walking down the ladder reveals caring responsibilities and early starts. The leader apologises.

Where it comes from

Chris Argyris’ ladder of inference; popularised by Peter Senge in “The Fifth Discipline” (mental models).

My notes

23
Shift the Team Frame family

Clean Language for Teams

Core move: Use the team’s own words and metaphors to unlock stuck or polarised language
4 options10 questions3 situations

1What it really is

Clean Language was developed by the therapist David Grove and turned into a practical approach (Symbolic Modelling) by Penny Tompkins and James Lawley. Clean questions use only the speaker’s words and a small set of question frames — such as “And what kind of X is that?”, “And is there anything else about X?”, “And where is X?” and “And what would you like to have happen?” — so the listener adds as little of their own assumption as possible. Teams often think and argue in metaphor: “we’re a family”, “a well-oiled machine”, “running on a hamster wheel”. Exploring those metaphors cleanly, and then building a shared metaphor for how the team wants to work, can shift a conversation that ordinary questions have not moved.

4How it works, deeply

Every question carries assumptions. A coach who asks “How can you collaborate better?” has already decided the issue is collaboration. Clean questions minimise this “contamination”, so the team’s own way of making sense of things becomes visible. Metaphors compress a lot of meaning — beliefs, feelings and relationships — into one image, and changing the metaphor often changes the behaviour. In teams, the discovery that members use the same word very differently is often the breakthrough: they were never actually disagreeing about the same thing.

Quick card

Reach for it when
The team uses strong metaphors (“we’re firefighting”, “a sinking ship”); the same loaded words keep recurring; members mean very different things by the same word
The move
Ask “clean” questions that use only the team’s own words, so the team explores its own metaphors without the coach adding meaning
Watch
Clean questions sound unusual at first. Explain briefly, then use them sparingly and slowly; the power is in the silence after the question.
Four questions that often open it
  1. And when the team is working at its best, that’s like what?
  2. And what kind of “firefighting” is that?
  3. And is there anything else about that?
  4. And what would you like to have happen?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Loaded words — “accountability”, “alignment” or “quality” mean different things to different members.
  • Strong metaphors — the team describes itself in vivid images.
  • Polarised language — members repeat the same positions in the same words.
  • Coach-led framing — the team has adopted the coach’s or leader’s language and lost its own.
  • Visioning — the team wants a shared picture of its best.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Clean definition round — each member answers “And what kind of [word] is that, for you?” for a contested word.
2Explore a metaphor — develop the team’s existing metaphor with clean questions.
3Best-working metaphor — each member answers “When this team is at its best, that’s like what?”, then the team builds a shared image.
4Clean feedback — feedback that separates observation, inference and impact, in the speaker’s own words.

5Where it gets stuck

Members find the questions repetitive or strange. One person’s metaphor dominates. The exploration becomes poetic but disconnected from work.

6How to move it forward

Explain what you are doing and why. Keep sessions short. Always bring the metaphor back to practice: “And when the team is like that, what happens on a Monday morning?”

7Questions to ask the team

Core questions
  • And what kind of [word] is that?
  • And is there anything else about [word]?
  • And when [metaphor], what happens next?
  • And what would you like to have happen?
  • And what needs to happen for that?
Going further
  • And where does that come from?
  • And that’s [word] like what?
  • And when the team is at its best, what’s different?
  • And what is between [X] and [Y]?
  • And what can the team do to make that more likely?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S3.9The same debate on loopThe team repeats the same argument without resolution
What is happening The team repeats the same argument without resolutionCoach move Map the pattern or polarity; change the structure of the conversation
In the room
Familiar arguments, same people, same positions. Frustration and fatigue.
What’s underneath
Repeated debates often indicate a polarity (both sides needed), a missing decision process, or a pattern of conversational moves.
Avoid here
Joining the debate. Forcing a decision.
Example
Product team. Speed vs quality polarity map ended a year-long debate.
Full situation card: questions, examples, sample exchange
Filed under methods1710923
S5.6Disagree on what success meansMembers use different definitions of success
What is happening Members use different definitions of successCoach move Build a shared preferred future; use data
In the room
Arguments about outcomes; “we’re doing well” vs “we’re failing”.
What’s underneath
Without a shared definition of success, teams pull in different directions.
Avoid here
Choosing one definition.
Example
Software team. Defined success as reliable releases and customer satisfaction.
Full situation card: questions, examples, sample exchange
Filed under methods338623
S8.11Generational or neurodiversity frictionDifferent ways of thinking, communicating and working cause misunderstanding
What is happening Different ways of thinking, communicating and working cause misunderstandingCoach move Make differences in style explicit and design working norms that let different minds contribute
In the room
Frustration about “how they communicate”. Some members find meetings overwhelming; others find written channels cold. Jokes about generations. Some people mask or withdraw.
What’s underneath
Differences in generation, neurotype and working style are often read as attitude problems (“disrespectful”, “slow”, “difficult”). Many standard team practices — fast open discussion, open-plan noise, unstructured brainstorming — favour some minds over others. Inclusion means designing for difference, not asking people to adapt to one norm. Disclosure of neurodivergence is personal and voluntary.
Avoid here
Stereotyping generations. Asking anyone to disclose a diagnosis. Treating one communication style as “professional” and others as wrong.
Example
Product team. User manuals revealed that two members needed agendas in advance and written follow-ups. The team adopted “agenda 24 hours ahead, decisions in writing” — and everyone benefited.
Full situation card: questions, examples, sample exchange
Filed under methods2642328

9Coach mistakes & watch-outs

  • Paraphrasing or adding words.
  • Interpreting the metaphor for the team.
  • Asking clean questions mechanically without pause.
  • Staying in metaphor and never landing.

10Team traps

  • Laughing off metaphors.
  • Arguing about whose metaphor is right.
  • Using metaphor to stay vague.

Three worked problems

1

“Accountability”. A leader wants “more accountability”. Asked “And what kind of accountability is that, for you?”, members give five different answers — from “blame” to “keeping promises”. The team agrees a definition and the tension eases.

2

The sinking ship. A team calls itself a sinking ship. Clean questions reveal that, for members, it is “leaking, not sinking” — specific holes in processes. The team lists its leaks and patches two.

3

The orchestra. Members describe the team at its best as “an orchestra without a conductor, where everyone listens”. The image becomes the guide for meeting design.

Where it comes from

David Grove’s Clean Language; Penny Tompkins and James Lawley’s Symbolic Modelling; Caitlin Walker’s “Systemic Modelling” for teams and organisations; Lakoff and Johnson’s work on metaphor.

My notes

24
Shift the Team Frame family

Theory U and Presencing Practices

Core move: Move the team from reacting with old patterns to sensing what the situation really needs
4 options10 questions4 situations

1What it really is

Otto Scharmer’s Theory U describes a journey down one side of a “U” — from downloading habitual patterns, to seeing freshly, to sensing from the whole system — to a point of stillness (presencing), and up the other side through crystallising an intention, prototyping and performing. Its four levels of listening are a practical coaching tool: downloading (hearing what confirms what we already know), factual (noticing new data), empathic (seeing through another’s eyes) and generative (listening for what wants to emerge). Operationalised for teams, the practices are: sensing journeys (visiting places where the problem lives), dialogue interviews with stakeholders, guided stillness and reflection, and rapid prototyping.

4How it works, deeply

Most team problem-solving happens at the top-left of the U: the team downloads its usual frame and applies its usual fix. Theory U argues that better solutions come from changing the quality of attention — the place from which people act. Sensing journeys break the expert stance by putting members in direct contact with reality. Shared stillness after intense sensing helps the team let go of old assumptions before it decides. Prototyping replaces big plans with fast learning. For the coach, the levels of listening are also a diagnostic: you can hear which level a team conversation is at.

Quick card

Reach for it when
The team keeps applying old solutions to new problems; it is stuck in expert or reactive mode; it needs innovation, not more analysis; the future is genuinely uncertain
The move
Slow the team down to see the system freshly — through sensing journeys, dialogue interviews and stillness — then prototype small and fast
Watch
Theory U can sound abstract or mystical. Keep it practical: real visits, real interviews, real prototypes.
Four questions that often open it
  1. What are we assuming because we’ve always assumed it?
  2. What would we see if we stood in our customer’s shoes for a day?
  3. What is emerging that we can’t yet name?
  4. What could we try in two weeks to learn fast?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Old solutions, new problems — the team keeps doing what worked before.
  • Expert trap — the team believes it already knows; little curiosity.
  • Reactive mode — constant firefighting, no space to think.
  • Innovation brief — the team must create something new.
  • Systemic stuckness — many stakeholders, no clear cause.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Sensing journey — small groups visit customers, partners or front-line sites with the brief to observe and listen, not to fix.
2Dialogue interviews — structured conversations with stakeholders about their experience and their hopes for the system.
3Presencing pause — silent reflection or journalling on “What is mine to do? What wants to emerge?”
4Prototyping — a small, fast, cheap experiment to learn from reality, not to prove a plan.

5Where it gets stuck

The team skips sensing and jumps to solutions. Members find the language too abstract. Stillness feels uncomfortable. Prototypes become pilots that are too big to fail.

6How to move it forward

Use plain language (“seeing with fresh eyes”, “testing quickly”). Make the sensing concrete and time-boxed. Keep stillness short (five minutes is enough). Insist that prototypes are small enough to throw away.

7Questions to ask the team

Core questions
  • Which level of listening are we at right now?
  • What did you see on the journey that surprised you?
  • What did the stakeholder say that we didn’t want to hear?
  • What wants to emerge here?
  • What’s the smallest prototype we could try?
Going further
  • What are we holding on to that we need to let go of?
  • Who in the system is closest to the problem?
  • What would our future self thank us for?
  • What would we try if we knew we couldn’t fail?
  • What will we learn from this prototype, whatever happens?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S3.4GroupthinkThe team agrees quickly; dissent is absent
What is happening The team agrees quickly; dissent is absentCoach move Legitimise dissent; use pre-mortems and red teams
In the room
Fast agreement, nodding, nobody challenges. Ideas aren’t tested.
What’s underneath
Groupthink (Irving Janis) happens with high cohesion and pressure for consensus. The team avoids conflict and misses risks.
Avoid here
Accepting quick agreement. Appointing the same devil’s advocate.
Example
Board. A pre-mortem revealed concerns about an acquisition.
Full situation card: questions, examples, sample exchange
Filed under methods34271024
S5.4Strategy unclearThe team doesn’t understand the organisation’s direction
What is happening The team doesn’t understand the organisation’s directionCoach move Clarify what is known; connect to stakeholders; build preferred future
In the room
Questions, confusion, speculation.
What’s underneath
Unclear strategy makes team prioritisation hard. The team may need to seek clarity or create its own direction.
Avoid here
Inventing strategy for the organisation.
Example
Regional team. Invited the strategy director to a session.
Full situation card: questions, examples, sample exchange
Filed under methods6163324
S3.12Innovation or creative stucknessThe team needs new ideas but keeps producing variations of old ones
What is happening The team needs new ideas but keeps producing variations of old onesCoach move Change the quality of attention: sense the system freshly, include every voice, then prototype small
In the room
Brainstorms produce the usual suspects. Ideas are judged within seconds. Energy is dutiful. Members say “we tried that” more than “what if”.
What’s underneath
Creative stuckness is rarely a lack of talent. It usually comes from downloading old patterns, premature judgment, fear of looking foolish, or being too far from the people who experience the problem. It is different from conflict or groupthink: the team agrees — on the old answer.
Avoid here
Another open brainstorm with the same people and the same format. Judging ideas as they emerge. Asking for “blue-sky” ideas without contact with reality.
Example
Retail product team. Three brainstorms produced nothing new. A half-day sensing journey in stores revealed staff workarounds that became the new product idea.
Full situation card: questions, examples, sample exchange
Filed under methods241520
S8.12AI or new tool adoption changes how the team worksNew AI or digital tools change roles, decisions and expertise
What is happening New AI or digital tools change roles, decisions and expertiseCoach move Treat adoption as a team change: explore hopes and fears, agree principles, and run small experiments with review
In the room
Excitement from some, anxiety from others. Unspoken worries about jobs and expertise. Inconsistent use: some members use AI for everything, others not at all. Confusion about who is accountable for AI-assisted work.
What’s underneath
New tools change more than tasks: they change status (whose expertise matters), decision rights (who checks what), trust and quality standards. If these are not discussed, teams split into enthusiasts and resisters, and risks go unmanaged. It is a classic polarity — speed and innovation versus quality and safety.
Avoid here
Taking sides between enthusiasts and sceptics. Ignoring job-security fears. Letting adoption happen individually without team agreements.
Example
Marketing team. Polarity mapping of speed vs quality led to principles: AI drafts, humans decide and check facts. Anxiety eased; output rose.
Full situation card: questions, examples, sample exchange
Filed under methods24374017

9Coach mistakes & watch-outs

  • Using the vocabulary without the practices.
  • Skipping the downward part of the U.
  • Making prototypes too big.
  • Forcing reflective practices on a sceptical team.

10Team traps

  • “We already know our customers.”
  • Treating stillness as wasted time.
  • Turning prototypes into plans.

Three worked problems

1

The sensing journey. A bank’s product team spends half a day in branches. They see customers struggling with a form they designed. Back in the session, after a short silent reflection, they prototype a simpler form in two weeks.

2

Levels of listening. The coach introduces the four levels. Members notice that most of their meetings are “downloading”. They add a rule: before debating, one person summarises the other’s view in a way the other agrees with.

3

Dialogue interviews. A leadership team interviews ten stakeholders. A recurring theme — “you never ask us” — reshapes the team’s purpose.

Where it comes from

C. Otto Scharmer, “Theory U” (2007) and the Presencing Institute; Peter Senge et al., “Presence”; related to design thinking and Agile prototyping.

Theory behind it · Knowledge Library10Theory U and the learning organisation

My notes

Family 4 of 6 · Methods 25–32 · When relationships limit the work

Trust, Conflict and Voice

Can the team say true things to each other and stay a team?

Every team problem eventually becomes a relationship problem, and every relationship problem shows up in the room. This family is about the conditions that let a team tell itself the truth: psychological safety, knowing each other as people, conflict about ideas rather than persons, voice for the minority, peer feedback, repair when something breaks, and honest work with the power of the leader.

These methods ask more of the coach’s presence than any others. The coach is no longer only facilitating a conversation about relationships; the relationships are happening, live, in front of them.

25
Trust, Conflict and Voice family

Build Psychological Safety

Core move: Make it safe to speak up, admit mistakes and ask for help
4 options10 questions8 situations

1What it really is

Amy Edmondson defines team psychological safety as a shared belief that the team is safe for interpersonal risk-taking. Google’s Project Aristotle found it was the most important factor in team effectiveness. Building it involves three leader and team behaviours: setting the stage (framing work as uncertain and needing everyone’s input), inviting participation (asking questions, acknowledging limits) and responding productively (appreciating voice, destigmatising failure). The coach helps the team assess its safety and practise these behaviours in sessions.

4How it works, deeply

Psychological safety is a group property, not an individual trait. It is created by repeated small experiences: how the team responds when someone takes a risk. The coach can help by naming the risk-taking, modelling curiosity and slowing down defensive reactions. The leader’s behaviour matters most, but members also shape safety through how they respond to each other. Safety is fragile: one harsh reaction can undo months of work.

Quick card

Reach for it when
Members don’t speak up; mistakes are hidden; questions are rare; the team avoids risk; after punishment of dissent
The move
Frame the work as learning, invite participation explicitly, and respond productively to every contribution
Watch
Psychological safety is not comfort or niceness. It is the confidence that candour will be welcomed, which often means more discomfort, not less.
Four questions that often open it
  1. What makes it risky to speak up here?
  2. When did someone take a risk and it went well?
  3. How do we respond when someone admits a mistake?
  4. What would make it easier to say “I don’t know”?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Silence — members rarely speak up in meetings.
  • Hidden mistakes — errors are discovered late.
  • Fear of the leader — members watch the leader before speaking.
  • Recent punishment — someone was criticised publicly for speaking up.
  • Homogeneous voices — only senior or majority voices are heard.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Safety check — anonymous scale: how safe is it to raise a difficult issue here?
2Failure stories — the leader and members share mistakes and what they learned.
3Response practice — practise responding productively to bad news.
4Norms for voice — agree specific behaviours (“no interruptions”, “questions welcome”).

5Where it gets stuck

The team says it is safe but behaviour shows otherwise. The leader is defensive when safety is discussed. Members wait for the leader to change first. Safety is confused with comfort.

6How to move it forward

Use anonymous data. Ask the leader to go first with vulnerability. Celebrate the first risk-taking in the room. Agree specific responses to bad news.

7Questions to ask the team

Core questions
  • How safe does it feel to raise a concern here, on a scale of 1–10?
  • What would make it a little safer?
  • What happens when someone makes a mistake?
  • Who do you watch before you speak?
  • What do we need from each other?
Going further
  • When did you last hold back? Why?
  • What did the team learn the last time someone failed?
  • How does the leader respond to bad news?
  • What would a new member need to feel safe?
  • What do we gain from staying quiet?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S2.1Low trustMembers protect themselves; candour is rare
What is happening Members protect themselves; candour is rareCoach move Build safety in small steps; start with understanding each other
In the room
Careful wording, guarded body language. People check each other’s reactions. Information is shared selectively.
What’s underneath
Low trust may come from past betrayal, competition, unclear intentions or a punishing culture. Trust grows from repeated experiences of vulnerability met with respect.
Avoid here
Forcing vulnerability. Trust-falls. Asking for honesty without protecting it.
Example
Sales leadership. Started with personal histories. Members heard each other’s backgrounds. Three sessions later, they shared performance worries.
Full situation card: questions, examples, sample exchange
Filed under methods25264
S2.2Fear after layoffs or restructuringMembers are anxious about their jobs; survivor guilt; silence
What is happening Members are anxious about their jobs; survivor guilt; silenceCoach move Acknowledge the fear; make space for what happened before moving on
In the room
Quiet. People look tired. Questions about future plans are met with “who knows”. Some members are overly busy.
What’s underneath
Layoffs create grief, fear and survivor guilt. The team may withdraw, avoid risk and protect itself. Ignoring the emotional impact makes any coaching superficial.
Avoid here
Jumping to vision or performance. Pretending things are normal. Making promises about job security.
Example
Tech team. After 20% cuts, the first session was a check-in and timeline. Members talked about colleagues who left. The next session moved to priorities with more energy.
Full situation card: questions, examples, sample exchange
Filed under methods25511
S2.5Anxiety about changeUpcoming change creates worry and speculation
What is happening Upcoming change creates worry and speculationCoach move Separate known from unknown; build a shared preferred future; manage polarities
In the room
Rumours, “what if” questions, catastrophising. Some members very vocal, others withdrawn.
What’s underneath
Uncertainty is harder than bad news. Anxiety often fills the vacuum with worst-case stories. Teams need to separate what they know, what they don’t, and what they can influence.
Avoid here
False reassurance. Spending the session on rumours. Dismissing anxiety.
Example
Finance shared services. Sorted rumours into known, unknown and influence. Sent questions to the sponsor. Anxiety dropped.
Full situation card: questions, examples, sample exchange
Filed under methods331725
S3.2Silent membersSome members rarely speak
What is happening Some members rarely speakCoach move Use structure and invitation; understand the silence
In the room
The same people silent each session. They may look engaged or withdrawn.
What’s underneath
Silence can mean thinking, disagreement, cultural norms, low safety, or disengagement. Don’t assume.
Avoid here
Putting people on the spot. Assuming silence means agreement.
Example
Multicultural team. Writing first and rounds increased contributions.
Full situation card: questions, examples, sample exchange
Filed under methods5282515
S4.3Conflict avoided at all costsThe team avoids any disagreement
What is happening The team avoids any disagreementCoach move Build safety and structures for productive conflict
In the room
Quick agreement, topic changes when tension rises, “let’s take it offline”.
What’s underneath
Conflict avoidance protects relationships short term and damages decisions long term. Lencioni calls it fear of conflict.
Avoid here
Forcing conflict before safety. Calling the team weak.
Example
Charity board. Red team exercise surfaced concerns about a project.
Full situation card: questions, examples, sample exchange
Filed under methods272534
S4.5Trust breach / leakSomething said in confidence was shared outside
What is happening Something said in confidence was shared outsideCoach move Revisit agreements; repair; rebuild confidentiality
In the room
Shock, anger, suspicion. Members are careful and silent.
What’s underneath
A leak damages the safety of the whole team. Without repair, members will withdraw.
Avoid here
Witch hunts. Ignoring the breach.
Example
Leadership team. Revisited confidentiality agreements; the person responsible apologised.
Full situation card: questions, examples, sample exchange
Filed under methods43125
S7.6Leader defensive under feedbackThe leader reacts badly to team feedback
What is happening The leader reacts badly to team feedbackCoach move Prepare the leader; model curiosity; safety
In the room
The leader explains, defends or corrects when feedback arrives; the team goes quiet and withdraws.
What’s underneath
Defensiveness under feedback quickly reduces team safety. Leaders often feel exposed in front of their own team.
Avoid here
Exposing the leader.
Example
Executive team. The leader prepared privately with the coach and responded with curiosity in the session.
Full situation card: questions, examples, sample exchange
Filed under methods32825
S4.11The team that is “too nice”Warm relationships, low challenge — and quietly declining performance
What is happening Warm relationships, low challenge — and quietly declining performanceCoach move Name the cost of harmony; make challenge a form of care
In the room
Lots of appreciation, few questions. Problems are softened into “small things”. Underperformance is worked around rather than discussed. People leave meetings smiling and nothing changes.
What’s underneath
Excessive harmony is a comfort zone (high safety, low standards). It protects relationships at the cost of results — and, over time, of the relationships themselves, because unspoken frustration builds. The team often has a shared value (“we’re caring”) that has become a shadow: directness is not allowed.
Avoid here
Shaming the team for being kind. Jumping straight to hard-hitting feedback. Treating it only as conflict avoidance — the performance cost must be visible.
Example
Charity leadership team. Scored very high on safety, low on accountability. The coach showed the learning-zone model; members placed themselves in the comfort zone. They agreed “kind and clear” norms.
Full situation card: questions, examples, sample exchange
Filed under methods27143025

9Coach mistakes & watch-outs

  • Equating safety with comfort.
  • Asking for honesty without protecting it.
  • Not addressing a harsh reaction in the room.
  • Putting the responsibility only on the leader.

10Team traps

  • Saying “we’re all friends here”.
  • Testing safety by attacking someone.
  • Waiting for others to take the first risk.

Three worked problems

1

The anonymous scale. Members rate safety at an average of 4 of 10; the leader rated 8. The gap shocks the leader. She asks what she does that makes speaking up risky. Members describe her quick “no” responses. She agrees to ask a question before responding.

2

Failure CV. Each member shares a professional failure and what they learned. The CEO goes first. The session is quieter and warmer than any before.

3

First risk. A junior member says she disagrees with the plan. The coach pauses: “What did it take to say that?” The leader thanks her. Two more people raise concerns.

Where it comes from

Amy Edmondson’s research on team psychological safety (“The Fearless Organization”); Google’s Project Aristotle; William Kahn’s work on engagement.

My notes

26
Trust, Conflict and Voice family

Personal Histories and User Manuals

Core move: Build trust by letting members know each other as people
4 options10 questions8 situations

1What it really is

Teams trust people they know. Patrick Lencioni’s personal histories exercise asks members to share simple personal information (where they grew up, number of siblings, a childhood challenge). The user manual approach asks members to describe how they work best: preferences, triggers, communication style, what they need from others. Both increase understanding and reduce misattribution. They are simple and low-risk, but often produce surprising shifts in how members see each other.

4How it works, deeply

Trust in teams is often “vulnerability-based trust”: confidence that team members will not use weaknesses against each other. Sharing personal information is a small step into vulnerability, and when it is received well, trust grows. User manuals also prevent attribution errors: once members know that someone needs time to think before responding, silence is no longer read as disagreement.

Quick card

Reach for it when
New team; low trust; members misread each other; conflicts based on working style differences
The move
Invite members to share a little personal history or a “user manual” for working with them
Watch
Vulnerability cannot be demanded. Offer choice about depth, and let the leader or coach model first.
Four questions that often open it
  1. Where did you grow up, and what was a challenge you faced as a child?
  2. What should people know about working with you?
  3. What brings out your best?
  4. What frustrates you in teams?

2The team’s context

A team needing this method usually shows up in one of these states:

  • New team — members don’t know each other.
  • Misreading — styles are misinterpreted (“he’s rude”, “she’s slow”).
  • Low vulnerability — members only show professional facades.
  • Diverse backgrounds — different cultures, ages, experiences.
  • Remote team — members have never met in person.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Personal histories — three simple questions, two minutes each.
2User manual — each member writes one page: how I work best, what I need, what annoys me.
3Journey line — personal or career journey shared in pairs.
4Values cards — each chooses values cards and explains them.

5Where it gets stuck

Members share superficial information. Someone shares too much and others feel uncomfortable. The exercise feels forced in some cultures. The leader does not participate.

6How to move it forward

Model with appropriate depth. Explicitly allow choice. Adapt questions to cultural context. Follow up: “How has what you learned changed how you work together?”

7Questions to ask the team

Core questions
  • What should we know about you to work well with you?
  • What helps you do your best work?
  • What triggers stress for you?
  • How do you prefer to get feedback?
  • What did you learn about each other today?
Going further
  • What do people often misunderstand about you?
  • What’s something about your background that shapes how you work?
  • What would you like to know about your colleagues?
  • How do your preferences clash with others’?
  • What will you do differently now?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S1.9Newly formed teamMembers are new to each other and to the task
What is happening Members are new to each other and to the taskCoach move Build working agreements, purpose and relationships early
In the room
Polite introductions, careful words. People explain their backgrounds. Questions about roles are tentative.
What’s underneath
Tuckman’s “forming” stage: members look for belonging and clarity. Early norms shape the team for years. This is a window of maximum influence.
Avoid here
Rushing into task without relationships. Assuming norms will form well by themselves.
Example
Startup leadership. Spent the first session on user manuals and working agreements. Six months later, they still referred to them.
Full situation card: questions, examples, sample exchange
Filed under methods42663
S1.10Merged team (“us and them”)Two former teams now one; old identities persist
What is happening Two former teams now one; old identities persistCoach move Honour both histories, then build a shared story and purpose
In the room
Members sit with their old team. Language like “we used to” and “their way”. Jokes with an edge.
What’s underneath
Mergers cause loss — of identity, status, ways of working. Unacknowledged loss turns into resistance. A new identity forms only after old ones are respected.
Avoid here
Forcing a new identity too quickly. Ignoring grief. Taking sides.
Example
Bank merger. Two teams drew their timelines and shared them. They found common experiences. A shared purpose emerged.
Full situation card: questions, examples, sample exchange
Filed under methods11262045
S2.1Low trustMembers protect themselves; candour is rare
What is happening Members protect themselves; candour is rareCoach move Build safety in small steps; start with understanding each other
In the room
Careful wording, guarded body language. People check each other’s reactions. Information is shared selectively.
What’s underneath
Low trust may come from past betrayal, competition, unclear intentions or a punishing culture. Trust grows from repeated experiences of vulnerability met with respect.
Avoid here
Forcing vulnerability. Trust-falls. Asking for honesty without protecting it.
Example
Sales leadership. Started with personal histories. Members heard each other’s backgrounds. Three sessions later, they shared performance worries.
Full situation card: questions, examples, sample exchange
Filed under methods25264
S4.7Cross-cultural misunderstandingDifferent cultural norms lead to misinterpretations
What is happening Different cultural norms lead to misinterpretationsCoach move Explore cultural assumptions; build shared norms
In the room
Confusion, frustration, members feeling disrespected without knowing why.
What’s underneath
Cultures differ in directness, hierarchy, time and conflict. Behaviours are often misread through one’s own cultural lens.
Avoid here
Stereotyping. Ignoring culture.
Example
Global team. User manuals revealed different norms; the team created communication guidelines.
Full situation card: questions, examples, sample exchange
Filed under methods26224
S7.4New leader inherits teamA new leader takes over an existing team
What is happening A new leader takes over an existing teamCoach move Timeline; personal histories; leader role contracting
In the room
Members compare the new leader with the old one, test boundaries, and hold back. The new leader tries to make a quick impact.
What’s underneath
Transitions create anxiety and loyalty conflicts. Members wonder what will change; the leader wonders whom to trust.
Avoid here
Comparing leaders.
Example
Finance team. A new-leader assimilation session let the team ask questions anonymously; the leader answered them openly.
Full situation card: questions, examples, sample exchange
Filed under methods11263245
S8.3Multicultural teamMembers from different cultures bring different norms
What is happening Members from different cultures bring different normsCoach move Surface norms; build shared agreements; treat difference as resource
In the room
Different speaking styles, silence norms, attitudes to hierarchy and time.
What’s underneath
Cultural differences in communication, hierarchy and conflict (Erin Meyer’s culture map) shape team dynamics. Differences can be strengths if they are discussed.
Avoid here
Stereotypes. Assuming one culture is the norm.
Example
Global IT team. Mapped members on directness and hierarchy scales and agreed norms.
Full situation card: questions, examples, sample exchange
Filed under methods26224
S8.4Rapid growth / many new membersThe team is growing fast; culture is diluting
What is happening The team is growing fast; culture is dilutingCoach move Explicit norms; onboarding rituals; rhythms
In the room
Many new faces; old-timers nostalgic; confusion about how things work.
What’s underneath
Growth stretches informal norms. What worked when small no longer works.
Avoid here
Nostalgia. Ignoring newcomers.
Example
Startup. Wrote team agreements and an onboarding guide; new joiners got up to speed faster.
Full situation card: questions, examples, sample exchange
Filed under methods426443
S8.11Generational or neurodiversity frictionDifferent ways of thinking, communicating and working cause misunderstanding
What is happening Different ways of thinking, communicating and working cause misunderstandingCoach move Make differences in style explicit and design working norms that let different minds contribute
In the room
Frustration about “how they communicate”. Some members find meetings overwhelming; others find written channels cold. Jokes about generations. Some people mask or withdraw.
What’s underneath
Differences in generation, neurotype and working style are often read as attitude problems (“disrespectful”, “slow”, “difficult”). Many standard team practices — fast open discussion, open-plan noise, unstructured brainstorming — favour some minds over others. Inclusion means designing for difference, not asking people to adapt to one norm. Disclosure of neurodivergence is personal and voluntary.
Avoid here
Stereotyping generations. Asking anyone to disclose a diagnosis. Treating one communication style as “professional” and others as wrong.
Example
Product team. User manuals revealed that two members needed agendas in advance and written follow-ups. The team adopted “agenda 24 hours ahead, decisions in writing” — and everyone benefited.
Full situation card: questions, examples, sample exchange
Filed under methods2642328

9Coach mistakes & watch-outs

  • Forcing personal disclosure.
  • Doing it once and never referring to it again.
  • Excluding the leader.
  • Ignoring cultural norms about privacy.

10Team traps

  • Over-sharing to impress.
  • Sharing only polished stories.
  • Using user manuals as excuses (“that’s just how I am”).

Three worked problems

1

The rude engineer. A team finds one engineer abrupt. In his user manual he explains he prefers brief messages and assumes others do too. The team agrees on communication norms. Tension drops.

2

Three questions. A new leadership team shares personal histories. The CFO talks about growing up in a refugee family. The team sees his caution differently.

3

Remote manual. A global remote team shares user manuals including time zones and preferred channels. Misunderstandings decrease.

Where it comes from

Patrick Lencioni’s “The Five Dysfunctions of a Team” (personal histories); user manual practice from Agile and leadership development.

My notes

27
Trust, Conflict and Voice family

Make Conflict Productive

Core move: Turn avoided or destructive conflict into useful debate about ideas
4 options10 questions6 situations

1What it really is

Research distinguishes task conflict (about ideas and decisions) from relationship conflict (about people and personalities). Moderate task conflict improves decisions; relationship conflict damages teams. Patrick Lencioni names fear of conflict as a core team dysfunction. This method helps the team examine its conflict norms, separate ideas from people, and use structured debate tools such as steelmanning (stating the other view at its strongest), red teams, and devil’s advocate roles.

4How it works, deeply

Teams need conflict about ideas to make good decisions. But conflict is uncomfortable, and many teams avoid it or let it become personal. Structures make conflict safe by depersonalising it: when someone is assigned to argue against a proposal, their challenge is seen as a role, not an attack. Steelmanning builds understanding. Clear norms reduce fear. Over time, the team learns that disagreement is a sign of engagement, not disloyalty.

Quick card

Reach for it when
The team avoids disagreement; conflict turns personal; decisions are weak because nobody challenged them
The move
Distinguish task conflict from relationship conflict, and give the team structures for debating ideas safely
Watch
Encouraging conflict in a team without safety can cause harm. Build norms and safety first.
Four questions that often open it
  1. What disagreements are we avoiding?
  2. How do we usually handle conflict?
  3. What makes disagreement feel personal?
  4. What structure would help us debate well?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Artificial harmony — everyone agrees in meetings and complains afterwards.
  • Personal attacks — disagreements become insults.
  • Conflict styles clash — some members argue loudly, others withdraw.
  • Leader avoidance — the leader shuts down conflict quickly.
  • Escalation — every disagreement goes to the boss.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Conflict norms — the team agrees how it wants to disagree.
2Steelman — each side states the other’s view until the other agrees it’s fair.
3Red team — a subgroup argues against the proposal.
4Conflict profile — the team maps members’ preferred conflict styles (e.g. Thomas-Kilmann).

5Where it gets stuck

The team tries debate and it becomes personal. Members use structured debate to score points. Avoidant members withdraw further. The leader still decides alone after the debate.

6How to move it forward

Debrief each debate: how did it feel, what did we learn? Name and stop personal attacks immediately. Agree how decisions will be made after debate.

7Questions to ask the team

Core questions
  • What are we not disagreeing about that we should?
  • What makes conflict feel risky here?
  • How do we want to disagree?
  • What does good conflict look like?
  • What would help us stay on the issue, not the person?
Going further
  • What is the best argument against our current plan?
  • Who usually avoids conflict? Who usually escalates?
  • What happens after we disagree?
  • When did a disagreement improve a decision?
  • What would you say if you knew it wouldn’t damage relationships?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S3.4GroupthinkThe team agrees quickly; dissent is absent
What is happening The team agrees quickly; dissent is absentCoach move Legitimise dissent; use pre-mortems and red teams
In the room
Fast agreement, nodding, nobody challenges. Ideas aren’t tested.
What’s underneath
Groupthink (Irving Janis) happens with high cohesion and pressure for consensus. The team avoids conflict and misses risks.
Avoid here
Accepting quick agreement. Appointing the same devil’s advocate.
Example
Board. A pre-mortem revealed concerns about an acquisition.
Full situation card: questions, examples, sample exchange
Filed under methods34271024
S4.1Open hostility between two membersTwo members clash openly; the team watches
What is happening Two members clash openly; the team watchesCoach move Slow down; separate positions from needs; negotiate specific agreements
In the room
Sharp tone, sarcasm, raised voices between two people. Others go quiet or take sides.
What’s underneath
Open conflict between two members affects the whole team. It may involve real differences in role, values or interests, plus personal history. The team often colludes by avoiding it.
Avoid here
Mediating a personal dispute in public without consent. Taking sides. Letting it escalate.
Example
Sales and delivery heads. Role negotiation produced three specific agreements; hostility fell.
Full situation card: questions, examples, sample exchange
Filed under methods313927
S4.2Covert conflict / passive aggressionConflict shows up as sarcasm, delays, missed deadlines
What is happening Conflict shows up as sarcasm, delays, missed deadlinesCoach move Name the pattern; make it discussable; explore underlying conflict
In the room
Polite words, sharp undertones. “Forgotten” tasks. Eye-rolls.
What’s underneath
Passive aggression occurs when open conflict feels unsafe. The conflict leaks out indirectly.
Avoid here
Accusing individuals. Ignoring the pattern.
Example
Marketing team. Left-hand column revealed unspoken criticism; the team discussed it openly.
Full situation card: questions, examples, sample exchange
Filed under methods13272214
S4.3Conflict avoided at all costsThe team avoids any disagreement
What is happening The team avoids any disagreementCoach move Build safety and structures for productive conflict
In the room
Quick agreement, topic changes when tension rises, “let’s take it offline”.
What’s underneath
Conflict avoidance protects relationships short term and damages decisions long term. Lencioni calls it fear of conflict.
Avoid here
Forcing conflict before safety. Calling the team weak.
Example
Charity board. Red team exercise surfaced concerns about a project.
Full situation card: questions, examples, sample exchange
Filed under methods272534
S4.4Disagreement turns personalA task disagreement becomes an attack on a person
What is happening A task disagreement becomes an attack on a personCoach move Pause; separate the idea from the person; restore norms
In the room
Tone sharpens, “you” statements, references to character.
What’s underneath
Task conflict turns into relationship conflict when people feel threatened or disrespected.
Avoid here
Ignoring personal attacks.
Example
Strategy team. Coach paused and reminded the team of its agreement; members rephrased.
Full situation card: questions, examples, sample exchange
Filed under methods27314
S4.11The team that is “too nice”Warm relationships, low challenge — and quietly declining performance
What is happening Warm relationships, low challenge — and quietly declining performanceCoach move Name the cost of harmony; make challenge a form of care
In the room
Lots of appreciation, few questions. Problems are softened into “small things”. Underperformance is worked around rather than discussed. People leave meetings smiling and nothing changes.
What’s underneath
Excessive harmony is a comfort zone (high safety, low standards). It protects relationships at the cost of results — and, over time, of the relationships themselves, because unspoken frustration builds. The team often has a shared value (“we’re caring”) that has become a shadow: directness is not allowed.
Avoid here
Shaming the team for being kind. Jumping straight to hard-hitting feedback. Treating it only as conflict avoidance — the performance cost must be visible.
Example
Charity leadership team. Scored very high on safety, low on accountability. The coach showed the learning-zone model; members placed themselves in the comfort zone. They agreed “kind and clear” norms.
Full situation card: questions, examples, sample exchange
Filed under methods27143025

9Coach mistakes & watch-outs

  • Encouraging conflict without safety.
  • Not intervening when conflict turns personal.
  • Treating all conflict as good.
  • Forgetting that some members find conflict very difficult.

10Team traps

  • Debate as performance.
  • Personalising disagreements.
  • Agreeing to debate norms and then avoiding conflict anyway.

Three worked problems

1

Artificial harmony. A team agrees with every proposal; complaints appear later. The coach introduces a rule: every proposal needs a red team. The first red team finds a serious flaw. The team starts to value challenge.

2

Steelman. Two members have argued about centralising procurement for months. Each must state the other’s view to the other’s satisfaction. It takes three attempts. Their final proposal combines both.

3

Conflict styles. The team maps conflict styles. The leader discovers she is the only “competing” style; others mostly “accommodate”. She realises why debates feel one-sided.

Where it comes from

Research on task and relationship conflict (Karen Jehn), Patrick Lencioni’s Five Dysfunctions, Thomas-Kilmann conflict modes, and decision-making practices like red teaming.

My notes

28
Trust, Conflict and Voice family

Hear the Minority Voice

Core move: Give voice to dissent and unspoken views before they go underground
4 options10 questions7 situations

1What it really is

Myrna Lewis’ Deep Democracy (the Lewis Method) assumes that the minority view often contains wisdom the group needs. If it is ignored, it goes underground and sabotages decisions. The method has the team surface all views, especially the minority’s, ask what it would take for the minority to come along, and add that wisdom to the majority decision. Even where the majority decides, the minority feels heard, and decisions are better.

4How it works, deeply

Teams often believe a quick majority vote is democratic. But unspoken disagreement doesn’t disappear; it becomes resistance. Deep Democracy makes the “no” visible and useful. It also distributes the minority position — often several people share part of the dissent but only one has spoken. When they speak, the dissenter is no longer isolated. The result is a decision more people commit to.

Quick card

Reach for it when
Majority views dominate; people agree but don’t commit; dissent is shut down; some members are always outvoted
The move
Ask who sees it differently, and give the minority view full attention until the team understands its wisdom
Watch
Inviting the minority voice is not the same as letting it win. The goal is that its wisdom is heard and included.
Four questions that often open it
  1. Who sees this differently?
  2. What’s the wisdom in the minority view?
  3. What would it take for everyone to go along with this?
  4. What are we not hearing yet?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Steamrolling — a majority or a senior subgroup always wins.
  • Quiet dissent — people agree but don’t commit.
  • Diverse team — some voices (gender, culture, age, role) are marginalised.
  • Repeated sabotage — decisions are undermined after meetings.
  • Leader decisions — the leader decides; dissenters withdraw.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Gather all views — round of opinions before decisions.
2Spread the no — ask others to say if they share any part of the minority view.
3What would it take — ask the minority what would help them come along.
4Add the wisdom — incorporate the minority’s concerns into the decision.

5Where it gets stuck

The minority feels pressured to agree. The majority loses patience. The minority voice is heard but nothing changes. One person always takes the minority role.

6How to move it forward

Ask the majority to be curious, not persuasive. Make concrete adjustments to the decision. Check commitment after the decision.

7Questions to ask the team

Core questions
  • Who has a different view?
  • Does anyone share part of that view?
  • What would it take for you to come along?
  • What wisdom does this view bring?
  • How can we add that to the decision?
Going further
  • What are we afraid will happen if we listen to the minority?
  • When did a minority view turn out to be right?
  • Who hasn’t spoken yet?
  • What’s the risk of deciding now?
  • What would make this decision stick?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S3.2Silent membersSome members rarely speak
What is happening Some members rarely speakCoach move Use structure and invitation; understand the silence
In the room
The same people silent each session. They may look engaged or withdrawn.
What’s underneath
Silence can mean thinking, disagreement, cultural norms, low safety, or disengagement. Don’t assume.
Avoid here
Putting people on the spot. Assuming silence means agreement.
Example
Multicultural team. Writing first and rounds increased contributions.
Full situation card: questions, examples, sample exchange
Filed under methods5282515
S3.6Subgroups and factionsThe team splits into camps
What is happening The team splits into campsCoach move Make the factions visible; explore their positions and needs
In the room
Members sit together by camp; alliances in voting; side glances.
What’s underneath
Factions form around location, function, history or values. They may be protecting legitimate interests.
Avoid here
Taking sides. Ignoring factions.
Example
Global team. Sculpting revealed a split between HQ and regions.
Full situation card: questions, examples, sample exchange
Filed under methods121728
S5.9Purpose conflicts with valuesMembers feel the team’s goals clash with their values
What is happening Members feel the team’s goals clash with their valuesCoach move Hear the minority voice; explore values and purpose
In the room
Moral language, discomfort, some members withdraw.
What’s underneath
Values conflicts are deep and can lead to disengagement or departure.
Avoid here
Dismissing concerns.
Example
Pharma team. Concern about marketing practices was escalated.
Full situation card: questions, examples, sample exchange
Filed under methods28617
S6.3Decisions don’t stickDecisions are reopened repeatedly
What is happening Decisions are reopened repeatedlyCoach move Clarify decision rights; test real agreement; hear dissent
In the room
The same decision appears on the agenda again; people refer to “what we discussed” rather than “what we decided”; side remarks about not really agreeing.
What’s underneath
Decisions don’t stick when it is unclear who had the authority to make them, or when disagreement was never voiced. Reopening is the minority’s delayed vote.
Avoid here
Forcing commitment.
Example
Leadership team. Gradients of agreement revealed that three members had only been at “can live with it”. Their concerns about timing were added and the decision held.
Full situation card: questions, examples, sample exchange
Filed under methods35362837
S9.2Agreeing too easilyCommitments are made quickly without real buy-in
What is happening Commitments are made quickly without real buy-inCoach move Test agreement; pre-mortem; hear dissent
In the room
Fast nods; no questions.
What’s underneath
Easy agreement may hide doubts.
Avoid here
Accepting at face value.
Example
Project team. Fist to five revealed doubts that improved the plan.
Full situation card: questions, examples, sample exchange
Filed under methods363428
S10.4Coach colluding with a subgroupThe coach aligns with one faction
What is happening The coach aligns with one factionCoach move Self-awareness; supervision; observation
In the room
The coach notices favouring some members.
What’s underneath
Coaches can unconsciously side with members they like.
Avoid here
Ignoring it.
Example
Coach. Noticed alignment with a subgroup and took it to supervision.
Full situation card: questions, examples, sample exchange
Filed under methods928
S8.11Generational or neurodiversity frictionDifferent ways of thinking, communicating and working cause misunderstanding
What is happening Different ways of thinking, communicating and working cause misunderstandingCoach move Make differences in style explicit and design working norms that let different minds contribute
In the room
Frustration about “how they communicate”. Some members find meetings overwhelming; others find written channels cold. Jokes about generations. Some people mask or withdraw.
What’s underneath
Differences in generation, neurotype and working style are often read as attitude problems (“disrespectful”, “slow”, “difficult”). Many standard team practices — fast open discussion, open-plan noise, unstructured brainstorming — favour some minds over others. Inclusion means designing for difference, not asking people to adapt to one norm. Disclosure of neurodivergence is personal and voluntary.
Avoid here
Stereotyping generations. Asking anyone to disclose a diagnosis. Treating one communication style as “professional” and others as wrong.
Example
Product team. User manuals revealed that two members needed agendas in advance and written follow-ups. The team adopted “agenda 24 hours ahead, decisions in writing” — and everyone benefited.
Full situation card: questions, examples, sample exchange
Filed under methods2642328

9Coach mistakes & watch-outs

  • Pressuring the minority.
  • Using voting to silence dissent.
  • Hearing the minority but not acting.
  • Making one person the permanent dissenter.

10Team traps

  • Using the minority role to block.
  • Silent compliance followed by sabotage.
  • Majority impatience.

Three worked problems

1

The quiet no. A team votes 7–1 for a new system. The coach asks who shares any part of the “no”. Three people raise concerns about training. The plan adds a training phase. Adoption is smooth.

2

The marginalised voice. In a male-dominated team, a female member’s ideas are often ignored. The coach slows down to hear her view fully. The team realises they have been dismissing her. They agree a practice of explicitly building on others’ ideas.

3

What would it take. A dissenter says he would agree if there were a six-month review. The team adds it. He becomes a strong supporter.

Where it comes from

Myrna Lewis’ Deep Democracy (Lewis Method), Arnold Mindell’s process work, and inclusion research.

My notes

29
Trust, Conflict and Voice family

Team Feedback Rounds

Core move: Give and receive feedback as a team, safely and specifically
4 options10 questions2 situations

1What it really is

Feedback within teams is often rare, indirect or only from the leader. Team feedback rounds create a structured space for peer feedback. Common formats include appreciation and request (“one thing I value, one thing I’d like more of”), keep–start–stop, and Marshall Goldsmith’s feedforward (suggestions for the future rather than criticism of the past). The coach ensures structure, safety and follow-up.

4How it works, deeply

Peer feedback builds accountability. Lencioni names avoidance of accountability as a core dysfunction: members don’t call each other on behaviour. When feedback is normal and structured, accountability grows without the leader being the enforcer. Appreciation is equally important: teams often underestimate how much members value recognition from peers. Feedforward reduces defensiveness by focusing on the future.

Quick card

Reach for it when
Members rarely give each other feedback; feedback only flows from the leader; tension builds silently; after a project
The move
Run a structured round where each member gives and receives specific appreciation and requests
Watch
Public feedback can embarrass. Build safety and use a clear structure; never let feedback become a group attack on one person.
Four questions that often open it
  1. What do you value about how each colleague contributes?
  2. What would you like more or less of?
  3. What’s one thing that would help you work better with each person?
  4. How did it feel to receive this?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Feedback vacuum — members don’t know how they are seen.
  • Leader-only feedback — the team depends on the leader for all feedback.
  • Hidden irritations — small frustrations accumulate.
  • After a project — a natural moment for reflection.
  • New norms — the team wants a feedback culture.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Appreciation and request round — one each per colleague.
2Feedforward — each member asks for suggestions about one thing they want to improve.
3Hot seat — one member at a time receives feedback from all (with consent).
4Written then spoken — notes first, conversation second.

5Where it gets stuck

Feedback is vague. Members only give positive feedback. Someone receives harsh feedback and shuts down. The exercise happens once and is never repeated.

6How to move it forward

Prepare members with examples of specific feedback. Ensure appreciation is real. Ask receivers to say “thank you” and ask clarifying questions only. Make it a regular practice.

7Questions to ask the team

Core questions
  • What do you appreciate about this colleague?
  • What’s one thing you’d like more of from them?
  • What did you hear that surprised you?
  • What will you try?
  • How can we make this a habit?
Going further
  • What feedback have you been holding back?
  • How do you prefer to receive feedback?
  • What do we need to make this safe?
  • What did we learn about the team as a whole?
  • What’s one request for the team?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S6.6Free ridersSome members contribute less
What is happening Some members contribute lessCoach move Peer feedback; peer accountability; role negotiation
In the room
Sighs when some names come up, uneven workload, sarcasm about “some people’s priorities”. Hard-working members look tired and resentful.
What’s underneath
Free riding affects fairness and motivation. It may reflect unclear roles, disengagement, overload elsewhere, or a lack of peer accountability norms. Assuming laziness is usually wrong.
Avoid here
Public shaming.
Example
Project team. Role negotiation clarified expectations; one “free rider” turned out to be supporting another department two days a week.
Full situation card: questions, examples, sample exchange
Filed under methods29413930
S6.11A star performer or hero cultureOne person carries critical work; others defer, or resent; the system depends on a hero
What is happening One person carries critical work; others defer, or resent; the system depends on a heroCoach move Make the pattern systemic rather than personal; spread capability and recognition
In the room
The star answers first and is thanked most. Others wait for them, or roll their eyes. The star works late and looks tired. The leader praises the star in public.
What’s underneath
Hero culture is co-created: the organisation rewards heroics, the hero gains identity and status, and others gain relief from responsibility. It creates fragility (key-person risk), burnout and unequal growth. The hero may also be carrying the team’s shadow — the competence or decisiveness others don’t own.
Avoid here
Attacking or diminishing the star. Ignoring the burnout risk. Treating it as only the star’s behaviour.
Example
Sales team. The top performer closed half the deals. The team redesigned key accounts into pairs; overall sales rose and the star worked fewer weekends.
Full situation card: questions, examples, sample exchange
Filed under methods14413929

9Coach mistakes & watch-outs

  • Allowing vague or harsh feedback.
  • Letting receivers argue.
  • Doing it without consent.
  • One-off exercise.

10Team traps

  • Only positive feedback.
  • Feedback as revenge.
  • Agreeing to everything and changing nothing.

Three worked problems

1

Appreciation round. A team gives each other one appreciation each. Several members are moved; they had no idea their work was noticed. Energy rises for the following session.

2

Feedforward. The leader asks for suggestions on how to run meetings. He receives twelve ideas, picks three, and reports back next session. Members start asking for feedforward too.

3

Hot seat with consent. A member asks for feedback on her influence. The team gives specific examples. She says, “I didn’t know I interrupt.” She asks the team to signal when she does.

Where it comes from

Feedback practice in team development; Marshall Goldsmith’s feedforward; Lencioni’s accountability dysfunction.

My notes

30
Trust, Conflict and Voice family

Feedforward and Start / Stop / Continue

Core move: Help members ask for future-focused suggestions instead of judgments about the past
4 options10 questions3 situations

1What it really is

Marshall Goldsmith’s feedforward replaces feedback about the past with suggestions for the future. A person names one behaviour they want to improve, asks a colleague for two suggestions, listens without judging or explaining, says “thank you”, and repeats with other colleagues. Because nobody discusses the past, defensiveness drops sharply. Start / Stop / Continue (also Keep–Start–Stop) is a close relative for the team as a whole: what should we start doing, stop doing and continue doing? Together they make improvement a light, regular habit rather than an annual event.

4How it works, deeply

Feedback about the past invites people to defend their identity (“that’s not who I am”). Feedforward focuses on what someone can do next, which feels like help rather than judgment. The “thank you only” rule trains listening and removes the debate. Because the person chooses the behaviour, motivation is high. At team level, Start / Stop / Continue gives balanced attention to what is working, which teams under pressure often forget. Repeated regularly, both practices build a culture where improvement is normal rather than a sign of failure.

Quick card

Reach for it when
Feedback feels risky or defensive; the team wants a quick, safe way to improve; after a project; as a regular habit in meetings
The move
Members ask for suggestions about the future on one specific behaviour, listen, and say only “thank you”
Watch
Feedforward is safer than feedback but can stay superficial. Keep it specific and follow up on what changes.
Four questions that often open it
  1. What one behaviour do you want to improve?
  2. What two suggestions could help me with that next time?
  3. What should we start, stop and continue as a team?
  4. What will you try from the suggestions you heard?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Feedback-shy team — classic feedback rounds feel too risky.
  • Defensive reactions — members explain and justify when they receive feedback.
  • Development goals — individuals want to work on a behaviour that affects the team.
  • End of project — a quick, forward-looking review.
  • Leader development — the leader wants input without putting the team on the spot.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Feedforward carousel — pairs rotate every three minutes; each person asks for and gives suggestions on one behaviour.
2Leader feedforward — the leader asks the team for suggestions on one behaviour and reports back later.
3Team Start / Stop / Continue — sticky notes in three columns, clustered and voted.
4Individual Start / Stop / Continue — each member receives one start, one stop and one continue from each colleague, in writing.

5Where it gets stuck

Suggestions are generic (“communicate more”). Members only choose safe behaviours. The leader uses Start / Stop / Continue to criticise the team. Nobody follows up.

6How to move it forward

Ask for behaviour-specific suggestions (“What could I say or do next time…?”). Model choosing a real behaviour. Schedule a follow-up: people report what they tried and what happened.

7Questions to ask the team

Core questions
  • What one behaviour would make the biggest difference to how you work with this team?
  • What suggestions do you have for my next meeting?
  • What should we start, stop and continue?
  • What will you try?
  • When will you report back?
Going further
  • Which suggestion surprised you?
  • What’s one thing we should keep doing that we take for granted?
  • What could we stop without losing anything?
  • Who could support you in trying this?
  • How will we make this a habit?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S6.6Free ridersSome members contribute less
What is happening Some members contribute lessCoach move Peer feedback; peer accountability; role negotiation
In the room
Sighs when some names come up, uneven workload, sarcasm about “some people’s priorities”. Hard-working members look tired and resentful.
What’s underneath
Free riding affects fairness and motivation. It may reflect unclear roles, disengagement, overload elsewhere, or a lack of peer accountability norms. Assuming laziness is usually wrong.
Avoid here
Public shaming.
Example
Project team. Role negotiation clarified expectations; one “free rider” turned out to be supporting another department two days a week.
Full situation card: questions, examples, sample exchange
Filed under methods29413930
S4.11The team that is “too nice”Warm relationships, low challenge — and quietly declining performance
What is happening Warm relationships, low challenge — and quietly declining performanceCoach move Name the cost of harmony; make challenge a form of care
In the room
Lots of appreciation, few questions. Problems are softened into “small things”. Underperformance is worked around rather than discussed. People leave meetings smiling and nothing changes.
What’s underneath
Excessive harmony is a comfort zone (high safety, low standards). It protects relationships at the cost of results — and, over time, of the relationships themselves, because unspoken frustration builds. The team often has a shared value (“we’re caring”) that has become a shadow: directness is not allowed.
Avoid here
Shaming the team for being kind. Jumping straight to hard-hitting feedback. Treating it only as conflict avoidance — the performance cost must be visible.
Example
Charity leadership team. Scored very high on safety, low on accountability. The coach showed the learning-zone model; members placed themselves in the comfort zone. They agreed “kind and clear” norms.
Full situation card: questions, examples, sample exchange
Filed under methods27143025
S5.10A good team that wants to become greatNo crisis, solid results — the team wants to raise its game
What is happening No crisis, solid results — the team wants to raise its gameCoach move Start from strengths, find the next level of value for stakeholders, and stretch with small, ambitious experiments
In the room
Relaxed, confident, curious. Members are proud of results and a little bored. They ask, “What’s next for us?”
What’s underneath
High-performing teams risk the comfort zone and the plateau. The challenge is not repair but stretch: more value for stakeholders, more learning, more distributed leadership. Problem-focused methods can feel wrong here; appreciative and future-focused methods fit better.
Avoid here
Inventing problems so the coaching has something to fix. Generic team-building. Complacent celebration with no stretch.
Example
Finance leadership team. Strong internally, weak at “connecting”. Stakeholder interviews revealed an appetite for strategic advice. The team redefined its purpose and doubled its strategic work.
Full situation card: questions, examples, sample exchange
Filed under methods863046

9Coach mistakes & watch-outs

  • Allowing feedback about the past to sneak in.
  • Letting receivers argue.
  • Generic suggestions.
  • No follow-up.

10Team traps

  • Choosing a behaviour that doesn’t matter.
  • Politeness without content.
  • Using “stop” to attack individuals.

Three worked problems

1

The carousel. In 20 minutes, each member collects ten suggestions on one behaviour. A senior engineer chooses “explaining technical decisions to non-engineers” and tries two suggestions in the next sprint review. Product managers notice immediately.

2

The leader asks first. The leader asks for feedforward on “making decisions faster”. She hears ten suggestions, picks two and reports back a month later. Members start asking for feedforward themselves.

3

Team Start / Stop / Continue. After a launch, the team agrees to start a weekly risk review, stop late-night emails and continue Friday demos. Three months later, all three are still in place.

Where it comes from

Marshall Goldsmith’s feedforward; Start / Stop / Continue from Agile retrospectives and management practice. Complements peer feedback rounds and Lencioni’s emphasis on peer accountability.

Theory behind it · Knowledge Library7Nonviolent Communication (NVC)

My notes

31
Trust, Conflict and Voice family

Repair a Rupture in the Room

Core move: When trust breaks between members in session, slow down and repair before moving on
4 options10 questions8 situations

1What it really is

Ruptures happen: a sharp remark, an unintended insult, an emotional outburst, a member walking out. How the team and coach respond is critical. Rupture and repair research shows that relationships that survive repaired ruptures often become stronger. This method gives the coach steps to pause the content, acknowledge what happened, give space to each person’s experience, support accountability and apology where appropriate, and agree how to continue.

4How it works, deeply

In teams, ruptures affect everyone, not just the people directly involved. Observers learn whether the team can handle conflict. If the coach ignores a rupture, members conclude it is not safe to be honest. If the coach overreacts, the team may become afraid. A calm, structured repair shows the team that difficult moments can be survived and learned from. It also models a skill the team needs outside sessions.

Quick card

Reach for it when
A member is hurt or offended in session; an argument escalates; someone leaves the room; trust is visibly damaged
The move
Stop the content, name what happened, give each person space to be heard, and agree how to proceed
Watch
Moving on quickly after a rupture tells the team that the space is not safe. Repairing takes time — make time.
Four questions that often open it
  1. Can we pause? Something just happened.
  2. What was that like for you?
  3. What do you need right now?
  4. How do we want to move forward?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Sharp words — someone is personally criticised.
  • Emotional outburst — someone cries or shouts.
  • Walkout — a member leaves the room.
  • Leaked information — someone discovers a confidence was broken.
  • Hidden hurt — someone goes quiet after a comment.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Pause — stop the topic immediately.
2Hear both — give each person time to speak without interruption.
3Team impact — ask how others experienced it.
4Repair options — apology, clarification, or break before return.

5Where it gets stuck

The people involved refuse to talk. The team tries to move on quickly. The apology feels forced. The coach is flooded and loses presence.

6How to move it forward

Take a short break if needed. Speak to individuals privately if appropriate, then return to the team. Focus on impact and learning, not blame. Ask what the team wants to learn from what happened.

7Questions to ask the team

Core questions
  • What happened just now?
  • How did that land for you?
  • What did you intend?
  • What does each of you need?
  • What do we want to agree?
Going further
  • How did others experience this?
  • What does this remind us of?
  • What would help us return to the topic?
  • What can we learn about how we handle tension?
  • What do we need to do after the session?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S2.4Grief after a lossA colleague has died, left suddenly or been seriously ill
What is happening A colleague has died, left suddenly or been seriously illCoach move Pause the agenda; create space to acknowledge the loss
In the room
Silence, tearfulness, avoidance. Some members want to “get on with work”; others can’t.
What’s underneath
Teams grieve collectively. Unacknowledged grief shows up as irritability, withdrawal or loss of purpose. People grieve differently; the team needs room for differences.
Avoid here
Rushing to tasks. Forcing emotional sharing. Acting as a therapist.
Example
Research team. A colleague died. The session became a remembrance; the team decided to name a project after her.
Full situation card: questions, examples, sample exchange
Filed under methods5113145
S2.11Tension you could cutSomething unnamed is creating tension in the room
What is happening Something unnamed is creating tension in the roomCoach move Name the tension neutrally; ask permission to explore
In the room
Short answers, avoidance of eye contact, stiff posture, long silences.
What’s underneath
Tension often signals an undiscussable or recent incident. Ignoring it makes the session feel false.
Avoid here
Ignoring it. Forcing it into the open.
Example
Leadership team. Coach named the tension; a member shared that a decision had been made without them.
Full situation card: questions, examples, sample exchange
Filed under methods13931
S4.1Open hostility between two membersTwo members clash openly; the team watches
What is happening Two members clash openly; the team watchesCoach move Slow down; separate positions from needs; negotiate specific agreements
In the room
Sharp tone, sarcasm, raised voices between two people. Others go quiet or take sides.
What’s underneath
Open conflict between two members affects the whole team. It may involve real differences in role, values or interests, plus personal history. The team often colludes by avoiding it.
Avoid here
Mediating a personal dispute in public without consent. Taking sides. Letting it escalate.
Example
Sales and delivery heads. Role negotiation produced three specific agreements; hostility fell.
Full situation card: questions, examples, sample exchange
Filed under methods313927
S4.4Disagreement turns personalA task disagreement becomes an attack on a person
What is happening A task disagreement becomes an attack on a personCoach move Pause; separate the idea from the person; restore norms
In the room
Tone sharpens, “you” statements, references to character.
What’s underneath
Task conflict turns into relationship conflict when people feel threatened or disrespected.
Avoid here
Ignoring personal attacks.
Example
Strategy team. Coach paused and reminded the team of its agreement; members rephrased.
Full situation card: questions, examples, sample exchange
Filed under methods27314
S4.5Trust breach / leakSomething said in confidence was shared outside
What is happening Something said in confidence was shared outsideCoach move Revisit agreements; repair; rebuild confidentiality
In the room
Shock, anger, suspicion. Members are careful and silent.
What’s underneath
A leak damages the safety of the whole team. Without repair, members will withdraw.
Avoid here
Witch hunts. Ignoring the breach.
Example
Leadership team. Revisited confidentiality agreements; the person responsible apologised.
Full situation card: questions, examples, sample exchange
Filed under methods43125
S4.6Old history resurfacesPast conflicts shape current interactions
What is happening Past conflicts shape current interactionsCoach move Map the history; acknowledge; decide what to carry forward
In the room
References to “last time”, “remember when”. Tension when certain topics come up.
What’s underneath
Unresolved history continues to influence the present. Teams need to acknowledge it before moving on.
Avoid here
Re-fighting the past. Dismissing it.
Example
Marketing team. Timeline revealed an old conflict; acknowledgement allowed a fresh start.
Full situation card: questions, examples, sample exchange
Filed under methods113122
S4.10Disclosure of bullying or harassment in sessionA member raises a serious allegation in the room
What is happening A member raises a serious allegation in the roomCoach move Pause; protect the individual; follow ethical and organisational procedures
In the room
Shock, silence, discomfort. The person may be upset.
What’s underneath
Allegations of bullying or harassment are not team coaching topics; they require formal processes. The coach’s duty is to the person’s safety and the organisation’s procedures.
Avoid here
Investigating in the room. Dismissing. Promising confidentiality you can’t keep.
Example
Hospital team. Coach paused the session, spoke to the member privately, and supported a referral to HR.
Full situation card: questions, examples, sample exchange
Filed under methods31132
S10.7Member discloses personal crisisA member shares a personal difficulty
What is happening A member shares a personal difficultyCoach move Support; refer; manage team impact
In the room
Emotion; silence.
What’s underneath
Personal crises affect the team; but team coaching is not therapy.
Avoid here
Therapy in the team.
Example
Member. Referred to the employee assistance programme.
Full situation card: questions, examples, sample exchange
Filed under methods314

9Coach mistakes & watch-outs

  • Ignoring the rupture.
  • Forcing an apology.
  • Taking sides.
  • Spending so long on the rupture that the team feels punished.

10Team traps

  • Moving on with a joke.
  • Demanding public apology.
  • Withdrawal.

Three worked problems

1

The sharp comment. A senior member says, “That’s a junior idea.” The junior member goes red. The coach pauses and asks the senior member what he meant. He explains he thought the idea needed more data. The junior member says how it felt. The senior member apologises for the wording. The team agrees a norm about critiquing ideas, not people.

2

The walkout. A member leaves the room after criticism. The coach takes a break and speaks to her privately. She returns and explains her frustration. The team listens.

3

Quiet hurt. The coach notices a member go silent after a joke. She checks in at the break. The member shares that the joke hurt. With consent, the coach raises it gently with the team.

Where it comes from

Rupture and repair research (Jeremy Safran and Christopher Muran in therapy; John Gottman on repair attempts in relationships); conflict resolution practice.

My notes

32
Trust, Conflict and Voice family

Coach the Leader in the Room

Core move: Work with the leader’s dual role — inside the team and above it
4 options10 questions13 situations

1What it really is

In most team coaching, the leader is both a member of the team and in authority over it. The leader’s behaviour casts a long shadow: team members watch for cues, defer to opinions and adjust what they say. This method includes contracting with the leader about their role (e.g. speak last, model vulnerability, accept challenge), observing the leader’s impact in sessions, and sometimes coaching the leader individually alongside team sessions (with clear agreements about confidentiality). The ICF competencies stress agreeing with the leader how ownership is shared between coach, leader and team.

4How it works, deeply

Hierarchy is real; pretending otherwise doesn’t help. The coach’s job is to make the leader’s influence visible and discussable. When leaders model learning — asking questions, admitting mistakes, accepting challenge — teams follow. Leaders often underestimate their impact; seeing it reflected can be a turning point. Coaching the leader alongside the team is powerful but requires careful contracting so the team doesn’t fear the coach is “the leader’s person”.

Quick card

Reach for it when
The team defers to the leader; the leader dominates or withdraws; the leader’s presence limits honesty; the leader is part of the problem
The move
Agree the leader’s role in sessions in advance, and intervene neutrally when power affects the dialogue
Watch
The coach must neither collude with the leader nor protect the team from the leader. The leader is part of the team-as-client.
Four questions that often open it
  1. What role will you play in our sessions?
  2. How does your presence affect the team?
  3. What do you need from the team that they aren’t giving?
  4. What do they need from you?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Dominant leader — the leader speaks most and decides everything.
  • Absent leader — the leader delegates the coaching and does not attend.
  • Defensive leader — the leader reacts badly to team feedback.
  • New leader — inherits a team and wants coaching to help.
  • Leader as member — the leader wants to be “one of the team” and avoids authority.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Pre-session contracting — agree the leader’s role in each session.
2Speak last — the leader shares views only after members.
3Leader feedback — the team gives feedback to the leader (with preparation).
4Parallel coaching — one-to-one coaching for the leader, with clear boundaries.

5Where it gets stuck

The leader agrees to speak last but doesn’t. The team still defers. The leader asks the coach for information about individuals. The leader uses coaching sessions to announce decisions.

6How to move it forward

Review the agreement with the leader after each session. Name the pattern neutrally in session (“I notice we pause and look to Anna before answering”). Hold the confidentiality boundary firmly.

7Questions to ask the team

Core questions
  • How would you like to show up in our sessions?
  • What do you notice about how the team responds to you?
  • What would help the team take more ownership?
  • What feedback would be most useful to you?
  • What will you do differently next session?
Going further
  • What are you afraid would happen if you stepped back?
  • What do you want the team to stop waiting for you to do?
  • How do you want to receive challenge?
  • What would your best leader say about this?
  • What does the team need from you that only you can give?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S1.2The leader’s agenda dressed as the team’sThe leader frames the topic; members nod but energy is elsewhere
What is happening The leader frames the topic; members nod but energy is elsewhereCoach move Test the agenda with the whole team before working on it
In the room
The leader introduces “our priorities”. Members look at the table. When asked directly, they agree quickly and briefly. Later, side remarks reveal different concerns.
What’s underneath
In hierarchical teams, the leader’s framing becomes the team’s by default. Members don’t contest it because the cost feels high. If the coach accepts the framing, the coaching becomes the leader’s instrument.
Avoid here
Accepting the agenda without testing it. Asking “do you agree?” in front of the leader (invites a yes). Exposing the leader publicly.
Example
Marketing team. The leader brings “accountability” as the topic. An anonymous card round shows most members want to discuss unclear priorities. The leader accepts. Accountability issues turn out to be a symptom of the priority problem.
Full situation card: questions, examples, sample exchange
Filed under methods7321
S4.10Disclosure of bullying or harassment in sessionA member raises a serious allegation in the room
What is happening A member raises a serious allegation in the roomCoach move Pause; protect the individual; follow ethical and organisational procedures
In the room
Shock, silence, discomfort. The person may be upset.
What’s underneath
Allegations of bullying or harassment are not team coaching topics; they require formal processes. The coach’s duty is to the person’s safety and the organisation’s procedures.
Avoid here
Investigating in the room. Dismissing. Promising confidentiality you can’t keep.
Example
Hospital team. Coach paused the session, spoke to the member privately, and supported a referral to HR.
Full situation card: questions, examples, sample exchange
Filed under methods31132
S6.4Everything escalates to the leaderThe team doesn’t decide without the leader
What is happening The team doesn’t decide without the leaderCoach move Clarify decision rights; coach the leader to step back
In the room
Members end discussions with “let’s ask Priya”; the leader’s calendar is overloaded; decisions wait for the leader’s return from travel.
What’s underneath
Escalation may reflect fear of getting it wrong, unclear authority, or a leader who unconsciously rewards dependence. Both the team and the leader are part of the pattern.
Avoid here
Blaming the leader or the team.
Example
Operations team. The leader agreed spending thresholds below which the team decided alone. Response time to customers halved.
Full situation card: questions, examples, sample exchange
Filed under methods353241
S7.1Leader dominatesThe leader talks most; the team defers
What is happening The leader talks most; the team defersCoach move Contract leader role; structure participation; observe
In the room
The leader speaks first and longest. Members nod, glance at the leader before answering, and rarely contradict.
What’s underneath
Leader dominance limits team thinking, even when the leader wants input. Members read status signals and edit themselves.
Avoid here
Undermining the leader publicly.
Example
CEO team. The CEO agreed to speak last; debate quality rose noticeably within two sessions.
Full situation card: questions, examples, sample exchange
Filed under methods3259
S7.2Leader absent or abdicatingThe leader delegates coaching and doesn’t engage
What is happening The leader delegates coaching and doesn’t engageCoach move Recontract; clarify leader’s role
In the room
The leader sends apologies; the team has no authority to decide; members ask “why are we doing this if she’s not here?”
What’s underneath
Leader absence signals low priority and blocks decisions. It may also mean the leader sees the team as the problem and coaching as something done to it.
Avoid here
Coaching around the leader.
Example
Leadership team. The coach recontracted with the leader and sponsor; the leader committed to attending half of each session.
Full situation card: questions, examples, sample exchange
Filed under methods13235
S7.3Leader wants the coach as allyThe leader tries to align the coach with their view
What is happening The leader tries to align the coach with their viewCoach move Hold the contract; coach the leader
In the room
Private calls from the leader, phrases like “between us”, “you see what I mean”. In sessions, the leader looks at the coach for agreement.
What’s underneath
Leaders may seek an ally against the team, especially if they feel isolated. Collusion feels like rapport while it is happening.
Avoid here
Collusion.
Example
CEO. The coach declined to deliver a message and helped the CEO rehearse saying it himself.
Full situation card: questions, examples, sample exchange
Filed under methods132
S7.4New leader inherits teamA new leader takes over an existing team
What is happening A new leader takes over an existing teamCoach move Timeline; personal histories; leader role contracting
In the room
Members compare the new leader with the old one, test boundaries, and hold back. The new leader tries to make a quick impact.
What’s underneath
Transitions create anxiety and loyalty conflicts. Members wonder what will change; the leader wonders whom to trust.
Avoid here
Comparing leaders.
Example
Finance team. A new-leader assimilation session let the team ask questions anonymously; the leader answered them openly.
Full situation card: questions, examples, sample exchange
Filed under methods11263245
S7.5Team defers to leaderMembers wait for the leader’s opinion
What is happening Members wait for the leader’s opinionCoach move Leader speaks last; interaction patterns; decision rights
In the room
Members glance at the leader before answering, use phrases like “whatever you think”, and wait for direction.
What’s underneath
Deference reflects hierarchy, cultural norms or a lack of safety. Sometimes it is learned: the leader has overruled people in the past.
Avoid here
Blaming the team.
Example
CEO team. A member was asked to make an “oppose” move as an experiment; the CEO thanked him and debate opened.
Full situation card: questions, examples, sample exchange
Filed under methods321036
S7.6Leader defensive under feedbackThe leader reacts badly to team feedback
What is happening The leader reacts badly to team feedbackCoach move Prepare the leader; model curiosity; safety
In the room
The leader explains, defends or corrects when feedback arrives; the team goes quiet and withdraws.
What’s underneath
Defensiveness under feedback quickly reduces team safety. Leaders often feel exposed in front of their own team.
Avoid here
Exposing the leader.
Example
Executive team. The leader prepared privately with the coach and responded with curiosity in the session.
Full situation card: questions, examples, sample exchange
Filed under methods32825
S7.7Leader asks coach about individualsThe leader asks for information about members
What is happening The leader asks for information about membersCoach move Hold confidentiality; redirect
In the room
A private request, often framed as concern: “Who is resisting?” or “What did X say about me?”
What’s underneath
Leaders may want information to manage people or protect themselves. Sharing it would break the team’s trust and the contract.
Avoid here
Sharing.
Example
Department head. The coach redirected to what the leader was observing; the leader raised it directly in the next session.
Full situation card: questions, examples, sample exchange
Filed under methods132
S7.8Leader is the issue no one namesThe team’s problem centres on the leader’s behaviour
What is happening The team’s problem centres on the leader’s behaviourCoach move Anonymous data; leader preparation; name the undiscussable
In the room
Indirect comments, careful silences, members exchanging looks when the leader speaks.
What’s underneath
Teams avoid naming leadership issues because of power. The undiscussable often drains energy from every other topic.
Avoid here
Exposing without preparation.
Example
CEO. Anonymous data feedback revealed a leadership issue; the coach prepared the CEO, who responded well.
Full situation card: questions, examples, sample exchange
Filed under methods13328
S7.10Leader wants to be “one of the team”The leader avoids authority
What is happening The leader avoids authorityCoach move Coach the leader’s role; clarify decisions
In the room
The leader avoids decisions, speaks of “all of us”, hesitates to use authority; members wait.
What’s underneath
Avoiding authority creates confusion and slows the team. Some leaders fear being seen as controlling.
Avoid here
Pushing authoritarianism.
Example
Startup. Leader clarified decision rights; the team welcomed it.
Full situation card: questions, examples, sample exchange
Filed under methods3235
S7.11The sponsor or a senior stakeholder is in the roomA powerful person attends; the team performs; real issues disappear
What is happening A powerful person attends; the team performs; real issues disappearCoach move Contract the visitor’s role in advance; make the power visible and the purpose clear
In the room
Polished answers, careful language, members watching the visitor. The leader is more formal than usual. The visitor asks questions that sound like assessment.
What’s underneath
When the sponsor or a senior stakeholder joins, the team’s attention shifts from learning to impression management. The “real client” of the commissioning relationship is present, and confidentiality feels at risk. The visitor may not realise their impact. Handled well, their presence can be a powerful “connecting” moment.
Avoid here
Letting the visitor turn the session into a review. Pretending the power isn’t there. Breaking confidentiality agreements by discussing previous sessions.
Example
Leadership team. The CEO joined for 40 minutes with a clear brief: share strategy, then listen. Members asked candid questions; the CEO later said it was the most useful hour of her month.
Full situation card: questions, examples, sample exchange
Filed under methods13297

9Coach mistakes & watch-outs

  • Colluding with the leader.
  • Avoiding the leader’s impact.
  • Sharing confidential team data with the leader.
  • Undermining the leader in front of the team.

10Team traps

  • Leader using the coach as a messenger.
  • Team blaming everything on the leader.
  • Leader being “one of us” and avoiding decisions.

Three worked problems

1

Speak last. The leader agrees to speak last. In the first session she breaks the agreement twice. The coach gently reminds her. By the third session, members start debating before she speaks, and decisions improve.

2

The leader’s shadow. The coach notices members look at the CEO before speaking. She describes this neutrally. The CEO is surprised. He asks the team what he does that creates this. They tell him: he frowns when he disagrees. He laughs and agrees to work on it.

3

Leader request. The leader asks the coach in private which members are resisting. The coach reminds him of the contract and offers to explore what he is seeing himself. The leader thanks her and later shares his concerns directly with the team.

Where it comes from

Leadership team coaching literature (Peter Hawkins; Ruth Wageman et al. “Senior Leadership Teams”); power and authority work in group relations; ICF Team Coaching Competency 3.

My notes

Family 5 of 6 · Methods 33–39 · When the team must choose a direction

Future and Decisions

Does the team share a picture of where it is going and how it decides?

A team that agrees on its problems can still be stuck because it does not share a destination, or because nobody knows how decisions are actually made. The Future and Decisions family builds a shared preferred future, stress-tests plans before reality does, clarifies decision rights and levels of agreement, chooses fewer priorities and makes the expectations between roles explicit.

These are the methods where team coaching sits closest to team facilitation. The difference is ownership: the coach provides the structure, the team provides every answer.

33
Future and Decisions family

Shared Preferred Future

Core move: Build one picture of “better” that every member can see themselves in
4 options10 questions6 situations

1What it really is

Solution-focused practice shows that describing a preferred future in detail creates energy and direction. In team coaching, this becomes a collective exercise: members imagine a future in which the team is thriving and describe it concretely. The miracle question (“If a miracle happened overnight and the problem were solved, what would you notice tomorrow?”) and future headlines (“What newspaper headline would describe our success?”) are popular tools. The key is to combine individual visions into a shared picture with concrete, observable details.

4How it works, deeply

A shared preferred future is motivating because it is co-created. It also reveals agreement that was invisible: members who argue about problems often agree about outcomes. Concrete detail makes the future real and testable. Back-casting connects aspiration to action. Teams that have a shared picture can coordinate without constant negotiation because members know what “good” looks like.

Quick card

Reach for it when
The team is stuck in problem talk; members want different things; there is no shared goal; after a crisis
The move
Ask the team to describe, concretely and together, what a good future looks like — then work back from it
Watch
A vision that only the leader is excited about will not move the team. Every member needs to see their part in it.
Four questions that often open it
  1. Imagine it’s a year from now and things have gone really well — what do we notice?
  2. What are we doing differently?
  3. What do our stakeholders say?
  4. What is the first sign we’re heading there?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Problem-saturated — the team only talks about what is wrong.
  • Divergent aspirations — members want different things.
  • Post-crisis — the team needs new direction.
  • New team — no shared vision yet.
  • Strategic transition — the organisation’s direction has changed.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Team miracle question — each member describes their miracle morning; the team finds common themes.
2Future headline — small groups write the headline and story of the team’s success.
3Future scale — 0–10, where are we today, and what does +1 look like?
4Back-casting — from the future, map the steps back to today.

5Where it gets stuck

The future is vague (“we’d be more aligned”). One member’s vision dominates. Members are cynical about envisioning. The future is described but no first steps follow.

6How to move it forward

Push for detail: “What would we see on Monday morning?” Ensure every member contributes before combining. Move to the scale and +1 quickly.

7Questions to ask the team

Core questions
  • What would tell us things have really improved?
  • What would we be doing? What would we stop doing?
  • What would stakeholders notice?
  • Where are we now on a scale of 0–10?
  • What would one step up look like?
Going further
  • What would surprise you in this future?
  • What part of this future is already happening?
  • What would you be proudest of?
  • What do we need to let go of?
  • Who would notice first?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S2.5Anxiety about changeUpcoming change creates worry and speculation
What is happening Upcoming change creates worry and speculationCoach move Separate known from unknown; build a shared preferred future; manage polarities
In the room
Rumours, “what if” questions, catastrophising. Some members very vocal, others withdrawn.
What’s underneath
Uncertainty is harder than bad news. Anxiety often fills the vacuum with worst-case stories. Teams need to separate what they know, what they don’t, and what they can influence.
Avoid here
False reassurance. Spending the session on rumours. Dismissing anxiety.
Example
Finance shared services. Sorted rumours into known, unknown and influence. Sent questions to the sponsor. Anxiety dropped.
Full situation card: questions, examples, sample exchange
Filed under methods331725
S2.10Disengaged / going through the motionsMembers show up physically but not mentally
What is happening Members show up physically but not mentallyCoach move Reconnect to purpose and to what each person cares about
In the room
Cameras off, multitasking, minimal participation, no questions.
What’s underneath
Disengagement often means the work has lost meaning, or members feel unheard. It may also signal burnout or plans to leave.
Avoid here
Lecturing about engagement. Assuming laziness.
Example
Admin team. Purpose exploration revealed members felt invisible to stakeholders. Stakeholder feedback restored meaning.
Full situation card: questions, examples, sample exchange
Filed under methods653345
S5.1No shared purposeMembers can’t say why the team exists
What is happening Members can’t say why the team existsCoach move Explore stakeholders and purpose; create a shared statement
In the room
Different answers to “what is this team for?” Confusion and some embarrassment.
What’s underneath
Without purpose, members default to individual goals and politics.
Avoid here
Writing the purpose for the team.
Example
IT leadership. Stakeholder interviews clarified purpose.
Full situation card: questions, examples, sample exchange
Filed under methods6332
S5.4Strategy unclearThe team doesn’t understand the organisation’s direction
What is happening The team doesn’t understand the organisation’s directionCoach move Clarify what is known; connect to stakeholders; build preferred future
In the room
Questions, confusion, speculation.
What’s underneath
Unclear strategy makes team prioritisation hard. The team may need to seek clarity or create its own direction.
Avoid here
Inventing strategy for the organisation.
Example
Regional team. Invited the strategy director to a session.
Full situation card: questions, examples, sample exchange
Filed under methods6163324
S5.6Disagree on what success meansMembers use different definitions of success
What is happening Members use different definitions of successCoach move Build a shared preferred future; use data
In the room
Arguments about outcomes; “we’re doing well” vs “we’re failing”.
What’s underneath
Without a shared definition of success, teams pull in different directions.
Avoid here
Choosing one definition.
Example
Software team. Defined success as reliable releases and customer satisfaction.
Full situation card: questions, examples, sample exchange
Filed under methods338623
S8.1Reorganisation or mergerStructural change disrupts roles, identity and relationships
What is happening Structural change disrupts roles, identity and relationshipsCoach move Honour the past; build a shared future; manage the tensions of change
In the room
Questions about new structures, anxious jokes, people counting who is “in” and “out”.
What’s underneath
Reorganisation triggers loss and uncertainty. Teams move through endings, a neutral zone and new beginnings (William Bridges). Coaching that skips the ending creates resistance.
Avoid here
Selling the change. Treating resistance as a problem to overcome.
Example
Bank integration. The team mapped what was ending, what continued and what was new; anxiety fell.
Full situation card: questions, examples, sample exchange
Filed under methods113317

9Coach mistakes & watch-outs

  • Accepting vague futures.
  • Letting the leader’s vision dominate.
  • Skipping the link to today.
  • Using it to avoid real problems.

10Team traps

  • Cynicism (“that’s fantasy”).
  • Agreeing to a vision without commitment.
  • Competing visions.

Three worked problems

1

The miracle morning. Members describe a morning after the miracle. Themes: fewer meetings, decisions in one go, customers praising speed. The team scales itself at 4 and agrees +1: decisions in one meeting with clear owners.

2

Headlines. Two groups write future headlines. One: “Smallest team delivers biggest growth.” The other: “The team everyone wants to join.” The combination leads to a purpose about growth and culture.

3

Already happening. The coach asks what part of the future is already happening. Members describe one project that works. They study it as a model.

Where it comes from

Solution-focused brief therapy (Steve de Shazer, Insoo Kim Berg), solution-focused team coaching (e.g. Mark McKergow), visioning practices in organisational development.

My notes

34
Future and Decisions family

Team Pre-Mortem

Core move: Imagine the plan failed, then work out why — before it does
4 options10 questions5 situations

1What it really is

Gary Klein’s pre-mortem uses prospective hindsight: imagining that an event has already happened increases the ability to identify reasons for it. The team imagines the project has failed spectacularly and each member writes down the reasons independently. Then the team shares and clusters the reasons and plans to prevent or mitigate the most likely and serious ones. In team coaching, the pre-mortem has a second benefit: it legitimises dissent, giving members permission to voice doubts they were holding back.

4How it works, deeply

Teams fall into planning fallacy: they underestimate risks and overestimate success. Pre-mortems counter this by making it easy to imagine failure. Because the failure is hypothetical and collective, members can speak more freely. The exercise also uncovers hidden assumptions and dependencies that might otherwise be missed.

Quick card

Reach for it when
Before a launch or big decision; when the team is overconfident; when dissent is suppressed; when risks are not discussed
The move
Ask members to imagine the project has failed and independently list reasons why, then plan to prevent the most likely ones
Watch
A pre-mortem with an anxious team can feed fear. Use it when the plan is stable and the team has enough confidence.
Four questions that often open it
  1. Imagine it’s a year from now and this has failed. What happened?
  2. What did we ignore?
  3. What’s the most likely cause?
  4. What can we do now to prevent it?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Overconfidence — the team is excited and nobody mentions risks.
  • Groupthink — strong pressure for agreement.
  • High-stakes launch — failure would be costly.
  • Suppressed doubts — members have concerns but don’t want to look negative.
  • Repeated failures — similar projects have failed before.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Individual writing first — prevents anchoring on the first reasons said.
2Cluster and rank — group reasons and vote on likelihood and impact.
3Prevention plan — assign actions to top risks.
4Pre-parade — the opposite: imagine spectacular success and identify what made it happen.

5Where it gets stuck

The team lists only external causes. The pre-mortem turns into pessimism and blocks action. Members don’t take it seriously. Risks are listed but not owned.

6How to move it forward

Ask for internal causes too: “What did we do that contributed?” Balance with a pre-parade. Assign owners and deadlines for mitigation.

7Questions to ask the team

Core questions
  • How did this fail?
  • What did we see and ignore?
  • What did we do that contributed?
  • Which causes are most likely?
  • What will we do now?
Going further
  • What would our critics have predicted?
  • What dependency did we underestimate?
  • What would make us abandon this plan?
  • What warning signs should we watch?
  • What would success have required?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S2.8Overconfidence / euphoriaAfter success, the team feels invincible and ignores risks
What is happening After success, the team feels invincible and ignores risksCoach move Celebrate, then test with pre-mortem and outside views
In the room
High energy, jokes, quick agreement on ambitious plans. Risks are waved away.
What’s underneath
Success can lead to overconfidence and groupthink. Teams under-examine their assumptions when they feel successful.
Avoid here
Killing the celebration. Lecturing about risk.
Example
Startup. After funding, a pre-mortem revealed hiring risks. The team planned hiring carefully.
Full situation card: questions, examples, sample exchange
Filed under methods34816
S3.4GroupthinkThe team agrees quickly; dissent is absent
What is happening The team agrees quickly; dissent is absentCoach move Legitimise dissent; use pre-mortems and red teams
In the room
Fast agreement, nodding, nobody challenges. Ideas aren’t tested.
What’s underneath
Groupthink (Irving Janis) happens with high cohesion and pressure for consensus. The team avoids conflict and misses risks.
Avoid here
Accepting quick agreement. Appointing the same devil’s advocate.
Example
Board. A pre-mortem revealed concerns about an acquisition.
Full situation card: questions, examples, sample exchange
Filed under methods34271024
S4.3Conflict avoided at all costsThe team avoids any disagreement
What is happening The team avoids any disagreementCoach move Build safety and structures for productive conflict
In the room
Quick agreement, topic changes when tension rises, “let’s take it offline”.
What’s underneath
Conflict avoidance protects relationships short term and damages decisions long term. Lencioni calls it fear of conflict.
Avoid here
Forcing conflict before safety. Calling the team weak.
Example
Charity board. Red team exercise surfaced concerns about a project.
Full situation card: questions, examples, sample exchange
Filed under methods272534
S8.6External crisisA sudden external event threatens the team
What is happening A sudden external event threatens the teamCoach move Contract the session around the crisis; plan; support
In the room
High stress, urgency, focus on immediate response.
What’s underneath
Crises demand rapid response but also reveal team strengths and weaknesses.
Avoid here
Forcing reflection during the acute phase.
Example
Pandemic response. Short weekly check-ins and pre-mortems helped the team act fast.
Full situation card: questions, examples, sample exchange
Filed under methods7345
S9.2Agreeing too easilyCommitments are made quickly without real buy-in
What is happening Commitments are made quickly without real buy-inCoach move Test agreement; pre-mortem; hear dissent
In the room
Fast nods; no questions.
What’s underneath
Easy agreement may hide doubts.
Avoid here
Accepting at face value.
Example
Project team. Fist to five revealed doubts that improved the plan.
Full situation card: questions, examples, sample exchange
Filed under methods363428

9Coach mistakes & watch-outs

  • Running it with an anxious or fragile team.
  • Skipping individual writing.
  • No action plan.
  • Using it to kill a project.

10Team traps

  • Listing only external blame.
  • Pessimism spiral.
  • Treating it as a ritual.

Three worked problems

1

The product launch. A team is excited about a launch. In the pre-mortem, three members write “sales didn’t understand the product”. The team adds a sales training plan.

2

Merger integration. A pre-mortem reveals that two members fear losing key staff. The team builds a retention plan.

3

Pre-parade balance. An anxious team starts with a pre-parade, then a pre-mortem. Confidence remains high while risks are addressed.

Where it comes from

Gary Klein’s pre-mortem (“Performing a Project Premortem”, Harvard Business Review, 2007); research on prospective hindsight (Mitchell, Russo and Pennington).

Theory behind it · Knowledge Library4Groupthink, social loafing and informal roles

My notes

35
Future and Decisions family

Clarify Decision Rights

Core move: Agree who decides what, and how
4 options10 questions9 situations

1What it really is

Many team problems are decision problems: unclear authority, slow decisions, decisions that don’t stick. Tools like RAPID (Recommend, Agree, Perform, Input, Decide) and RACI (Responsible, Accountable, Consulted, Informed) help teams clarify decision rights. Victor Vroom’s decision styles (from leader decides alone to team consensus) help teams choose the right decision process. This method helps the team create a decision map for its most important recurring decisions.

4How it works, deeply

Clear decision rights reduce friction. When members know who decides and how, they spend less energy guessing and politicking. Decisions stick because people know they were made legitimately. The process of clarifying also builds trust: members negotiate openly instead of fighting covertly. Leaders often discover they are holding decisions the team could make.

Quick card

Reach for it when
Decisions are relitigated; everything escalates to the leader; members don’t know whether to decide or consult; conflicts about authority
The move
List the team’s recurring decisions and agree for each who decides, who is consulted and how
Watch
Clarifying decision rights can expose power struggles. Expect tension and treat it as useful data.
Four questions that often open it
  1. Which decisions keep coming back?
  2. Who should decide this?
  3. Who needs to be consulted?
  4. How will we decide — consensus, consultation, leader decision?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Relitigating — decisions are reopened repeatedly.
  • Escalation — everything goes to the leader.
  • Turf battles — members compete for authority.
  • Slow decisions — consensus on everything.
  • Unclear delegation — members don’t know how much freedom they have.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Decision inventory — list recurring decisions and current decision makers.
2RAPID or RACI map — assign roles for each decision.
3Decision style — choose consensus, consultative, delegated or leader decision per type.
4Decision log — record decisions and rationale.

5Where it gets stuck

The team creates a beautiful matrix but doesn’t use it. Power struggles erupt. The leader won’t let go of decisions. Members avoid being accountable.

6How to move it forward

Start with a few important decisions. Review the map after a month. Name power issues openly.

7Questions to ask the team

Core questions
  • What decisions do we make regularly?
  • Who decides now?
  • Who should decide?
  • Who needs input?
  • How will we communicate decisions?
Going further
  • Which decisions slow us down most?
  • What decisions could the leader delegate?
  • What happens when we disagree with a decision?
  • How will we know the decision process is working?
  • What decisions do we avoid making?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S6.1Role confusionMembers are unsure who does what
What is happening Members are unsure who does whatCoach move Negotiate roles; clarify decision rights
In the room
Duplicate emails to the same client, tasks that nobody picks up, and repeated “I thought you had it.” Members are friendly but quietly frustrated.
What’s underneath
Role confusion causes friction, waste and conflict that is often misread as personality clash. It usually appears after growth, restructuring or a change of leader, when old informal agreements no longer fit.
Avoid here
Writing job descriptions for the team.
Example
New product team. Role negotiation revealed nobody owned customer onboarding; one member took it on and complaints dropped within a month.
Full situation card: questions, examples, sample exchange
Filed under methods3935
S6.2Turf warsMembers compete for territory and authority
What is happening Members compete for territory and authorityCoach move Negotiate roles; zoom to the ecosystem; clarify decisions
In the room
Possessive language (“my clients”, “my project”), copying the boss on emails, defensive body language when another member’s name is mentioned.
What’s underneath
Turf wars usually reflect unclear roles, scarce resources or incentives that reward individual territory. They can also protect status and identity during uncertainty.
Avoid here
Taking sides.
Example
Marketing and sales leads. Both claimed ownership of the key-account campaigns. Role negotiation produced a shared-ownership agreement with clear decision rights.
Full situation card: questions, examples, sample exchange
Filed under methods391635
S6.3Decisions don’t stickDecisions are reopened repeatedly
What is happening Decisions are reopened repeatedlyCoach move Clarify decision rights; test real agreement; hear dissent
In the room
The same decision appears on the agenda again; people refer to “what we discussed” rather than “what we decided”; side remarks about not really agreeing.
What’s underneath
Decisions don’t stick when it is unclear who had the authority to make them, or when disagreement was never voiced. Reopening is the minority’s delayed vote.
Avoid here
Forcing commitment.
Example
Leadership team. Gradients of agreement revealed that three members had only been at “can live with it”. Their concerns about timing were added and the decision held.
Full situation card: questions, examples, sample exchange
Filed under methods35362837
S6.4Everything escalates to the leaderThe team doesn’t decide without the leader
What is happening The team doesn’t decide without the leaderCoach move Clarify decision rights; coach the leader to step back
In the room
Members end discussions with “let’s ask Priya”; the leader’s calendar is overloaded; decisions wait for the leader’s return from travel.
What’s underneath
Escalation may reflect fear of getting it wrong, unclear authority, or a leader who unconsciously rewards dependence. Both the team and the leader are part of the pattern.
Avoid here
Blaming the leader or the team.
Example
Operations team. The leader agreed spending thresholds below which the team decided alone. Response time to customers halved.
Full situation card: questions, examples, sample exchange
Filed under methods353241
S6.5Consensus paralysisThe team insists on consensus for everything
What is happening The team insists on consensus for everythingCoach move Choose decision styles; use gradients of agreement
In the room
Long discussions, polite rounds, no closure. Members leave meetings tired and unsure what was decided.
What’s underneath
Consensus for everything slows teams down and often hides an unwillingness to accept a leader’s or colleague’s authority. It can also be a value (fairness) applied too widely.
Avoid here
Imposing decisions.
Example
NGO leadership team. Chose consensus only for strategy and values; consultation for operational decisions. Meeting time fell by a third.
Full situation card: questions, examples, sample exchange
Filed under methods363537
S7.2Leader absent or abdicatingThe leader delegates coaching and doesn’t engage
What is happening The leader delegates coaching and doesn’t engageCoach move Recontract; clarify leader’s role
In the room
The leader sends apologies; the team has no authority to decide; members ask “why are we doing this if she’s not here?”
What’s underneath
Leader absence signals low priority and blocks decisions. It may also mean the leader sees the team as the problem and coaching as something done to it.
Avoid here
Coaching around the leader.
Example
Leadership team. The coach recontracted with the leader and sponsor; the leader committed to attending half of each session.
Full situation card: questions, examples, sample exchange
Filed under methods13235
S7.10Leader wants to be “one of the team”The leader avoids authority
What is happening The leader avoids authorityCoach move Coach the leader’s role; clarify decisions
In the room
The leader avoids decisions, speaks of “all of us”, hesitates to use authority; members wait.
What’s underneath
Avoiding authority creates confusion and slows the team. Some leaders fear being seen as controlling.
Avoid here
Pushing authoritarianism.
Example
Startup. Leader clarified decision rights; the team welcomed it.
Full situation card: questions, examples, sample exchange
Filed under methods3235
S9.6Waiting for permissionThe team waits for approval to act
What is happening The team waits for approval to actCoach move Drama to empowerment; decision rights; test assumptions
In the room
“We’d need approval”.
What’s underneath
Waiting may reflect real constraints or learned helplessness.
Avoid here
Encouraging rule-breaking.
Example
Public sector team. Discovered it had more authority than assumed.
Full situation card: questions, examples, sample exchange
Filed under methods19351815
S9.9Can’t agree the next stepThe team agrees on the issue but not the action
What is happening The team agrees on the issue but not the actionCoach move Gradients of agreement; decision rights; experiments
In the room
Competing proposals; frustration.
What’s underneath
Disagreement about action may hide different risk tolerances.
Avoid here
Endless discussion.
Example
Product team. Tested two options in parallel for two weeks.
Full situation card: questions, examples, sample exchange
Filed under methods36354037

9Coach mistakes & watch-outs

  • Building an overly complex matrix.
  • Ignoring power dynamics.
  • Not reviewing the map.
  • Imposing a model without adapting it.

10Team traps

  • Agreeing on paper, behaving as before.
  • Using the map to avoid accountability.
  • Turf protection.

Three worked problems

1

The escalating team. Every budget decision goes to the leader. Mapping decisions shows that most could be delegated. The leader delegates decisions under a threshold. Response times halve.

2

Relitigated decisions. A team keeps reopening hiring decisions. They agree a consultative process: the hiring manager decides after input. Decisions stick.

3

Consensus paralysis. A team uses consensus for everything. They choose consensus for strategy, consultation for operations. Meetings shorten.

Where it comes from

Bain & Company’s RAPID model, RACI matrices, Victor Vroom and Philip Yetton’s decision styles.

My notes

36
Future and Decisions family

Gradients of Agreement

Core move: Replace the yes/no vote with a scale that shows real levels of support
4 options10 questions6 situations

1What it really is

Sam Kaner’s gradients of agreement and the “fist to five” technique replace binary votes with a scale: from enthusiastic support to strong disagreement or veto. This shows the real level of support for a proposal, reveals hidden reservations, and helps the team move from consensus-by-silence to genuine commitment. It also supports “disagree and commit”: members can express disagreement but commit to support the decision.

4How it works, deeply

Binary decisions hide nuance. A “yes” can mean “I love it” or “I can live with it”. Seeing the distribution helps the team decide whether there is enough support to proceed. Exploring reservations improves the proposal. The norm of disagree-and-commit builds trust because members know their disagreement will be heard but not used to sabotage.

Quick card

Reach for it when
The team needs to decide but agreement is unclear; members say yes but don’t commit; decisions are blocked by one “no”
The move
Ask each member to show their level of agreement on a scale, then explore the reservations
Watch
A scale reveals disagreement. The team must be ready to work with what it shows.
Four questions that often open it
  1. On a scale from full support to block, where are you?
  2. What would move you one step closer to support?
  3. Can you live with this?
  4. What do we need to commit?

2The team’s context

A team needing this method usually shows up in one of these states:

  • False consensus — everyone says yes, nobody follows through.
  • Blocked decisions — one strong objection stops everything.
  • Unclear support — the leader isn’t sure if the team really agrees.
  • Remote decisions — hard to read the room on video calls.
  • Repeated reopening — decisions come back because of hidden reservations.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Fist to five — show fingers from 0 (block) to 5 (full support).
2Gradients scale — eight levels from “whole-hearted endorsement” to “block”.
3Reservation round — those below a threshold explain what would move them.
4Disagree and commit — agree to commit even if not fully supportive.

5Where it gets stuck

Members feel pressured to show high support. The team spends too long on reservations. The leader overrides the scale.

6How to move it forward

Use anonymous tools if needed. Set a threshold in advance (e.g. no one below 2). Agree when to proceed.

7Questions to ask the team

Core questions
  • Where are you on the scale?
  • What would help you move up?
  • Can you commit to this even if you disagree?
  • What reservations should we address?
  • What would make this decision stick?
Going further
  • What does a 3 mean for you?
  • What would make you block?
  • What do we need to watch for after the decision?
  • Who needs to hear our decision?
  • How will we review?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S3.3The meeting after the meetingReal conversations happen outside sessions
What is happening Real conversations happen outside sessionsCoach move Bring the corridor conversation into the room
In the room
Agreement in sessions, complaints afterwards. Decisions are undermined.
What’s underneath
The team lacks safety or norms for disagreement in the room. Outside conversations carry the real content.
Avoid here
Accusing people of gossip. Ignoring the pattern.
Example
Executive team. Anonymous cards captured corridor talk. Real issues surfaced.
Full situation card: questions, examples, sample exchange
Filed under methods13436
S6.3Decisions don’t stickDecisions are reopened repeatedly
What is happening Decisions are reopened repeatedlyCoach move Clarify decision rights; test real agreement; hear dissent
In the room
The same decision appears on the agenda again; people refer to “what we discussed” rather than “what we decided”; side remarks about not really agreeing.
What’s underneath
Decisions don’t stick when it is unclear who had the authority to make them, or when disagreement was never voiced. Reopening is the minority’s delayed vote.
Avoid here
Forcing commitment.
Example
Leadership team. Gradients of agreement revealed that three members had only been at “can live with it”. Their concerns about timing were added and the decision held.
Full situation card: questions, examples, sample exchange
Filed under methods35362837
S6.5Consensus paralysisThe team insists on consensus for everything
What is happening The team insists on consensus for everythingCoach move Choose decision styles; use gradients of agreement
In the room
Long discussions, polite rounds, no closure. Members leave meetings tired and unsure what was decided.
What’s underneath
Consensus for everything slows teams down and often hides an unwillingness to accept a leader’s or colleague’s authority. It can also be a value (fairness) applied too widely.
Avoid here
Imposing decisions.
Example
NGO leadership team. Chose consensus only for strategy and values; consultation for operational decisions. Meeting time fell by a third.
Full situation card: questions, examples, sample exchange
Filed under methods363537
S7.5Team defers to leaderMembers wait for the leader’s opinion
What is happening Members wait for the leader’s opinionCoach move Leader speaks last; interaction patterns; decision rights
In the room
Members glance at the leader before answering, use phrases like “whatever you think”, and wait for direction.
What’s underneath
Deference reflects hierarchy, cultural norms or a lack of safety. Sometimes it is learned: the leader has overruled people in the past.
Avoid here
Blaming the team.
Example
CEO team. A member was asked to make an “oppose” move as an experiment; the CEO thanked him and debate opened.
Full situation card: questions, examples, sample exchange
Filed under methods321036
S9.2Agreeing too easilyCommitments are made quickly without real buy-in
What is happening Commitments are made quickly without real buy-inCoach move Test agreement; pre-mortem; hear dissent
In the room
Fast nods; no questions.
What’s underneath
Easy agreement may hide doubts.
Avoid here
Accepting at face value.
Example
Project team. Fist to five revealed doubts that improved the plan.
Full situation card: questions, examples, sample exchange
Filed under methods363428
S9.9Can’t agree the next stepThe team agrees on the issue but not the action
What is happening The team agrees on the issue but not the actionCoach move Gradients of agreement; decision rights; experiments
In the room
Competing proposals; frustration.
What’s underneath
Disagreement about action may hide different risk tolerances.
Avoid here
Endless discussion.
Example
Product team. Tested two options in parallel for two weeks.
Full situation card: questions, examples, sample exchange
Filed under methods36354037

9Coach mistakes & watch-outs

  • Not exploring low scores.
  • Treating the scale as a vote.
  • Pressuring members.
  • Using it for trivial decisions.

10Team traps

  • Everyone shows 5 without meaning it.
  • Blocking without proposing alternatives.
  • Commitment without follow-through.

Three worked problems

1

The fake yes. A team agrees a new process. Fist to five shows two 1s. Their reservations reveal a resource issue. The plan changes. Both move to 4.

2

Disagree and commit. A member strongly disagrees but commits publicly. Six months later, she leads the implementation.

3

Remote scale. A remote team uses a poll. Results show a split. The team spends ten minutes on concerns and votes again.

Where it comes from

Sam Kaner’s “Facilitator’s Guide to Participatory Decision-Making” (gradients of agreement); fist-to-five practice in Agile teams; Intel and Amazon’s “disagree and commit”.

My notes

37
Future and Decisions family

Consent-Based Decision Making

Core move: Decide when full agreement isn’t possible: ask not “do you agree?” but “is it safe enough to try?”
4 options10 questions4 situations

1What it really is

Consent-based decision making comes from sociocracy (and was adapted in holacracy and other self-management practices). Instead of seeking everyone’s agreement, the team asks whether anyone has a reasoned objection: a reason the proposal would harm the team’s aims or move it backwards. Preferences (“I’d do it differently”) are noted but don’t block. Objections are used to improve the proposal. The decision is “good enough for now, safe enough to try”, with a review date. A typical round: present the proposal, clarifying questions, quick reactions, amend, then an objection round, integrating objections until there are none. Many teams combine this with a decision-rights tool, deciding who drafts the proposal and which decisions go to consent.

4How it works, deeply

Many teams confuse two questions: “Is this the best decision?” and “Is this decision acceptable to try?” Waiting for the best decision under uncertainty is often impossible. Consent lowers the bar to “safe enough”, which speeds decisions without silencing dissent, because reasoned objections must be addressed. Separating objections from preferences reduces ego battles. Review dates make decisions feel reversible, so people are more willing to try. It also distributes power: anyone can raise an objection, and the leader’s preference is treated like anyone else’s within agreed decision areas.

Quick card

Reach for it when
Consensus is slow; decisions stall on one person’s preference; the team needs to move under uncertainty; the same decisions keep being reopened
The move
Present a proposal, clarify, react, then ask for objections — reasons the proposal would cause harm or move the team backwards — and improve it until there are none
Watch
Consent is not majority voting and not a veto for preferences. An objection must be reasoned and about the team’s aims, not personal taste.
Four questions that often open it
  1. Is this good enough for now and safe enough to try?
  2. Do you have an objection — a reason this would harm our aims?
  3. What would change your objection into consent?
  4. When will we review this?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Consensus paralysis — long discussions, no decisions.
  • One person blocks — decisions stall on one strong preference.
  • High uncertainty — nobody can be sure of the best option.
  • Relitigated decisions — decisions keep coming back.
  • Self-managing teams — teams with more autonomy need a clear way to decide.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Full consent round — proposal, clarifying questions, reactions, amendments, objection round, integration.
2Quick consent — for small decisions: “Any objections? … Decided, review in a month.”
3Proposal owner — one person drafts the proposal, informed by input, before the round.
4Review date — every consent decision has a date when it will be reviewed.

5Where it gets stuck

Members raise preferences as objections. The team debates every objection at length. The leader overrides the process. Reviews never happen.

6How to move it forward

Teach the difference between objection and preference with examples. Ask objectors “What would make this safe enough?” Agree in advance which decisions use consent. Put review dates in the calendar.

7Questions to ask the team

Core questions
  • What exactly is the proposal?
  • What clarifying questions do you have?
  • What is your reaction, in one sentence?
  • Do you have an objection — and how would this harm our aims?
  • What change would resolve it?
Going further
  • Is this an objection or a preference?
  • What’s the worst that could happen if we try this for a month?
  • What would we need to see to change course?
  • Who will check how it’s going?
  • Which decisions should never use consent?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S6.3Decisions don’t stickDecisions are reopened repeatedly
What is happening Decisions are reopened repeatedlyCoach move Clarify decision rights; test real agreement; hear dissent
In the room
The same decision appears on the agenda again; people refer to “what we discussed” rather than “what we decided”; side remarks about not really agreeing.
What’s underneath
Decisions don’t stick when it is unclear who had the authority to make them, or when disagreement was never voiced. Reopening is the minority’s delayed vote.
Avoid here
Forcing commitment.
Example
Leadership team. Gradients of agreement revealed that three members had only been at “can live with it”. Their concerns about timing were added and the decision held.
Full situation card: questions, examples, sample exchange
Filed under methods35362837
S6.5Consensus paralysisThe team insists on consensus for everything
What is happening The team insists on consensus for everythingCoach move Choose decision styles; use gradients of agreement
In the room
Long discussions, polite rounds, no closure. Members leave meetings tired and unsure what was decided.
What’s underneath
Consensus for everything slows teams down and often hides an unwillingness to accept a leader’s or colleague’s authority. It can also be a value (fairness) applied too widely.
Avoid here
Imposing decisions.
Example
NGO leadership team. Chose consensus only for strategy and values; consultation for operational decisions. Meeting time fell by a third.
Full situation card: questions, examples, sample exchange
Filed under methods363537
S9.9Can’t agree the next stepThe team agrees on the issue but not the action
What is happening The team agrees on the issue but not the actionCoach move Gradients of agreement; decision rights; experiments
In the room
Competing proposals; frustration.
What’s underneath
Disagreement about action may hide different risk tolerances.
Avoid here
Endless discussion.
Example
Product team. Tested two options in parallel for two weeks.
Full situation card: questions, examples, sample exchange
Filed under methods36354037
S8.12AI or new tool adoption changes how the team worksNew AI or digital tools change roles, decisions and expertise
What is happening New AI or digital tools change roles, decisions and expertiseCoach move Treat adoption as a team change: explore hopes and fears, agree principles, and run small experiments with review
In the room
Excitement from some, anxiety from others. Unspoken worries about jobs and expertise. Inconsistent use: some members use AI for everything, others not at all. Confusion about who is accountable for AI-assisted work.
What’s underneath
New tools change more than tasks: they change status (whose expertise matters), decision rights (who checks what), trust and quality standards. If these are not discussed, teams split into enthusiasts and resisters, and risks go unmanaged. It is a classic polarity — speed and innovation versus quality and safety.
Avoid here
Taking sides between enthusiasts and sceptics. Ignoring job-security fears. Letting adoption happen individually without team agreements.
Example
Marketing team. Polarity mapping of speed vs quality led to principles: AI drafts, humans decide and check facts. Anxiety eased; output rose.
Full situation card: questions, examples, sample exchange
Filed under methods24374017

9Coach mistakes & watch-outs

  • Treating consent as voting.
  • Allowing preferences to block.
  • Using consent for every decision.
  • Skipping the review.

10Team traps

  • Weaponising objections.
  • Silent consent followed by sabotage.
  • Leader vetoes outside the process.

Three worked problems

1

The slow team. A team has discussed a new hybrid-work policy for three months. With a consent round, two objections are raised and resolved in 20 minutes. The policy is adopted with a three-month review.

2

Preference vs objection. A member objects to a new tool because she prefers the old one. The coach asks how it would harm the team’s aims. She can’t say, records it as a preference, and the team proceeds — with her agreement to help evaluate it.

3

Leader inside the process. The leader agrees that team process decisions go to consent. Her objections are handled like anyone else’s. Members report feeling more ownership.

Where it comes from

Sociocracy (Gerard Endenburg, building on Kees Boeke), Sociocracy 3.0, holacracy (Brian Robertson). Related to Kaner’s gradients of agreement and decision-rights tools (RACI, RAPID, DACI).

My notes

38
Future and Decisions family

Prioritize and Stop Doing

Core move: Help the team choose fewer things — and agree what it will stop
4 options10 questions9 situations

1What it really is

Many teams are overloaded not because they lack skill but because they say yes to everything. This method makes the team’s full portfolio visible (projects, meetings, reports, requests), then uses criteria (value, strategic fit, effort, urgency) to decide what to keep, stop, pause or delegate. A “stop doing” list is often more powerful than a to-do list. The team also agrees how to protect its priorities and how to say no.

4How it works, deeply

Prioritisation is a team act, not just an individual one. When individuals prioritise alone, they protect their own work and the team’s collective priorities suffer. A shared view of all work shows the true load and the trade-offs. Teams often discover that low-value work exists because nobody had permission to stop it. A collective decision gives that permission.

Quick card

Reach for it when
The team is overloaded; everything is a priority; the team keeps adding without removing; burnout is rising
The move
Make the full workload visible, then decide together what the team will stop, pause or hand over
Watch
Stopping work often means disappointing stakeholders. Help the team plan how to communicate it, or it will quietly restart.
Four questions that often open it
  1. What are we doing that we should stop?
  2. If we could only do three things, what would they be?
  3. What would happen if we stopped this?
  4. Who needs to know?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Overload — the team works long hours and still falls behind.
  • Everything is urgent — no real priorities.
  • Legacy work — the team continues work nobody needs.
  • Stakeholder pressure — the team accepts every request.
  • Burnout — members are exhausted.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Portfolio wall — list everything the team does on sticky notes.
2Value/effort grid — cluster by value and effort.
3Stop–pause–start — decide categories.
4Saying no script — practise declining requests.

5Where it gets stuck

Every item is defended. Stopping requires approval from above. The team agrees to stop but slips back. Members fear being seen as not committed.

6How to move it forward

Involve the sponsor where needed. Start with one or two clear stops. Communicate stops to stakeholders. Review after a month.

7Questions to ask the team

Core questions
  • What is everything we’re doing?
  • Which things create the most value?
  • What could we stop without harm?
  • What should we pause?
  • How will we protect our priorities?
Going further
  • What do we do because we’ve always done it?
  • Who would notice if we stopped?
  • What would we do with the time we free up?
  • What request should we decline this week?
  • What makes it hard to stop?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S1.5Too many topics at onceThe team arrives with a long list; everything feels urgent
What is happening The team arrives with a long list; everything feels urgentCoach move Harvest, prioritise, and test which topics need the whole team
In the room
Flip chart fills quickly. Members talk over each other to add items. The leader looks anxious about time.
What’s underneath
An overloaded agenda can be a sign of overload in the work, or a way to avoid depth. Covering everything means engaging with nothing.
Avoid here
Trying to cover everything. Choosing for the team. Letting the leader decide alone.
Example
Product leadership. Twelve topics. Dot voting gave two clear priorities; four topics belonged to subgroups. The session achieved a real decision for the first time in months.
Full situation card: questions, examples, sample exchange
Filed under methods738
S1.6Firefighting / crisis modeUrgent operational issues hijack every session
What is happening Urgent operational issues hijack every sessionCoach move Acknowledge the crisis; separate what needs solving now from what the crisis reveals about the team
In the room
Phones buzz. Members arrive late, leave early. Every topic becomes today’s fire. The tone is tense and fast.
What’s underneath
Some teams live in permanent crisis because the crisis protects them from strategic or relational work. Others are genuinely overwhelmed. The coach needs to tell the difference without dismissing the urgency.
Avoid here
Ignoring a real emergency. Turning the session into operational problem-solving. Lecturing about firefighting.
Example
IT operations. A major outage hit on session day. The coach rescheduled. The next session started with “what did the outage teach you about the team?”
Full situation card: questions, examples, sample exchange
Filed under methods7385
S2.3Exhausted / burnoutMembers are depleted; coaching feels like another demand
What is happening Members are depleted; coaching feels like another demandCoach move Make load visible; decide what to stop; protect energy
In the room
Yawns, slumped posture, cameras off. People arrive late from back-to-back meetings. Reactions are slow.
What’s underneath
Burnout is a team and system issue, not only individual. Coaching that adds demands will fail. Reducing load is the intervention.
Avoid here
Asking for more commitments. Resilience lectures. Ignoring systemic causes.
Example
Nursing team. Used the session to list all recurring tasks and stopped three.
Full situation card: questions, examples, sample exchange
Filed under methods38544
S5.2Competing prioritiesMembers pull in different directions
What is happening Members pull in different directionsCoach move Make priorities visible; decide together; manage polarities
In the room
Arguments about what matters most; members defend their areas.
What’s underneath
Competing priorities often reflect unclear strategy or misaligned incentives.
Avoid here
Deciding for the team.
Example
Product team. Portfolio wall led to stopping two projects.
Full situation card: questions, examples, sample exchange
Filed under methods38176
S5.7Short-termism / always urgentThe team focuses only on immediate issues
What is happening The team focuses only on immediate issuesCoach move Manage the short/long polarity; protect strategic time
In the room
Discussion of this week’s issues; no space for strategy.
What’s underneath
Short-termism may reflect pressure, incentives or anxiety.
Avoid here
Ignoring real urgency.
Example
Retail team. Agreed a monthly strategy session.
Full situation card: questions, examples, sample exchange
Filed under methods173844
S6.8Meeting overloadToo many meetings, too little value
What is happening Too many meetings, too little valueCoach move Audit and redesign rhythms; stop doing
In the room
Members arrive late from back-to-back calls, laptops open, “this could have been an email” muttered. Calendars full from 8 to 6.
What’s underneath
Meeting overload drains energy and reduces time for real work. Meetings often accumulate because nobody has authority or permission to stop them.
Avoid here
Adding more meetings.
Example
Leadership team. A meeting audit listed 22 hours a week of recurring meetings; they cut six hours per person.
Full situation card: questions, examples, sample exchange
Filed under methods4438
S8.8Resource cutsBudget or staff reduced; same expectations
What is happening Budget or staff reduced; same expectationsCoach move Prioritise; test assumptions; engage stakeholders
In the room
Frustration, overload, resentment.
What’s underneath
Cuts force trade-offs. Without explicit prioritisation, teams burn out.
Avoid here
Accepting impossible expectations.
Example
Public sector. A stop list was agreed with the sponsor.
Full situation card: questions, examples, sample exchange
Filed under methods381816
S8.9Change fatigueRepeated changes exhaust the team
What is happening Repeated changes exhaust the teamCoach move Test assumptions; appreciate stability; prioritise
In the room
Weariness, cynicism, low energy.
What’s underneath
Change fatigue reduces engagement and capacity.
Avoid here
Adding more change.
Example
Bank. Appreciative inquiry on how the team had coped with past change rebuilt confidence.
Full situation card: questions, examples, sample exchange
Filed under methods182038
S9.3Action list too longMany actions; little focus
What is happening Many actions; little focusCoach move Prioritise; small experiments
In the room
Long flipchart of actions.
What’s underneath
Long lists signal low commitment.
Avoid here
Approving everything.
Example
Leadership team. Reduced 15 actions to three experiments.
Full situation card: questions, examples, sample exchange
Filed under methods4038

9Coach mistakes & watch-outs

  • Generating a long list without decisions.
  • Ignoring stakeholder impact.
  • Making stops without authority.
  • Not reviewing.

10Team traps

  • “Everything is important.”
  • Quietly continuing stopped work.
  • Using overload as a badge of honour.

Three worked problems

1

The meeting audit. A team lists all its recurring meetings: 22 hours a week. They stop three, shorten two, and free six hours each.

2

The report nobody reads. The team asks stakeholders which reports they use. Two weekly reports are unread. They stop them.

3

Saying no. The team practises a script for declining low-priority requests. Members report feeling more confident and less resentful.

Where it comes from

Strategic prioritisation practice, Jim Collins’ “stop doing list”, Eisenhower matrix, Agile portfolio management.

Theory behind it · Knowledge Library8Liberating Structures8Force-field analysis

My notes

39
Future and Decisions family

Role Negotiation (Give and Get)

Core move: Make expectations between members explicit and negotiate them
4 options10 questions11 situations

1What it really is

Roger Harrison’s role negotiation technique treats team relationships as a set of negotiable agreements about behaviour. Each member writes, for each colleague, what they would like them to do more of, less of, or continue. Then pairs negotiate quid-pro-quo agreements (“I will send you data by Tuesday if you give me feedback by Thursday”). The method is practical, depersonalised and highly effective for role clarity and interface problems.

4How it works, deeply

Role negotiation works because it addresses behaviour, not personality. It also requires reciprocity, so nobody is only the giver or receiver. Writing first reduces emotional escalation. Specific agreements make accountability possible. Roles become clearer not through job descriptions but through real-time negotiation of expectations.

Quick card

Reach for it when
Roles overlap or conflict; members have unspoken expectations; handoffs fail; tension between specific members
The move
Each member writes what they need from others and what they offer; pairs negotiate specific agreements
Watch
Role negotiation is a negotiation, not a wish list. Agreements must be specific, two-way and reviewed.
Four questions that often open it
  1. What do you need more of, less of, or the same from each colleague?
  2. What can you offer in return?
  3. What specific agreement can we make?
  4. How will we check it’s working?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Overlaps — two members do the same work.
  • Gaps — work falls between roles.
  • Handoff failures — work stalls at interfaces.
  • Silent frustration — members resent each other without saying why.
  • New roles — after a restructure.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1More–less–same messages — written by each member to each colleague.
2Pair negotiations — pairs negotiate specific agreements.
3Give and get map — what each role gives to and needs from others.
4Agreement review — check after a few weeks.

5Where it gets stuck

Members write vague messages. Negotiations become arguments. Agreements are made but forgotten. Power differences prevent real negotiation.

6How to move it forward

Coach for specificity. Facilitate tough pairs. Record agreements and review them in the next session.

7Questions to ask the team

Core questions
  • What do you need from each colleague?
  • What would you like them to keep doing?
  • What can you offer?
  • What specific agreement can we write?
  • When will we review?
Going further
  • Where do handoffs break down?
  • What do you assume others know about your role?
  • What would make your job easier?
  • What do you do that others might not know about?
  • What agreement would make the biggest difference?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S4.1Open hostility between two membersTwo members clash openly; the team watches
What is happening Two members clash openly; the team watchesCoach move Slow down; separate positions from needs; negotiate specific agreements
In the room
Sharp tone, sarcasm, raised voices between two people. Others go quiet or take sides.
What’s underneath
Open conflict between two members affects the whole team. It may involve real differences in role, values or interests, plus personal history. The team often colludes by avoiding it.
Avoid here
Mediating a personal dispute in public without consent. Taking sides. Letting it escalate.
Example
Sales and delivery heads. Role negotiation produced three specific agreements; hostility fell.
Full situation card: questions, examples, sample exchange
Filed under methods313927
S4.9Silo war with another teamConflict between this team and another
What is happening Conflict between this team and anotherCoach move Zoom to the ecosystem; negotiate the interface
In the room
Strong language about the other team; history of disputes.
What’s underneath
Interteam conflicts often reflect structural issues, competing goals or poor interfaces. Each team sees itself as the victim.
Avoid here
Joining blame. Ignoring structural causes.
Example
Sales and operations. Joint role negotiation produced handoff agreements.
Full situation card: questions, examples, sample exchange
Filed under methods16391915
S6.1Role confusionMembers are unsure who does what
What is happening Members are unsure who does whatCoach move Negotiate roles; clarify decision rights
In the room
Duplicate emails to the same client, tasks that nobody picks up, and repeated “I thought you had it.” Members are friendly but quietly frustrated.
What’s underneath
Role confusion causes friction, waste and conflict that is often misread as personality clash. It usually appears after growth, restructuring or a change of leader, when old informal agreements no longer fit.
Avoid here
Writing job descriptions for the team.
Example
New product team. Role negotiation revealed nobody owned customer onboarding; one member took it on and complaints dropped within a month.
Full situation card: questions, examples, sample exchange
Filed under methods3935
S6.2Turf warsMembers compete for territory and authority
What is happening Members compete for territory and authorityCoach move Negotiate roles; zoom to the ecosystem; clarify decisions
In the room
Possessive language (“my clients”, “my project”), copying the boss on emails, defensive body language when another member’s name is mentioned.
What’s underneath
Turf wars usually reflect unclear roles, scarce resources or incentives that reward individual territory. They can also protect status and identity during uncertainty.
Avoid here
Taking sides.
Example
Marketing and sales leads. Both claimed ownership of the key-account campaigns. Role negotiation produced a shared-ownership agreement with clear decision rights.
Full situation card: questions, examples, sample exchange
Filed under methods391635
S6.6Free ridersSome members contribute less
What is happening Some members contribute lessCoach move Peer feedback; peer accountability; role negotiation
In the room
Sighs when some names come up, uneven workload, sarcasm about “some people’s priorities”. Hard-working members look tired and resentful.
What’s underneath
Free riding affects fairness and motivation. It may reflect unclear roles, disengagement, overload elsewhere, or a lack of peer accountability norms. Assuming laziness is usually wrong.
Avoid here
Public shaming.
Example
Project team. Role negotiation clarified expectations; one “free rider” turned out to be supporting another department two days a week.
Full situation card: questions, examples, sample exchange
Filed under methods29413930
S6.9Matrix / dual reporting tensionMembers serve two bosses; conflicting demands
What is happening Members serve two bosses; conflicting demandsCoach move Negotiate roles; manage polarities; map the system
In the room
Members hesitate before committing (“I need to check with my other boss”), conflicting deadlines, frustration about divided loyalties.
What’s underneath
Matrix structures create competing loyalties and conflicting priorities. Members can feel they belong nowhere and are judged by everyone.
Avoid here
Choosing for the member.
Example
Global product team. Role negotiation with both functional and project leads produced a shared priority list.
Full situation card: questions, examples, sample exchange
Filed under methods391716
S6.10Handoffs keep failingWork stalls at interfaces
What is happening Work stalls at interfacesCoach move Role negotiation; AAR; interaction patterns
In the room
Complaints that work arrives late, incomplete or without context; blame bouncing between functions.
What’s underneath
Handoffs fail when expectations about timing, quality and information are not explicit. Each side sees only its own pressures.
Avoid here
Blame.
Example
Sales–delivery handoff. Role negotiation produced a one-page handoff checklist; rework fell.
Full situation card: questions, examples, sample exchange
Filed under methods39431015
S8.5Key member leavingAn important member is leaving
What is happening An important member is leavingCoach move Acknowledge; redistribute roles; capture knowledge
In the room
Sadness, worry, role gaps.
What’s underneath
Losing a key member affects roles, relationships and identity.
Avoid here
Ignoring the loss.
Example
Product team. A farewell round and role negotiation covered the gap.
Full situation card: questions, examples, sample exchange
Filed under methods5391145
S8.10Team of teams / cross-team coordinationSeveral teams must deliver together; nobody owns the whole
What is happening Several teams must deliver together; nobody owns the wholeCoach move Coach the system of teams: shared purpose, explicit interfaces, liaison roles and regular cross-team learning
In the room
Representatives defend their own team’s priorities. Coordination meetings are long and report-heavy. Problems appear at the boundaries between teams. Each team blames the others; the programme lead is overwhelmed.
What’s underneath
In a team of teams, the critical work happens between teams. Each team is optimised for itself, and the system is optimised for nobody. Stanley McChrystal’s “team of teams” idea is that the network needs shared consciousness (everyone sees the whole picture) and empowered execution (teams decide locally within shared intent). Fluid membership and dual loyalties make it harder. The client may be the whole network, not one team.
Avoid here
Coaching each team separately and hoping the system improves. More status meetings. Ignoring the different incentives of each team.
Example
Programme team. An ecosystem map and interface agreements cut escalations.
Full situation card: questions, examples, sample exchange
Filed under methods16315392
S6.11A star performer or hero cultureOne person carries critical work; others defer, or resent; the system depends on a hero
What is happening One person carries critical work; others defer, or resent; the system depends on a heroCoach move Make the pattern systemic rather than personal; spread capability and recognition
In the room
The star answers first and is thanked most. Others wait for them, or roll their eyes. The star works late and looks tired. The leader praises the star in public.
What’s underneath
Hero culture is co-created: the organisation rewards heroics, the hero gains identity and status, and others gain relief from responsibility. It creates fragility (key-person risk), burnout and unequal growth. The hero may also be carrying the team’s shadow — the competence or decisiveness others don’t own.
Avoid here
Attacking or diminishing the star. Ignoring the burnout risk. Treating it as only the star’s behaviour.
Example
Sales team. The top performer closed half the deals. The team redesigned key accounts into pairs; overall sales rose and the star worked fewer weekends.
Full situation card: questions, examples, sample exchange
Filed under methods14413929
S6.12Knowledge loss and key-person dependencyCritical knowledge lives in a few heads; departures cause crises
What is happening Critical knowledge lives in a few heads; departures cause crisesCoach move Make knowledge flow a team responsibility: map dependencies, pair, document and hand over by design
In the room
Anxious jokes about “if she wins the lottery”. Work stalls during holidays. New members take months to become productive. Old decisions can’t be explained.
What’s underneath
Key-person dependency is a systemic risk, not an individual failing. It grows when the team is overloaded, when expertise is rewarded more than sharing, and when membership changes often. It links to fluid teaming and hero culture.
Avoid here
Asking experts to “document everything” on top of their work. Blaming those who leave. Treating it as an IT problem only.
Example
Engineering team. Built a dependency map; three critical systems had one expert. Pairing rotations and a monthly “teach-back” cut the risk in a quarter.
Full situation card: questions, examples, sample exchange
Filed under methods3423944

9Coach mistakes & watch-outs

  • Allowing vague requests.
  • Not facilitating difficult pairs.
  • Ignoring power differences.
  • No review.

10Team traps

  • Wish lists without offers.
  • Agreeing to everything.
  • Revenge messages.

Three worked problems

1

Sales and delivery. Sales and delivery leads clash. Role negotiation leads to an agreement: sales consults delivery before promising dates; delivery responds within 24 hours.

2

New roles. After a restructure, the team negotiates roles. Gaps appear: nobody owns customer onboarding. A member takes it on.

3

Leader negotiation. Members negotiate with the leader. She agrees to give earlier notice of changes; they agree to escalate issues earlier.

Where it comes from

Roger Harrison’s role negotiation (1972), organisational development practice, interface management.

My notes

Family 6 of 6 · Methods 40–48 · End of every session; second half of an engagement

Land, Learn and Sustain

Has enough opened that it must become something the team does?

The most common failure in team coaching is a series of rich sessions that leave the team’s Monday morning unchanged. The Land, Learn and Sustain family turns insight into owned experiments, builds peer accountability, makes learning from experience routine, moves new behaviours into the team’s real meetings, harvests what the team has learned about how it learns, closes the loop with stakeholders and, finally, hands the coaching role back to the team.

The test of good team coaching is not what happens in the sessions. It is whether the team keeps coaching itself after the coach has left.

40
Land, Learn and Sustain family

Team Experiments and Commitments

Core move: Turn insight into a small, owned experiment the whole team can see
4 options10 questions8 situations

1What it really is

Team coaching sessions often generate insight that disappears by Monday. Experiments convert insight into practice: small, specific, time-bound changes the team tries and reviews. Framing actions as experiments reduces fear of failure — an experiment that “fails” still produces learning. Commitments are owned by named people, visible to the whole team, and reviewed at the next session.

4How it works, deeply

Teams learn by doing. Small experiments create quick feedback and build momentum. Ownership matters: when an experiment has a name attached, it is far more likely to happen. Reviewing experiments at the next session closes the loop and builds a learning culture.

Quick card

Reach for it when
End of every session; when insight is high but action is vague; when previous action plans failed
The move
Agree one or two specific experiments, with owners, dates and a way to know if they worked
Watch
Long action lists signal low commitment. Small experiments signal seriousness.
Four questions that often open it
  1. What will we try before we meet again?
  2. Who will own it?
  3. How will we know it worked?
  4. What might get in the way?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Insight without action — great sessions, nothing changes.
  • Long lists — action plans with fifteen items.
  • Unowned actions — “we” will do it, nobody does.
  • Fear of failure — the team avoids trying new things.
  • Repeat commitments — the same actions are agreed every session.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1One experiment per insight — choose one small change.
2Owner and buddy — each experiment has an owner and a supporter.
3Success sign — define what evidence will show it worked.
4Obstacle check — what might get in the way and how to handle it.

5Where it gets stuck

Experiments are too big. Owners don’t follow through. The team forgets the experiments between sessions. Experiments are not reviewed.

6How to move it forward

Shrink the experiment. Use a visible tracker. Open the next session with experiment review.

7Questions to ask the team

Core questions
  • What will we try?
  • Who owns it?
  • By when?
  • How will we know it worked?
  • What might stop us?
Going further
  • What’s the smallest version of this?
  • What support does the owner need?
  • How will we remind ourselves?
  • What would make this easy?
  • What will we do if it fails?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S2.6Collective cynicismThe team believes nothing will improve
What is happening The team believes nothing will improveCoach move Find exceptions; test assumptions; start very small
In the room
Sarcasm, shrugging, “seen it all before”. Ideas are dismissed quickly.
What’s underneath
Cynicism protects against disappointment. It often contains valid criticism. Shifting it requires evidence, not persuasion.
Avoid here
Arguing against the cynicism. Positivity pushing. Ignoring legitimate grievances.
Example
Factory supervisors. Mapped immunity to change; assumption was “management will ignore us”. Tested it with one proposal — approved. Cynicism softened.
Full situation card: questions, examples, sample exchange
Filed under methods201840
S6.7Nobody owns actionsActions are agreed but no one follows through
What is happening Actions are agreed but no one follows throughCoach move Named owners; experiments; peer accountability
In the room
Action lists full of “we”, actions repeated from last session, nobody quite sure who was meant to do what.
What’s underneath
Collective ownership often becomes no ownership. Without a named person and a date, every member assumes someone else will act.
Avoid here
Coach owning follow-up.
Example
Leadership team. Introduced owner-and-buddy for every action; follow-through rose from about a third to most actions.
Full situation card: questions, examples, sample exchange
Filed under methods404142
S9.1Great session, nothing changesInsight in sessions; no change in daily work
What is happening Insight in sessions; no change in daily workCoach move Small experiments; redesign routines; review
In the room
Next session starts with “we didn’t get to it”.
What’s underneath
Insight without structure fades. Daily routines pull the team back.
Avoid here
Blame.
Example
Leadership team. Experiments tracked on a visible board; follow-through improved.
Full situation card: questions, examples, sample exchange
Filed under methods40444345
S9.3Action list too longMany actions; little focus
What is happening Many actions; little focusCoach move Prioritise; small experiments
In the room
Long flipchart of actions.
What’s underneath
Long lists signal low commitment.
Avoid here
Approving everything.
Example
Leadership team. Reduced 15 actions to three experiments.
Full situation card: questions, examples, sample exchange
Filed under methods4038
S9.5Experiment fails and team gives upA failed experiment leads to abandonment
What is happening A failed experiment leads to abandonmentCoach move AAR; reframe failure as learning; adapt
In the room
Disappointment; “told you so”.
What’s underneath
Teams often confuse failure of an experiment with failure of the goal.
Avoid here
Forcing the same experiment.
Example
Product team. Adjusted a daily stand-up to weekly after the daily version failed.
Full situation card: questions, examples, sample exchange
Filed under methods434020
S9.8Breakthrough momentA significant insight lands
What is happening A significant insight landsCoach move Harvest; land in experiments
In the room
Energy, silence, surprise.
What’s underneath
Breakthroughs need to be captured and acted on.
Avoid here
Rushing on.
Example
Leadership team. Harvested an insight about decision-making into an experiment.
Full situation card: questions, examples, sample exchange
Filed under methods4640
S9.9Can’t agree the next stepThe team agrees on the issue but not the action
What is happening The team agrees on the issue but not the actionCoach move Gradients of agreement; decision rights; experiments
In the room
Competing proposals; frustration.
What’s underneath
Disagreement about action may hide different risk tolerances.
Avoid here
Endless discussion.
Example
Product team. Tested two options in parallel for two weeks.
Full situation card: questions, examples, sample exchange
Filed under methods36354037
S8.12AI or new tool adoption changes how the team worksNew AI or digital tools change roles, decisions and expertise
What is happening New AI or digital tools change roles, decisions and expertiseCoach move Treat adoption as a team change: explore hopes and fears, agree principles, and run small experiments with review
In the room
Excitement from some, anxiety from others. Unspoken worries about jobs and expertise. Inconsistent use: some members use AI for everything, others not at all. Confusion about who is accountable for AI-assisted work.
What’s underneath
New tools change more than tasks: they change status (whose expertise matters), decision rights (who checks what), trust and quality standards. If these are not discussed, teams split into enthusiasts and resisters, and risks go unmanaged. It is a classic polarity — speed and innovation versus quality and safety.
Avoid here
Taking sides between enthusiasts and sceptics. Ignoring job-security fears. Letting adoption happen individually without team agreements.
Example
Marketing team. Polarity mapping of speed vs quality led to principles: AI drafts, humans decide and check facts. Anxiety eased; output rose.
Full situation card: questions, examples, sample exchange
Filed under methods24374017

9Coach mistakes & watch-outs

  • Accepting vague actions.
  • Too many actions.
  • Not reviewing.
  • The coach owning the follow-up.

10Team traps

  • Over-committing.
  • Assigning actions to absent members.
  • Forgetting.

Three worked problems

1

One experiment. After a session on meetings, the team agrees one experiment: standing meetings for two weeks. They review and keep it.

2

Owner and buddy. Each experiment gets an owner and a buddy. Follow-through rises from 30% to 80%.

3

Failed experiment. An experiment to share information daily fails. The team learns that a weekly update is enough. They adapt.

Where it comes from

Experimentation in Agile and lean practice; Kolb’s experiential learning cycle; action learning (Reg Revans).

My notes

41
Land, Learn and Sustain family

Peer Accountability and Peer Coaching

Core move: Help members hold each other accountable without the leader as enforcer
4 options10 questions6 situations

1What it really is

In high-performing teams, accountability is mutual: members expect each other to deliver and say so when they don’t. Lencioni calls this peer accountability and notes that teams often depend on the leader to hold members accountable. This method helps the team set up peer structures — accountability partners, peer coaching triads — that support members between sessions and build the team’s own coaching capacity.

4How it works, deeply

Peer accountability is stronger than leader accountability because it comes from colleagues whose respect members value. It also distributes the leadership burden. Peer coaching triads build coaching skills across the team, so it becomes less dependent on the coach. Over time, the team’s own capacity to coach itself is the most sustainable outcome of team coaching.

Quick card

Reach for it when
Accountability flows only from the leader; members don’t challenge each other; commitments slip; the team wants to build coaching capability
The move
Set up peer pairs or triads who check in on commitments and coach each other between sessions
Watch
Peer accountability without trust becomes peer policing. Build trust and norms first.
Four questions that often open it
  1. How do we hold each other accountable now?
  2. What would make it easier to call each other on missed commitments?
  3. Who could support you between sessions?
  4. What would good peer coaching look like?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Leader as enforcer — only the leader follows up.
  • Avoided accountability — members don’t call each other on missed commitments.
  • Uneven contributions — some members do more than others.
  • Coaching capability — the team wants to coach itself.
  • Remote team — members need support between meetings.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Accountability partners — pairs check in weekly.
2Peer coaching triads — coach, coachee, observer rotate.
3Team scoreboard — visible commitments and progress.
4Accountability norms — how we will raise missed commitments.

5Where it gets stuck

Pairs stop meeting. Members are reluctant to challenge each other. Peer coaching becomes advice-giving.

6How to move it forward

Keep structures simple. Model peer coaching in sessions. Review how the structures are working.

7Questions to ask the team

Core questions
  • Who will be your accountability partner?
  • How often will you check in?
  • How will we raise missed commitments?
  • What skills do we need for peer coaching?
  • How will we review?
Going further
  • What makes holding a peer accountable hard?
  • What would good accountability feel like?
  • How can we support rather than police?
  • What do we need from the leader?
  • What would a self-coaching team look like?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S3.10Advice-giving instead of thinkingMembers jump to solutions for each other
What is happening Members jump to solutions for each otherCoach move Slow down; ask questions; use structured thinking
In the room
Someone shares a problem; others immediately suggest fixes.
What’s underneath
Advice-giving is quick and well-meant but can block thinking and ownership.
Avoid here
Lecturing about coaching. Shutting down all suggestions.
Example
Leadership team. Practised “questions only” rounds; quality of thinking improved.
Full situation card: questions, examples, sample exchange
Filed under methods954142
S6.4Everything escalates to the leaderThe team doesn’t decide without the leader
What is happening The team doesn’t decide without the leaderCoach move Clarify decision rights; coach the leader to step back
In the room
Members end discussions with “let’s ask Priya”; the leader’s calendar is overloaded; decisions wait for the leader’s return from travel.
What’s underneath
Escalation may reflect fear of getting it wrong, unclear authority, or a leader who unconsciously rewards dependence. Both the team and the leader are part of the pattern.
Avoid here
Blaming the leader or the team.
Example
Operations team. The leader agreed spending thresholds below which the team decided alone. Response time to customers halved.
Full situation card: questions, examples, sample exchange
Filed under methods353241
S6.6Free ridersSome members contribute less
What is happening Some members contribute lessCoach move Peer feedback; peer accountability; role negotiation
In the room
Sighs when some names come up, uneven workload, sarcasm about “some people’s priorities”. Hard-working members look tired and resentful.
What’s underneath
Free riding affects fairness and motivation. It may reflect unclear roles, disengagement, overload elsewhere, or a lack of peer accountability norms. Assuming laziness is usually wrong.
Avoid here
Public shaming.
Example
Project team. Role negotiation clarified expectations; one “free rider” turned out to be supporting another department two days a week.
Full situation card: questions, examples, sample exchange
Filed under methods29413930
S6.7Nobody owns actionsActions are agreed but no one follows through
What is happening Actions are agreed but no one follows throughCoach move Named owners; experiments; peer accountability
In the room
Action lists full of “we”, actions repeated from last session, nobody quite sure who was meant to do what.
What’s underneath
Collective ownership often becomes no ownership. Without a named person and a date, every member assumes someone else will act.
Avoid here
Coach owning follow-up.
Example
Leadership team. Introduced owner-and-buddy for every action; follow-through rose from about a third to most actions.
Full situation card: questions, examples, sample exchange
Filed under methods404142
S9.4Reverting under pressureNew behaviours disappear when stress rises
What is happening New behaviours disappear when stress risesCoach move Immunity to change; rhythm; peer support
In the room
The team describes going back to old habits.
What’s underneath
Old habits feel safer under stress.
Avoid here
Blame.
Example
Sales team. An immunity map revealed the assumption that only speed mattered under pressure.
Full situation card: questions, examples, sample exchange
Filed under methods184441
S6.11A star performer or hero cultureOne person carries critical work; others defer, or resent; the system depends on a hero
What is happening One person carries critical work; others defer, or resent; the system depends on a heroCoach move Make the pattern systemic rather than personal; spread capability and recognition
In the room
The star answers first and is thanked most. Others wait for them, or roll their eyes. The star works late and looks tired. The leader praises the star in public.
What’s underneath
Hero culture is co-created: the organisation rewards heroics, the hero gains identity and status, and others gain relief from responsibility. It creates fragility (key-person risk), burnout and unequal growth. The hero may also be carrying the team’s shadow — the competence or decisiveness others don’t own.
Avoid here
Attacking or diminishing the star. Ignoring the burnout risk. Treating it as only the star’s behaviour.
Example
Sales team. The top performer closed half the deals. The team redesigned key accounts into pairs; overall sales rose and the star worked fewer weekends.
Full situation card: questions, examples, sample exchange
Filed under methods14413929

9Coach mistakes & watch-outs

  • Setting up structures without trust.
  • Too many structures.
  • Not teaching peer coaching skills.
  • The coach remaining the only accountability.

10Team traps

  • Pairs that become gossip.
  • Accountability as blame.
  • Abandoning pairs after two weeks.

Three worked problems

1

Triads. A leadership team forms peer coaching triads that meet fortnightly. After three months, members say the triads are more useful than the monthly team meeting.

2

Missed commitments. The team agrees a norm: anyone can ask “Where are we on this?” without it being an attack. Follow-through improves.

3

Leader relief. The leader is no longer the only one following up. She says she can finally focus on strategy.

Where it comes from

Patrick Lencioni (peer accountability), Jon Katzenbach and Douglas Smith (mutual accountability), peer coaching and action learning sets.

My notes

42
Land, Learn and Sustain family

Action Learning Sets for Intact Teams

Core move: Structured peer problem-solving: questions first, action between meetings, reflection on learning
4 options10 questions3 situations

1What it really is

Reg Revans developed action learning on the principle that learning comes from programmed knowledge plus questioning insight (L = P + Q). In a classic action learning set, a small group meets regularly; each meeting, one or more members present a real problem; others ask questions to help the presenter think; the presenter commits to action; and the group reflects on its own learning. Adapted for intact teams, sets can work on individual challenges that affect the team, or on shared team challenges. Michael Marquardt’s version adds a “learning coach” role, which the team coach models and then hands to members.

4How it works, deeply

Questions shift ownership to the presenter, who knows the context better than anyone else. Advice, however good, takes ownership away. Action learning also builds the team’s collective questioning skill — one of the most transferable outcomes of team coaching. Regular reflection on the process (“How well did we help?”) builds meta-learning: the team learns how it learns. When the team coach models and then hands over the learning coach role, the team becomes less dependent on the coach.

Quick card

Reach for it when
Members face real, complex challenges; the team defaults to advice-giving; the team wants to build its own coaching capability; between coaching sessions
The move
One member presents a real challenge; the others ask only questions; the presenter commits to an action; the set reflects on how it learned
Watch
The questions-only rule is the heart of the method. The moment advice starts, the presenter stops thinking.
Four questions that often open it
  1. What is the challenge you want to bring?
  2. What questions would help you see it differently?
  3. What action will you take before we meet again?
  4. What did we learn about how we help each other?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Advice-giving culture — members jump to solutions for each other.
  • Complex challenges — problems with no clear answer.
  • Self-coaching goal — the team wants to coach itself.
  • Between sessions — the team needs structure between coaching sessions.
  • Leadership development — members developing as leaders.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Classic set — 60–90 minutes; one or two presenters; questions only; action and reflection.
2Team challenge — the whole team is the “presenter” for a shared problem; a few members act as questioners.
3Learning coach role — one member watches the process and intervenes to improve questions and reflection.
4Rotating sets — subgroups of four to six meet between coaching sessions.

5Where it gets stuck

Questions become disguised advice (“Have you thought about…?”). Presenters bring safe problems. Actions aren’t followed up. Sets fade when people get busy.

6How to move it forward

Name disguised advice gently. Ask presenters to bring a problem that genuinely matters and is theirs. Start each set with action review. Schedule sets in advance as a team routine.

7Questions to ask the team

Core questions
  • What is the problem, and why is it yours?
  • What have you tried?
  • What questions would help?
  • What action will you take?
  • What did we learn about helping?
Going further
  • What are you not saying about this problem?
  • Who else is affected?
  • What would success look like?
  • What’s stopping you?
  • What did the questions open up that advice wouldn’t have?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S3.10Advice-giving instead of thinkingMembers jump to solutions for each other
What is happening Members jump to solutions for each otherCoach move Slow down; ask questions; use structured thinking
In the room
Someone shares a problem; others immediately suggest fixes.
What’s underneath
Advice-giving is quick and well-meant but can block thinking and ownership.
Avoid here
Lecturing about coaching. Shutting down all suggestions.
Example
Leadership team. Practised “questions only” rounds; quality of thinking improved.
Full situation card: questions, examples, sample exchange
Filed under methods954142
S6.7Nobody owns actionsActions are agreed but no one follows through
What is happening Actions are agreed but no one follows throughCoach move Named owners; experiments; peer accountability
In the room
Action lists full of “we”, actions repeated from last session, nobody quite sure who was meant to do what.
What’s underneath
Collective ownership often becomes no ownership. Without a named person and a date, every member assumes someone else will act.
Avoid here
Coach owning follow-up.
Example
Leadership team. Introduced owner-and-buddy for every action; follow-through rose from about a third to most actions.
Full situation card: questions, examples, sample exchange
Filed under methods404142
S6.12Knowledge loss and key-person dependencyCritical knowledge lives in a few heads; departures cause crises
What is happening Critical knowledge lives in a few heads; departures cause crisesCoach move Make knowledge flow a team responsibility: map dependencies, pair, document and hand over by design
In the room
Anxious jokes about “if she wins the lottery”. Work stalls during holidays. New members take months to become productive. Old decisions can’t be explained.
What’s underneath
Key-person dependency is a systemic risk, not an individual failing. It grows when the team is overloaded, when expertise is rewarded more than sharing, and when membership changes often. It links to fluid teaming and hero culture.
Avoid here
Asking experts to “document everything” on top of their work. Blaming those who leave. Treating it as an IT problem only.
Example
Engineering team. Built a dependency map; three critical systems had one expert. Pairing rotations and a monthly “teach-back” cut the risk in a quarter.
Full situation card: questions, examples, sample exchange
Filed under methods3423944

9Coach mistakes & watch-outs

  • Allowing advice.
  • Bringing trivial problems.
  • No reflection on process.
  • The coach remaining the learning coach forever.

10Team traps

  • Disguised advice.
  • Presenters defending rather than thinking.
  • Skipping sets when busy.

Three worked problems

1

The advice habit. A leadership team always gives advice. In its first action learning set, the questions-only rule is broken eleven times; by the fourth set, only twice. Members say their thinking has changed more than in any training.

2

Team challenge. The team brings a shared challenge — falling customer satisfaction. Questions reveal three different assumptions about the cause. The team agrees to test each one.

3

Handing over. After three sets led by the coach, members rotate the learning coach role. The sets continue after the engagement ends.

Where it comes from

Reg Revans’ action learning (1940s onwards); Michael Marquardt’s action learning model and the learning coach role; widely used in leadership development and team coaching.

My notes

43
Land, Learn and Sustain family

After-Action Review / Retrospective

Core move: Make learning from experience a routine, not an accident
4 options10 questions5 situations

1What it really is

The US Army’s after-action review (AAR) and Agile retrospectives are structured ways for teams to learn from experience. The core questions are simple: what was supposed to happen, what actually happened, why there was a difference, and what we will sustain or improve. The key is a blame-free culture in which the goal is learning, not judgment. In team coaching, the coach helps the team build this as a routine, so learning becomes part of how the team works.

4How it works, deeply

Learning teams outperform others because they adapt faster. AARs make learning explicit and shared. Separating learning from blame is essential: people share information only if they feel safe. Regular AARs also build the team’s reflective capacity — they begin to notice and adjust in real time.

Quick card

Reach for it when
After a project, event, crisis or sprint; when the team repeats mistakes; when learning is not shared
The move
Ask four questions — what was supposed to happen, what happened, why, and what we’ll do next time — without blame
Watch
A review that turns into blame will teach the team to hide information next time.
Four questions that often open it
  1. What did we intend?
  2. What actually happened?
  3. Why the difference?
  4. What will we keep and change next time?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Repeated mistakes — the team keeps making the same errors.
  • Post-crisis — the team needs to learn from a difficult event.
  • Project end — a natural reflection point.
  • Blame culture — reviews become fault-finding.
  • Fast pace — the team never pauses to reflect.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Four-question AAR — intended, actual, why, next time.
2Sailboat retro — wind (helped), anchors (held back), rocks (risks), island (goal).
3Timeline retro — map events and emotions.
4Learning harvest — record lessons and share them.

5Where it gets stuck

The review becomes blame. Insights are generated but not acted on. The team skips reviews when busy.

6How to move it forward

Set ground rules: no blame, focus on systems. Ask the leader to share mistakes first. Turn insights into experiments.

7Questions to ask the team

Core questions
  • What was supposed to happen?
  • What actually happened?
  • What caused the difference?
  • What will we keep?
  • What will we change?
Going further
  • What surprised us?
  • What did we learn about how we work together?
  • What signal did we miss?
  • Who else needs to learn this?
  • How will we make this change stick?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S2.9Shame after a public failureThe team failed visibly and members feel embarrassed
What is happening The team failed visibly and members feel embarrassedCoach move Make learning safe; separate identity from event; review without blame
In the room
Avoidance of the topic, defensive explanations, self-criticism or blame.
What’s underneath
Shame makes teams hide and defend. Learning requires turning shame into curiosity. Blame and withdrawal are both shame responses.
Avoid here
Rushing past the failure. Blaming. Over-reassuring.
Example
Launch failure. After-action review with no blame; team found process gaps. Confidence recovered.
Full situation card: questions, examples, sample exchange
Filed under methods432120
S6.10Handoffs keep failingWork stalls at interfaces
What is happening Work stalls at interfacesCoach move Role negotiation; AAR; interaction patterns
In the room
Complaints that work arrives late, incomplete or without context; blame bouncing between functions.
What’s underneath
Handoffs fail when expectations about timing, quality and information are not explicit. Each side sees only its own pressures.
Avoid here
Blame.
Example
Sales–delivery handoff. Role negotiation produced a one-page handoff checklist; rework fell.
Full situation card: questions, examples, sample exchange
Filed under methods39431015
S9.1Great session, nothing changesInsight in sessions; no change in daily work
What is happening Insight in sessions; no change in daily workCoach move Small experiments; redesign routines; review
In the room
Next session starts with “we didn’t get to it”.
What’s underneath
Insight without structure fades. Daily routines pull the team back.
Avoid here
Blame.
Example
Leadership team. Experiments tracked on a visible board; follow-through improved.
Full situation card: questions, examples, sample exchange
Filed under methods40444345
S9.5Experiment fails and team gives upA failed experiment leads to abandonment
What is happening A failed experiment leads to abandonmentCoach move AAR; reframe failure as learning; adapt
In the room
Disappointment; “told you so”.
What’s underneath
Teams often confuse failure of an experiment with failure of the goal.
Avoid here
Forcing the same experiment.
Example
Product team. Adjusted a daily stand-up to weekly after the daily version failed.
Full situation card: questions, examples, sample exchange
Filed under methods434020
S10.5Co-coach disagreementCo-coaches disagree on approach
What is happening Co-coaches disagree on approachCoach move Contracting between coaches; review
In the room
Visible tension between coaches.
What’s underneath
Co-coach dynamics affect the team.
Avoid here
Arguing in front of the team.
Example
Co-coaches. Agreed roles and a signal for time-outs.
Full situation card: questions, examples, sample exchange
Filed under methods143

9Coach mistakes & watch-outs

  • Allowing blame.
  • Skipping action.
  • Making reviews too long.
  • Only reviewing failures.

10Team traps

  • Defensiveness.
  • Superficial lessons (“communicate better”).
  • Skipping reviews when busy.

Three worked problems

1

The product launch AAR. The team reviews a launch. The difference between plan and reality was late design changes. The team agrees a design freeze date for next time.

2

Success review. The team reviews a successful project to understand why it worked. They find early stakeholder involvement was key and make it standard.

3

Sailboat. A retro using the sailboat reveals an anchor: too many approvals. The team escalates the issue and gets one approval layer removed.

Where it comes from

US Army after-action review; Agile retrospectives (Esther Derby and Diana Larsen); organisational learning (Peter Senge, Chris Argyris).

My notes

44
Land, Learn and Sustain family

Redesign the Team Rhythm

Core move: Change the team’s meetings and routines so new behaviours have a home
4 options10 questions11 situations

1What it really is

Team behaviour is shaped by its routines: meetings, check-ins, reports, reviews. If routines stay the same, behaviour tends to revert. This method helps the team redesign its operating rhythm: what meetings it has, their purpose, frequency, format and participants. It also embeds coaching outcomes — e.g. a monthly process check, a quarterly stakeholder review, a weekly experiment check-in — into routine work.

4How it works, deeply

Structures shape behaviour. A meeting that always starts with status updates will never become strategic. By redesigning routines, the team creates spaces where new behaviours can happen naturally. This is how coaching outcomes become sustainable: they become “how we work”, not “what we did in coaching”.

Quick card

Reach for it when
Meetings are ineffective; insights from coaching don’t transfer to daily work; the team’s rhythm doesn’t fit its work
The move
Audit the team’s meetings and routines, then redesign them to support the team’s purpose and new agreements
Watch
New habits need structure. Without redesigning routines, coaching insights fade.
Four questions that often open it
  1. What meetings do we have, and what is each for?
  2. Which ones help us? Which drain us?
  3. Where would our new agreements live?
  4. What rhythm fits our work?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Meeting overload — too many meetings, little value.
  • Status-only meetings — meetings are reporting, not deciding.
  • Coaching insights fade — new behaviours disappear between sessions.
  • Mismatched cadence — strategic issues discussed weekly, operational issues quarterly.
  • Hybrid challenges — routines don’t work for remote members.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Meeting audit — list meetings, purposes, time and value.
2Meeting design — define purpose, outputs, roles and format for each.
3Rhythm map — daily, weekly, monthly, quarterly routines.
4Embed reflection — add short process checks to existing meetings.

5Where it gets stuck

The team audits meetings but changes nothing. The leader is attached to existing routines. New routines are too complex.

6How to move it forward

Start with one meeting. Try the redesign for a month. Review and adjust.

7Questions to ask the team

Core questions
  • What is each meeting for?
  • What outcome should it produce?
  • Who needs to be there?
  • How often?
  • Where will we reflect on how we work?
Going further
  • Which meeting would you cancel if you could?
  • What’s missing from our rhythm?
  • What would a remote member say about our routines?
  • How do we start and end meetings?
  • What routine would help our new agreements stick?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S2.3Exhausted / burnoutMembers are depleted; coaching feels like another demand
What is happening Members are depleted; coaching feels like another demandCoach move Make load visible; decide what to stop; protect energy
In the room
Yawns, slumped posture, cameras off. People arrive late from back-to-back meetings. Reactions are slow.
What’s underneath
Burnout is a team and system issue, not only individual. Coaching that adds demands will fail. Reducing load is the intervention.
Avoid here
Asking for more commitments. Resilience lectures. Ignoring systemic causes.
Example
Nursing team. Used the session to list all recurring tasks and stopped three.
Full situation card: questions, examples, sample exchange
Filed under methods38544
S3.11Remote members invisibleHybrid meetings favour those in the room
What is happening Hybrid meetings favour those in the roomCoach move Agree hybrid norms; equalise participation
In the room
In-room members talk to each other; remote members struggle to join; side conversations.
What’s underneath
Hybrid meetings create unequal access. Remote members lose influence and belonging.
Avoid here
Treating remote members as an afterthought.
Example
Global team. Everyone joined from laptops; remote members spoke more.
Full situation card: questions, examples, sample exchange
Filed under methods4544
S5.7Short-termism / always urgentThe team focuses only on immediate issues
What is happening The team focuses only on immediate issuesCoach move Manage the short/long polarity; protect strategic time
In the room
Discussion of this week’s issues; no space for strategy.
What’s underneath
Short-termism may reflect pressure, incentives or anxiety.
Avoid here
Ignoring real urgency.
Example
Retail team. Agreed a monthly strategy session.
Full situation card: questions, examples, sample exchange
Filed under methods173844
S6.8Meeting overloadToo many meetings, too little value
What is happening Too many meetings, too little valueCoach move Audit and redesign rhythms; stop doing
In the room
Members arrive late from back-to-back calls, laptops open, “this could have been an email” muttered. Calendars full from 8 to 6.
What’s underneath
Meeting overload drains energy and reduces time for real work. Meetings often accumulate because nobody has authority or permission to stop them.
Avoid here
Adding more meetings.
Example
Leadership team. A meeting audit listed 22 hours a week of recurring meetings; they cut six hours per person.
Full situation card: questions, examples, sample exchange
Filed under methods4438
S8.2Hybrid frictionHybrid working creates unequal access and misunderstandings
What is happening Hybrid working creates unequal access and misunderstandingsCoach move Agree hybrid norms; redesign rhythms; map the team in space
In the room
Office group and remote group; separate chats; remote members feel second-class.
What’s underneath
Hybrid creates proximity bias and different experiences of the same team.
Avoid here
Choosing a side (office vs remote).
Example
Consultancy team. Agreed decisions only in shared channels; in-office days aligned.
Full situation card: questions, examples, sample exchange
Filed under methods44412
S8.4Rapid growth / many new membersThe team is growing fast; culture is diluting
What is happening The team is growing fast; culture is dilutingCoach move Explicit norms; onboarding rituals; rhythms
In the room
Many new faces; old-timers nostalgic; confusion about how things work.
What’s underneath
Growth stretches informal norms. What worked when small no longer works.
Avoid here
Nostalgia. Ignoring newcomers.
Example
Startup. Wrote team agreements and an onboarding guide; new joiners got up to speed faster.
Full situation card: questions, examples, sample exchange
Filed under methods426443
S9.1Great session, nothing changesInsight in sessions; no change in daily work
What is happening Insight in sessions; no change in daily workCoach move Small experiments; redesign routines; review
In the room
Next session starts with “we didn’t get to it”.
What’s underneath
Insight without structure fades. Daily routines pull the team back.
Avoid here
Blame.
Example
Leadership team. Experiments tracked on a visible board; follow-through improved.
Full situation card: questions, examples, sample exchange
Filed under methods40444345
S9.4Reverting under pressureNew behaviours disappear when stress rises
What is happening New behaviours disappear when stress risesCoach move Immunity to change; rhythm; peer support
In the room
The team describes going back to old habits.
What’s underneath
Old habits feel safer under stress.
Avoid here
Blame.
Example
Sales team. An immunity map revealed the assumption that only speed mattered under pressure.
Full situation card: questions, examples, sample exchange
Filed under methods184441
S9.7Learning stays in the roomTeam learning isn’t shared with stakeholders
What is happening Team learning isn’t shared with stakeholdersCoach move Close the loop; harvest; rhythms
In the room
Stakeholders unaware of changes.
What’s underneath
Change needs to be visible to have impact.
Avoid here
The coach reporting for the team.
Example
Leadership team. Shared learning with the sponsor in a short presentation.
Full situation card: questions, examples, sample exchange
Filed under methods474644
S10.11Cameras off on videoRemote members turn off cameras
What is happening Remote members turn off camerasCoach move Norms; check-in; rhythms
In the room
Black screens.
What’s underneath
Cameras off may reflect fatigue or disengagement.
Avoid here
Forcing cameras.
Example
Team. Cameras on for check-in only.
Full situation card: questions, examples, sample exchange
Filed under methods4544
S6.12Knowledge loss and key-person dependencyCritical knowledge lives in a few heads; departures cause crises
What is happening Critical knowledge lives in a few heads; departures cause crisesCoach move Make knowledge flow a team responsibility: map dependencies, pair, document and hand over by design
In the room
Anxious jokes about “if she wins the lottery”. Work stalls during holidays. New members take months to become productive. Old decisions can’t be explained.
What’s underneath
Key-person dependency is a systemic risk, not an individual failing. It grows when the team is overloaded, when expertise is rewarded more than sharing, and when membership changes often. It links to fluid teaming and hero culture.
Avoid here
Asking experts to “document everything” on top of their work. Blaming those who leave. Treating it as an IT problem only.
Example
Engineering team. Built a dependency map; three critical systems had one expert. Pairing rotations and a monthly “teach-back” cut the risk in a quarter.
Full situation card: questions, examples, sample exchange
Filed under methods3423944

9Coach mistakes & watch-outs

  • Redesigning everything at once.
  • Ignoring the leader’s needs.
  • Not reviewing.
  • Creating more meetings.

10Team traps

  • Attachment to old routines.
  • Adding without removing.
  • Abandoning new routines under pressure.

Three worked problems

1

Strategic meeting. A leadership team’s weekly meeting is all status. They move status to a dashboard and use the meeting for one strategic issue. Members say it is the first useful meeting in months.

2

Process check. The team adds a five-minute process check at the end of each meeting: “What worked? What would we change?” Behaviour improves steadily.

3

Hybrid redesign. A hybrid team agrees all meetings are remote-first. Remote members report feeling included.

Where it comes from

Operating rhythm and meeting design practice (e.g. Patrick Lencioni’s “Death by Meeting”), Agile ceremonies, organisational routines research.

My notes

45
Land, Learn and Sustain family

Team Rituals and Ceremonies

Core move: Design how the team marks beginnings, endings, transitions, wins and losses
4 options10 questions9 situations

1What it really is

Rituals are repeated, symbolic actions that give meaning to moments: a welcome lunch, a farewell round, a bell rung when a deal closes, a minute of silence after a loss, a retrospective after a launch. Teams that mark their moments build belonging and identity; teams that don’t often feel transactional and lose energy. This method goes beyond check-ins: it asks the team to look at its whole life cycle — beginnings, endings, transitions, wins and losses — and design small rituals for each. Research on rituals shows they reduce anxiety, increase meaning and strengthen group identity.

4How it works, deeply

Anthropologists describe rituals as markers of transition: they help people let go of one state and enter another (separation, transition, incorporation). Organisational rituals do the same: a farewell lets the team grieve and redistribute roles; a welcome tells a newcomer they belong; a celebration converts effort into meaning. Research by Michael Norton and Francesca Gino shows that even simple rituals reduce anxiety and increase the sense of control. For teams, shared rituals also strengthen collective identity — the feeling of “us”.

Quick card

Reach for it when
Joins and departures pass without notice; wins are not celebrated; losses are not acknowledged; the team feels transactional; after a merger or crisis
The move
Help the team design simple, meaningful rituals for the moments that matter — and decide which ones to keep
Watch
Rituals imposed from above feel fake. The team must design them, and they must fit its culture — small and genuine beats big and forced.
Four questions that often open it
  1. Which moments in our team’s life go unmarked?
  2. How do we welcome people, and how do we say goodbye?
  3. How do we celebrate a win, and how do we acknowledge a loss?
  4. Which rituals do we already have that we value?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Transactional feel — the team works but doesn’t feel like a team.
  • Unmarked transitions — people join and leave without acknowledgement.
  • No celebration — wins pass straight to the next target.
  • Unacknowledged loss — a failure, layoff or death is not marked.
  • Merged or remote team — no shared rituals yet.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Ritual audit — list the moments in the team’s life cycle and how each is marked today.
2Design a ritual — for one moment, agree what will happen, who leads, and what makes it meaningful.
3Welcome and farewell — standard, personal ways to join and leave the team.
4Wins and losses — a regular moment to celebrate and to acknowledge what didn’t work.

5Where it gets stuck

Rituals feel cheesy or forced. They are designed but quietly dropped. One person always organises them. Rituals exclude remote members.

6How to move it forward

Keep them small, short and genuine. Let the team choose. Rotate responsibility. Design remote-friendly versions from the start.

7Questions to ask the team

Core questions
  • Which moments matter most in our team’s year?
  • How are they marked today?
  • What would feel meaningful, not forced?
  • Who will lead it?
  • How will remote members take part?
Going further
  • What rituals from previous teams did you love?
  • What loss have we never properly acknowledged?
  • What is a small way to celebrate weekly?
  • How should we mark the end of this coaching engagement?
  • Which ritual would we miss most if it stopped?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S1.10Merged team (“us and them”)Two former teams now one; old identities persist
What is happening Two former teams now one; old identities persistCoach move Honour both histories, then build a shared story and purpose
In the room
Members sit with their old team. Language like “we used to” and “their way”. Jokes with an edge.
What’s underneath
Mergers cause loss — of identity, status, ways of working. Unacknowledged loss turns into resistance. A new identity forms only after old ones are respected.
Avoid here
Forcing a new identity too quickly. Ignoring grief. Taking sides.
Example
Bank merger. Two teams drew their timelines and shared them. They found common experiences. A shared purpose emerged.
Full situation card: questions, examples, sample exchange
Filed under methods11262045
S2.4Grief after a lossA colleague has died, left suddenly or been seriously ill
What is happening A colleague has died, left suddenly or been seriously illCoach move Pause the agenda; create space to acknowledge the loss
In the room
Silence, tearfulness, avoidance. Some members want to “get on with work”; others can’t.
What’s underneath
Teams grieve collectively. Unacknowledged grief shows up as irritability, withdrawal or loss of purpose. People grieve differently; the team needs room for differences.
Avoid here
Rushing to tasks. Forcing emotional sharing. Acting as a therapist.
Example
Research team. A colleague died. The session became a remembrance; the team decided to name a project after her.
Full situation card: questions, examples, sample exchange
Filed under methods5113145
S2.10Disengaged / going through the motionsMembers show up physically but not mentally
What is happening Members show up physically but not mentallyCoach move Reconnect to purpose and to what each person cares about
In the room
Cameras off, multitasking, minimal participation, no questions.
What’s underneath
Disengagement often means the work has lost meaning, or members feel unheard. It may also signal burnout or plans to leave.
Avoid here
Lecturing about engagement. Assuming laziness.
Example
Admin team. Purpose exploration revealed members felt invisible to stakeholders. Stakeholder feedback restored meaning.
Full situation card: questions, examples, sample exchange
Filed under methods653345
S7.4New leader inherits teamA new leader takes over an existing team
What is happening A new leader takes over an existing teamCoach move Timeline; personal histories; leader role contracting
In the room
Members compare the new leader with the old one, test boundaries, and hold back. The new leader tries to make a quick impact.
What’s underneath
Transitions create anxiety and loyalty conflicts. Members wonder what will change; the leader wonders whom to trust.
Avoid here
Comparing leaders.
Example
Finance team. A new-leader assimilation session let the team ask questions anonymously; the leader answered them openly.
Full situation card: questions, examples, sample exchange
Filed under methods11263245
S8.5Key member leavingAn important member is leaving
What is happening An important member is leavingCoach move Acknowledge; redistribute roles; capture knowledge
In the room
Sadness, worry, role gaps.
What’s underneath
Losing a key member affects roles, relationships and identity.
Avoid here
Ignoring the loss.
Example
Product team. A farewell round and role negotiation covered the gap.
Full situation card: questions, examples, sample exchange
Filed under methods5391145
S9.1Great session, nothing changesInsight in sessions; no change in daily work
What is happening Insight in sessions; no change in daily workCoach move Small experiments; redesign routines; review
In the room
Next session starts with “we didn’t get to it”.
What’s underneath
Insight without structure fades. Daily routines pull the team back.
Avoid here
Blame.
Example
Leadership team. Experiments tracked on a visible board; follow-through improved.
Full situation card: questions, examples, sample exchange
Filed under methods40444345
S10.9Ending the engagementThe coaching is ending
What is happening The coaching is endingCoach move Harvest; handover; close the loop
In the room
Mixed emotions.
What’s underneath
Endings consolidate learning.
Avoid here
Abrupt endings.
Example
Team. Closing ritual and self-coaching plan.
Full situation card: questions, examples, sample exchange
Filed under methods48464745
S8.13A purely virtual teamMembers have never (or rarely) met; all work happens online
What is happening Members have never (or rarely) met; all work happens onlineCoach move Design connection, communication and rituals deliberately — nothing happens by accident online
In the room
Cameras off, chat-heavy, quick transactional meetings. People know each other’s work but not each other. Silence is hard to read. Time zones mean someone is always tired.
What’s underneath
Purely virtual teams differ from hybrid teams: there is no office core, but there is also no informal glue. Trust must be built deliberately, through reliability, responsiveness and some personal connection. Misunderstandings escalate in text. Belonging depends on rituals and norms designed for the medium.
Avoid here
Copying office practices online. Long video sessions. Assuming silence means agreement.
Example
Global consulting team. Introduced a weekly 15-minute “no work talk” call and rotating meeting times. Engagement scores rose.
Full situation card: questions, examples, sample exchange
Filed under methods345415
S8.14Fluid membership: the team keeps changingPeople join and leave constantly; the team never settles
What is happening People join and leave constantly; the team never settlesCoach move Shift from building a stable team to building teaming routines that survive turnover
In the room
New faces every month. Old-timers tired of re-explaining. Newcomers unsure how things work. Norms quietly erode.
What’s underneath
Stable-team models assume membership that lasts. Many teams are now fluid. Without explicit routines, every change resets trust and shared understanding. The answer is not to stop the change but to make joining, working and leaving routine and quick.
Avoid here
Long trust-building processes. Blaming newcomers for not knowing. Treating turnover as temporary when it’s structural.
Example
Agile squads. A one-page team passport and a 60-minute re-launch every quarter. New joiners were productive in days.
Full situation card: questions, examples, sample exchange
Filed under methods3454

9Coach mistakes & watch-outs

  • Imposing rituals.
  • Making them elaborate.
  • Ignoring losses.
  • Forgetting remote members.

10Team traps

  • Cynicism about “team fun”.
  • Rituals that become obligations.
  • Only celebrating the leader’s priorities.

Three worked problems

1

The farewell. A respected engineer leaves. The team creates a farewell ritual: each person shares one thing they learned from her. She calls it the best goodbye of her career. The ritual becomes standard.

2

The loss. After a failed bid, the team holds a 20-minute “wake”: what we’re proud of, what we learned, what we let go. Energy returns faster than after previous losses.

3

Remote wins. A distributed team adds a weekly “wins” thread with a fixed time on Friday. Members say they feel more connected.

Where it comes from

Arnold van Gennep and Victor Turner on rites of passage; research on rituals by Michael Norton and Francesca Gino; William Bridges on transitions; team culture and belonging research.

Theory behind it · Knowledge Library9Bridges’ Transitions model

My notes

46
Land, Learn and Sustain family

Harvest Team Learning

Core move: Help the team notice what it has learned about how it learns
4 options10 questions5 situations

1What it really is

Team coaching aims to build the team’s capacity to learn, not just to solve current problems. Harvesting learning means stepping back to notice changes in the team’s behaviour, relationships and thinking, and how those changes happened. Chris Argyris’ double-loop learning — learning about the assumptions behind actions — is central. A team that understands how it learns can keep learning after coaching ends.

4How it works, deeply

Teams often underestimate their own growth. Making it visible builds confidence and reinforces new behaviours. Reflecting on how learning happened (double-loop learning) makes the team more independent of the coach. The harvest also helps the team explain its development to stakeholders.

Quick card

Reach for it when
Mid-point or end of an engagement; after a significant breakthrough; when the team wants to sustain learning
The move
Ask the team to reflect on what it has learned — not only about the work, but about itself and how it learns
Watch
Harvesting is not summarising. It’s the team naming its own learning in its own words.
Four questions that often open it
  1. What have we learned about ourselves as a team?
  2. What do we do differently now?
  3. How did we learn it?
  4. What do we want to keep learning?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Mid-engagement review — checking progress.
  • End of engagement — consolidating.
  • After a breakthrough — understanding what made it possible.
  • Stagnation — the team feels it has stopped learning.
  • New members — sharing learning with newcomers.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Before and after — compare the team’s initial data or description with now.
2Learning timeline — map key moments of learning.
3Learning principles — the team writes principles of how it learns best.
4Letter to the future team — what would we want a future version of ourselves to know?

5Where it gets stuck

The team lists events but not learning. The leader summarises for the team. The team focuses only on what is still wrong.

6How to move it forward

Ask for evidence: “What would we have done six months ago?” Give each member a voice. Celebrate progress.

7Questions to ask the team

Core questions
  • What do we do now that we didn’t before?
  • What helped us change?
  • What did we learn about each other?
  • What would we tell a new member?
  • What do we want to keep learning?
Going further
  • Which moment in our coaching mattered most?
  • What assumption have we changed?
  • What have we stopped doing?
  • How do we learn best?
  • What would we do differently if we started again?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S5.8Purpose drift after successAfter achieving goals, the team loses direction
What is happening After achieving goals, the team loses directionCoach move Revisit purpose; harvest learning; set new goals
In the room
Low energy, uncertainty, “what now?”
What’s underneath
Achievement can create a vacuum. Teams need a new purpose or a renewed one.
Avoid here
Rushing to new goals without reflection.
Example
Project team. Harvested learning and set a new purpose.
Full situation card: questions, examples, sample exchange
Filed under methods61146
S9.7Learning stays in the roomTeam learning isn’t shared with stakeholders
What is happening Team learning isn’t shared with stakeholdersCoach move Close the loop; harvest; rhythms
In the room
Stakeholders unaware of changes.
What’s underneath
Change needs to be visible to have impact.
Avoid here
The coach reporting for the team.
Example
Leadership team. Shared learning with the sponsor in a short presentation.
Full situation card: questions, examples, sample exchange
Filed under methods474644
S9.8Breakthrough momentA significant insight lands
What is happening A significant insight landsCoach move Harvest; land in experiments
In the room
Energy, silence, surprise.
What’s underneath
Breakthroughs need to be captured and acted on.
Avoid here
Rushing on.
Example
Leadership team. Harvested an insight about decision-making into an experiment.
Full situation card: questions, examples, sample exchange
Filed under methods4640
S10.9Ending the engagementThe coaching is ending
What is happening The coaching is endingCoach move Harvest; handover; close the loop
In the room
Mixed emotions.
What’s underneath
Endings consolidate learning.
Avoid here
Abrupt endings.
Example
Team. Closing ritual and self-coaching plan.
Full situation card: questions, examples, sample exchange
Filed under methods48464745
S5.10A good team that wants to become greatNo crisis, solid results — the team wants to raise its game
What is happening No crisis, solid results — the team wants to raise its gameCoach move Start from strengths, find the next level of value for stakeholders, and stretch with small, ambitious experiments
In the room
Relaxed, confident, curious. Members are proud of results and a little bored. They ask, “What’s next for us?”
What’s underneath
High-performing teams risk the comfort zone and the plateau. The challenge is not repair but stretch: more value for stakeholders, more learning, more distributed leadership. Problem-focused methods can feel wrong here; appreciative and future-focused methods fit better.
Avoid here
Inventing problems so the coaching has something to fix. Generic team-building. Complacent celebration with no stretch.
Example
Finance leadership team. Strong internally, weak at “connecting”. Stakeholder interviews revealed an appetite for strategic advice. The team redefined its purpose and doubled its strategic work.
Full situation card: questions, examples, sample exchange
Filed under methods863046

9Coach mistakes & watch-outs

  • Summarising for the team.
  • Only focusing on gaps.
  • Skipping the “how” of learning.
  • Making it too abstract.

10Team traps

  • False modesty (“we haven’t changed”).
  • Overclaiming change.
  • Losing learning when members leave.

Three worked problems

1

Before and after. The team rereads its interview themes from six months ago. Members laugh at “we never disagree”. They now debate regularly. The harvest helps them see their growth.

2

Learning principles. The team writes principles: “We learn best when we try small things and review them.” These guide future work.

3

Letter to the future. Members write a letter to the team a year from now. It becomes part of their onboarding.

Where it comes from

Organisational learning (Chris Argyris and Donald Schön, double-loop learning), Peter Hawkins’ core learning discipline, reflective practice.

My notes

47
Land, Learn and Sustain family

Close the Loop with Stakeholders

Core move: Share progress with stakeholders and bring their feedback back in
4 options10 questions4 situations

1What it really is

Team coaching is not only for the team; it is for the organisation the team serves. Closing the loop means the team updates stakeholders on what it is changing, asks what they notice, and uses the feedback to adjust. This demonstrates value, builds credibility and keeps the team connected to its purpose. It also completes the multi-stakeholder contracting cycle that started the engagement.

4How it works, deeply

Stakeholder perception often lags behind reality. Closing the loop speeds up recognition and strengthens relationships. It also tests whether the team’s internal change creates external value — the ultimate purpose of team coaching. When the team owns the conversation, it builds confidence and ownership.

Quick card

Reach for it when
Mid-point or end of engagement; when stakeholders don’t see change; when the team needs external feedback
The move
Help the team communicate its progress to stakeholders, gather feedback and use it to adjust
Watch
The team should own the stakeholder conversation. The coach supports; the team speaks.
Four questions that often open it
  1. What do our stakeholders need to know about our progress?
  2. What would we like to hear from them?
  3. How will we invite feedback?
  4. What will we do with it?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Invisible change — the team has changed but stakeholders haven’t noticed.
  • Sponsor review — the sponsor wants evidence of value.
  • Disconnected team — the team has turned inward during coaching.
  • Feedback need — the team wants external validation.
  • End of engagement — time to report.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Stakeholder update — the team presents its learning and changes.
2Pulse survey — short stakeholder feedback survey.
3Stakeholder session — invite stakeholders to a coaching session.
4Feedforward from stakeholders — ask for suggestions for the future.

5Where it gets stuck

The team is reluctant to ask for feedback. Stakeholders don’t respond. Feedback is negative and the team becomes defensive.

6How to move it forward

Prepare the team for feedback. Use simple, specific questions. Treat feedback as data, not judgment.

7Questions to ask the team

Core questions
  • What change do we want stakeholders to notice?
  • How will we tell them?
  • What feedback do we want?
  • How will we use it?
  • Who will lead this?
Going further
  • What do we fear hearing?
  • What would make stakeholders more invested in our success?
  • How will we keep the loop going after coaching?
  • What would surprise them?
  • What do we need from them?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S8.7Stakeholders unhappyStakeholders complain about the team
What is happening Stakeholders complain about the teamCoach move Zoom to stakeholders; close the loop; revisit purpose
In the room
Defensiveness; stories about unreasonable stakeholders.
What’s underneath
Stakeholder dissatisfaction is valuable data, even when partly unfair.
Avoid here
Dismissing complaints.
Example
IT team. Stakeholder interviews led to a new intake process.
Full situation card: questions, examples, sample exchange
Filed under methods16476
S9.7Learning stays in the roomTeam learning isn’t shared with stakeholders
What is happening Team learning isn’t shared with stakeholdersCoach move Close the loop; harvest; rhythms
In the room
Stakeholders unaware of changes.
What’s underneath
Change needs to be visible to have impact.
Avoid here
The coach reporting for the team.
Example
Leadership team. Shared learning with the sponsor in a short presentation.
Full situation card: questions, examples, sample exchange
Filed under methods474644
S10.1Sponsor asks for a report on individualsThe sponsor wants information about team members
What is happening The sponsor wants information about team membersCoach move Hold contract; offer team-level reporting
In the room
Private request.
What’s underneath
Sponsors may misuse coaching for assessment.
Avoid here
Sharing individual data.
Example
CFO sponsor. Accepted monthly theme reports co-written with the team.
Full situation card: questions, examples, sample exchange
Filed under methods147
S10.9Ending the engagementThe coaching is ending
What is happening The coaching is endingCoach move Harvest; handover; close the loop
In the room
Mixed emotions.
What’s underneath
Endings consolidate learning.
Avoid here
Abrupt endings.
Example
Team. Closing ritual and self-coaching plan.
Full situation card: questions, examples, sample exchange
Filed under methods48464745

9Coach mistakes & watch-outs

  • The coach presenting for the team.
  • Asking vague questions.
  • Ignoring negative feedback.
  • Doing it only at the end.

10Team traps

  • Overselling change.
  • Defensive reaction to feedback.
  • Forgetting to report back.

Three worked problems

1

Sponsor review. The team presents its learning to the sponsor. The sponsor is impressed by the team’s ownership and extends the engagement.

2

Pulse survey. Stakeholders rate the team’s responsiveness. Scores have improved from 2.8 to 3.9. The team celebrates and identifies the next improvement.

3

Negative feedback. A stakeholder says nothing has changed. The team is upset but asks for specifics. They learn their changes are invisible to that stakeholder and adjust their communication.

Where it comes from

Peter Hawkins’ systemic team coaching (connecting discipline), stakeholder management, Marshall Goldsmith’s stakeholder-centred coaching.

My notes

48
Land, Learn and Sustain family

Fade the Coach and End Well

Core move: Transfer the coaching role to the team and close the engagement deliberately
4 options10 questions3 situations

1What it really is

Good team coaching makes itself unnecessary. Over the engagement, the coach gradually hands over functions — process observation, check-ins, contracting, reviews — to team members. The final sessions consolidate learning, evaluate outcomes against the original contract, and plan how the team will sustain its development. Ending well also means acknowledging the relationship and the work done.

4How it works, deeply

Endings shape how people remember experiences. A clear, well-designed ending consolidates learning and builds confidence. Handing over coaching functions builds lasting capability. Evaluation closes the multi-stakeholder contract and helps the organisation learn. And acknowledging the relationship models a healthy ending — something many teams rarely practise.

Quick card

Reach for it when
Later in the engagement; when the team depends on the coach; when the engagement is ending
The move
Gradually hand the coaching functions to the team and design an ending that consolidates learning
Watch
An ending that isn’t planned becomes an ending that isn’t noticed. Plan it.
Four questions that often open it
  1. What do we still need from a coach?
  2. Which coaching roles can we take on ourselves?
  3. How will we keep learning after this?
  4. How do we want to end?

2The team’s context

A team needing this method usually shows up in one of these states:

  • Dependency — the team waits for the coach to lead.
  • Sudden end — the engagement ends without closure.
  • Ongoing needs — the team wants to continue some practices.
  • Evaluation — the sponsor wants results.
  • Celebration — the team has achieved significant change.

3The coach’s options

The coach is choosing between these moves, depending on what the team needs:

1Role handover — members take on the coach’s functions.
2Self-coaching plan — the team designs its own development routines.
3Final evaluation — compare outcomes to the contract.
4Closing ritual — acknowledge the journey and the people.

5Where it gets stuck

The team resists ending. The coach is reluctant to let go. The evaluation shows mixed results. There is no plan for sustaining practices.

6How to move it forward

Start talking about the ending early. Plan the handover in stages. Normalise mixed results and focus on learning.

7Questions to ask the team

Core questions
  • Which coaching functions can we take over?
  • What practices will we keep?
  • How will we know if we’re slipping?
  • What did we achieve?
  • How do we want to mark the end?
Going further
  • What would we do differently if we started again?
  • What will we miss?
  • Who will hold the team’s learning?
  • When will we review ourselves?
  • What would we tell another team starting this journey?

8Situations from the field

The recognisable team situations where this method is a first-line or strong second-line move. Open one for a summary, or jump to its full card in the Situation Atlas.

S7.9Leader leaves mid-engagementThe leader exits during coaching
What is happening The leader exits during coachingCoach move Recontract; timeline; transition
In the room
Uncertainty, loss, questions about the coaching’s future and who now owns the contract.
What’s underneath
Leader departure changes the system and the contract. The team may grieve, worry or feel relief.
Avoid here
Continuing as if nothing changed.
Example
Leadership team. Recontracted with the new leader after a farewell session for the old one.
Full situation card: questions, examples, sample exchange
Filed under methods11148
S10.3Coach pulled into expert roleThe team wants the coach to give answers
What is happening The team wants the coach to give answersCoach move Return ownership; process observation; fade the coach
In the room
“What do you think?” “What would you do?”
What’s underneath
Teams may want answers to avoid responsibility.
Avoid here
Becoming the consultant without contracting.
Example
Leadership team. The coach offered a model with permission, then returned to coaching.
Full situation card: questions, examples, sample exchange
Filed under methods9748
S10.9Ending the engagementThe coaching is ending
What is happening The coaching is endingCoach move Harvest; handover; close the loop
In the room
Mixed emotions.
What’s underneath
Endings consolidate learning.
Avoid here
Abrupt endings.
Example
Team. Closing ritual and self-coaching plan.
Full situation card: questions, examples, sample exchange
Filed under methods48464745

9Coach mistakes & watch-outs

  • Ending abruptly.
  • Fostering dependency.
  • Skipping evaluation.
  • Not acknowledging feelings about ending.

10Team traps

  • Asking the coach to stay indefinitely.
  • Denying any change.
  • Forgetting practices quickly.

Three worked problems

1

Rotating facilitator. Over six months, members take turns facilitating sessions. By the end, the team runs its own quarterly reviews.

2

Evaluation. The team compares current data to the baseline. Three of four outcomes improved. One didn’t. They plan how to continue work on it.

3

Closing ritual. Members share one thing they appreciated about the journey and one commitment for the future. Several say it was the most meaningful team moment of the year.

Where it comes from

Coaching ethics and practice on endings and dependency; ICF Team Coaching Competency 8 (promoting team autonomy and growth); group development theory (Tuckman and Jensen’s “adjourning” stage).

My notes

Situation map: which method handles which kind of situation

This counts the situations filed under each method, by situation group. Darker cells mean the method is a heavier-used tool for that kind of situation. It shows, for example, that leader situations lean on contracting and leader-in-the-room work, while action situations lean on the Land family. Click a method to jump to it.

S1ArrivalS2ClimateS3PatternsS4ConflictS5PurposeS6StructureS7LeaderS8ContextS9ActionS10CoachTotal
Contract and Convene
1 Contract with the Three Clients415616
2 Test for Team-ness1214
3 Teaming for Fluid Teams1146
4 Co-create Working Agreements21346319
5 Check-in Rounds25512217
6 Purpose and Stakeholder Expectations319114
7 Contract the Session Live41139
Surface the System
8 Diagnostic and Data Feedback112217
9 Process Observation in Real Time11512313
10 Map Interaction Patterns4116
11 Team Timeline / Journey Line1211229
12 Sculpt the Team (Constellations)112
13 Name the Undiscussable112116
14 Collective Shadow11215
15 Liberating Structures1311219
Shift the Team Frame
16 Zoom to the Ecosystem (Stakeholder Chairs)12122311
17 Polarity Map for Teams1241210
18 Team Immunity to Change11226
19 From Drama to Empowerment111115
20 Appreciative Inquiry: What Is Working221117
21 Externalize the Team Problem11114
22 Walk Down the Ladder of Inference11316
23 Clean Language for Teams1113
24 Theory U and Presencing Practices2114
Trust, Conflict and Voice
25 Build Psychological Safety31318
26 Personal Histories and User Manuals211138
27 Make Conflict Productive156
28 Hear the Minority Voice2111117
29 Team Feedback Rounds22
30 Feedforward and Start / Stop / Continue1113
31 Repair a Rupture in the Room2518
32 Coach the Leader in the Room1111013
Future and Decisions
33 Shared Preferred Future2316
34 Team Pre-Mortem111115
35 Clarify Decision Rights5229
36 Gradients of Agreement12126
37 Consent-Based Decision Making2114
38 Prioritize and Stop Doing2121219
39 Role Negotiation (Give and Get)27211
Land, Learn and Sustain
40 Team Experiments and Commitments11158
41 Peer Accountability and Peer Coaching1416
42 Action Learning Sets for Intact Teams123
43 After-Action Review / Retrospective11215
44 Redesign the Team Rhythm111223111
45 Team Rituals and Ceremonies1213119
46 Harvest Team Learning2215
47 Close the Loop with Stakeholders1124
48 Fade the Coach and End Well123

Situation Atlas

113 situations that come up in team coaching, sorted into 10 groups. Each card shows what is happening and the recommended move at a glance. Open it for what you’ll see in the room, what members might say, what’s underneath, questions to ask the team, what to avoid, examples, a sample exchange, signs it’s working, a look-alike not to confuse it with, and related situations.

Situation groupsS111 cardsArrivalS211 cardsClimateS312 cardsPatternsS411 cardsConflictS510 cardsPurposeS612 cardsStructureS711 cardsLeaderS814 cardsContextS99 cardsActionS1012 cardsCoach
S1
Situation group · 11 situations

How the team arrives

About this group

The first minutes with a team reveal whether you are about to meet a living inquiry or a performance staged for the sponsor. This group maps the ways a team can arrive: sent by someone else, carrying the leader’s agenda, politely flat, wanting one person fixed, overloaded, in crisis, not really a team at all, cynical, brand new, freshly merged, or focused entirely on other teams. The arrival shape predicts which method will help far better than the topic does. Listen for whose agenda is driving, how much ownership is in the room, and whether the energy matches the official story.

S1.1Sent by the sponsor
The team attends because someone above asked; low ownership of the agenda
Name the three clients; find the team’s own stake in the work
In the room

Arms folded, polite questions about “what HR wants”. Members look at the leader to see how seriously to take this. Energy is dutiful, not curious.

Members might say
  • So, what exactly were you told about us?
  • We’re here because the exec team thinks we need fixing.
  • Honestly, we’re fine — we just need more people.
What’s underneath

An assigned engagement feels like a judgment. Members protect themselves until they know whose side the coach is on and whether anything they say will travel upward. Ownership cannot be demanded; it is found when the team locates something it wants from the work.

Questions to ask the team
  1. What would make this worth your time — not the sponsor’s, yours?
  2. What do you think the sponsor is worried about?
  3. What would you put on the agenda if nobody had sent you?
  4. What would you need to know about confidentiality to speak freely?
Avoid here

Defending the sponsor. Launching into diagnostics before the contract is clear. Pretending the request came from the team.

Watch

Say plainly what you will and will not report. Ambiguity here poisons every later session.

Examples from the field
Operations leadership team
The COO commissions coaching after two missed targets. The team opens with sarcasm. The coach shares the sponsor’s brief word for word and asks what they would change. They rewrite the objectives around cross-shift hand-offs — the issue they had been raising for a year.
Hospital ward team
Sent after a complaint. Members expect blame. The coach asks what they are proud of first; ownership grows from there.
Sample exchange
Member

So is this about the complaint?

Coach

The sponsor asked for it after the complaint, yes. What you choose to work on is something we’ll decide together.

Member

Even if it’s not what they want?

Coach

Then we’d find where your agenda and theirs overlap, and I’d say that openly to them.

Signs it’s working

Members start proposing topics; questions shift from “what do they want” to “what do we want”.

Don’t confuse with

S1.8 Cynical about coaching (“been here before”)

Cynicism comes from bad past experiences of coaching; sponsor-sent resistance comes from not choosing this one. Both can coexist.

S1.2The leader’s agenda dressed as the team’s
The leader frames the topic; members nod but energy is elsewhere
Test the agenda with the whole team before working on it
In the room

The leader introduces “our priorities”. Members look at the table. When asked directly, they agree quickly and briefly. Later, side remarks reveal different concerns.

Members might say
  • As we agreed, the focus is accountability.
  • Yes, that’s fine.
  • (after the session) That wasn’t really the problem.
What’s underneath

In hierarchical teams, the leader’s framing becomes the team’s by default. Members don’t contest it because the cost feels high. If the coach accepts the framing, the coaching becomes the leader’s instrument.

Questions to ask the team
  1. Before we start: what would you each add or change about this focus?
  2. If the leader weren’t here, what topic would you choose?
  3. On a scale of 1–10, how much energy do you have for this topic?
  4. What’s missing from this agenda?
Avoid here

Accepting the agenda without testing it. Asking “do you agree?” in front of the leader (invites a yes). Exposing the leader publicly.

Watch

Agree with the leader beforehand that you will test agendas with the team.

Examples from the field
Marketing team
The leader brings “accountability” as the topic. An anonymous card round shows most members want to discuss unclear priorities. The leader accepts. Accountability issues turn out to be a symptom of the priority problem.
Engineering leads
The leader reads the agenda aloud. The coach asks members to rate their energy for each item. The lowest-rated item is dropped.
Sample exchange
Leader

So today is about accountability.

Coach

Thanks, Anna. Before we begin, can I check with everyone: on a scale of 1–10, how much does this topic matter to you today?

Member

Six, maybe.

Another member

Four. Honestly the bigger issue for me is we don’t know what our priorities are.

Signs it’s working

Members add topics; the leader engages with them; energy rises.

Don’t confuse with

S7.1 Leader dominates

A dominant leader shapes every conversation, not just the agenda. Here the issue is specifically ownership of the session focus.

S1.3Polite, flat and “fine”
Everyone is pleasant; nothing real is said; energy is low
Name the pattern lightly; use anonymous or individual ways to surface the real material
In the room

Smiles, agreement, short answers. Nobody disagrees. The conversation feels like a corporate brochure. Time passes slowly.

Members might say
  • We get on really well.
  • No major issues, really.
  • I think we’re a pretty good team.
What’s underneath

Pseudo-harmony (what Scott Peck called pseudo-community) protects the team from conflict and exposure. It is often a sign of low safety, not high trust. The real conversations happen elsewhere.

Questions to ask the team
  1. If you had to name one thing this team could do better, what would it be?
  2. What would people say in the corridor after this session?
  3. What’s the conversation we’re not having?
  4. If an outsider watched this, what would they notice?
Avoid here

Pushing hard for “honesty” before any safety exists. Accepting “fine” as the full picture. Moralising about politeness.

Watch

Politeness is information. Ask what it protects.

Examples from the field
Finance team
Interviews revealed tensions, but the first session was all smiles. The coach shared the interview themes anonymously. Silence, then a member said, “Yes, that’s true.” The real work started.
Senior partners
The coach asked each to write the one thing they’d never say in this room. Cards revealed fears about succession.
Sample exchange
Coach

I’m noticing a lot of agreement today. Can I check — is there anything we’re skating over?

Member

Not really.

Coach

Let’s try it anonymously. Write one thing this team could do better, no names.

Coach

(cards read out) Five of the seven mention decisions being remade later. What do we make of that?

Signs it’s working

The anonymous data matches the interviews; members start referring to the cards; voices change tone.

Don’t confuse with

S2.10 Disengaged / going through the motions

Disengagement is low energy because people have stopped caring; pseudo-harmony is low energy because people are protecting themselves. Disengaged teams rarely smile this much.

S1.4Wants the coach to fix one person
The team or leader frames the problem as one member
Contract for team patterns; widen from person to system
In the room

Members glance at one colleague (often absent or quiet). Stories all point to the same person. The leader says in private, “If X changed, we’d be fine.”

Members might say
  • Honestly, it’s mostly about one person.
  • We all know who the problem is.
  • Can you coach her separately?
What’s underneath

Scapegoating simplifies complexity. The team avoids its own contribution by locating the problem in one person. Even when the person’s behaviour is a real issue, the system usually sustains it.

Questions to ask the team
  1. If this person changed tomorrow, what else would still need to change?
  2. How does the team respond when this behaviour happens?
  3. What does the team gain by focusing here?
  4. What part might each of us play?
Avoid here

Agreeing to “fix” anyone. Running a session that becomes a group attack. Ignoring genuine performance issues that the leader needs to manage.

Watch

Performance management belongs to the leader, not the team coach. Say so.

Examples from the field
Sales team
Members blamed one colleague for losing a big account. A timeline showed three handoffs failed before that colleague was involved. The team redesigned handoffs.
Leadership team
The CEO asked the coach to “sort out” the CTO. The coach explained the boundary and offered to explore what the team’s pattern with the CTO was.
Sample exchange
Leader

Let’s be honest, the issue is Raj.

Coach

I hear real frustration. My role is to coach the team as a whole — if there’s an individual performance issue, that’s yours to address directly.

Leader

Fair.

Coach

Shall we look at how the team works around this, so we can see what’s in the team’s hands?

Signs it’s working

Language shifts from “he” to “we”; members describe their own reactions.

Don’t confuse with

S3.7 A scapegoat

A scapegoat is an ongoing team pattern; this situation is the request at contracting stage.

S1.5Too many topics at once
The team arrives with a long list; everything feels urgent
Harvest, prioritise, and test which topics need the whole team
In the room

Flip chart fills quickly. Members talk over each other to add items. The leader looks anxious about time.

Members might say
  • There are about ten things we need to cover.
  • They’re all connected anyway.
  • We can’t leave any of this.
What’s underneath

An overloaded agenda can be a sign of overload in the work, or a way to avoid depth. Covering everything means engaging with nothing.

Questions to ask the team
  1. Which one, if we made progress, would make the others easier?
  2. Which of these need everyone here?
  3. What’s the cost of not choosing?
  4. What could wait a month?
Avoid here

Trying to cover everything. Choosing for the team. Letting the leader decide alone.

Watch

The way the team chooses is data about how it decides.

Examples from the field
Product leadership
Twelve topics. Dot voting gave two clear priorities; four topics belonged to subgroups. The session achieved a real decision for the first time in months.
School leadership team
The coach asked which topic would “unlock” others. They chose communication with staff.
Sample exchange
Member

Can we get through the first five quickly?

Coach

We could touch all five, or make real progress on one. What would be more useful?

Another member

One. Probably the handoff issue — it causes the others.

Coach

Does that work for everyone?

Signs it’s working

The team commits to one or two topics and the list stops growing.

Don’t confuse with

S1.6 Firefighting / crisis mode

Firefighting is about urgent crises pulling attention; too many topics is about breadth and choice.

S1.6Firefighting / crisis mode
Urgent operational issues hijack every session
Acknowledge the crisis; separate what needs solving now from what the crisis reveals about the team
In the room

Phones buzz. Members arrive late, leave early. Every topic becomes today’s fire. The tone is tense and fast.

Members might say
  • Sorry, we have a live issue.
  • We don’t have time for the softer stuff right now.
  • Can we just use this hour to solve the outage?
What’s underneath

Some teams live in permanent crisis because the crisis protects them from strategic or relational work. Others are genuinely overwhelmed. The coach needs to tell the difference without dismissing the urgency.

Questions to ask the team
  1. What is truly urgent today, and what feels urgent?
  2. How often does this happen?
  3. What does the crisis pattern tell us about how we work?
  4. What would you need to be less in crisis next month?
Avoid here

Ignoring a real emergency. Turning the session into operational problem-solving. Lecturing about firefighting.

Watch

If there is a genuine emergency, reschedule. Coaching a team in emergency mode rarely works.

Examples from the field
IT operations
A major outage hit on session day. The coach rescheduled. The next session started with “what did the outage teach you about the team?”
Agency team
Every session began with a client crisis. The coach named the pattern; the team realised it accepted unreasonable deadlines.
Sample exchange
Member

We have to sort the client issue first.

Coach

Is it something we need to solve in this room, or something you need to go and handle?

Member

Honestly, two of us need to handle it.

Coach

Then let’s free those two, and the rest of us look at why this keeps happening.

Signs it’s working

The team distinguishes urgent from important and makes space for both.

Don’t confuse with

S2.3 Exhausted / burnout

Burnout is the emotional cost; firefighting is the behavioural pattern. Often both appear together.

S1.7A group, not a team
Members report to the same leader but rarely depend on each other
Test for team-ness; find the few genuinely collective tasks
In the room

Meetings are a round of updates. Members multitask. Questions about “collaboration” produce blank looks.

Members might say
  • We don’t really need each other for our day jobs.
  • Team meetings are mostly updates.
  • I’m not sure what we’d collaborate on.
What’s underneath

Teamwork has costs. If the work doesn’t need interdependence, team coaching on collaboration feels like theatre. The real question is where interdependence would add value.

Questions to ask the team
  1. What can only this group do together?
  2. When did you last need each other?
  3. What would suffer if this team stopped meeting?
  4. What should this group decide jointly?
Avoid here

Running trust-building for a group with no shared task. Making the leader feel judged.

Watch

Discovering you are a working group is a valid outcome.

Examples from the field
Regional managers
They found two genuinely shared decisions and focused coaching there. Meetings halved.
Research leads
Realised the real collective task was allocating lab resources; the rest could stay individual.
Sample exchange
Coach

What does this team need to do together that none of you could do alone?

Member

Honestly… not much.

Another member

Budget allocation, maybe. And hiring for shared roles.

Coach

Let’s look at those two. How well do you do them today?

Signs it’s working

The team names specific joint outputs; meeting time is redesigned around them.

Don’t confuse with

S5.5 Individual goals beat team goals

Individual goals beating team goals happens in real teams with conflicting incentives; here the team itself may not need to exist as a team.

S1.8Cynical about coaching (“been here before”)
The team has had away-days and consultants; expects another one
Make past experience into design input; promise less, deliver more
In the room

Eye-rolls. Jokes about “trust falls”. A senior member checks emails ostentatiously.

Members might say
  • We did a team day last year. Nothing changed.
  • Is this going to be personality tests again?
  • I’ll believe it when I see it.
What’s underneath

Cynicism is often disappointed hope. Past interventions created energy that the organisation didn’t sustain. Members protect themselves from another disappointment.

Questions to ask the team
  1. What made past interventions useless?
  2. What would make this one different?
  3. What would you need to see after three sessions to believe it’s worth it?
  4. What did work, even a bit?
Avoid here

Defending coaching. Overpromising. Treating cynics as obstacles.

Watch

Cynics often become the strongest champions once they see real change.

Examples from the field
Public sector team
The coach asked for a list of what made past interventions useless. It became the “we won’t do” list. Cynicism dropped.
Engineering team
A sceptic was asked to be the “reality check” role at each session; he became the team’s most active reflector.
Sample exchange
Member

Here we go again.

Coach

Sounds like you’ve been through this before. What made it not work?

Member

Lots of talk, no change.

Coach

Then let’s build in a check: at session three, if nothing has changed in your daily work, we stop and rethink.

Signs it’s working

Cynics contribute critique that improves the design; jokes become less defensive.

Don’t confuse with

S2.6 Collective cynicism

Collective cynicism is about the organisation and work in general; this is cynicism about coaching specifically.

S1.9Newly formed team
Members are new to each other and to the task
Build working agreements, purpose and relationships early
In the room

Polite introductions, careful words. People explain their backgrounds. Questions about roles are tentative.

Members might say
  • I’m still figuring out where I fit.
  • We’re in the honeymoon phase.
  • Who does what here?
What’s underneath

Tuckman’s “forming” stage: members look for belonging and clarity. Early norms shape the team for years. This is a window of maximum influence.

Questions to ask the team
  1. What do you need from each other to do your best work?
  2. What did your best previous team do that you want here?
  3. What is this team for?
  4. What should we agree early?
Avoid here

Rushing into task without relationships. Assuming norms will form well by themselves.

Watch

Norms set in the first month are hard to change later.

Examples from the field
Startup leadership
Spent the first session on user manuals and working agreements. Six months later, they still referred to them.
Project team
Agreed purpose and decision rights in session one. Fewer conflicts later.
Sample exchange
Coach

Think of the best team you’ve been in. What made it great?

Member

We trusted each other to disagree.

Another member

Clear roles.

Coach

Shall we build those into how this team works from day one?

Signs it’s working

The team writes agreements and refers to them unprompted.

Don’t confuse with

S8.4 Rapid growth / many new members

Rapid growth adds new members to an existing team with established norms; a new team has no norms yet.

S1.10Merged team (“us and them”)
Two former teams now one; old identities persist
Honour both histories, then build a shared story and purpose
In the room

Members sit with their old team. Language like “we used to” and “their way”. Jokes with an edge.

Members might say
  • In our old team we did it properly.
  • They don’t understand how we work.
  • It still feels like two teams.
What’s underneath

Mergers cause loss — of identity, status, ways of working. Unacknowledged loss turns into resistance. A new identity forms only after old ones are respected.

Questions to ask the team
  1. What were you proud of in your old team?
  2. What did you lose in the merger?
  3. What do you want to keep from each history?
  4. What could this team be that neither was before?
Avoid here

Forcing a new identity too quickly. Ignoring grief. Taking sides.

Watch

Seating, language and in-jokes are powerful signals of integration.

Examples from the field
Bank merger
Two teams drew their timelines and shared them. They found common experiences. A shared purpose emerged.
Hospital departments
Appreciative interviews across the old boundary softened resistance.
Sample exchange
Member

Their process is just slower.

Coach

It sounds like each team had ways of working it valued. What did yours do well?

Member

We were fast.

Coach

And what might the other team say they did well?

Another member

Thorough. We need both, honestly.

Signs it’s working

Members use “we” for the new team; mixed seating; shared stories.

Don’t confuse with

S4.6 Old history resurfaces

Old history resurfacing is about past conflict events; this is about two identities.

S1.11Talks only about other teams
Every problem is located outside the team
Zoom to the ecosystem, then explore the team’s part
In the room

Stories about head office, sales, IT, the board. Energy rises when complaining. Silence when asked about the team’s own role.

Members might say
  • The real problem is upstream.
  • If finance did their job, we’d be fine.
  • There’s nothing we can do until they change.
What’s underneath

External blame protects the team from looking at itself — and often contains real truth. The team may also feel powerless. The coach needs to validate the system issues while finding the team’s sphere of influence.

Questions to ask the team
  1. What would the other team say about you?
  2. What part of this is in your control?
  3. What do you need from them, and have you asked?
  4. How might your behaviour make their behaviour more likely?
Avoid here

Dismissing the complaints. Joining the blame. Lecturing about ownership.

Watch

Systems problems are real. Help the team act on the system, not just accept it.

Examples from the field
Customer service
Blamed product for bugs. Empty chair for product revealed they never shared customer data with product. They started a monthly data share.
Regional office
Blamed head office. Agreed to invite head office to a session.
Sample exchange
Member

Sales over-promise every time.

Coach

Let’s put a chair here for sales. Someone sit in it — what would sales say about you?

Member

(in chair) “You never tell us what’s realistic.”

Coach

Is there anything true in that?

Signs it’s working

The team identifies its own contribution and an action toward the other team.

Don’t confuse with

S4.9 Silo war with another team

Silo war is an active conflict between teams; here it is the team’s habit of externalising.

S2
Situation group · 11 situations

The team’s emotional climate

About this group

Teams have weather. Low trust, fear after layoffs, exhaustion, grief, anxiety, cynicism, anger, euphoria, shame, disengagement and unnamed tension all change what a team can do in a session. Climate is collective: it is more than the sum of individual moods, and it often belongs to the system rather than to anyone in the room. The discipline here is to read the climate before working on the task, and to address it with the team rather than around it.

S2.1Low trust
Members protect themselves; candour is rare
Build safety in small steps; start with understanding each other
In the room

Careful wording, guarded body language. People check each other’s reactions. Information is shared selectively.

Members might say
  • I’d rather discuss that offline.
  • I’m not sure it’s safe to say.
  • People here remember everything.
What’s underneath

Low trust may come from past betrayal, competition, unclear intentions or a punishing culture. Trust grows from repeated experiences of vulnerability met with respect.

Questions to ask the team
  1. What would help you say a bit more than you normally would?
  2. What has made trust hard here?
  3. What does trust look like in action?
  4. What small risk could we take today?
Avoid here

Forcing vulnerability. Trust-falls. Asking for honesty without protecting it.

Watch

Trust breaks faster than it builds. Protect the first risk-taker.

Examples from the field
Sales leadership
Started with personal histories. Members heard each other’s backgrounds. Three sessions later, they shared performance worries.
Legal team
Used anonymous safety scale; leader responded well to low scores. Trust grew.
Sample exchange
Coach

How safe does it feel to disagree here, from 1 to 10? Write it down.

Coach

(cards) Mostly 3s and 4s. What would make it a 5?

Member

Knowing it won’t come back to bite us.

Coach

What would that look like in practice?

Signs it’s working

More “I” statements; members admit uncertainty; information flows more freely.

Don’t confuse with

S4.5 Trust breach / leak

A trust breach is a specific incident; low trust is the general climate.

S2.2Fear after layoffs or restructuring
Members are anxious about their jobs; survivor guilt; silence
Acknowledge the fear; make space for what happened before moving on
In the room

Quiet. People look tired. Questions about future plans are met with “who knows”. Some members are overly busy.

Members might say
  • We don’t know who’s next.
  • It feels wrong to talk about team development when people lost their jobs.
  • We just keep our heads down.
What’s underneath

Layoffs create grief, fear and survivor guilt. The team may withdraw, avoid risk and protect itself. Ignoring the emotional impact makes any coaching superficial.

Questions to ask the team
  1. How is the team doing after what happened?
  2. What do you miss?
  3. What do you need now?
  4. What’s in our control?
Avoid here

Jumping to vision or performance. Pretending things are normal. Making promises about job security.

Watch

Be honest about what you don’t know. Don’t speak for the organisation.

Examples from the field
Tech team
After 20% cuts, the first session was a check-in and timeline. Members talked about colleagues who left. The next session moved to priorities with more energy.
Retail head office
The coach worked with the leader to share what she knew openly.
Sample exchange
Coach

Before we start on the plan, can we take a moment for what’s happened?

Member

It’s been hard. I lost my closest colleague.

Another member

I feel guilty I’m still here.

Coach

Thank you. What do you each need from this team now?

Signs it’s working

Members speak about the loss; energy slowly returns; questions become more forward-looking.

Don’t confuse with

S2.4 Grief after a loss

Grief after loss of a person (death or departure) is more personal; fear after layoffs combines grief with insecurity.

S2.3Exhausted / burnout
Members are depleted; coaching feels like another demand
Make load visible; decide what to stop; protect energy
In the room

Yawns, slumped posture, cameras off. People arrive late from back-to-back meetings. Reactions are slow.

Members might say
  • Can we keep this short?
  • We’re running on empty.
  • I don’t have capacity for anything else.
What’s underneath

Burnout is a team and system issue, not only individual. Coaching that adds demands will fail. Reducing load is the intervention.

Questions to ask the team
  1. What is draining us most?
  2. What could we stop doing?
  3. What gives us energy?
  4. What would make the next month sustainable?
Avoid here

Asking for more commitments. Resilience lectures. Ignoring systemic causes.

Watch

Sometimes the best session is a shorter one with one clear decision to reduce load.

Examples from the field
Nursing team
Used the session to list all recurring tasks and stopped three.
Consulting team
Agreed a no-meeting day each week; burnout scores improved.
Sample exchange
Coach

Energy check, 1–10?

Member

Three.

Another member

Two.

Coach

Then let’s not add anything today. What could we take away?

Signs it’s working

The team agrees to stop something; energy lifts slightly.

Don’t confuse with

S1.6 Firefighting / crisis mode

Firefighting is the behaviour pattern; exhaustion is its emotional cost.

S2.4Grief after a loss
A colleague has died, left suddenly or been seriously ill
Pause the agenda; create space to acknowledge the loss
In the room

Silence, tearfulness, avoidance. Some members want to “get on with work”; others can’t.

Members might say
  • It doesn’t feel right to carry on as normal.
  • She held this team together.
  • I don’t know what to say.
What’s underneath

Teams grieve collectively. Unacknowledged grief shows up as irritability, withdrawal or loss of purpose. People grieve differently; the team needs room for differences.

Questions to ask the team
  1. How are we doing with what has happened?
  2. What do we want to remember?
  3. What do we each need?
  4. How do we want to honour this?
Avoid here

Rushing to tasks. Forcing emotional sharing. Acting as a therapist.

Watch

Offer referrals (employee assistance programmes) if individuals are struggling.

Examples from the field
Research team
A colleague died. The session became a remembrance; the team decided to name a project after her.
Sales team
A popular leader left suddenly; the team used a timeline to process the change.
Sample exchange
Coach

I know we planned to discuss targets. Given what’s happened, what do you need today?

Member

I think we need to talk about Sam.

Coach

Let’s do that. Anyone who wants to share something about Sam, please do.

Signs it’s working

Members share stories; tension eases; some energy returns for work later.

Don’t confuse with

S2.2 Fear after layoffs or restructuring

Fear after layoffs includes job insecurity; grief here is about a person.

S2.5Anxiety about change
Upcoming change creates worry and speculation
Separate known from unknown; build a shared preferred future; manage polarities
In the room

Rumours, “what if” questions, catastrophising. Some members very vocal, others withdrawn.

Members might say
  • What if they outsource us?
  • Nobody is telling us anything.
  • I just want to know what’s happening.
What’s underneath

Uncertainty is harder than bad news. Anxiety often fills the vacuum with worst-case stories. Teams need to separate what they know, what they don’t, and what they can influence.

Questions to ask the team
  1. What do we know for sure?
  2. What are we guessing?
  3. What can we influence?
  4. What would a good outcome look like for us?
Avoid here

False reassurance. Spending the session on rumours. Dismissing anxiety.

Watch

Help the team plan how to get information, not just speculate.

Examples from the field
Finance shared services
Sorted rumours into known, unknown and influence. Sent questions to the sponsor. Anxiety dropped.
Product team
Built a preferred future for the new structure.
Sample exchange
Member

I heard they’re closing our office.

Coach

Let’s sort what we know from what we’ve heard. What do we know for sure?

Another member

Only that there’s a review.

Coach

And what can we do while we wait?

Signs it’s working

The team asks for information; plans contingencies; calmer tone.

Don’t confuse with

S8.9 Change fatigue

Change fatigue is exhaustion from too much change; anxiety here is about an upcoming change.

S2.6Collective cynicism
The team believes nothing will improve
Find exceptions; test assumptions; start very small
In the room

Sarcasm, shrugging, “seen it all before”. Ideas are dismissed quickly.

Members might say
  • It won’t make any difference.
  • Nothing ever changes here.
  • Management doesn’t care.
What’s underneath

Cynicism protects against disappointment. It often contains valid criticism. Shifting it requires evidence, not persuasion.

Questions to ask the team
  1. When did something change for the better here, even slightly?
  2. What’s the cynicism protecting?
  3. What small test would show us something?
  4. What’s in our control?
Avoid here

Arguing against the cynicism. Positivity pushing. Ignoring legitimate grievances.

Watch

Cynics need evidence. Design experiments that produce it quickly.

Examples from the field
Factory supervisors
Mapped immunity to change; assumption was “management will ignore us”. Tested it with one proposal — approved. Cynicism softened.
Teachers
Appreciative inquiry found successful past initiatives.
Sample exchange
Member

This won’t change anything.

Coach

You might be right. What would you need to see to think otherwise?

Member

One thing actually changing.

Coach

Then let’s pick something small enough to test this month.

Signs it’s working

Members engage in experiments; sarcasm lessens.

Don’t confuse with

S1.8 Cynical about coaching (“been here before”)

Cynicism about coaching is specific; collective cynicism is about everything.

S2.7Anger at the organisation
The team is angry about decisions made above
Acknowledge the anger; separate venting from influence; connect to the system
In the room

Raised voices, strong language, members agreeing loudly. Energy is high but directed outward.

Members might say
  • They just don’t care about us.
  • Another stupid decision from the top.
  • Why should we bother?
What’s underneath

Anger signals perceived injustice. It contains energy that can be redirected toward influence. But staying in anger creates a victim-persecutor dynamic.

Questions to ask the team
  1. What exactly makes us angry?
  2. What do we want them to understand?
  3. What can we influence?
  4. What would a creator do here?
Avoid here

Defending the organisation. Shutting down anger. Letting the whole session become venting.

Watch

Give anger space, then time-box it.

Examples from the field
Engineering team
Angry about a reorganisation. Ten minutes venting, then mapped what they could influence. Wrote a joint proposal.
Call centre
Drama triangle mapping helped them move from victim to creator.
Sample exchange
Member

They just decided without asking anyone!

Coach

You’re angry about not being consulted. What would you want them to understand?

Member

How it affects our customers.

Coach

Who could you tell, and how?

Signs it’s working

The team moves from blame to proposals.

Don’t confuse with

S1.11 Talks only about other teams

Talking only about other teams is a habit; anger here is a strong emotional reaction to specific decisions.

S2.8Overconfidence / euphoria
After success, the team feels invincible and ignores risks
Celebrate, then test with pre-mortem and outside views
In the room

High energy, jokes, quick agreement on ambitious plans. Risks are waved away.

Members might say
  • We’ve nailed it.
  • Nothing can stop us now.
  • Let’s just do it.
What’s underneath

Success can lead to overconfidence and groupthink. Teams under-examine their assumptions when they feel successful.

Questions to ask the team
  1. What could make this fail?
  2. What did we get lucky with?
  3. What would our critics say?
  4. What should we watch?
Avoid here

Killing the celebration. Lecturing about risk.

Watch

Celebrate first. Then pre-mortem.

Examples from the field
Startup
After funding, a pre-mortem revealed hiring risks. The team planned hiring carefully.
Sales team
After a record quarter, an outside-view exercise revealed market changes.
Sample exchange
Member

Next year we’ll double it.

Coach

That’s exciting. Let’s imagine it’s a year from now and it didn’t happen. What went wrong?

Another member

We hired too fast.

Coach

Good. What else?

Signs it’s working

Risks are discussed without killing the energy.

Don’t confuse with

S3.4 Groupthink

Groupthink is a conversational pattern; euphoria is an emotional state that can drive it.

S2.9Shame after a public failure
The team failed visibly and members feel embarrassed
Make learning safe; separate identity from event; review without blame
In the room

Avoidance of the topic, defensive explanations, self-criticism or blame.

Members might say
  • We let everyone down.
  • We don’t want to talk about it.
  • It was mostly X’s fault.
What’s underneath

Shame makes teams hide and defend. Learning requires turning shame into curiosity. Blame and withdrawal are both shame responses.

Questions to ask the team
  1. What happened?
  2. What did we learn?
  3. What would we do differently?
  4. What does this failure not say about us?
Avoid here

Rushing past the failure. Blaming. Over-reassuring.

Watch

Ask the leader to own their part first.

Examples from the field
Launch failure
After-action review with no blame; team found process gaps. Confidence recovered.
Audit finding
Externalized “Last Minute” as a problem; team designed early checks.
Sample exchange
Coach

Can we look at what happened, focused on learning not blame?

Member

It was a disaster.

Coach

What part of it do you want to understand better?

Another member

Why nobody raised concerns earlier.

Signs it’s working

The team talks about the failure openly and identifies learning.

Don’t confuse with

S9.5 Experiment fails and team gives up

An experiment failing is expected; a public failure carries shame.

S2.10Disengaged / going through the motions
Members show up physically but not mentally
Reconnect to purpose and to what each person cares about
In the room

Cameras off, multitasking, minimal participation, no questions.

Members might say
  • Whatever you think.
  • I don’t mind.
  • Can we finish early?
What’s underneath

Disengagement often means the work has lost meaning, or members feel unheard. It may also signal burnout or plans to leave.

Questions to ask the team
  1. What matters to you about this work?
  2. What would make this session useful?
  3. When did you last feel energised here?
  4. What has changed?
Avoid here

Lecturing about engagement. Assuming laziness.

Watch

Individual one-to-one conversations may reveal what group sessions can’t.

Examples from the field
Admin team
Purpose exploration revealed members felt invisible to stakeholders. Stakeholder feedback restored meaning.
Engineering team
Check-ins revealed several were job hunting; the leader addressed career paths.
Sample exchange
Coach

On a scale of 1–10, how much does this team’s work matter to you right now?

Member

Honestly, a four.

Coach

What would make it a five?

Signs it’s working

Members share what they care about; participation increases.

Don’t confuse with

S1.3 Polite, flat and “fine”

Pseudo-harmony is polite and smiling; disengagement is withdrawn.

S2.11Tension you could cut
Something unnamed is creating tension in the room
Name the tension neutrally; ask permission to explore
In the room

Short answers, avoidance of eye contact, stiff posture, long silences.

Members might say
  • Let’s just move on.
  • It’s fine.
  • (sigh)
What’s underneath

Tension often signals an undiscussable or recent incident. Ignoring it makes the session feel false.

Questions to ask the team
  1. I’m sensing some tension — is that right?
  2. What’s happening?
  3. What would help us talk about it?
  4. Should we address this now?
Avoid here

Ignoring it. Forcing it into the open.

Watch

Check privately with individuals if needed.

Examples from the field
Leadership team
Coach named the tension; a member shared that a decision had been made without them.
Project team
Tension was about a member’s promotion; the leader explained.
Sample exchange
Coach

I’m noticing it’s quiet and a bit tense. Am I reading that right?

Member

Yeah.

Coach

Is it something we should talk about here?

Another member

It’s about the budget decision.

Signs it’s working

The tension is named; the team relaxes or engages.

Don’t confuse with

S4.2 Covert conflict / passive aggression

Covert conflict is a pattern over time; tension here is an immediate atmosphere.

S3
Situation group · 12 situations

Patterns in the conversation

About this group

How the team talks is often the problem the team is trying to talk about. These situations describe recurring conversational patterns: dominant voices, silent members, the meeting after the meeting, groupthink, interruptions, factions, scapegoats, deflecting humour, endless loops, advice-giving and invisible remote members. The coach’s main tool is process observation: describing what is happening, neutrally, so the team can choose differently.

S3.1One or two voices dominate
A few members do most of the talking
Structure participation; make the pattern visible
In the room

Two people speak; others nod or look at phones. Ideas from quieter members are lost.

Members might say
  • Let me just add…
  • I think what we all believe is…
  • (others) I agree with what’s been said.
What’s underneath

Dominance may come from rank, extroversion, expertise or anxiety. Quieter members may feel unheard or unsafe. The team loses diverse input.

Questions to ask the team
  1. Who hasn’t spoken yet?
  2. What do others think?
  3. What would help everyone contribute?
  4. What do you notice about airtime?
Avoid here

Shaming dominant members. Calling on quiet members suddenly.

Watch

Structure (rounds, writing first) works better than exhortation.

Examples from the field
Strategy team
Coach shared airtime count; dominant members agreed to speak second.
Engineering team
Silent writing first, then rounds.
Sample exchange
Coach

Can I share something? In the last twenty minutes, two people have done most of the talking. What do we make of that?

Member

That’s usually how it is.

Coach

Shall we try a round for the next question?

Signs it’s working

More voices; dominant members ask others for views.

Don’t confuse with

S7.1 Leader dominates

Leader dominance has hierarchy behind it; here it may be peers.

S3.2Silent members
Some members rarely speak
Use structure and invitation; understand the silence
In the room

The same people silent each session. They may look engaged or withdrawn.

Members might say
  • I don’t have anything to add.
  • (in private) I don’t feel heard.
  • I agree with the others.
What’s underneath

Silence can mean thinking, disagreement, cultural norms, low safety, or disengagement. Don’t assume.

Questions to ask the team
  1. What would make it easier to share?
  2. Would writing first help?
  3. What’s on your mind?
  4. What are you noticing?
Avoid here

Putting people on the spot. Assuming silence means agreement.

Watch

Check privately what silence means.

Examples from the field
Multicultural team
Writing first and rounds increased contributions.
Introverted engineer
Asked to share in pairs first.
Sample exchange
Coach

Let’s write individually for two minutes, then hear from everyone.

Member (quiet)

I think we’re missing the customer view.

Coach

Thanks. Can we explore that?

Signs it’s working

Quiet members contribute; their ideas are built on.

Don’t confuse with

S10.11 Cameras off on video

Cameras off is a virtual phenomenon; silence can happen anywhere.

S3.3The meeting after the meeting
Real conversations happen outside sessions
Bring the corridor conversation into the room
In the room

Agreement in sessions, complaints afterwards. Decisions are undermined.

Members might say
  • I didn’t want to say it in the meeting.
  • You know what people really think.
  • We all agreed, but…
What’s underneath

The team lacks safety or norms for disagreement in the room. Outside conversations carry the real content.

Questions to ask the team
  1. What would people say in the corridor?
  2. What do we discuss outside that we should discuss here?
  3. What would help us say it here?
Avoid here

Accusing people of gossip. Ignoring the pattern.

Watch

Make it safe to bring the corridor in.

Examples from the field
Executive team
Anonymous cards captured corridor talk. Real issues surfaced.
Project team
Agreed a norm: “If you’d say it outside, say it here.”
Sample exchange
Coach

What will people say about this meeting on the way out?

Member

(laugh) That we didn’t really decide.

Coach

Let’s talk about that here.

Signs it’s working

Fewer surprises after sessions; decisions stick.

Don’t confuse with

S4.2 Covert conflict / passive aggression

Covert conflict is passive aggression; the meeting after the meeting is a communication pattern.

S3.4Groupthink
The team agrees quickly; dissent is absent
Legitimise dissent; use pre-mortems and red teams
In the room

Fast agreement, nodding, nobody challenges. Ideas aren’t tested.

Members might say
  • Great, we all agree.
  • That’s obviously the right decision.
  • Let’s not overthink it.
What’s underneath

Groupthink (Irving Janis) happens with high cohesion and pressure for consensus. The team avoids conflict and misses risks.

Questions to ask the team
  1. What’s the strongest argument against this?
  2. What would our critics say?
  3. What could go wrong?
  4. Who has a different view?
Avoid here

Accepting quick agreement. Appointing the same devil’s advocate.

Watch

Rotate devil’s advocate roles.

Examples from the field
Board
A pre-mortem revealed concerns about an acquisition.
Product team
Red teams improved decisions.
Sample exchange
Member

Everyone agrees, let’s move on.

Coach

Before we do, let’s spend five minutes on why this could fail.

Another member

Actually, I’m worried about the timing.

Signs it’s working

Concerns are raised and addressed.

Don’t confuse with

S9.2 Agreeing too easily

Agreeing too easily on actions vs groupthink on decisions — similar but groupthink concerns the quality of decisions.

S3.5Interrupting and talking over
Members cut each other off
Use agreements and process observation
In the room

Overlapping voices, raised volume, unfinished sentences.

Members might say
  • Sorry, can I just…
  • Let me finish!
  • Yes, but…
What’s underneath

Interrupting may reflect enthusiasm, dominance, cultural norms or not listening. It reduces thinking quality.

Questions to ask the team
  1. What do you notice about how we’re talking?
  2. Would an agreement help?
  3. What happens when someone is interrupted?
Avoid here

Policing individuals. Ignoring it.

Watch

Use a talking object or round if needed.

Examples from the field
Sales team
Agreed to let people finish; the coach used a talking object.
Engineering team
Process observer counted interruptions.
Sample exchange
Coach

Can I pause? I counted six interruptions in five minutes. What’s happening?

Member

We get excited.

Coach

Shall we try finishing each other’s points first?

Signs it’s working

People finish sentences; listening improves.

Don’t confuse with

S3.1 One or two voices dominate

Dominance is about airtime; interrupting is about how airtime is taken.

S3.6Subgroups and factions
The team splits into camps
Make the factions visible; explore their positions and needs
In the room

Members sit together by camp; alliances in voting; side glances.

Members might say
  • We think… (meaning our camp)
  • They always side together.
  • It’s us versus them.
What’s underneath

Factions form around location, function, history or values. They may be protecting legitimate interests.

Questions to ask the team
  1. What groups do we have here?
  2. What does each group care about?
  3. What do we share?
  4. What would bridge?
Avoid here

Taking sides. Ignoring factions.

Watch

Spatial mapping can make factions visible safely.

Examples from the field
Global team
Sculpting revealed a split between HQ and regions.
Product team
Polarity map honoured both camps.
Sample exchange
Coach

Let’s stand according to which approach you favour.

Coach

(two groups form) What do you notice?

Member

We’re split down the middle.

Signs it’s working

Members talk across groups; shared interests emerge.

Don’t confuse with

S1.10 Merged team (“us and them”)

Merged teams have historic camps; factions can form anywhere.

S3.7A scapegoat
One person carries blame for team problems
Externalize the problem; explore the team pattern
In the room

Members look at one person when problems arise; jokes at their expense.

Members might say
  • That’s typical of him.
  • If she weren’t here…
  • We all know who caused this.
What’s underneath

Scapegoating protects the team from looking at itself. The scapegoat often carries something the team avoids.

Questions to ask the team
  1. What would happen if this person left?
  2. What does the team gain?
  3. What is the team’s part?
  4. What’s the problem, separate from the person?
Avoid here

Group attacks. Ignoring the scapegoat’s hurt.

Watch

Protect the individual.

Examples from the field
Project team
Externalizing “the delay monster” shifted blame.
Leadership team
Drama triangle showed the team as persecutors.
Sample exchange
Member

It’s always Tom’s fault.

Coach

Let’s look at the pattern rather than Tom. What happens before the delays?

Another member

We give him late inputs.

Signs it’s working

The team takes shared responsibility.

Don’t confuse with

S1.4 Wants the coach to fix one person

Wanting the coach to fix one person is a request at contracting; scapegoating is an ongoing team pattern.

S3.8Joking to deflect
Humour shuts down serious discussion
Notice the pattern lightly; invite what’s under the joke
In the room

Laughs at key moments; tension released before issues are explored.

Members might say
  • (joke)
  • Let’s not get too deep.
  • We’re just having fun.
What’s underneath

Humour is a healthy team resource, but also a defence. Jokes at critical moments avoid discomfort.

Questions to ask the team
  1. What’s under that joke?
  2. What happens if we don’t laugh this off?
  3. What are we avoiding?
Avoid here

Banning humour. Shaming jokers.

Watch

Appreciate humour while naming its function.

Examples from the field
Sales team
Coach noted jokes appeared whenever targets were discussed; the team talked about pressure.
IT team
A joker became the team’s “tension detector”.
Sample exchange
Member

(joke)

Coach

That’s funny — and I notice we laugh every time this comes up. What’s under it?

Member

Honestly, we’re worried.

Signs it’s working

The team stays with difficult topics longer.

Don’t confuse with

S1.3 Polite, flat and “fine”

Pseudo-harmony is general politeness; joking is a specific deflection.

S3.9The same debate on loop
The team repeats the same argument without resolution
Map the pattern or polarity; change the structure of the conversation
In the room

Familiar arguments, same people, same positions. Frustration and fatigue.

Members might say
  • We’ve been here before.
  • Same old debate.
  • We never resolve this.
What’s underneath

Repeated debates often indicate a polarity (both sides needed), a missing decision process, or a pattern of conversational moves.

Questions to ask the team
  1. How many times have we had this debate?
  2. Is this a problem to solve or a tension to manage?
  3. What would end it?
  4. What move is missing?
Avoid here

Joining the debate. Forcing a decision.

Watch

Name the loop as a pattern.

Examples from the field
Product team
Speed vs quality polarity map ended a year-long debate.
Leadership team
Decision rights clarified who decides.
Sample exchange
Coach

This sounds like a debate you’ve had before.

Member

Every month.

Coach

Let’s map both sides and see what each is protecting.

Signs it’s working

The team moves from debate to joint management.

Don’t confuse with

S6.3 Decisions don’t stick

Decisions not sticking is about authority; the loop here is about the debate itself.

S3.10Advice-giving instead of thinking
Members jump to solutions for each other
Slow down; ask questions; use structured thinking
In the room

Someone shares a problem; others immediately suggest fixes.

Members might say
  • Have you tried…?
  • What you need to do is…
  • Easy — just…
What’s underneath

Advice-giving is quick and well-meant but can block thinking and ownership.

Questions to ask the team
  1. What questions could we ask before giving advice?
  2. What does the person need?
  3. What happens when we jump to solutions?
Avoid here

Lecturing about coaching. Shutting down all suggestions.

Watch

Model questions.

Examples from the field
Leadership team
Practised “questions only” rounds; quality of thinking improved.
Peer triads
Learned coaching skills.
Sample exchange
Member

Just escalate it!

Coach

Before we suggest solutions, what questions might help her think?

Another member

What have you tried already?

Signs it’s working

More questions; problem owners think more deeply.

Don’t confuse with

S10.3 Coach pulled into expert role

Coach pulled into expert role is about the coach; advice-giving is among members.

S3.11Remote members invisible
Hybrid meetings favour those in the room
Agree hybrid norms; equalise participation
In the room

In-room members talk to each other; remote members struggle to join; side conversations.

Members might say
  • Sorry, we couldn’t hear.
  • Can the people online go next?
  • I feel left out on the call.
What’s underneath

Hybrid meetings create unequal access. Remote members lose influence and belonging.

Questions to ask the team
  1. What’s it like to join remotely?
  2. What would make it fairer?
  3. What norms do we need?
Avoid here

Treating remote members as an afterthought.

Watch

“One remote, all remote” is a powerful norm.

Examples from the field
Global team
Everyone joined from laptops; remote members spoke more.
Project team
Remote members went first in rounds.
Sample exchange
Coach

Let’s hear from those online first.

Member (remote)

Thanks — I’ve been trying to get in for a while.

Signs it’s working

Remote participation increases; inclusion improves.

Don’t confuse with

S8.2 Hybrid friction

Hybrid friction is broader; this is about participation in sessions.

S3.12Innovation or creative stuckness
The team needs new ideas but keeps producing variations of old ones
Change the quality of attention: sense the system freshly, include every voice, then prototype small
In the room

Brainstorms produce the usual suspects. Ideas are judged within seconds. Energy is dutiful. Members say “we tried that” more than “what if”.

Members might say
  • We’ve looked at every option.
  • Honestly, there’s nothing new under the sun here.
  • Let’s just go with what worked last time.
What’s underneath

Creative stuckness is rarely a lack of talent. It usually comes from downloading old patterns, premature judgment, fear of looking foolish, or being too far from the people who experience the problem. It is different from conflict or groupthink: the team agrees — on the old answer.

Questions to ask the team
  1. What would we see if we spent a day where the problem actually lives?
  2. What would guarantee that we never come up with anything new?
  3. What would we try if it only had to work for two weeks?
  4. Whose perspective have we not heard yet?
Avoid here

Another open brainstorm with the same people and the same format. Judging ideas as they emerge. Asking for “blue-sky” ideas without contact with reality.

Watch

Separate generating from judging, and include the quiet and the new. The best idea often comes from the least senior person.

Examples from the field
Retail product team
Three brainstorms produced nothing new. A half-day sensing journey in stores revealed staff workarounds that became the new product idea.
Policy team
TRIZ (“how could we make sure nothing changes?”) made the team laugh — and spot four habits killing ideas. They paused two of them.
Sample exchange
Member

We’ve brainstormed this to death.

Coach

What would guarantee we never have a new idea?

Another member

(laughs) Have the same five people in the same room judging everything immediately.

Coach

How many of those are we doing?

Member

All of them.

Coach

So what could we change today?

Signs it’s working

Unusual ideas appear; people build on each other’s ideas; the team agrees a small prototype rather than a big plan.

Don’t confuse with

S3.4 Groupthink

Groupthink suppresses dissent about a decision; creative stuckness is a lack of new options, even when the team welcomes them.

S4
Situation group · 11 situations

Conflict and trust

About this group

Conflict is not the enemy of teams; avoided, personalised or covert conflict is. This group covers open hostility, passive aggression, avoidance, escalation into the personal, breaches of trust, old history, cultural misreadings, venting about absent colleagues, war between teams and — at the edge of coaching — disclosures that require formal processes. Each card helps you decide whether the conflict belongs in the team session, in a separate conversation or in another process altogether.

S4.1Open hostility between two members
Two members clash openly; the team watches
Slow down; separate positions from needs; negotiate specific agreements
In the room

Sharp tone, sarcasm, raised voices between two people. Others go quiet or take sides.

Members might say
  • That’s exactly the problem with your approach.
  • You never listen.
  • Here we go again.
What’s underneath

Open conflict between two members affects the whole team. It may involve real differences in role, values or interests, plus personal history. The team often colludes by avoiding it.

Questions to ask the team
  1. What does each of you need from the other?
  2. How does this affect the team?
  3. What would a workable agreement look like?
  4. What does the team need from you both?
Avoid here

Mediating a personal dispute in public without consent. Taking sides. Letting it escalate.

Watch

Some conflicts need a separate facilitated conversation outside the team session.

Examples from the field
Sales and delivery heads
Role negotiation produced three specific agreements; hostility fell.
Two senior engineers
Coach suggested a separate conversation; they returned with a joint proposal.
Sample exchange
Member

You always change the scope at the last minute!

Another member

Because you never ask what the client needs!

Coach

Can I pause? I hear strong feelings on both sides. What does each of you need from the other to do your job?

Member

Earlier warning.

Another member

Earlier involvement.

Coach

Those sound connected.

Signs it’s working

Members talk about needs, not blame; specific agreements emerge.

Don’t confuse with

S4.4 Disagreement turns personal

Disagreement turning personal is an escalation of a task disagreement; open hostility is an existing relationship conflict.

S4.2Covert conflict / passive aggression
Conflict shows up as sarcasm, delays, missed deadlines
Name the pattern; make it discussable; explore underlying conflict
In the room

Polite words, sharp undertones. “Forgotten” tasks. Eye-rolls.

Members might say
  • As I already mentioned…
  • I’m sure you’re very busy.
  • Fine, whatever you want.
What’s underneath

Passive aggression occurs when open conflict feels unsafe. The conflict leaks out indirectly.

Questions to ask the team
  1. What’s not being said?
  2. What would happen if we disagreed openly?
  3. What’s the real disagreement?
  4. What would make open conflict safer?
Avoid here

Accusing individuals. Ignoring the pattern.

Watch

Covert conflict needs safety more than confrontation.

Examples from the field
Marketing team
Left-hand column revealed unspoken criticism; the team discussed it openly.
Operations team
Ladder of inference showed mutual misreadings.
Sample exchange
Coach

I notice there’s a lot of “as I said before” today. What’s going on?

Member

I feel like I’m not being heard.

Coach

Can you say more?

Signs it’s working

Indirect comments become direct statements.

Don’t confuse with

S2.11 Tension you could cut

Tension in the room is an atmosphere; covert conflict is a recurring behaviour pattern.

S4.3Conflict avoided at all costs
The team avoids any disagreement
Build safety and structures for productive conflict
In the room

Quick agreement, topic changes when tension rises, “let’s take it offline”.

Members might say
  • Let’s not go there.
  • We don’t want to upset anyone.
  • It’s not worth the fight.
What’s underneath

Conflict avoidance protects relationships short term and damages decisions long term. Lencioni calls it fear of conflict.

Questions to ask the team
  1. What disagreements are we avoiding?
  2. What’s the cost of avoiding them?
  3. What would make disagreement safer?
  4. When did disagreement help us?
Avoid here

Forcing conflict before safety. Calling the team weak.

Watch

Introduce conflict through structured roles (red team, devil’s advocate).

Examples from the field
Charity board
Red team exercise surfaced concerns about a project.
Admin team
Conflict norms helped members disagree.
Sample exchange
Coach

What’s one thing we disagree about that we never discuss?

Member

Probably budget allocation.

Coach

What makes it hard to discuss?

Signs it’s working

Members disagree openly and the relationship survives.

Don’t confuse with

S3.4 Groupthink

Groupthink is about decision quality under cohesion; conflict avoidance is about fear of interpersonal friction.

S4.4Disagreement turns personal
A task disagreement becomes an attack on a person
Pause; separate the idea from the person; restore norms
In the room

Tone sharpens, “you” statements, references to character.

Members might say
  • That’s typical of you.
  • You don’t understand the business.
  • You always do this.
What’s underneath

Task conflict turns into relationship conflict when people feel threatened or disrespected.

Questions to ask the team
  1. What’s the disagreement about the idea?
  2. What did you hear as personal?
  3. What agreement do we need?
Avoid here

Ignoring personal attacks.

Watch

Name it immediately but neutrally.

Examples from the field
Strategy team
Coach paused and reminded the team of its agreement; members rephrased.
Finance team
Steelmanning helped return to the idea.
Sample exchange
Member

You clearly don’t understand finance.

Coach

Let’s pause. I want to separate the idea from the person. What’s the concern about the proposal?

Member

The costs are underestimated.

Signs it’s working

Language returns to ideas.

Don’t confuse with

S4.1 Open hostility between two members

Open hostility is ongoing; this is a moment of escalation.

S4.5Trust breach / leak
Something said in confidence was shared outside
Revisit agreements; repair; rebuild confidentiality
In the room

Shock, anger, suspicion. Members are careful and silent.

Members might say
  • I can’t believe that got out.
  • How can we trust anyone?
  • I’m not saying anything else here.
What’s underneath

A leak damages the safety of the whole team. Without repair, members will withdraw.

Questions to ask the team
  1. What happened?
  2. How has it affected us?
  3. What do we need to rebuild trust?
  4. What agreement do we need now?
Avoid here

Witch hunts. Ignoring the breach.

Watch

The coach must model confidentiality strictly.

Examples from the field
Leadership team
Revisited confidentiality agreements; the person responsible apologised.
Project team
Agreed what can and can’t be shared.
Sample exchange
Member

Something I said here got back to my boss.

Coach

That’s serious. Let’s stop and look at our agreements. What do we need to make this space safe again?

Signs it’s working

Agreements are renewed; trust slowly returns.

Don’t confuse with

S10.12 Interview data tempting to use

Coach temptation to use interview data is about the coach’s confidentiality; this is a member breach.

S4.6Old history resurfaces
Past conflicts shape current interactions
Map the history; acknowledge; decide what to carry forward
In the room

References to “last time”, “remember when”. Tension when certain topics come up.

Members might say
  • This is just like 2019.
  • We tried that and it blew up.
  • You did the same thing last year.
What’s underneath

Unresolved history continues to influence the present. Teams need to acknowledge it before moving on.

Questions to ask the team
  1. What happened then?
  2. How does it affect us now?
  3. What did we learn?
  4. What do we want to leave behind?
Avoid here

Re-fighting the past. Dismissing it.

Watch

Focus on learning, not blame.

Examples from the field
Marketing team
Timeline revealed an old conflict; acknowledgement allowed a fresh start.
Engineering
A past failure explained risk aversion.
Sample exchange
Member

We tried that before and it was a disaster.

Coach

What happened?

Member

The project failed and two people left.

Coach

What do we want to learn from that?

Signs it’s working

The past is discussed without blame; the team decides how to move forward.

Don’t confuse with

S1.10 Merged team (“us and them”)

Merged teams carry two histories; here one team carries its own past.

S4.7Cross-cultural misunderstanding
Different cultural norms lead to misinterpretations
Explore cultural assumptions; build shared norms
In the room

Confusion, frustration, members feeling disrespected without knowing why.

Members might say
  • He was so rude in that email.
  • She never gives her opinion.
  • They’re too direct.
What’s underneath

Cultures differ in directness, hierarchy, time and conflict. Behaviours are often misread through one’s own cultural lens.

Questions to ask the team
  1. What norms do we each bring?
  2. How do we interpret directness?
  3. What would help us understand each other?
  4. What shared norms do we need?
Avoid here

Stereotyping. Ignoring culture.

Watch

Treat cultural differences as resources.

Examples from the field
Global team
User manuals revealed different norms; the team created communication guidelines.
Indian–German team
Discussed directness; agreed norms.
Sample exchange
Member

He was really rude in that email.

Coach

Let’s walk down the ladder of inference. What exactly did he write?

Member

Just “Do this by Friday.”

Coach

What could that mean in his context?

Signs it’s working

Members ask before assuming; norms are agreed.

Don’t confuse with

S8.3 Multicultural team

A multicultural team context is broader; this is a specific misunderstanding.

S4.8Venting about an absent colleague
The team criticises someone who isn’t present
Refer to agreements; refocus on the team’s part
In the room

Stories about the absent person; agreement; laughter.

Members might say
  • You know what she’s like.
  • He’s not here, so we can say it.
  • If only he’d…
What’s underneath

Venting can release frustration but undermines trust: members wonder what is said about them when they are absent.

Questions to ask the team
  1. How would we feel if this were said about us?
  2. What do we need from this person?
  3. What’s our part?
  4. How could we talk to them directly?
Avoid here

Joining. Shaming.

Watch

Agreement about absent members protects everyone.

Examples from the field
Sales team
Agreed not to discuss absent members without them.
Project team
Converted complaints into requests.
Sample exchange
Member

Sarah never delivers on time.

Coach

Sarah isn’t here. What would we want her to know, and how could we tell her directly?

Signs it’s working

Complaints become requests.

Don’t confuse with

S3.7 A scapegoat

A scapegoat can be present; venting is about the absent.

S4.9Silo war with another team
Conflict between this team and another
Zoom to the ecosystem; negotiate the interface
In the room

Strong language about the other team; history of disputes.

Members might say
  • They never support us.
  • It’s a war with procurement.
  • They don’t care about our customers.
What’s underneath

Interteam conflicts often reflect structural issues, competing goals or poor interfaces. Each team sees itself as the victim.

Questions to ask the team
  1. How does the other team see us?
  2. What do they need from us?
  3. What do we need from them?
  4. What’s our shared goal?
Avoid here

Joining blame. Ignoring structural causes.

Watch

Bring both teams together if possible.

Examples from the field
Sales and operations
Joint role negotiation produced handoff agreements.
HR and finance
Empty chair work led to a joint workshop.
Sample exchange
Member

Procurement blocks everything.

Coach

Let’s sit someone in procurement’s chair. What would they say?

Another member

“You ask too late and change your mind.”

Signs it’s working

The team identifies its part and proposes joint action.

Don’t confuse with

S1.11 Talks only about other teams

Talking about other teams is a habit; a silo war is an active conflict.

S4.10Disclosure of bullying or harassment in session
A member raises a serious allegation in the room
Pause; protect the individual; follow ethical and organisational procedures
In the room

Shock, silence, discomfort. The person may be upset.

Members might say
  • I’ve been treated badly by someone in this team.
  • This has been going on for months.
  • I can’t keep quiet anymore.
What’s underneath

Allegations of bullying or harassment are not team coaching topics; they require formal processes. The coach’s duty is to the person’s safety and the organisation’s procedures.

Questions to ask the team
  1. (privately) What do you need right now?
  2. Are you safe?
  3. Do you know the support available?
  4. What would you like to happen next?
Avoid here

Investigating in the room. Dismissing. Promising confidentiality you can’t keep.

Watch

Know the organisation’s procedures and your contract’s safeguarding clauses.

Examples from the field
Hospital team
Coach paused the session, spoke to the member privately, and supported a referral to HR.
Startup
Coach informed the sponsor per contract after discussing with the member.
Sample exchange
Member

I need to say something. I’ve been bullied.

Coach

Thank you for telling us. This is important and needs proper support. Can we take a break, and I’ll talk with you privately about what you need?

Signs it’s working

The person feels supported; appropriate processes are followed.

Don’t confuse with

S10.7 Member discloses personal crisis

A personal crisis disclosure (e.g. illness) is different from an allegation about a team member.

S4.11The team that is “too nice”
Warm relationships, low challenge — and quietly declining performance
Name the cost of harmony; make challenge a form of care
In the room

Lots of appreciation, few questions. Problems are softened into “small things”. Underperformance is worked around rather than discussed. People leave meetings smiling and nothing changes.

Members might say
  • We really like each other here.
  • I didn’t want to upset her.
  • It’s not a big deal — I’ll just fix it myself.
What’s underneath

Excessive harmony is a comfort zone (high safety, low standards). It protects relationships at the cost of results — and, over time, of the relationships themselves, because unspoken frustration builds. The team often has a shared value (“we’re caring”) that has become a shadow: directness is not allowed.

Questions to ask the team
  1. What does our niceness protect us from?
  2. What is it costing us — in results, in fairness, in workload?
  3. What would caring and direct look like together?
  4. What is one thing we’ve all noticed but never said?
Avoid here

Shaming the team for being kind. Jumping straight to hard-hitting feedback. Treating it only as conflict avoidance — the performance cost must be visible.

Watch

Frame challenge as care: “We tell each other the truth because we want each other to succeed.”

Examples from the field
Charity leadership team
Scored very high on safety, low on accountability. The coach showed the learning-zone model; members placed themselves in the comfort zone. They agreed “kind and clear” norms.
Design team
Two members silently redid a colleague’s work for months. Collective shadow work revealed that directness was “not who we are”. They added a weekly feedforward round.
Sample exchange
Coach

You score very high on trust. What would you say about challenge?

Member

Hmm. We don’t really do that.

Another member

Honestly, I redo some work rather than say anything.

Coach

What does that cost you — and the colleague?

Another member

Time. And they never learn.

Coach

What would caring and clear look like?

Signs it’s working

Members raise issues earlier; performance conversations happen; warmth survives the honesty.

Don’t confuse with

S4.3 Conflict avoided at all costs

Conflict avoidance is fear-driven; “too nice” is comfort-driven, often in teams that feel very safe.

S5
Situation group · 10 situations

Purpose, goals and direction

About this group

Teams without shared purpose fall back on individual goals and politics. These situations describe missing purpose, competing priorities, imposed goals, unclear strategy, incentive conflicts, different definitions of success, short-termism, drift after success and clashes between purpose and values. The general move is outward and forward: who does this team serve, and what future would make the work worth it?

S5.1No shared purpose
Members can’t say why the team exists
Explore stakeholders and purpose; create a shared statement
In the room

Different answers to “what is this team for?” Confusion and some embarrassment.

Members might say
  • We’ve never really talked about that.
  • Isn’t it obvious?
  • Each of us has our own job.
What’s underneath

Without purpose, members default to individual goals and politics.

Questions to ask the team
  1. Why does this team exist?
  2. Who depends on us?
  3. What can only we do?
  4. What would be lost without us?
Avoid here

Writing the purpose for the team.

Watch

Purpose should help the team say no.

Examples from the field
IT leadership
Stakeholder interviews clarified purpose.
HR team
One-sentence purposes compared.
Sample exchange
Coach

Each of you, write the team’s purpose in one sentence.

Coach

(read aloud) Seven different answers. What do we notice?

Signs it’s working

The team agrees a purpose and uses it in decisions.

Don’t confuse with

S5.4 Strategy unclear

Unclear strategy is about direction; no shared purpose is about reason for existing.

S5.2Competing priorities
Members pull in different directions
Make priorities visible; decide together; manage polarities
In the room

Arguments about what matters most; members defend their areas.

Members might say
  • My project is critical.
  • We can’t do everything.
  • Everything is a priority.
What’s underneath

Competing priorities often reflect unclear strategy or misaligned incentives.

Questions to ask the team
  1. What are all our priorities?
  2. What matters most to our stakeholders?
  3. What can we stop?
  4. What trade-offs are we willing to make?
Avoid here

Deciding for the team.

Watch

Involve the sponsor if priorities conflict with mandates.

Examples from the field
Product team
Portfolio wall led to stopping two projects.
Marketing
Polarity of brand vs sales managed.
Sample exchange
Member

My project is the top priority.

Another member

So is mine.

Coach

Let’s put all priorities on the wall and look at them against our purpose.

Signs it’s working

The team agrees a ranked list.

Don’t confuse with

S5.7 Short-termism / always urgent

Short-termism is about time horizon; competing priorities is about choice.

S5.3Goals imposed from above
Targets set without team input; low ownership
Explore what the team can own; test assumptions; connect to stakeholders
In the room

Frustration, cynicism, low commitment.

Members might say
  • These targets are unrealistic.
  • Nobody asked us.
  • We’ll do what we can.
What’s underneath

Imposed goals reduce autonomy and motivation. The team may resist or comply without commitment.

Questions to ask the team
  1. What part of these goals do we believe in?
  2. What would make them achievable?
  3. What can we influence?
  4. What would we tell the people who set them?
Avoid here

Defending the targets.

Watch

Help the team give feedback upward.

Examples from the field
Sales team
Team immunity map revealed assumption that pushing back was pointless; they tested it.
Hospital ward
Connected targets to patient outcomes.
Sample exchange
Member

These targets are ridiculous.

Coach

What would make them achievable?

Another member

More staff. Or fewer projects.

Coach

Who could you tell that to, and how?

Signs it’s working

The team finds ownership in part of the goals or influences them.

Don’t confuse with

S1.1 Sent by the sponsor

Being sent to coaching is about the engagement; imposed goals are about work targets.

S5.4Strategy unclear
The team doesn’t understand the organisation’s direction
Clarify what is known; connect to stakeholders; build preferred future
In the room

Questions, confusion, speculation.

Members might say
  • What is the strategy, anyway?
  • It changes every quarter.
  • We’re guessing.
What’s underneath

Unclear strategy makes team prioritisation hard. The team may need to seek clarity or create its own direction.

Questions to ask the team
  1. What do we know about the strategy?
  2. What do we need to know?
  3. Who can tell us?
  4. What direction can we set ourselves?
Avoid here

Inventing strategy for the organisation.

Watch

Encourage the team to seek clarity upward.

Examples from the field
Regional team
Invited the strategy director to a session.
Product team
Created its own preferred future aligned with what was known.
Sample exchange
Member

Nobody knows the strategy.

Coach

What do you know?

Another member

Growth in Asia. Cost control.

Coach

What does that mean for this team?

Signs it’s working

The team identifies what it knows and asks for the rest.

Don’t confuse with

S5.1 No shared purpose

No shared purpose is internal; unclear strategy is about the wider organisation.

S5.5Individual goals beat team goals
Incentives reward individuals; collaboration suffers
Clarify collective goals; manage the individual/team polarity
In the room

Members protect their own targets; reluctance to help others.

Members might say
  • My bonus depends on my numbers.
  • I don’t have time to help.
  • That’s not my target.
What’s underneath

Incentive structures shape behaviour. Teams can’t collaborate if every reward is individual.

Questions to ask the team
  1. What goals do we share?
  2. How do incentives affect us?
  3. What would make collaboration worth it?
  4. What can we change?
Avoid here

Lecturing about teamwork.

Watch

Raise structural issues with the sponsor.

Examples from the field
Sales team
Proposed a shared target component; the sponsor agreed.
Research team
Polarity map balanced individual and team excellence.
Sample exchange
Member

Helping others doesn’t pay.

Coach

What would need to change for collaboration to pay?

Another member

Some shared target.

Signs it’s working

Shared goals are agreed; incentives discussed.

Don’t confuse with

S1.7 A group, not a team

A group not a team may not need collective goals; here the team does but incentives work against them.

S5.6Disagree on what success means
Members use different definitions of success
Build a shared preferred future; use data
In the room

Arguments about outcomes; “we’re doing well” vs “we’re failing”.

Members might say
  • We hit our numbers.
  • Customers are unhappy.
  • Success is growth, not profit.
What’s underneath

Without a shared definition of success, teams pull in different directions.

Questions to ask the team
  1. What does success look like for each of you?
  2. What would stakeholders say?
  3. What measures matter most?
Avoid here

Choosing one definition.

Watch

Use stakeholder data.

Examples from the field
Software team
Defined success as reliable releases and customer satisfaction.
NGO
Combined impact and sustainability measures.
Sample exchange
Coach

What does success look like in a year?

Member

Revenue up.

Another member

Happy customers.

Coach

Can we have both? What would that look like?

Signs it’s working

A shared success picture emerges.

Don’t confuse with

S5.2 Competing priorities

Competing priorities are about where to focus; this is about outcomes.

S5.7Short-termism / always urgent
The team focuses only on immediate issues
Manage the short/long polarity; protect strategic time
In the room

Discussion of this week’s issues; no space for strategy.

Members might say
  • We don’t have time for long-term thinking.
  • Let’s get through this quarter.
  • Strategy is a luxury.
What’s underneath

Short-termism may reflect pressure, incentives or anxiety.

Questions to ask the team
  1. What will matter in a year?
  2. What are we neglecting?
  3. How can we protect time for the long term?
Avoid here

Ignoring real urgency.

Watch

Polarity map is useful.

Examples from the field
Retail team
Agreed a monthly strategy session.
Tech team
Polarity map of short and long term.
Sample exchange
Coach

If we keep focusing on this quarter, where will we be in a year?

Member

Probably in the same place.

Signs it’s working

Strategic time is scheduled and protected.

Don’t confuse with

S1.6 Firefighting / crisis mode

Firefighting is crisis mode; short-termism is a time-horizon habit.

S5.8Purpose drift after success
After achieving goals, the team loses direction
Revisit purpose; harvest learning; set new goals
In the room

Low energy, uncertainty, “what now?”

Members might say
  • We did it — now what?
  • It feels flat.
  • Our job is done.
What’s underneath

Achievement can create a vacuum. Teams need a new purpose or a renewed one.

Questions to ask the team
  1. What did we achieve?
  2. What did we learn?
  3. What’s next?
  4. What do stakeholders need now?
Avoid here

Rushing to new goals without reflection.

Watch

Celebrate first.

Examples from the field
Project team
Harvested learning and set a new purpose.
Startup
Revisited purpose after funding.
Sample exchange
Coach

You achieved the goal. What did you learn, and what’s next?

Member

I’m not sure what’s next.

Signs it’s working

New purpose and goals emerge.

Don’t confuse with

S2.10 Disengaged / going through the motions

Disengagement can come from many causes; this drift follows success.

S5.9Purpose conflicts with values
Members feel the team’s goals clash with their values
Hear the minority voice; explore values and purpose
In the room

Moral language, discomfort, some members withdraw.

Members might say
  • This doesn’t feel right.
  • We’re being asked to cut corners.
  • I didn’t sign up for this.
What’s underneath

Values conflicts are deep and can lead to disengagement or departure.

Questions to ask the team
  1. What values are at stake?
  2. What do we stand for?
  3. Who shares this concern?
  4. What can we do about it?
Avoid here

Dismissing concerns.

Watch

Ethical concerns may require escalation.

Examples from the field
Pharma team
Concern about marketing practices was escalated.
NGO
Values and purpose were reconnected.
Sample exchange
Member

This campaign doesn’t feel right to me.

Coach

Does anyone share any part of that concern?

Another member

I do.

Signs it’s working

Concerns are heard and addressed.

Don’t confuse with

S5.3 Goals imposed from above

Imposed goals are about ownership; this is about values.

S5.10A good team that wants to become great
No crisis, solid results — the team wants to raise its game
Start from strengths, find the next level of value for stakeholders, and stretch with small, ambitious experiments
In the room

Relaxed, confident, curious. Members are proud of results and a little bored. They ask, “What’s next for us?”

Members might say
  • We’re doing well, but we could be better.
  • We don’t want to get complacent.
  • What do the best teams do that we don’t?
What’s underneath

High-performing teams risk the comfort zone and the plateau. The challenge is not repair but stretch: more value for stakeholders, more learning, more distributed leadership. Problem-focused methods can feel wrong here; appreciative and future-focused methods fit better.

Questions to ask the team
  1. What are we at our best, and how could we do more of it?
  2. What do our stakeholders need next from us?
  3. What would a team twice as good as us do differently?
  4. Which of Hawkins’ five disciplines is our weakest?
Avoid here

Inventing problems so the coaching has something to fix. Generic team-building. Complacent celebration with no stretch.

Watch

Great teams often grow by connecting outward (stakeholders, the wider system) and by learning faster, not by improving relationships further.

Examples from the field
Finance leadership team
Strong internally, weak at “connecting”. Stakeholder interviews revealed an appetite for strategic advice. The team redefined its purpose and doubled its strategic work.
Engineering team
Used feedforward and a stretch goal; introduced peer coaching triads to grow leadership across the team.
Sample exchange
Leader

We’re in good shape — but I want us to be exceptional.

Coach

What would exceptional look like to your stakeholders?

Member

Probably being ahead of their needs, not reacting.

Coach

What would that take?

Another member

Talking to them more. And learning faster.

Coach

Which would you test first?

Signs it’s working

The team sets a stretch goal it owns; stakeholders notice new value; learning practices become routine.

Don’t confuse with

S5.8 Purpose drift after success

Purpose drift after success is losing direction; good-to-great is a team with direction looking for the next level.

S6
Situation group · 12 situations

Roles, decisions and accountability

About this group

Many “people problems” are structure problems in disguise. Role confusion, turf wars, decisions that don’t stick, escalation, consensus paralysis, free riding, unowned actions, meeting overload, dual reporting and failing handoffs are all about the design of the team’s work. The coach does not design the structure for the team; they help the team negotiate it explicitly instead of fighting about it implicitly.

S6.1Role confusion
Members are unsure who does what
Negotiate roles; clarify decision rights
In the room

Duplicate emails to the same client, tasks that nobody picks up, and repeated “I thought you had it.” Members are friendly but quietly frustrated.

Members might say
  • I thought you were doing it.
  • Is that my job?
  • We both did the same thing.
What’s underneath

Role confusion causes friction, waste and conflict that is often misread as personality clash. It usually appears after growth, restructuring or a change of leader, when old informal agreements no longer fit.

Questions to ask the team
  1. What does each role exist to deliver?
  2. Where do we overlap or double up?
  3. What falls between us?
  4. What do you need from each other at the handoffs?
Avoid here

Writing job descriptions for the team.

Watch

Focus on interfaces.

Examples from the field
New product team
Role negotiation revealed nobody owned customer onboarding; one member took it on and complaints dropped within a month.
Merged finance team
Mapping overlaps showed two people producing the same monthly report in different formats. They agreed one owner and one format.
Sample exchange
Member

I thought you were handling that client.

Another member

I thought you were!

Coach

That seems to happen a lot. Shall we map who does what, starting with the work that keeps falling between you?

Member

Yes — onboarding, renewals and escalations.

Coach

Let’s take them one at a time: who owns, who supports, who needs to know?

Signs it’s working

Clear agreements; fewer duplications.

Don’t confuse with

S6.2 Turf wars

Turf wars are about competition; role confusion is about clarity.

S6.2Turf wars
Members compete for territory and authority
Negotiate roles; zoom to the ecosystem; clarify decisions
In the room

Possessive language (“my clients”, “my project”), copying the boss on emails, defensive body language when another member’s name is mentioned.

Members might say
  • That’s my area.
  • Stay out of my project.
  • Who gave you authority?
What’s underneath

Turf wars usually reflect unclear roles, scarce resources or incentives that reward individual territory. They can also protect status and identity during uncertainty.

Questions to ask the team
  1. What is each of us protecting?
  2. What does the organisation need from this area?
  3. Where would sharing create more value?
  4. What agreement would make it safe to share?
Avoid here

Taking sides.

Watch

Address structural issues.

Examples from the field
Marketing and sales leads
Both claimed ownership of the key-account campaigns. Role negotiation produced a shared-ownership agreement with clear decision rights.
Two IT unit heads
Decision-rights mapping showed both were approving the same changes; they agreed one approver per category.
Sample exchange
Member

That’s my area — please stay out of it.

Coach

It sounds important to you. What would you be worried about if someone else were involved?

Member

Losing control of quality.

Another member

I only want to help with capacity.

Coach

So quality and capacity both matter. What agreement could protect both?

Signs it’s working

Collaboration replaces competition.

Don’t confuse with

S6.1 Role confusion

Role confusion is about clarity; turf wars are about competition.

S6.3Decisions don’t stick
Decisions are reopened repeatedly
Clarify decision rights; test real agreement; hear dissent
In the room

The same decision appears on the agenda again; people refer to “what we discussed” rather than “what we decided”; side remarks about not really agreeing.

Members might say
  • Didn’t we decide this already?
  • I never agreed.
  • Let’s revisit.
What’s underneath

Decisions don’t stick when it is unclear who had the authority to make them, or when disagreement was never voiced. Reopening is the minority’s delayed vote.

Questions to ask the team
  1. Who decides this kind of decision?
  2. How strongly did each of us actually support it?
  3. What reservations were not heard?
  4. What would make this decision stick?
Avoid here

Forcing commitment.

Watch

Use gradients of agreement.

Examples from the field
Leadership team
Gradients of agreement revealed that three members had only been at “can live with it”. Their concerns about timing were added and the decision held.
Product team
Started a simple decision log with owner, rationale and review date; reopening fell sharply.
Sample exchange
Member

Can we revisit the hiring decision from last month?

Coach

Before we do — how was it made, and who had the authority to make it?

Leader

I suppose we all agreed.

Another member

I didn’t really. I just didn’t say so.

Coach

That’s useful to know. What would have needed to happen for you to say so at the time?

Signs it’s working

Decisions are respected.

Don’t confuse with

S3.9 The same debate on loop

Loop debates are about arguments; this is about decisions.

S6.4Everything escalates to the leader
The team doesn’t decide without the leader
Clarify decision rights; coach the leader to step back
In the room

Members end discussions with “let’s ask Priya”; the leader’s calendar is overloaded; decisions wait for the leader’s return from travel.

Members might say
  • Let’s ask the boss.
  • She’ll decide anyway.
  • I don’t want to make the call.
What’s underneath

Escalation may reflect fear of getting it wrong, unclear authority, or a leader who unconsciously rewards dependence. Both the team and the leader are part of the pattern.

Questions to ask the team
  1. Which decisions could this team make without the leader?
  2. What stops us from deciding now?
  3. What does the leader need in order to let go?
  4. What would happen if we got one wrong?
Avoid here

Blaming the leader or the team.

Watch

Work with both.

Examples from the field
Operations team
The leader agreed spending thresholds below which the team decided alone. Response time to customers halved.
Startup team
Peer accountability pairs replaced daily check-ins with the founder.
Sample exchange
Member

Let’s wait for the leader to decide.

Coach

What would happen if this team decided?

Member

We might get it wrong.

Leader

Honestly, I’d trust you with this one.

Coach

What would help you make decisions like this without waiting — and how will we learn from any that go wrong?

Signs it’s working

The team makes decisions without escalation.

Don’t confuse with

S7.5 Team defers to leader

Team defers to leader is a general pattern; escalation is specifically about decisions.

S6.5Consensus paralysis
The team insists on consensus for everything
Choose decision styles; use gradients of agreement
In the room

Long discussions, polite rounds, no closure. Members leave meetings tired and unsure what was decided.

Members might say
  • We need everyone on board.
  • We can’t decide until everyone agrees.
  • Let’s discuss more.
What’s underneath

Consensus for everything slows teams down and often hides an unwillingness to accept a leader’s or colleague’s authority. It can also be a value (fairness) applied too widely.

Questions to ask the team
  1. What kind of decision is this?
  2. What level of agreement is enough?
  3. Who decides if we can’t agree?
  4. Which decisions truly need everyone?
Avoid here

Imposing decisions.

Watch

Agree decision styles in advance.

Examples from the field
NGO leadership team
Chose consensus only for strategy and values; consultation for operational decisions. Meeting time fell by a third.
School leaders
Used fist to five; a threshold of “no one below 2” let them move forward.
Sample exchange
Member

We need everyone on board before we decide.

Coach

For this decision, does it need full consensus, or would consultation then a clear decision work?

Another member

Honestly, consultation. It’s operational.

Coach

Who should decide, then?

Member

The operations lead, after hearing us all today.

Signs it’s working

Faster decisions.

Don’t confuse with

S6.3 Decisions don’t stick

Decisions not sticking is the opposite problem.

S6.6Free riders
Some members contribute less
Peer feedback; peer accountability; role negotiation
In the room

Sighs when some names come up, uneven workload, sarcasm about “some people’s priorities”. Hard-working members look tired and resentful.

Members might say
  • Some people aren’t pulling their weight.
  • Why should I do more?
  • Same people always do the work.
What’s underneath

Free riding affects fairness and motivation. It may reflect unclear roles, disengagement, overload elsewhere, or a lack of peer accountability norms. Assuming laziness is usually wrong.

Questions to ask the team
  1. How is the work actually distributed?
  2. What do we expect from each other?
  3. How will we raise it when a commitment slips?
  4. What might be getting in the way for people who seem to contribute less?
Avoid here

Public shaming.

Watch

Address with specific feedback.

Examples from the field
Project team
Role negotiation clarified expectations; one “free rider” turned out to be supporting another department two days a week.
Graduate cohort team
Peer accountability pairs reduced resentment and evened out contributions.
Sample exchange
Member

Some people aren’t doing their share.

Coach

What do we expect from each other, and how would we say it directly?

Another member

I’d rather we just said it.

Third member

I didn’t realise people felt that way — I’ve been pulled onto another project.

Coach

That’s important. What does the team need to agree about capacity?

Signs it’s working

Clearer expectations; fairer workload.

Don’t confuse with

S2.10 Disengaged / going through the motions

Disengagement can cause free riding.

S6.7Nobody owns actions
Actions are agreed but no one follows through
Named owners; experiments; peer accountability
In the room

Action lists full of “we”, actions repeated from last session, nobody quite sure who was meant to do what.

Members might say
  • We’ll look into it.
  • Someone should do that.
  • I thought you were.
What’s underneath

Collective ownership often becomes no ownership. Without a named person and a date, every member assumes someone else will act.

Questions to ask the team
  1. Who will own this?
  2. By when?
  3. How will we know it’s done?
  4. Who will support the owner?
Avoid here

Coach owning follow-up.

Watch

Names and dates.

Examples from the field
Leadership team
Introduced owner-and-buddy for every action; follow-through rose from about a third to most actions.
Project team
A visible tracker reviewed at the start of each meeting ended repeat actions.
Sample exchange
Coach

Who will own this?

Member

Well, all of us.

Coach

If all of us own it, who will notice first if it doesn’t happen?

Another member

Fair point. I’ll own it, by Friday.

Coach

And who will be your buddy?

Signs it’s working

Follow-through improves.

Don’t confuse with

S9.3 Action list too long

Too many actions is about volume; this is ownership.

S6.8Meeting overload
Too many meetings, too little value
Audit and redesign rhythms; stop doing
In the room

Members arrive late from back-to-back calls, laptops open, “this could have been an email” muttered. Calendars full from 8 to 6.

Members might say
  • We spend all day in meetings.
  • This could have been an email.
  • No time for real work.
What’s underneath

Meeting overload drains energy and reduces time for real work. Meetings often accumulate because nobody has authority or permission to stop them.

Questions to ask the team
  1. What meetings do we have?
  2. What is each one for?
  3. Which could we stop, shorten or merge?
  4. What would we do with the time?
Avoid here

Adding more meetings.

Watch

Start with one meeting.

Examples from the field
Leadership team
A meeting audit listed 22 hours a week of recurring meetings; they cut six hours per person.
Tech team
A no-meeting Wednesday became the most protected day of the week.
Sample exchange
Coach

Let’s list every recurring meeting and its purpose.

Member

The Monday update… I’m not sure what it’s for any more.

Another member

We could replace it with a written update.

Coach

Shall we try that for a month, and review?

Signs it’s working

Fewer, better meetings.

Don’t confuse with

S2.3 Exhausted / burnout

Burnout can result from meeting overload.

S6.9Matrix / dual reporting tension
Members serve two bosses; conflicting demands
Negotiate roles; manage polarities; map the system
In the room

Members hesitate before committing (“I need to check with my other boss”), conflicting deadlines, frustration about divided loyalties.

Members might say
  • My other boss wants something else.
  • I’m caught in the middle.
  • Which team do I belong to?
What’s underneath

Matrix structures create competing loyalties and conflicting priorities. Members can feel they belong nowhere and are judged by everyone.

Questions to ask the team
  1. What does each boss need?
  2. Where do their needs genuinely conflict?
  3. Who resolves conflicts between them?
  4. What agreement would help you serve both?
Avoid here

Choosing for the member.

Watch

Involve both leaders if possible.

Examples from the field
Global product team
Role negotiation with both functional and project leads produced a shared priority list.
Regional matrix team
Polarity map of global standards versus local responsiveness clarified when each would win.
Sample exchange
Member

My functional boss wants X, the project wants Y.

Coach

Let’s map what both need. What’s each of them trying to achieve?

Member

Quality for one, speed for the other.

Coach

Who could resolve the conflict when you can’t?

Member

Both of them, together — they’ve never actually talked about it.

Signs it’s working

Clear agreements.

Don’t confuse with

S6.2 Turf wars

Turf wars are between peers; this is about dual reporting.

S6.10Handoffs keep failing
Work stalls at interfaces
Role negotiation; AAR; interaction patterns
In the room

Complaints that work arrives late, incomplete or without context; blame bouncing between functions.

Members might say
  • We got it too late.
  • It was incomplete.
  • Nobody told us.
What’s underneath

Handoffs fail when expectations about timing, quality and information are not explicit. Each side sees only its own pressures.

Questions to ask the team
  1. What happens at the handoff today?
  2. What do you need to receive?
  3. What can you give in return?
  4. How will we know the handoff worked?
Avoid here

Blame.

Watch

Map the process.

Examples from the field
Sales–delivery handoff
Role negotiation produced a one-page handoff checklist; rework fell.
Product–engineering
An after-action review of a failed release showed design changes after handoff; they agreed a design freeze.
Sample exchange
Coach

Let’s look at the last handoff. What happened?

Member

We got the spec two days before launch.

Another member

We were still waiting for customer sign-off.

Coach

So both of you were waiting on someone. What would a good handoff look like?

Signs it’s working

Smoother handoffs.

Don’t confuse with

S6.1 Role confusion

Role confusion is broader.

S6.11A star performer or hero culture
One person carries critical work; others defer, or resent; the system depends on a hero
Make the pattern systemic rather than personal; spread capability and recognition
In the room

The star answers first and is thanked most. Others wait for them, or roll their eyes. The star works late and looks tired. The leader praises the star in public.

Members might say
  • Ask Priya, she’ll know.
  • Without him this whole thing falls apart.
  • I just get it done — it’s faster than explaining.
What’s underneath

Hero culture is co-created: the organisation rewards heroics, the hero gains identity and status, and others gain relief from responsibility. It creates fragility (key-person risk), burnout and unequal growth. The hero may also be carrying the team’s shadow — the competence or decisiveness others don’t own.

Questions to ask the team
  1. What would happen if Priya were away for a month?
  2. What does the team gain from having a hero — and what does it lose?
  3. What does the hero gain, and what does it cost them?
  4. How could we share what the hero knows?
Avoid here

Attacking or diminishing the star. Ignoring the burnout risk. Treating it as only the star’s behaviour.

Watch

Talk privately with the star first; they often want relief but fear losing status.

Examples from the field
Sales team
The top performer closed half the deals. The team redesigned key accounts into pairs; overall sales rose and the star worked fewer weekends.
IT operations
One engineer resolved every outage. The team ran action learning sets on outages and created runbooks; dependency fell.
Sample exchange
Coach

What happens when Ravi isn’t here?

Member

Things wait.

Another member

Or break.

Member (Ravi)

Honestly, I’m exhausted.

Coach

So the team relies on Ravi, and Ravi is paying for it. What would a different design look like?

Member

Pairs on the critical systems.

Signs it’s working

Knowledge is shared; the star’s load drops; others step up and are recognised.

Don’t confuse with

S6.6 Free riders

Free riding is people doing too little; hero culture is one person doing too much — often the same system seen from the other side.

S6.12Knowledge loss and key-person dependency
Critical knowledge lives in a few heads; departures cause crises
Make knowledge flow a team responsibility: map dependencies, pair, document and hand over by design
In the room

Anxious jokes about “if she wins the lottery”. Work stalls during holidays. New members take months to become productive. Old decisions can’t be explained.

Members might say
  • Only Sam knows how that works.
  • We lost all of that when Ana left.
  • Nobody wrote it down.
What’s underneath

Key-person dependency is a systemic risk, not an individual failing. It grows when the team is overloaded, when expertise is rewarded more than sharing, and when membership changes often. It links to fluid teaming and hero culture.

Questions to ask the team
  1. Whose absence would hurt us most next month?
  2. What knowledge would leave with them?
  3. How do newcomers learn how things really work here?
  4. What would make sharing knowledge part of the job, not extra?
Avoid here

Asking experts to “document everything” on top of their work. Blaming those who leave. Treating it as an IT problem only.

Watch

Make knowledge-sharing visible and valued, or people protect expertise as security.

Examples from the field
Engineering team
Built a dependency map; three critical systems had one expert. Pairing rotations and a monthly “teach-back” cut the risk in a quarter.
Consulting team
Created a leaving ritual with structured hand-over; client continuity improved.
Sample exchange
Coach

Whose absence would hurt us most?

Member

Sam’s.

Member (Sam)

And I can’t take a holiday because of it.

Coach

What would it take for two more people to know what Sam knows?

Another member

Pairing on the next release.

Coach

Shall we try that, and review in a month?

Signs it’s working

Fewer single points of failure; smoother holidays and departures; newcomers productive faster.

Don’t confuse with

S8.5 Key member leaving

A key member leaving is an event; key-person dependency is the underlying system risk, present before anyone leaves.

S7
Situation group · 11 situations

The leader and the team

About this group

The leader is both a member of the team-as-client and the person with authority over it. That dual position shapes almost every session. These situations cover dominant, absent, allying, new, deferred-to, defensive, information-seeking, unnamed, departing and over-egalitarian leaders. The coach’s task is to make the leader’s influence visible and discussable without colluding with them or protecting the team from them.

S7.1Leader dominates
The leader talks most; the team defers
Contract leader role; structure participation; observe
In the room

The leader speaks first and longest. Members nod, glance at the leader before answering, and rarely contradict.

Members might say
  • As I said…
  • What does the boss think?
  • I agree with Anna.
What’s underneath

Leader dominance limits team thinking, even when the leader wants input. Members read status signals and edit themselves.

Questions to ask the team
  1. What happens when the leader speaks first?
  2. What would change if the leader spoke last?
  3. How does the team want to use the leader’s view?
  4. What would you say if the leader’s opinion were not yet known?
Avoid here

Undermining the leader publicly.

Watch

Agree speak-last in advance.

Examples from the field
CEO team
The CEO agreed to speak last; debate quality rose noticeably within two sessions.
Startup founders
The coach shared an airtime count; the founder laughed and asked a colleague to time-keep him.
Sample exchange
Coach

Let’s hear from the team first, then Anna.

Leader

Sure — I’ll hold back.

Member

Then… I think the timeline is too ambitious.

Another member

I agree, and I hadn’t said so.

Coach

Anna, what do you hear?

Signs it’s working

Members speak before the leader.

Don’t confuse with

S3.1 One or two voices dominate

Dominance by peers.

S7.2Leader absent or abdicating
The leader delegates coaching and doesn’t engage
Recontract; clarify leader’s role
In the room

The leader sends apologies; the team has no authority to decide; members ask “why are we doing this if she’s not here?”

Members might say
  • She’s too busy.
  • We can’t decide without him.
  • Why bother if he’s not here?
What’s underneath

Leader absence signals low priority and blocks decisions. It may also mean the leader sees the team as the problem and coaching as something done to it.

Questions to ask the team
  1. What role should the leader play in our sessions?
  2. What do we need from the leader?
  3. What can we decide without them?
  4. How will we involve them?
Avoid here

Coaching around the leader.

Watch

Recontract with leader and sponsor.

Examples from the field
Leadership team
The coach recontracted with the leader and sponsor; the leader committed to attending half of each session.
Project team
Clarifying decision rights let the team make progress while the leader travelled.
Sample exchange
Coach

How does the leader’s absence affect our work?

Member

We can talk, but we can’t decide.

Coach

What would you want to say to her about that?

Another member

That we need her here, or her trust to decide.

Coach

Shall we agree how to tell her?

Signs it’s working

Leader engages; decisions progress.

Don’t confuse with

S7.10 Leader wants to be “one of the team”

One-of-the-team leader is present but avoids authority.

S7.3Leader wants the coach as ally
The leader tries to align the coach with their view
Hold the contract; coach the leader
In the room

Private calls from the leader, phrases like “between us”, “you see what I mean”. In sessions, the leader looks at the coach for agreement.

Members might say
  • You see what I mean, right?
  • Can you tell them?
  • Help me get them on board.
What’s underneath

Leaders may seek an ally against the team, especially if they feel isolated. Collusion feels like rapport while it is happening.

Questions to ask the team
  1. What are you hoping I will do?
  2. How could you raise this directly with the team?
  3. What would it cost the team’s trust if I carried messages?
  4. What support do you need for yourself?
Avoid here

Collusion.

Watch

Remind of the contract.

Examples from the field
CEO
The coach declined to deliver a message and helped the CEO rehearse saying it himself.
Department head
The coach offered separate leader coaching with clear boundaries agreed with the team.
Sample exchange
Leader

Can you tell them to step up?

Coach

My role is to coach the team as a whole. How could you tell them yourself?

Leader

I’m worried they’ll get defensive.

Coach

Shall we think about how to say it so they can hear it?

Signs it’s working

Leader speaks directly.

Don’t confuse with

S7.7 Leader asks coach about individuals

Asking about individuals is a specific breach request.

S7.4New leader inherits team
A new leader takes over an existing team
Timeline; personal histories; leader role contracting
In the room

Members compare the new leader with the old one, test boundaries, and hold back. The new leader tries to make a quick impact.

Members might say
  • Our old boss did it differently.
  • What will change?
  • We’ll see.
What’s underneath

Transitions create anxiety and loyalty conflicts. Members wonder what will change; the leader wonders whom to trust.

Questions to ask the team
  1. What do you want the new leader to know about this team?
  2. What do you want to keep?
  3. What does the leader need from the team?
  4. What will we do in the first 90 days?
Avoid here

Comparing leaders.

Watch

New leader assimilation sessions can help.

Examples from the field
Finance team
A new-leader assimilation session let the team ask questions anonymously; the leader answered them openly.
IT team
A timeline exercise helped the new leader understand old sensitivities.
Sample exchange
Coach

What should the new leader know about this team?

Member

We’ve had four leaders in three years.

Leader

That’s helpful to know. What has that been like?

Another member

Exhausting. We need some stability.

Signs it’s working

Relationship forms.

Don’t confuse with

S1.9 Newly formed team

New team vs new leader.

S7.5Team defers to leader
Members wait for the leader’s opinion
Leader speaks last; interaction patterns; decision rights
In the room

Members glance at the leader before answering, use phrases like “whatever you think”, and wait for direction.

Members might say
  • What do you think, boss?
  • I’ll go with whatever you decide.
  • It’s your call.
What’s underneath

Deference reflects hierarchy, cultural norms or a lack of safety. Sometimes it is learned: the leader has overruled people in the past.

Questions to ask the team
  1. What happens if we disagree with the leader?
  2. What would you say if the leader weren’t here?
  3. What would help you speak first?
  4. What does the leader want from you?
Avoid here

Blaming the team.

Watch

Work with the leader.

Examples from the field
CEO team
A member was asked to make an “oppose” move as an experiment; the CEO thanked him and debate opened.
Hospital team
Fist to five showed varied support that had been invisible.
Sample exchange
Coach

What would you say if the leader weren’t here?

Member

Probably that this plan won’t work.

Leader

I want to hear that.

Coach

What made it hard to say with her here?

Signs it’s working

Members voice views first.

Don’t confuse with

S6.4 Everything escalates to the leader

Escalation is about decisions.

S7.6Leader defensive under feedback
The leader reacts badly to team feedback
Prepare the leader; model curiosity; safety
In the room

The leader explains, defends or corrects when feedback arrives; the team goes quiet and withdraws.

Members might say
  • That’s not fair.
  • You don’t understand the pressures.
  • I disagree.
What’s underneath

Defensiveness under feedback quickly reduces team safety. Leaders often feel exposed in front of their own team.

Questions to ask the team
  1. What feedback is hardest to hear?
  2. What would help you stay curious?
  3. What do you want the team to know about how you’ll respond?
  4. What did you learn?
Avoid here

Exposing the leader.

Watch

Prepare beforehand.

Examples from the field
Executive team
The leader prepared privately with the coach and responded with curiosity in the session.
Engineering leader
After a defensive reaction, he came back next session to apologise; trust rose.
Sample exchange
Leader

That’s not fair.

Coach

It may not feel fair. What part of it might be useful to understand?

Leader

The part about decisions changing.

Coach

Would you like to ask the team about that?

Signs it’s working

Leader asks questions.

Don’t confuse with

S7.8 Leader is the issue no one names

Leader as unnamed issue.

S7.7Leader asks coach about individuals
The leader asks for information about members
Hold confidentiality; redirect
In the room

A private request, often framed as concern: “Who is resisting?” or “What did X say about me?”

Members might say
  • Who is resisting?
  • What did X say about me?
  • Just between us…
What’s underneath

Leaders may want information to manage people or protect themselves. Sharing it would break the team’s trust and the contract.

Questions to ask the team
  1. What are you noticing?
  2. What would you do with that information?
  3. How could you ask the team directly?
  4. What support do you need?
Avoid here

Sharing.

Watch

Contract clarity.

Examples from the field
Department head
The coach redirected to what the leader was observing; the leader raised it directly in the next session.
CEO
The coach reminded him of the contract; he agreed it protected him too.
Sample exchange
Leader

Who’s the problem?

Coach

I don’t share individual information — that’s part of our agreement. What are you seeing?

Leader

Resistance to the new plan.

Coach

How could you explore that with the team directly?

Signs it’s working

Leader respects boundary.

Don’t confuse with

S10.1 Sponsor asks for a report on individuals

Sponsor requests similar.

S7.8Leader is the issue no one names
The team’s problem centres on the leader’s behaviour
Anonymous data; leader preparation; name the undiscussable
In the room

Indirect comments, careful silences, members exchanging looks when the leader speaks.

Members might say
  • It’s complicated.
  • We can’t say.
  • You know…
What’s underneath

Teams avoid naming leadership issues because of power. The undiscussable often drains energy from every other topic.

Questions to ask the team
  1. What makes it hard to talk about leadership here?
  2. What would you want the leader to know?
  3. What would make it safe?
  4. What does the leader need to hear it well?
Avoid here

Exposing without preparation.

Watch

Work with the leader privately.

Examples from the field
CEO
Anonymous data feedback revealed a leadership issue; the coach prepared the CEO, who responded well.
Director
Anonymous cards named her late-night emails; she agreed new norms.
Sample exchange
Coach

What would you say about leadership if it were safe?

Member

That decisions come late.

Leader

I didn’t realise.

Coach

What would help the team say this more easily?

Signs it’s working

Issue is named and discussed.

Don’t confuse with

S7.6 Leader defensive under feedback

Defensive leader.

S7.9Leader leaves mid-engagement
The leader exits during coaching
Recontract; timeline; transition
In the room

Uncertainty, loss, questions about the coaching’s future and who now owns the contract.

Members might say
  • What happens now?
  • Is the coaching still on?
  • It won’t be the same.
What’s underneath

Leader departure changes the system and the contract. The team may grieve, worry or feel relief.

Questions to ask the team
  1. What do we want to keep?
  2. What do we need now?
  3. Who will sponsor the work?
  4. How do we want to say goodbye?
Avoid here

Continuing as if nothing changed.

Watch

Recontract with sponsor.

Examples from the field
Leadership team
Recontracted with the new leader after a farewell session for the old one.
Project team
Used a timeline to process the change.
Sample exchange
Coach

How does the leader’s departure change our work?

Member

We don’t know who’s in charge.

Coach

What do you need to know, and from whom?

Another member

The sponsor — we need a conversation.

Signs it’s working

New agreement.

Don’t confuse with

S8.5 Key member leaving

Key member leaving.

S7.10Leader wants to be “one of the team”
The leader avoids authority
Coach the leader’s role; clarify decisions
In the room

The leader avoids decisions, speaks of “all of us”, hesitates to use authority; members wait.

Members might say
  • I’m just one of you.
  • Let’s all decide.
  • I don’t want to pull rank.
What’s underneath

Avoiding authority creates confusion and slows the team. Some leaders fear being seen as controlling.

Questions to ask the team
  1. What decisions do you need to make as leader?
  2. What does the team need from you?
  3. What does authority mean to you?
  4. What would clarity look like?
Avoid here

Pushing authoritarianism.

Watch

Clarity is kindness.

Examples from the field
Startup
Leader clarified decision rights; the team welcomed it.
NGO
Leader learned to say “I’ve heard you; I’m deciding X.”
Sample exchange
Coach

What does the team need from you as their leader?

Member

Sometimes, just a decision.

Leader

I didn’t want to impose.

Coach

What would deciding clearly, after listening, look like?

Signs it’s working

Clear leadership.

Don’t confuse with

S7.2 Leader absent or abdicating

Absent leader.

S7.11The sponsor or a senior stakeholder is in the room
A powerful person attends; the team performs; real issues disappear
Contract the visitor’s role in advance; make the power visible and the purpose clear
In the room

Polished answers, careful language, members watching the visitor. The leader is more formal than usual. The visitor asks questions that sound like assessment.

Members might say
  • Everything is on track.
  • We’re fully aligned.
  • (later) We couldn’t say anything with her there.
What’s underneath

When the sponsor or a senior stakeholder joins, the team’s attention shifts from learning to impression management. The “real client” of the commissioning relationship is present, and confidentiality feels at risk. The visitor may not realise their impact. Handled well, their presence can be a powerful “connecting” moment.

Questions to ask the team
  1. (beforehand, to the visitor) What do you hope the team gets from you being here?
  2. What would make it safe for them to be honest with you present?
  3. (to the team) What do you most want the sponsor to understand?
  4. What would you want to ask her?
Avoid here

Letting the visitor turn the session into a review. Pretending the power isn’t there. Breaking confidentiality agreements by discussing previous sessions.

Watch

Agree a clear, time-boxed role: listen, share context, answer questions — then leave.

Examples from the field
Leadership team
The CEO joined for 40 minutes with a clear brief: share strategy, then listen. Members asked candid questions; the CEO later said it was the most useful hour of her month.
Project team
The sponsor attended unannounced. The coach named the change openly and re-contracted the session; the team chose to use the time to clarify priorities with him.
Sample exchange
Coach

Before we start, can we agree how we’ll use Maria’s time with us today?

Sponsor

I’m here to listen.

Coach

And what would the team like from Maria?

Member

Honestly — clarity on what “success” means for this project.

Sponsor

That’s a fair question. Let me be straight about it.

Signs it’s working

The team asks real questions; the visitor listens more than they evaluate; the team reports afterwards that it was useful.

Don’t confuse with

S7.1 Leader dominates

A dominant leader is the team’s own leader; here the power comes from outside the team, often from the commissioning relationship.

S8
Situation group · 14 situations

Change, context and the wider system

About this group

Teams live inside organisations, markets and societies that keep moving. Reorganisations, hybrid working, multicultural membership, rapid growth, departures, external crises, unhappy stakeholders, resource cuts, change fatigue and cross-team work all shape what the team can do. The coaching move here is almost always systemic: bring the context into the room and help the team find its real sphere of influence.

S8.1Reorganisation or merger
Structural change disrupts roles, identity and relationships
Honour the past; build a shared future; manage the tensions of change
In the room

Questions about new structures, anxious jokes, people counting who is “in” and “out”.

Members might say
  • Nobody knows the new structure yet.
  • We’re being merged with the team we used to compete with.
  • Is it even worth planning?
What’s underneath

Reorganisation triggers loss and uncertainty. Teams move through endings, a neutral zone and new beginnings (William Bridges). Coaching that skips the ending creates resistance.

Questions to ask the team
  1. What is ending for us?
  2. What stays the same?
  3. What do we want the new team to be?
  4. What tensions will we need to manage?
Avoid here

Selling the change. Treating resistance as a problem to overcome.

Watch

Bridges’ transition model is a helpful frame for the team.

Examples from the field
Bank integration
The team mapped what was ending, what continued and what was new; anxiety fell.
Pharma reorg
Polarity map of global standards versus local agility.
Sample exchange
Member

Why plan anything when the structure might change again?

Coach

What will stay true for this team whatever the structure?

Another member

Our customers. And probably most of us.

Coach

Let’s start there.

Signs it’s working

The team distinguishes what it can influence from what it can’t, and starts planning.

Don’t confuse with

S1.10 Merged team (“us and them”)

A merged team is after the change; this is during or before it.

S8.2Hybrid friction
Hybrid working creates unequal access and misunderstandings
Agree hybrid norms; redesign rhythms; map the team in space
In the room

Office group and remote group; separate chats; remote members feel second-class.

Members might say
  • The office crowd decides everything over coffee.
  • Remote people never turn up.
  • We’ve lost the team feel.
What’s underneath

Hybrid creates proximity bias and different experiences of the same team.

Questions to ask the team
  1. What’s working about hybrid for us?
  2. What isn’t?
  3. What norms would make it fairer?
  4. Where do decisions really happen?
Avoid here

Choosing a side (office vs remote).

Watch

Design decisions about where and when the team meets deliberately.

Examples from the field
Consultancy team
Agreed decisions only in shared channels; in-office days aligned.
Tech team
Virtual sculpt showed remote members at the edge; meeting rotation changed.
Sample exchange
Member (remote)

I feel like I hear about decisions last.

Member (office)

We don’t mean to exclude you.

Coach

Where do decisions actually get made right now?

Signs it’s working

Hybrid norms are written and used; remote members influence decisions.

Don’t confuse with

S3.11 Remote members invisible

Remote members invisible in sessions is about participation; hybrid friction is about the whole way of working.

S8.3Multicultural team
Members from different cultures bring different norms
Surface norms; build shared agreements; treat difference as resource
In the room

Different speaking styles, silence norms, attitudes to hierarchy and time.

Members might say
  • In my culture we wouldn’t say that directly.
  • Why don’t they speak up?
  • Deadlines mean different things here.
What’s underneath

Cultural differences in communication, hierarchy and conflict (Erin Meyer’s culture map) shape team dynamics. Differences can be strengths if they are discussed.

Questions to ask the team
  1. What norms do each of us bring?
  2. What do we need to agree as a team?
  3. Where do our differences help us?
Avoid here

Stereotypes. Assuming one culture is the norm.

Watch

Check that methods (e.g. direct feedback rounds) fit the team.

Examples from the field
Global IT team
Mapped members on directness and hierarchy scales and agreed norms.
Asian–European team
User manuals created understanding.
Sample exchange
Member

I always wait to be asked.

Another member

I thought you had no view!

Coach

What norm would work for both of you?

Signs it’s working

Norms are discussed openly; misunderstandings reduce.

Don’t confuse with

S4.7 Cross-cultural misunderstanding

A specific misunderstanding vs the general context.

S8.4Rapid growth / many new members
The team is growing fast; culture is diluting
Explicit norms; onboarding rituals; rhythms
In the room

Many new faces; old-timers nostalgic; confusion about how things work.

Members might say
  • It used to be easier.
  • Nobody tells new people how things work.
  • Who are all these people?
What’s underneath

Growth stretches informal norms. What worked when small no longer works.

Questions to ask the team
  1. What do we want to keep?
  2. What do new people need?
  3. What should become explicit?
Avoid here

Nostalgia. Ignoring newcomers.

Watch

Make implicit knowledge explicit.

Examples from the field
Startup
Wrote team agreements and an onboarding guide; new joiners got up to speed faster.
NGO
Peer buddies helped new members learn the unwritten rules.
Sample exchange
Member

It used to be simpler.

Coach

What made it simpler?

Another member

We all knew how things worked.

Coach

How could we make that knowledge available to new people?

Signs it’s working

New members integrate faster; old-timers share knowledge.

Don’t confuse with

S1.9 Newly formed team

A new team has no norms; growth strains existing ones.

S8.5Key member leaving
An important member is leaving
Acknowledge; redistribute roles; capture knowledge
In the room

Sadness, worry, role gaps.

Members might say
  • How will we cope without her?
  • Who will do his work?
  • It won’t be the same.
What’s underneath

Losing a key member affects roles, relationships and identity.

Questions to ask the team
  1. What will we miss?
  2. What roles need covering?
  3. What knowledge do we need to capture?
  4. How do we say goodbye?
Avoid here

Ignoring the loss.

Watch

Use role negotiation to reallocate work.

Examples from the field
Product team
A farewell round and role negotiation covered the gap.
Research team
Knowledge-capture sessions recorded key contacts and methods.
Sample exchange
Coach

What will we miss when Priya leaves?

Member

Her customer knowledge.

Coach

How could we capture some of it?

Another member

Shadowing for two weeks.

Signs it’s working

Roles are covered; farewell happens well.

Don’t confuse with

S7.9 Leader leaves mid-engagement

The leader leaving changes the system more fundamentally.

S8.6External crisis
A sudden external event threatens the team
Contract the session around the crisis; plan; support
In the room

High stress, urgency, focus on immediate response.

Members might say
  • We need to act now.
  • This changes everything.
  • We don’t have time for coaching.
What’s underneath

Crises demand rapid response but also reveal team strengths and weaknesses.

Questions to ask the team
  1. What do we need to do now?
  2. How are we doing?
  3. What could go wrong?
  4. What do we learn?
Avoid here

Forcing reflection during the acute phase.

Watch

Offer short, focused support sessions.

Examples from the field
Pandemic response
Short weekly check-ins and pre-mortems helped the team act fast.
Cyber attack
An after-action review two weeks later produced lasting changes.
Sample exchange
Coach

What does the team need from this hour, given the crisis?

Member

Clarity on priorities.

Coach

What are the top three for the next week?

Another member

Customers, staff, systems.

Signs it’s working

The team acts coherently; learning happens later.

Don’t confuse with

S1.6 Firefighting / crisis mode

Internal firefighting vs an external crisis.

S8.7Stakeholders unhappy
Stakeholders complain about the team
Zoom to stakeholders; close the loop; revisit purpose
In the room

Defensiveness; stories about unreasonable stakeholders.

Members might say
  • They don’t understand our constraints.
  • They complain about everything.
  • We’re doing our best.
What’s underneath

Stakeholder dissatisfaction is valuable data, even when partly unfair.

Questions to ask the team
  1. What are stakeholders saying?
  2. What’s true in it?
  3. What do they need?
  4. How can we respond?
Avoid here

Dismissing complaints.

Watch

Bring real stakeholder data.

Examples from the field
IT team
Stakeholder interviews led to a new intake process.
HR team
A quarterly pulse survey tracked improvement.
Sample exchange
Member

They’re never satisfied.

Coach

What are they actually asking for?

Another member

Faster responses.

Coach

What would that take?

Signs it’s working

The team engages with stakeholders.

Don’t confuse with

S1.11 Talks only about other teams

Blaming other teams is habitual; unhappy stakeholders is a real feedback situation.

S8.8Resource cuts
Budget or staff reduced; same expectations
Prioritise; test assumptions; engage stakeholders
In the room

Frustration, overload, resentment.

Members might say
  • We can’t do more with less.
  • Something has to give.
  • They expect miracles.
What’s underneath

Cuts force trade-offs. Without explicit prioritisation, teams burn out.

Questions to ask the team
  1. What must we keep?
  2. What can we stop?
  3. Who needs to agree?
  4. What assumptions are we making?
Avoid here

Accepting impossible expectations.

Watch

Help the team negotiate scope.

Examples from the field
Public sector
A stop list was agreed with the sponsor.
Hospital
An immunity map revealed the assumption that saying no was disloyal.
Sample exchange
Coach

If we can’t do everything, what matters most?

Member

Patient safety.

Coach

What could we stop?

Another member

Two reports nobody reads.

Signs it’s working

Scope is renegotiated.

Don’t confuse with

S2.3 Exhausted / burnout

Burnout may result.

S8.9Change fatigue
Repeated changes exhaust the team
Test assumptions; appreciate stability; prioritise
In the room

Weariness, cynicism, low energy.

Members might say
  • Not another change.
  • We’ve barely recovered.
  • What’s the point?
What’s underneath

Change fatigue reduces engagement and capacity.

Questions to ask the team
  1. What changes have we been through?
  2. What has helped us cope?
  3. What can we control?
Avoid here

Adding more change.

Watch

Focus on stability where possible.

Examples from the field
Bank
Appreciative inquiry on how the team had coped with past change rebuilt confidence.
Tech
A stop-doing list reduced overload.
Sample exchange
Coach

What has helped you get through the changes so far?

Member

Each other.

Coach

How could we lean on that now?

Another member

More time together, less time in status meetings.

Signs it’s working

Energy stabilises.

Don’t confuse with

S2.5 Anxiety about change

Anxiety about an upcoming change.

S8.10Team of teams / cross-team coordination
Several teams must deliver together; nobody owns the whole
Coach the system of teams: shared purpose, explicit interfaces, liaison roles and regular cross-team learning
In the room

Representatives defend their own team’s priorities. Coordination meetings are long and report-heavy. Problems appear at the boundaries between teams. Each team blames the others; the programme lead is overwhelmed.

Members might say
  • That’s their dependency, not ours.
  • We need another coordination meeting.
  • Nobody owns the end-to-end result.
What’s underneath

In a team of teams, the critical work happens between teams. Each team is optimised for itself, and the system is optimised for nobody. Stanley McChrystal’s “team of teams” idea is that the network needs shared consciousness (everyone sees the whole picture) and empowered execution (teams decide locally within shared intent). Fluid membership and dual loyalties make it harder. The client may be the whole network, not one team.

Questions to ask the team
  1. What do we need to deliver together that no single team can?
  2. Where do the handoffs between teams break down?
  3. Who connects the teams, and how?
  4. How does each team’s success depend on the others?
  5. How will the network learn together?
Avoid here

Coaching each team separately and hoping the system improves. More status meetings. Ignoring the different incentives of each team.

Watch

Contract clearly: who is the client — one team, the leadership group across teams, or the network?

Examples from the field
Programme team
An ecosystem map and interface agreements cut escalations.
Cross-functional launch
A team-of-teams charter clarified who decides what.
Sample exchange
Coach

What do we need to deliver together that no single team can?

Member

The launch.

Coach

Who decides what for the launch?

Another member

That’s the problem — nobody knows.

Signs it’s working

Fewer boundary failures; shorter coordination meetings; teams talk about shared outcomes; cross-team learning happens regularly.

Don’t confuse with

S4.9 Silo war with another team

A silo war is conflict between two teams; team of teams is the design and coordination of many teams around shared work.

S8.11Generational or neurodiversity friction
Different ways of thinking, communicating and working cause misunderstanding
Make differences in style explicit and design working norms that let different minds contribute
In the room

Frustration about “how they communicate”. Some members find meetings overwhelming; others find written channels cold. Jokes about generations. Some people mask or withdraw.

Members might say
  • They always want everything on chat.
  • Why can’t he just say it in the meeting?
  • I need time to process before I answer.
What’s underneath

Differences in generation, neurotype and working style are often read as attitude problems (“disrespectful”, “slow”, “difficult”). Many standard team practices — fast open discussion, open-plan noise, unstructured brainstorming — favour some minds over others. Inclusion means designing for difference, not asking people to adapt to one norm. Disclosure of neurodivergence is personal and voluntary.

Questions to ask the team
  1. What helps you do your best thinking?
  2. What makes meetings hard for you?
  3. What norms would let different styles contribute?
  4. What assumptions do we make about each other’s generation or style?
Avoid here

Stereotyping generations. Asking anyone to disclose a diagnosis. Treating one communication style as “professional” and others as wrong.

Watch

Focus on preferences and needs, not labels; offer multiple ways to contribute (written, spoken, prepared, spontaneous).

Examples from the field
Product team
User manuals revealed that two members needed agendas in advance and written follow-ups. The team adopted “agenda 24 hours ahead, decisions in writing” — and everyone benefited.
Multi-generational team
Clean Language exploration of the word “respect” showed it meant “speaking up” for some and “not interrupting” for others. The team agreed shared norms.
Sample exchange
Member

He never contributes in meetings.

Another member

I contribute — just not on the spot.

Coach

What would help you contribute?

Another member

Seeing the questions beforehand.

Coach

Would that help anyone else?

Third member

Me, actually.

Signs it’s working

Members state preferences openly; meetings offer several ways to contribute; fewer attributions of bad intent.

Don’t confuse with

S8.3 Multicultural team

Multicultural difference is about cultural norms; this is about generational, cognitive and neurological differences within any culture.

S8.12AI or new tool adoption changes how the team works
New AI or digital tools change roles, decisions and expertise
Treat adoption as a team change: explore hopes and fears, agree principles, and run small experiments with review
In the room

Excitement from some, anxiety from others. Unspoken worries about jobs and expertise. Inconsistent use: some members use AI for everything, others not at all. Confusion about who is accountable for AI-assisted work.

Members might say
  • Will this replace part of my job?
  • Half of us use it, half of us don’t trust it.
  • Who’s responsible if the AI gets it wrong?
What’s underneath

New tools change more than tasks: they change status (whose expertise matters), decision rights (who checks what), trust and quality standards. If these are not discussed, teams split into enthusiasts and resisters, and risks go unmanaged. It is a classic polarity — speed and innovation versus quality and safety.

Questions to ask the team
  1. What do we hope this tool will help us do?
  2. What are we worried about?
  3. What principles should guide how we use it?
  4. Who is accountable for the quality of AI-assisted work?
  5. What small experiment could we run and review?
Avoid here

Taking sides between enthusiasts and sceptics. Ignoring job-security fears. Letting adoption happen individually without team agreements.

Watch

Bring data protection, ethics and organisational policy into the conversation early.

Examples from the field
Marketing team
Polarity mapping of speed vs quality led to principles: AI drafts, humans decide and check facts. Anxiety eased; output rose.
Legal team
A consent decision on a three-month AI pilot, with clear objections integrated (confidentiality, accuracy checks), ended months of stalemate.
Sample exchange
Member

I use AI for all my first drafts.

Another member

I don’t trust it at all.

Coach

It sounds like both speed and quality matter here. What would getting the best of both look like?

Another member

Clear rules on checking.

Member

And sharing what works.

Coach

Could we agree principles and try them for a month?

Signs it’s working

Shared principles exist; experiments are reviewed; worries are discussed openly; use becomes more consistent.

Don’t confuse with

S8.9 Change fatigue

Change fatigue is exhaustion from repeated change; this is a specific change in how work and expertise are done.

S8.13A purely virtual team
Members have never (or rarely) met; all work happens online
Design connection, communication and rituals deliberately — nothing happens by accident online
In the room

Cameras off, chat-heavy, quick transactional meetings. People know each other’s work but not each other. Silence is hard to read. Time zones mean someone is always tired.

Members might say
  • I’ve never actually met most of the team.
  • I don’t know if silence means agreement.
  • It’s always 10pm for me.
What’s underneath

Purely virtual teams differ from hybrid teams: there is no office core, but there is also no informal glue. Trust must be built deliberately, through reliability, responsiveness and some personal connection. Misunderstandings escalate in text. Belonging depends on rituals and norms designed for the medium.

Questions to ask the team
  1. How do we get to know each other beyond work?
  2. What norms do we need for chat, video and response times?
  3. How do we share the burden of time zones?
  4. What rituals would make us feel like a team?
Avoid here

Copying office practices online. Long video sessions. Assuming silence means agreement.

Watch

Use writing-first methods and short sessions; check understanding explicitly.

Examples from the field
Global consulting team
Introduced a weekly 15-minute “no work talk” call and rotating meeting times. Engagement scores rose.
Startup
Agreed response-time norms and a “camera on for decisions” rule; misunderstandings fell.
Sample exchange
Coach

How do you know when someone disagrees?

Member

We don’t, really.

Another member

We find out later.

Coach

What could make disagreement visible online?

Member

A quick poll before decisions.

Coach

Shall we try it?

Signs it’s working

Members know each other personally; norms are explicit; disagreement surfaces in meetings; time-zone burden is shared.

Don’t confuse with

S8.2 Hybrid friction

Hybrid friction is about unequal access between office and remote; a purely virtual team has equal distance but no informal connection.

S8.14Fluid membership: the team keeps changing
People join and leave constantly; the team never settles
Shift from building a stable team to building teaming routines that survive turnover
In the room

New faces every month. Old-timers tired of re-explaining. Newcomers unsure how things work. Norms quietly erode.

Members might say
  • Who’s on the team this month?
  • I’ve explained this five times.
  • Nobody told me that’s how we do it here.
What’s underneath

Stable-team models assume membership that lasts. Many teams are now fluid. Without explicit routines, every change resets trust and shared understanding. The answer is not to stop the change but to make joining, working and leaving routine and quick.

Questions to ask the team
  1. What does a newcomer need in their first week?
  2. What do we lose every time someone leaves?
  3. What routines would help us re-launch quickly?
  4. Who looks after our norms?
Avoid here

Long trust-building processes. Blaming newcomers for not knowing. Treating turnover as temporary when it’s structural.

Watch

Re-launch the team whenever a third of its members have changed.

Examples from the field
Agile squads
A one-page team passport and a 60-minute re-launch every quarter. New joiners were productive in days.
Hospital unit
Five-minute shift huddles with names and roles reduced errors.
Sample exchange
Member

Every month there are new people.

Coach

What would they need to know on day one?

Another member

Our norms and who to ask.

Coach

Could we write that on one page and keep it current?

Member

Yes — and someone owns it each month.

Signs it’s working

Faster onboarding; stable norms despite turnover; less re-explaining.

Don’t confuse with

S8.4 Rapid growth / many new members

Rapid growth adds members; fluid membership means members constantly come and go.

S9
Situation group · 9 situations

From insight to action

About this group

The gap between a good session and a changed team is where most team coaching fails. This group covers insight that never travels, easy agreement, overlong action lists, reverting under pressure, abandoning a failed experiment, waiting for permission, learning that stays private, breakthrough moments and disagreement about next steps.

S9.1Great session, nothing changes
Insight in sessions; no change in daily work
Small experiments; redesign routines; review
In the room

Next session starts with “we didn’t get to it”.

Members might say
  • We were busy.
  • We meant to.
  • Things got in the way.
What’s underneath

Insight without structure fades. Daily routines pull the team back.

Questions to ask the team
  1. What got in the way?
  2. What small change could we make?
  3. Where would it live in our routines?
Avoid here

Blame.

Watch

Open every session with experiment review.

Examples from the field
Leadership team
Experiments tracked on a visible board; follow-through improved.
Agency
A five-minute process check added to weekly meetings kept new behaviours alive.
Sample exchange
Coach

Last session we agreed to try X. What happened?

Member

We forgot.

Coach

What would help it stick?

Another member

Putting it on the weekly agenda.

Signs it’s working

Experiments happen.

Don’t confuse with

S6.7 Nobody owns actions

Ownership issue.

S9.2Agreeing too easily
Commitments are made quickly without real buy-in
Test agreement; pre-mortem; hear dissent
In the room

Fast nods; no questions.

Members might say
  • Sure, sounds good.
  • Yes, let’s do it.
  • No problem.
What’s underneath

Easy agreement may hide doubts.

Questions to ask the team
  1. What level of support do we have?
  2. What might get in the way?
  3. Who has a different view?
Avoid here

Accepting at face value.

Watch

Use fist to five.

Examples from the field
Project team
Fist to five revealed doubts that improved the plan.
Leadership team
A pre-mortem uncovered risks nobody had mentioned.
Sample exchange
Coach

Fist to five — how committed are we?

Coach

(hands go up) Mostly fives, two twos. What would move you up?

Member

More time to prepare the team.

Coach

What would that look like?

Another member

Two extra weeks before launch.

Signs it’s working

Reservations surface.

Don’t confuse with

S3.4 Groupthink

Groupthink on decisions.

S9.3Action list too long
Many actions; little focus
Prioritise; small experiments
In the room

Long flipchart of actions.

Members might say
  • Let’s add that too.
  • We need to do all of these.
  • We’ll get to them.
What’s underneath

Long lists signal low commitment.

Questions to ask the team
  1. Which one or two matter most?
  2. What can we drop?
Avoid here

Approving everything.

Watch

Fewer is better.

Examples from the field
Leadership team
Reduced 15 actions to three experiments.
Project team
Moved the rest to a “parking lot” reviewed monthly.
Sample exchange
Coach

If we only did two of these, which ones?

Member

The handoff and the meeting change.

Coach

What happens to the rest?

Another member

Parking lot.

Signs it’s working

Focused list.

Don’t confuse with

S6.7 Nobody owns actions

Ownership.

S9.4Reverting under pressure
New behaviours disappear when stress rises
Immunity to change; rhythm; peer support
In the room

The team describes going back to old habits.

Members might say
  • When things got busy, we went back to old ways.
  • Under pressure it’s easier.
  • We don’t have time.
What’s underneath

Old habits feel safer under stress.

Questions to ask the team
  1. What happens under pressure?
  2. What assumption drives it?
  3. What support helps?
Avoid here

Blame.

Watch

Plan for pressure.

Examples from the field
Sales team
An immunity map revealed the assumption that only speed mattered under pressure.
Operations
Agreed a “pressure plan” for which new behaviours to keep even in busy weeks.
Sample exchange
Coach

What did the pressure make us believe we had to do?

Member

Skip the review to save time.

Coach

What did skipping it cost?

Another member

Mistakes we then had to fix.

Signs it’s working

Plans for pressure.

Don’t confuse with

S9.1 Great session, nothing changes

Nothing changes at all.

S9.5Experiment fails and team gives up
A failed experiment leads to abandonment
AAR; reframe failure as learning; adapt
In the room

Disappointment; “told you so”.

Members might say
  • That didn’t work.
  • We tried.
  • Let’s go back.
What’s underneath

Teams often confuse failure of an experiment with failure of the goal.

Questions to ask the team
  1. What did we learn?
  2. What would we adjust?
  3. What still matters?
Avoid here

Forcing the same experiment.

Watch

Celebrate learning.

Examples from the field
Product team
Adjusted a daily stand-up to weekly after the daily version failed.
Leadership team
Turned a failed experiment into a learning harvest.
Sample exchange
Coach

What did the experiment teach us?

Member

Daily is too much.

Coach

What would we try next?

Another member

Weekly, with a clearer purpose.

Signs it’s working

New experiment designed.

Don’t confuse with

S2.9 Shame after a public failure

Public failure and shame.

S9.6Waiting for permission
The team waits for approval to act
Drama to empowerment; decision rights; test assumptions
In the room

“We’d need approval”.

Members might say
  • We can’t do that without sign-off.
  • They won’t let us.
  • Let’s ask first.
What’s underneath

Waiting may reflect real constraints or learned helplessness.

Questions to ask the team
  1. What do we actually need permission for?
  2. What can we do now?
  3. What assumption are we making?
Avoid here

Encouraging rule-breaking.

Watch

Check real authority.

Examples from the field
Public sector team
Discovered it had more authority than assumed.
Charity
Mapped what really needed approval.
Sample exchange
Coach

What would happen if you did it without asking?

Member

Probably nothing.

Coach

Let’s check what really needs permission.

Another member

Only the budget part.

Signs it’s working

The team acts within its authority.

Don’t confuse with

S6.4 Everything escalates to the leader

Escalation.

S9.7Learning stays in the room
Team learning isn’t shared with stakeholders
Close the loop; harvest; rhythms
In the room

Stakeholders unaware of changes.

Members might say
  • Nobody outside knows what we’ve done.
  • We haven’t told anyone.
  • Should we?
What’s underneath

Change needs to be visible to have impact.

Questions to ask the team
  1. Who needs to know?
  2. How will we share it?
Avoid here

The coach reporting for the team.

Watch

Team owns communication.

Examples from the field
Leadership team
Shared learning with the sponsor in a short presentation.
Project team
Monthly update to stakeholders.
Sample exchange
Coach

Who should hear about what we’ve learned?

Member

Our sponsor.

Coach

What would you want them to know?

Another member

That we decide faster now.

Signs it’s working

Stakeholders notice changes.

Don’t confuse with

S8.7 Stakeholders unhappy

Unhappy stakeholders.

S9.8Breakthrough moment
A significant insight lands
Harvest; land in experiments
In the room

Energy, silence, surprise.

Members might say
  • That’s it!
  • I’ve never seen it that way.
  • Wow.
What’s underneath

Breakthroughs need to be captured and acted on.

Questions to ask the team
  1. What just happened?
  2. What do we want to do with it?
Avoid here

Rushing on.

Watch

Pause to harvest.

Examples from the field
Leadership team
Harvested an insight about decision-making into an experiment.
Project team
Paused to name the shift and record it.
Sample exchange
Coach

Let’s pause. What just shifted?

Member

We realised we never disagree openly.

Coach

What do you want to do with that?

Another member

Try it next meeting.

Signs it’s working

Insight turns into action.

Don’t confuse with

S9.1 Great session, nothing changes

Insight without action.

S9.9Can’t agree the next step
The team agrees on the issue but not the action
Gradients of agreement; decision rights; experiments
In the room

Competing proposals; frustration.

Members might say
  • We all want to change, but how?
  • Your idea won’t work.
  • Let’s keep discussing.
What’s underneath

Disagreement about action may hide different risk tolerances.

Questions to ask the team
  1. What would we try first?
  2. Can we test both?
  3. Who decides?
Avoid here

Endless discussion.

Watch

Small tests.

Examples from the field
Product team
Tested two options in parallel for two weeks.
Leadership team
Clarified who decides when consensus fails.
Sample exchange
Coach

Can we test both ideas for two weeks?

Member

That would work.

Coach

How will we compare them?

Another member

Customer response time.

Signs it’s working

Action agreed.

Don’t confuse with

S6.5 Consensus paralysis

Consensus paralysis.

S10
Situation group · 12 situations

The engagement and the coach

About this group

Some of the hardest moments in team coaching are about the coach and the contract rather than the team: sponsors who want reports on individuals, members who want private coaching, pressure to become the expert, unconscious collusion, co-coach friction, requests for training, personal disclosures, scope creep, endings, the coach’s own anxiety, cameras off and the temptation of confidential interview data. These cards are about holding the role.

S10.1Sponsor asks for a report on individuals
The sponsor wants information about team members
Hold contract; offer team-level reporting
In the room

Private request.

Members might say
  • Who’s not engaging?
  • Can you tell me who’s the problem?
  • I need to know for performance reviews.
What’s underneath

Sponsors may misuse coaching for assessment.

Questions to ask the team
  1. What do you need to know, and why?
  2. What team-level information would help?
Avoid here

Sharing individual data.

Watch

Contract clarity.

Examples from the field
CFO sponsor
Accepted monthly theme reports co-written with the team.
HR sponsor
Agreed to team-level measures only after the coach explained the impact on trust.
Sample exchange
Sponsor

Who’s resisting?

Coach

I report on team themes and agreed measures, not individuals. What would help you?

Sponsor

I want to know if it’s working.

Coach

Let’s agree what evidence would show that.

Signs it’s working

Sponsor respects boundary.

Don’t confuse with

S7.7 Leader asks coach about individuals

Leader request.

S10.2Member asks for private coaching mid-engagement
A member wants individual coaching from the team coach
Clarify roles; refer if needed
In the room

Private request.

Members might say
  • Could we have a one-to-one?
  • I need help with my own stuff.
  • Just between us.
What’s underneath

Dual roles create confidentiality and fairness issues.

Questions to ask the team
  1. What do you need?
  2. How would it affect the team work?
Avoid here

Agreeing without contract.

Watch

Consider referral to another coach.

Examples from the field
Member
Referred to another coach for individual work.
Leader
Individual coaching agreed with the team’s knowledge and clear boundaries.
Sample exchange
Member

Can we meet one-to-one?

Coach

Let’s look at whether that fits our team agreement, or whether another coach would serve you better.

Member

Another coach is fine.

Coach

I can suggest some names.

Signs it’s working

Clear boundaries.

Don’t confuse with

S10.12 Interview data tempting to use

Data use.

S10.3Coach pulled into expert role
The team wants the coach to give answers
Return ownership; process observation; fade the coach
In the room

“What do you think?” “What would you do?”

Members might say
  • You’re the expert.
  • Just tell us.
  • What do other teams do?
What’s underneath

Teams may want answers to avoid responsibility.

Questions to ask the team
  1. What do you think?
  2. What would help you decide?
Avoid here

Becoming the consultant without contracting.

Watch

Offer input transparently if appropriate.

Examples from the field
Leadership team
The coach offered a model with permission, then returned to coaching.
Project team
The coach asked the team to generate options before sharing any.
Sample exchange
Member

Just tell us what to do.

Coach

I could share what I’ve seen elsewhere, but first — what do you think?

Member

We’re not sure.

Coach

What options can you see?

Signs it’s working

The team owns decisions.

Don’t confuse with

S3.10 Advice-giving instead of thinking

Advice-giving among members.

S10.4Coach colluding with a subgroup
The coach aligns with one faction
Self-awareness; supervision; observation
In the room

The coach notices favouring some members.

Members might say
  • (coach’s thought) They’re the reasonable ones.
  • Others see the coach as biased.
  • You always agree with them.
What’s underneath

Coaches can unconsciously side with members they like.

Questions to ask the team
  1. (self) Who am I aligned with?
  2. What am I not seeing?
Avoid here

Ignoring it.

Watch

Supervision.

Examples from the field
Coach
Noticed alignment with a subgroup and took it to supervision.
Co-coach
Gave feedback on the coach’s bias; the coach adjusted.
Sample exchange
Member

You always agree with them.

Coach

Thank you. Let me check that. What have you noticed?

Member

You nod when they speak.

Coach

That’s helpful — I’ll watch it.

Signs it’s working

Coach rebalances.

Don’t confuse with

S10.10 Coach’s own anxiety in the group

Coach anxiety.

S10.5Co-coach disagreement
Co-coaches disagree on approach
Contracting between coaches; review
In the room

Visible tension between coaches.

Members might say
  • (co-coach) I’d go another way.
  • We need to align.
  • Let’s talk at the break.
What’s underneath

Co-coach dynamics affect the team.

Questions to ask the team
  1. What does the team need?
  2. How do we decide between us?
Avoid here

Arguing in front of the team.

Watch

Contract co-coaching in advance.

Examples from the field
Co-coaches
Agreed roles and a signal for time-outs.
Co-coaches
Debriefed after each session to align.
Sample exchange
Coach

Let’s take a moment to align on what the team needs.

Co-coach

I think they need more time on conflict.

Coach

Agreed — let’s do that.

Signs it’s working

Coaches work smoothly.

Don’t confuse with

S10.4 Coach colluding with a subgroup

Collusion.

S10.6Team wants training, not coaching
The team asks for content
Clarify modalities; contract
In the room

Requests for models, tools, slides.

Members might say
  • Can you teach us something?
  • Give us a framework.
  • We want practical tools.
What’s underneath

Teams may need training. The coach must distinguish modalities.

Questions to ask the team
  1. What do you need?
  2. How would training help?
  3. What would coaching add?
Avoid here

Switching modes without contracting.

Watch

ICF competencies stress distinguishing modalities.

Examples from the field
Team
Agreed a short training input followed by coaching.
Team
Training delivered separately by a trainer; coaching kept distinct.
Sample exchange
Member

Can you teach us a model?

Coach

I can share one briefly, if that helps — and then let’s work on how it applies to you.

Member

That works.

Coach

Here’s the model…

Signs it’s working

Clear contracting.

Don’t confuse with

S10.3 Coach pulled into expert role

Expert role.

S10.7Member discloses personal crisis
A member shares a personal difficulty
Support; refer; manage team impact
In the room

Emotion; silence.

Members might say
  • I’m going through a divorce.
  • I’m not well.
  • I’m struggling.
What’s underneath

Personal crises affect the team; but team coaching is not therapy.

Questions to ask the team
  1. (privately) What do you need?
  2. What support do you have?
Avoid here

Therapy in the team.

Watch

Refer to support services.

Examples from the field
Member
Referred to the employee assistance programme.
Team
Agreed how to support a colleague during illness.
Sample exchange
Coach

Thank you for sharing. What would be helpful from the team right now?

Member

Just some understanding.

Coach

How can the team show that?

Signs it’s working

Member supported.

S10.8Scope creep
The engagement expands without agreement
Recontract
In the room

New requests.

Members might say
  • Can you also…
  • While you’re here…
  • Could you help with…
What’s underneath

Scope creep dilutes the work.

Questions to ask the team
  1. What’s the priority?
  2. How does this fit the contract?
Avoid here

Saying yes to everything.

Watch

Recontract with sponsor.

Examples from the field
Engagement
Recontracted with the sponsor.
Leader
Agreed a separate piece of work for recruitment.
Sample exchange
Leader

Can you also help with recruitment?

Coach

Let’s check how that fits our agreement.

Leader

Maybe separately.

Coach

Let’s discuss that with the sponsor.

Signs it’s working

Clear scope.

Don’t confuse with

S10.6 Team wants training, not coaching

Training request.

S10.9Ending the engagement
The coaching is ending
Harvest; handover; close the loop
In the room

Mixed emotions.

Members might say
  • What now?
  • We’ll miss this.
  • Can we continue?
What’s underneath

Endings consolidate learning.

Questions to ask the team
  1. What did we learn?
  2. What will we keep?
  3. How will we continue?
Avoid here

Abrupt endings.

Watch

Plan the ending early.

Examples from the field
Team
Closing ritual and self-coaching plan.
Team
Final evaluation against the baseline.
Sample exchange
Coach

As we end, what will you take forward?

Member

The check-in.

Another member

The process observer role.

Coach

Who will lead them?

Signs it’s working

Clear plan.

Don’t confuse with

S7.9 Leader leaves mid-engagement

Leader leaving.

S10.10Coach’s own anxiety in the group
The coach feels overwhelmed by the group
Self-regulation; supervision; process
In the room

Coach notices racing thoughts, over-talking.

Members might say
  • (coach’s thought) I’m losing them.
  • This is going badly.
  • I need to fix this.
What’s underneath

Groups amplify anxiety.

Questions to ask the team
  1. (self) What am I feeling?
  2. What does the group need?
Avoid here

Over-controlling.

Watch

Breathe; use co-coach or supervision.

Examples from the field
Coach
Paused, breathed, asked the team what they noticed.
Coach
Took the session to supervision.
Sample exchange
Coach

Let’s pause. What do you notice about this conversation?

Member

It’s getting heated.

Coach

What do we need right now?

Signs it’s working

Coach regains presence.

Don’t confuse with

S10.4 Coach colluding with a subgroup

Collusion.

S10.11Cameras off on video
Remote members turn off cameras
Norms; check-in; rhythms
In the room

Black screens.

Members might say
  • My connection is bad.
  • I’m multitasking.
  • I prefer cameras off.
What’s underneath

Cameras off may reflect fatigue or disengagement.

Questions to ask the team
  1. What would help us connect?
  2. What norms do we need?
Avoid here

Forcing cameras.

Watch

Agree norms.

Examples from the field
Team
Cameras on for check-in only.
Team
Discussed camera fatigue and agreed norms.
Sample exchange
Coach

Could we have cameras on for the check-in?

Member

Sure.

Coach

What norms would work for the rest of the session?

Signs it’s working

Engagement increases.

Don’t confuse with

S3.11 Remote members invisible

Remote invisibility.

S10.12Interview data tempting to use
The coach knows individual information from interviews
Hold confidentiality; feed back only themes
In the room

Coach holds private knowledge.

Members might say
  • (coach’s thought) I know who said that.
  • I could use this.
  • They don’t know I know.
What’s underneath

Individual data is confidential.

Questions to ask the team
  1. (self) Am I using private information?
Avoid here

Hints.

Watch

Themes only.

Examples from the field
Coach
Kept themes anonymous.
Coach
Took a dilemma to supervision.
Sample exchange
Coach

(to team) Here are the themes, without attribution.

Member

Who said this?

Coach

That’s part of our agreement — I don’t share who said what.

Signs it’s working

Trust maintained.

Don’t confuse with

S4.5 Trust breach / leak

Trust breach.

Phrase finder: what team members say

Start from the words you hear in the room. Type part of what someone said and jump to the situations it most often points to. There are 329 phrases here. They are clues, not diagnoses: the same words mean different things in different teams.

Knowledge Library: the ACTC curriculum map

The ICF competencies describe what a team coach does. ACTC education programmes also teach a body of knowledge behind the practice: team effectiveness models, group psychology, systemic thinking, diagnostics, conflict models, facilitation structures, change, team learning, culture and the coach’s own development. This library collects the 69 frameworks most commonly taught, in 12 knowledge areas. Each card explains the idea, how a team coach uses it, what to watch for, and which methods and situations in this guide let you practise it.

Theory linked to practice

Every framework links to the methods that put it to work. Method pages now show “Theory behind it” chips that link back here.

What is new

Cards marked New in the library add knowledge not covered elsewhere in the guide; Also in the guide cards summarise and point to the fuller treatment.

Track your learning

Tick “I can explain this” on each card. Your progress below is saved in this browser — useful when planning ACTC education hours.

A suggested ten-week study path

Weeks 1–2

Foundations

How teams work and fail: effectiveness models, group dynamics and psychological safety. Read alongside Methods 2, 6, 9 and 25.

Weeks 3–4

The system and the room

Systemic thinking and conflict and communication models — the lenses you will use in every session.

Weeks 5–6

Structures and context

Facilitation structures, culture and change, and working across cultures and virtual teams.

Weeks 7–8

Instruments and roles

Profiles and diagnostics — and above all, how to debrief them collectively and ethically.

Weeks 9–10

Learning and the coach

How teams learn and share leadership; supervision, co-coaching and evaluating impact. Prepare a supervision case.

Curricula vary by training provider. Check your programme’s syllabus and ICF’s website for current ACTC requirements. Instruments such as DiSC, MBTI, FIRO-B, TDS and Belbin require training or accreditation to administer.

1
Knowledge area 1 of 12 · 8 frameworks · 4 new

Team effectiveness models

Core frameworks for diagnosing and improving team performance

These are the maps you use before and during an engagement to decide where to look. Most programmes teach several, because each highlights different things: design conditions, stakeholder value, stages, relationships or complexity.

Most relevant ICF competenciesICF 3ICF 7

Six conditions for team effectiveness

J. Richard Hackman and Ruth Wageman
Also in the guide
The idea

Most of a team’s effectiveness comes from its design. Three essentials (a real team, a compelling direction, the right people) and three enablers (a solid structure, a supportive context, competent team coaching) predict performance better than members’ personalities or the leader’s style.

In team coaching

Test the essentials during contracting. If the team is not a real team or has no compelling direction, coaching relationships alone will disappoint. Coaching is most useful at the beginning, the midpoint and the end of a piece of work.

Watch

Don’t over-promise what coaching can fix when the design conditions are missing.

Five disciplines of systemic team coaching

Peter Hawkins
Also in the guide
The idea

High-value-creating teams master five disciplines: commissioning (what the team is asked to deliver), clarifying (its own purpose, goals and roles), co-creating (how members work together), connecting (with stakeholders) and core learning (at the centre).

In team coaching

Use it as a coverage check: many teams only work on co-creating. Ask which discipline is weakest and plan sessions accordingly.

Watch

The disciplines interact; don’t treat them as separate workstreams.

CID-CLEAR engagement process

Peter Hawkins
Also in the guide
The idea

A process for a whole engagement: Contracting, Inquiry, Diagnosis and design (the first phase), then Contracting again with the whole team, Listening, Exploring, Action and Review.

In team coaching

Use it to plan the engagement and to explain it to the sponsor. Note the second contracting phase: the first contract is with the commissioners, the second with the team itself.

Watch

It is a guide, not a rigid sequence; teams loop back.

Five dysfunctions of a team

Patrick Lencioni
New in the library
Five dysfunctions pyramidResultsAccountabilityCommitmentConflictTrust
The idea

A pyramid of five dysfunctions: absence of trust at the base, then fear of conflict, lack of commitment, avoidance of accountability, and inattention to results at the top. Each builds on the one below.

In team coaching

Easy for teams to grasp and use as a shared language. Helpful for sequencing: build trust before inviting conflict; build commitment before expecting peer accountability.

Watch

It is a popular practitioner model, not a research-validated one. Use it as a conversation starter, not a diagnosis.

The “real team” definition

Jon Katzenbach and Douglas Smith
Also in the guide
The idea

A real team is a small group with complementary skills, committed to a shared purpose, shared performance goals and a common approach, for which members hold themselves mutually accountable. They distinguish working groups, pseudo-teams, potential teams, real teams and high-performance teams.

In team coaching

Helps the group decide whether it needs to be a team at all, and on which work.

Watch

Calling a working group “not a real team” can feel like criticism; present it as a design choice.

PERILL model

David Clutterbuck
New in the library
The idea

Six interacting influences on team performance: Purpose and motivation, External systems and processes, Relationships, Internal systems and processes, Learning, and Leadership. It treats the team as a complex adaptive system in which problems in one area show up in others.

In team coaching

Use it when the presenting problem (often relationships) is probably a symptom of something else, such as unclear purpose or poor processes.

Watch

Resist fixing the symptom; trace the connections first.

GRPI model

Richard Beckhard
New in the library
GRPIGoalsRolesProcessesInterpersonalstart here
The idea

Teams fail mostly from unclear Goals, then unclear Roles, then poor Processes, and only then Interpersonal problems. Work from the top down: many “personality clashes” disappear once goals and roles are clear.

In team coaching

A quick, practical diagnostic for new teams and project teams. Ask members to rate each level and start at the highest one that is weak.

Watch

Don’t use it to dismiss genuine relationship issues.

Drexler-Sibbet Team Performance Model

Allan Drexler, David Sibbet and Russ Forrester
New in the library
Drexler-Sibbet seven stagesCreatingSustaining1OrientationWhy am I here?2TrustbuildingWho are you?3GoalclarificationWhat are we doing?4CommitmentHow will we do it?5ImplementationWho does what?6HighperformanceWow!7RenewalWhy continue?
The idea

Seven stages, each with a key question: Orientation (why am I here?), Trust building (who are you?), Goal clarification (what are we doing?), Commitment (how will we do it?), Implementation (who does what, when, where?), High performance (wow!), and Renewal (why continue?).

In team coaching

Diagnose which unanswered question is blocking the team. A team stuck at implementation may really have an unresolved commitment question.

Watch

Like all stage models, teams loop back when something changes.

2
Knowledge area 2 of 12 · 4 frameworks · 4 new

Team roles and personality frameworks

Tools that help teams understand contribution styles

Profiles give teams a shared, non-blaming vocabulary for differences. Used well, they explain friction and reveal missing contributions. Used badly, they put people in boxes. ICF ethics apply: use instruments you are qualified in, with consent, for development not selection.

Most relevant ICF competenciesICF 4ICF 6

Belbin Team Roles

Meredith Belbin
New in the library
Belbin roles in three clustersThinkingPlantMonitorEvaluatorSpecialistActionShaperImplementerCompleterFinisherPeopleCoordinatorTeamworkerResourceInvestigator
The idea

Nine roles in three clusters. Thinking: Plant, Monitor Evaluator, Specialist. Action: Shaper, Implementer, Completer Finisher. People: Coordinator, Teamworker, Resource Investigator. Each role has typical strengths and “allowable weaknesses”.

In team coaching

Map the team’s role profile to see overloaded and missing roles. Use it to explain recurring friction (e.g. Shapers and Teamworkers) and to agree who will consciously cover a missing role.

Watch

Roles are behavioural preferences, not fixed types. Avoid labelling people in front of the team.

Team Management Wheel

Charles Margerison and Dick McCann
New in the library
The idea

Eight work preferences around a wheel — Reporter-Adviser, Creator-Innovator, Explorer-Promoter, Assessor-Developer, Thruster-Organiser, Concluder-Producer, Controller-Inspector, Upholder-Maintainer — with Linking skills at the centre, which everyone needs.

In team coaching

Useful for linking preferences to the types of work the team must do, and for discussing how work is allocated.

Watch

Preferences are not abilities.

Team versions of DiSC, Insights Discovery and MBTI

Various publishers
New in the library
The idea

Personality-style tools adapted for teams. DiSC uses Dominance, influence, Steadiness and Conscientiousness; Insights Discovery uses four colour energies; MBTI uses four preference pairs. Team reports show the team’s overall style and likely blind spots.

In team coaching

Good for building self-awareness and empathy early in an engagement (see user manuals). Debrief collectively: “What does our team profile make easy, and what does it make hard?”

Watch

MBTI’s reliability is debated and it is often over-interpreted; never use any of these for selection or to explain away behaviour.

CliftonStrengths team reports

Gallup
New in the library
The idea

Each member’s top talent themes (from 34) are grouped into four domains — Executing, Influencing, Relationship Building and Strategic Thinking — and combined into a team grid.

In team coaching

A strengths-based way to discuss contribution, ideal alongside appreciative inquiry. Ask which domain is crowded, which is thin, and how strengths can be aimed at the team’s current challenge.

Watch

Strengths overused become weaknesses; discuss both.

3
Knowledge area 3 of 12 · 7 frameworks · 6 new

Team diagnostic instruments

Structured assessment tools and how to debrief them collectively

Instruments give the team a shared mirror and a baseline for evaluation. The skill is less in the instrument than in the collective debrief: presenting data as a mirror, letting the team make meaning, protecting anonymity and preparing the leader.

Most relevant ICF competenciesICF 1ICF 7

Team Diagnostic Survey (TDS)

Ruth Wageman, J. Richard Hackman and Erin Lehman
Also in the guide
The idea

A research-based survey that measures the six team conditions and indicators of team effectiveness.

In team coaching

Use it to see whether the team’s problems are design problems (direction, structure, people, context) before coaching on process.

Watch

Requires accreditation; results are about conditions, not individuals.

Team Diagnostic Assessment

Team Coaching International (Phillip Sandahl, Alexis Phillips)
New in the library
The idea

Measures team strengths on two dimensions: productivity (task-related) and positivity (relationship-related), with comparisons between members’ views.

In team coaching

The productivity–positivity balance is an accessible starting point; the spread of scores often matters more than averages.

Watch

Don’t let the team chase scores instead of conversations.

High-Value Creating Team questionnaire

Peter Hawkins
New in the library
The idea

A questionnaire based on the five disciplines, often completed by team members and stakeholders, comparing how the team sees itself with how others see it.

In team coaching

Especially powerful for inward-looking teams: the stakeholder gap makes the case for “connecting” work.

Watch

Stakeholder data can sting; prepare the team.

Five Behaviors assessment

Wiley, based on Lencioni (with DiSC)
New in the library
The idea

Measures the team on trust, conflict, commitment, accountability and results, combined with members’ DiSC styles.

In team coaching

Fits teams already using Lencioni’s language; the DiSC element links team scores with individual styles.

Watch

Inherits the limits of the underlying model.

Aston Team Performance Inventory

Michael West and colleagues, Aston University
New in the library
The idea

A research-based inventory covering team inputs (such as task design and resources), processes (such as communication, decision-making and leadership) and outputs (performance, wellbeing, innovation).

In team coaching

Useful in healthcare and public-sector settings, where the Aston team-working programmes are well known.

Watch

Choose the instrument for the question you are asking, not the other way round.

Team Climate Inventory

Neil Anderson and Michael West
New in the library
The idea

Measures four aspects of team climate linked to innovation: vision, participative safety, task orientation (commitment to excellence) and support for innovation.

In team coaching

Good for teams expected to innovate; participative safety links closely to psychological safety work.

Watch

Climate changes quickly; time repeat measures carefully.

Team Development Measure

As listed in many curricula (attributed to Stroebel)
New in the library
The idea

A short questionnaire that tracks how far a team has developed, used for before-and-after comparisons.

In team coaching

Useful for evaluating an engagement over time alongside stakeholder feedback.

Watch

Less widely documented than other instruments; check the source and validity before using.

4
Knowledge area 4 of 12 · 7 frameworks · 5 new

Group dynamics and group psychology

Classic and practical models of how groups function

These models explain what happens below the surface of a team: stages, hidden assumptions, needs for inclusion and control, and the pull of the group on individuals. They help a coach stay calm and curious when strange group behaviour appears.

Most relevant ICF competenciesICF 5ICF 6

Tuckman’s stages

Bruce Tuckman (1965); adjourning added with Mary Ann Jensen (1977)
Also in the guide
The idea

Forming, storming, norming, performing and adjourning.

In team coaching

Normalise the stage the team is in (“storming is a stage, not a failure”) and choose methods that fit it.

Watch

Teams loop back when membership or context changes; don’t treat it as a ladder.

Punctuated equilibrium

Connie Gersick
New in the library
Punctuated equilibriumPhase 1: inertiamidpoint transitionPhase 2: new approachfinal pushprogress
The idea

Project teams often do not move through gradual stages. They set a pattern early, stay with it for the first half of their time, then go through a burst of change around the midpoint before a final push.

In team coaching

Plan a coaching session near the team’s midpoint — it is a natural window for re-thinking approach.

Watch

Applies best to teams with a fixed deadline.

Basic assumptions

Wilfred Bion
New in the library
The idea

Groups can work on their real task (“work group”) or fall into unconscious basic assumptions: dependency (waiting for a leader to rescue them), fight/flight (attacking or avoiding an enemy) and pairing (hoping two members will produce a solution).

In team coaching

When a team behaves strangely — idealising the coach, blaming an outside enemy, pinning hopes on a pair — name the pattern gently and return to the task.

Watch

Interpretations from this tradition can feel intrusive; offer them as observations and questions.

Systems psychodynamics (Tavistock tradition)

Tavistock Institute, group relations conferences
New in the library
The idea

Combines systems thinking with psychoanalytic ideas. Pays attention to boundaries, authority, role and task (often summarised as BART), and to anxieties and defences that organisations build to avoid painful work.

In team coaching

Ask: what is the primary task? Who has authority for what? Where are the boundaries unclear? What anxiety might this behaviour be defending against?

Watch

Needs training and supervision to use well.

FIRO-B and Element B

Will Schutz
New in the library
The idea

Three interpersonal needs — Inclusion, Control and Affection (later Openness) — each with an expressed and a wanted dimension. Element B updated the model with a stronger focus on self-awareness.

In team coaching

Helps explain stage-like patterns: teams first deal with inclusion (am I in?), then control (who decides?), then openness (how close?).

Watch

Use the licensed instrument only if qualified; the concepts alone are useful for conversation.

Lewin’s equation B = f(P, E)

Kurt Lewin
New in the library
The idea

Behaviour is a function of the person and their environment. You cannot explain behaviour from personality alone.

In team coaching

A short antidote to scapegoating: when the team blames one member, ask what in the environment makes that behaviour likely.

Watch

Doesn’t remove individual responsibility; it widens the view.

Groupthink, social loafing and informal roles

Irving Janis; Bibb Latané and colleagues; Kenneth Benne and Paul Sheats
Also in the guide
The idea

Groupthink: cohesive groups under pressure suppress dissent. Social loafing: people put in less effort when their contribution is not identifiable. Informal roles: members take task roles (initiator, summariser), maintenance roles (encourager, harmoniser) and self-oriented roles (blocker, dominator).

In team coaching

Pre-mortems and red teams counter groupthink; visible ownership counters loafing; naming informal roles helps the team share them.

Watch

Don’t use the labels to blame individuals.

5
Knowledge area 5 of 12 · 4 frameworks · 1 new

Systems and systemic thinking

Treating the team as a living system nested in larger systems

Systemic thinking is what most distinguishes team coaching from coaching individuals in a group. The team is a system, nested within organisational and stakeholder systems, and patterns are usually held by the system rather than by any one person.

Most relevant ICF competenciesICF 5ICF 7

The team as a nested system

Systems theory; Peter Hawkins; Peter Senge
Also in the guide
The idea

The team is a living system made of members and relationships, and itself part of larger systems — the organisation, customers, the market, society. Value is created at the boundaries between them.

In team coaching

Keep asking: whose voice is missing? What is the system asking of this team? What happens around the team that keeps the pattern in place?

Watch

“It’s the system” can become an excuse; always look for the team’s sphere of influence.

Systemic constellations and ORSC

Bert Hellinger and organisational adaptations; ORSC by Faith Fuller and Marita Fridjhon (CRR Global)
Also in the guide
The idea

Constellations use spatial representation to reveal hidden dynamics. Organisation and Relationship Systems Coaching (ORSC) develops Relationship Systems Intelligence: every voice expresses something about the system, and the relationship itself (the “third entity”) can be coached.

In team coaching

Use spatial maps and “voices of the system” exercises when words keep going round in circles.

Watch

Needs careful contracting and safety; explain clearly and offer choice.

Feedback loops and circular causality

Gregory Bateson; systems thinking (Peter Senge)
New in the library
A reinforcing loopMembers stay silentProblems surface lateLeader reacts sharplySafety dropsR
The idea

In systems, A affects B and B affects A. Reinforcing loops amplify (more silence → less safety → more silence); balancing loops resist change. Looking for loops replaces “who started it?” with “what keeps it going?”

In team coaching

Draw the loop with the team. Ask where a small change would interrupt it.

Watch

Loops are hypotheses; test them with the team’s data.

Stakeholder mapping and systemic pattern awareness

Stakeholder theory; systemic team coaching
Also in the guide
The idea

Map who depends on the team, who influences it and what each needs. Notice patterns that repeat across levels (e.g. the same conflict between the team and another team appears inside the team).

In team coaching

Use stakeholder maps in contracting and in connecting work; watch for patterns that mirror the wider organisation.

Watch

Stakeholder views must be checked with real stakeholders.

6
Knowledge area 6 of 12 · 3 frameworks · 0 new

Psychological safety and trust

Foundational conditions for high performance

Safety and trust are preconditions for almost every other method in this guide. ACTC programmes emphasise the research base, how to measure safety, and the difference between safety and comfort.

Most relevant ICF competenciesICF 4

Edmondson’s research and seven-item scale

Amy Edmondson (1999 onwards)
Also in the guide
The idea

Team psychological safety is a shared belief that the team is safe for interpersonal risk-taking. Her seven-item survey asks, for example, whether mistakes are held against people, whether members can raise problems and tough issues, and whether it is safe to take a risk. High safety plus high standards creates a learning zone.

In team coaching

Use a short anonymous safety check early and at the midpoint; compare the leader’s rating with the team’s.

Watch

Safety is not comfort or niceness; it often means more productive discomfort.

Google’s Project Aristotle

Google People Analytics (2012–2015)
Also in the guide
The idea

Google studied 180 of its teams and found that who was on a team mattered less than how the team worked together. Five dynamics stood out: psychological safety (the most important), dependability, structure and clarity, meaning, and impact.

In team coaching

A credible business case for sponsors who doubt the value of “soft” work. The five dynamics also make a simple check-list.

Watch

Findings came from one company’s context; treat them as supportive evidence, not universal law.

Vulnerability-based trust

Patrick Lencioni
Also in the guide
The idea

Trust that comes from members being willing to admit weaknesses, mistakes and needs for help, confident that others will not use them against them. Distinct from predictive trust (“I know what you’ll do”).

In team coaching

Leaders going first with vulnerability (a mistake, a doubt) makes it easier for members. Personal histories and failure stories build it gradually.

Watch

Vulnerability must be invited, not demanded, and adapted to culture.

7
Knowledge area 7 of 12 · 8 frameworks · 4 new

Conflict and communication models

Practical tools for handling tension and improving dialogue

Teams need language for tension. These models help members see their conflict habits, understand what threatens them in a conversation, and talk about difficult things without attacking each other.

Most relevant ICF competenciesICF 4ICF 6ICF 7

Thomas-Kilmann conflict modes

Kenneth Thomas and Ralph Kilmann
Also in the guide
Thomas-Kilmann conflict modesCooperativeness →Assertiveness →CompetingCollaboratingCompromisingAvoidingAccommodating
The idea

Five modes on two axes — assertiveness and cooperativeness: competing, collaborating, compromising, avoiding and accommodating. Every mode is useful in some situations; problems come from over-using one.

In team coaching

Map the team’s preferred modes. A team of accommodators avoids debate; a team of competitors escalates. Agree which mode suits which kind of decision.

Watch

Modes are habits, not identities.

Lencioni’s conflict continuum

Patrick Lencioni
New in the library
Conflict continuumArtificial harmonyPersonal attacksIdeal conflict pointpassionate debate about ideasmost teams
The idea

A line from artificial harmony (no conflict) to mean-spirited personal attacks. The ideal conflict point sits in the middle: passionate debate about ideas without personal attack. Most teams sit too far towards harmony.

In team coaching

Ask the team to mark where it usually sits and where it wants to be. Then agree norms that move it towards the ideal point.

Watch

Moving a fearful team towards debate needs safety first.

SCARF model

David Rock
New in the library
SCARFSStatusCCertaintyAAutonomyRRelatednessFFairnessEach domain can feel like a threat or a reward
The idea

Five social domains the brain treats like threats or rewards: Status, Certainty, Autonomy, Relatedness and Fairness. A conversation that threatens one of these can trigger defensiveness, whatever its content.

In team coaching

Diagnose why a reasonable proposal caused a strong reaction (e.g. a reorganisation threatens certainty and status). Design changes and conversations that protect these domains.

Watch

The neuroscience is simplified; use it as a practical lens.

Transactional Analysis

Eric Berne
New in the library
The idea

People communicate from Parent, Adult or Child ego states. Crossed transactions (Parent to Child when Adult to Adult was expected) cause friction; “games” are repeated patterns with a predictable bad ending. TA also gave coaching contracting and the drama triangle.

In team coaching

Notice the ego state a team conversation is happening in — e.g. the leader in critical Parent, the team in adapted Child — and invite Adult-to-Adult dialogue.

Watch

Keep the language simple and non-clinical.

Nonviolent Communication (NVC)

Marshall Rosenberg
New in the library
The idea

Four components: observations (without evaluation), feelings, needs and requests. It separates what happened from the judgment about it, and turns complaints into requests.

In team coaching

A simple structure for feedback rounds and repair conversations: “When I saw…, I felt…, because I need…, would you be willing to…?”

Watch

Can sound scripted; encourage the spirit rather than the formula.

8
Knowledge area 8 of 12 · 7 frameworks · 3 new

Facilitation methods for teams

Structured approaches to collective dialogue and decision-making

Team coaches borrow structures from facilitation to make sure every voice is heard and decisions are real. ICF expects you to be open when you move into a more facilitative or directive mode, and to keep ownership of content with the team.

Most relevant ICF competenciesICF 1ICF 4ICF 8

Liberating Structures

Henri Lipmanowicz and Keith McCandless
New in the library
The idea

A collection of 33 simple microstructures that include everyone. Examples: 1-2-4-All (think alone, in pairs, in fours, then whole group), TRIZ (list what would guarantee the worst result, then stop doing it), 15% Solutions (what can you do now without permission?) and Troika Consulting (peer coaching in threes).

In team coaching

Use 1-2-4-All whenever a few voices dominate; TRIZ for stop-doing work; 15% Solutions for teams waiting for permission; Troika for building peer coaching.

Watch

Structures support coaching; they are not a substitute for it.

Open Space and World Café

Harrison Owen; Juanita Brown and David Isaacs
New in the library
The idea

Open Space: participants create the agenda themselves and move freely between conversations (“the law of two feet”). World Café: rounds of small-table conversations on shared questions, with people moving between tables and harvesting insights.

In team coaching

Good for large teams, teams of teams or stakeholder sessions where you want many voices and self-organisation.

Watch

Needs a clear question and a good harvest, or energy dissipates.

Force-field analysis

Kurt Lewin
New in the library
Force-field analysiscurrent stateDriving forcesRestraining forcesCustomer pressureOld habitsLeader supportFear of blameShared goalNo time
The idea

List the driving forces pushing towards a change and the restraining forces holding it back. Change usually comes more easily from reducing restraining forces than from pushing harder.

In team coaching

Use it when a team agrees on a goal but keeps not moving; combine with immunity to change for the hidden restraining forces.

Watch

Score forces honestly, including the team’s own habits.

Team charters and working agreements

Team effectiveness and facilitation practice
Also in the guide
The idea

Explicit documents covering purpose, goals, roles, norms and decision processes. Working agreements focus on behaviour in meetings and sessions.

In team coaching

See Methods 4 and 6. A full charter is useful for new and project teams.

Watch

A charter nobody revisits is decoration.

Decision-rights tools (RACI, DACI)

Project management practice
Also in the guide
The idea

RACI: Responsible, Accountable, Consulted, Informed. DACI: Driver, Approver, Contributors, Informed — designed specifically for decisions, with one approver.

In team coaching

See Method 35. DACI is often simpler for decisions because it forces a single approver.

Watch

Start with the few decisions that cause the most friction.

9
Knowledge area 9 of 12 · 4 frameworks · 2 new

Organisational culture and change

The context in which teams operate

Teams change inside organisations that are also changing. Understanding culture and change models helps the coach help the team make sense of what is happening to it — and what it can influence.

Most relevant ICF competenciesICF 7ICF 8

Schein’s levels of culture

Edgar Schein
New in the library
Schein levels of cultureArtefactsEspoused valuesBasic assumptionsvisibleinvisible, taken for granted
The idea

Three levels: artefacts (what you can see and hear), espoused beliefs and values (what people say they value), and basic underlying assumptions (taken-for-granted beliefs that really drive behaviour). Real culture lives at the deepest level.

In team coaching

When the team’s stated values and its behaviour don’t match, look for the underlying assumption — then test it.

Watch

Assumptions are best surfaced by the team, not announced by the coach.

Kotter’s and Lewin’s change models

John Kotter; Kurt Lewin
New in the library
The idea

Lewin: unfreeze, change, refreeze. Kotter’s eight steps: create urgency, build a guiding coalition, form a vision, communicate it, empower action by removing barriers, generate short-term wins, consolidate gains, and anchor changes in the culture.

In team coaching

Help the team locate where it is in a change programme, and which step is missing (often short-term wins or anchoring).

Watch

Planned-change models can underplay emotion; pair them with Bridges.

Bridges’ Transitions model

William Bridges
Also in the guide
Bridges transitionsEndingNeutralzoneNewbeginningletting goconfusion and creativitynew identityThe phases overlap and people move at different speeds
The idea

Change is the external event; transition is the inner psychological process. Transitions start with an ending (letting go), move through a neutral zone (confusion and creativity) and only then reach a new beginning.

In team coaching

Ask the team what is ending for it, and honour that before asking for commitment to the new. The neutral zone is a good time for experiments.

Watch

Different members move through the phases at different speeds.

10
Knowledge area 10 of 12 · 7 frameworks · 4 new

Team learning and collective leadership

How teams learn and share leadership

The lasting outcome of team coaching is a team that learns and leads itself. These models describe how learning happens and how leadership can be shared rather than sitting with one person.

Most relevant ICF competenciesICF 7ICF 8

Action Learning

Reg Revans
New in the library
The idea

Learning comes from programmed knowledge plus questioning (L = P + Q). Small groups (“sets”) work on real problems, asking questions rather than giving advice, and take action between meetings.

In team coaching

Peer coaching triads and question-only rounds are forms of action learning that build the team’s self-coaching capacity.

Watch

Keep the focus on questions; advice creeps in quickly.

Kolb’s experiential learning cycle

David Kolb
New in the library
Kolb learning cycleConcrete experienceReflective observationAbstract conceptualisationActive experimentation↻
The idea

Learning moves through four stages: concrete experience, reflective observation, abstract conceptualisation and active experimentation.

In team coaching

Design sessions and engagements around the full cycle: experiences between sessions, reflection in sessions, sense-making, and new experiments.

Watch

Teams often skip reflection; that is where the coach adds most.

Double-loop learning

Chris Argyris and Donald Schön
Also in the guide
The idea

Single-loop learning changes actions to reach the same goal; double-loop learning questions the assumptions and goals behind the actions.

In team coaching

Ask not only “what will we do differently?” but “what did we assume that turned out wrong?”

Watch

Double-loop learning feels threatening; build safety first.

Coaching the team leader alongside the team

Leadership team coaching practice
Also in the guide
The idea

Leaders often receive individual coaching in parallel with team coaching, so they can reflect on their impact and practise new behaviours.

In team coaching

See Method 32. Agree boundaries with the leader and the team.

Watch

Dual roles create confidentiality risks; consider a separate coach.

Shared and distributed leadership

Craig Pearce and Jay Conger and others
New in the library
The idea

Leadership as a set of functions (direction, coordination, challenge, support) that can be shared across members rather than held by one person.

In team coaching

Ask which leadership functions the team needs and who could take them; rotate facilitation and process observation.

Watch

Shared leadership still needs clarity about final authority.

Theory U and the learning organisation

Otto Scharmer; Peter Senge
New in the library
The idea

Theory U describes moving from downloading old patterns to sensing, presencing (connecting to what wants to emerge) and prototyping. It distinguishes four levels of listening: downloading, factual, empathic and generative. Senge’s five disciplines are personal mastery, mental models, shared vision, team learning and systems thinking.

In team coaching

Use the levels of listening to help the team notice how it listens; use Senge’s disciplines to frame long-term learning goals.

Watch

Can feel abstract; anchor it in concrete practices.

11
Knowledge area 11 of 12 · 5 frameworks · 2 new

Diversity, culture and context

Coaching teams across cultures, locations and ways of working

Modern teams are multicultural, distributed and often agile. A team coach needs frameworks for cultural difference, power and inclusion, and practical skills for virtual and agile settings.

Most relevant ICF competenciesICF 2ICF 4

Hofstede’s cultural dimensions

Geert Hofstede
New in the library
The idea

Dimensions on which national cultures differ on average: power distance, individualism versus collectivism, motivation towards achievement (originally called masculinity–femininity), uncertainty avoidance, long-term orientation and indulgence.

In team coaching

Useful to anticipate differences in hierarchy, directness and risk tolerance.

Watch

Dimensions describe national averages, not individuals. Always ask the person.

The Culture Map

Erin Meyer
Also in the guide
The idea

Eight scales for workplace behaviour: communicating (low to high context), evaluating (direct to indirect negative feedback), persuading, leading (egalitarian to hierarchical), deciding (consensual to top-down), trusting (task-based to relationship-based), disagreeing (confrontational to avoids confrontation) and scheduling (linear to flexible time).

In team coaching

Ask members to place themselves on the scales; compare as a team and agree norms for feedback, decisions and disagreement.

Watch

Positions are relative: “direct” depends on whom you compare with.

Inclusion and power dynamics

Inclusion research; Deep Democracy; group relations
Also in the guide
The idea

Rank, role, identity and majority status shape who speaks, who is heard and whose ideas are adopted. Inclusion means every member can contribute fully, not only attend.

In team coaching

Track airtime and whose ideas are built on; invite minority voices; make the leader’s power discussable.

Watch

The coach has rank too; notice your own influence.

Virtual, hybrid and global teams

Remote and hybrid team research and practice
Also in the guide
The idea

Distance reduces informal communication, increases misunderstanding and creates in-room/remote inequality. Successful virtual teams make norms explicit and design communication deliberately.

In team coaching

Agree norms (cameras, channels, time zones), use writing-first and digital whiteboards, keep sessions shorter.

Watch

Don’t assume co-located norms transfer.

Agile and self-managing teams

Scrum (Ken Schwaber and Jeff Sutherland); Lyssa Adkins’ “Coaching Agile Teams”
New in the library
The idea

Agile teams work in short cycles with built-in reflection (retrospectives). Scrum defines a product owner, a scrum master and developers. Agile coaches combine teaching, facilitation and coaching.

In team coaching

Build on existing ceremonies — retrospectives, planning — rather than adding new meetings; clarify how team coaching differs from the scrum master’s role.

Watch

Agile frameworks can become rituals without reflection.

12
Knowledge area 12 of 12 · 5 frameworks · 2 new

Coach development, supervision and evaluation

The team coach’s own practice and how impact is measured

ACTC requires coaching supervision, and team coaching places heavy demands on the coach. This area covers how to reflect on your practice, work with a co-coach, use yourself as an instrument and show the value of the work.

Most relevant ICF competenciesICF 1ICF 2ICF 5

Seven-eyed model of supervision

Peter Hawkins and Robin Shohet
New in the library
Seven-eyed modelCoaching sessionSupervision12345671 team · 2 interventions · 3 relationship · 4 coach5 parallel process · 6 supervisor · 7 wider context
The idea

Seven perspectives in supervision: (1) the client team, (2) the coach’s interventions, (3) the relationship between coach and team, (4) the coach themselves, (5) parallel process — the coach–team dynamic showing up in supervision, (6) the supervisor’s own reactions, and (7) the wider context.

In team coaching

Bring a session to supervision and look at it through several eyes, especially 3, 4 and 5, which are easy to miss alone.

Watch

Use the eyes as prompts, not a checklist.

Use of self and parallel process

Gestalt and psychodynamic traditions; supervision literature
Also in the guide
The idea

The coach’s own reactions are data about the system. Parallel process: the dynamics of the team can be unconsciously reproduced between coach and team, or between coach and supervisor.

In team coaching

Notice when you feel what the team might be feeling (stuck, rushed, excluded) and offer it tentatively.

Watch

Your reactions can also be your own; check in supervision.

Ethics specific to team coaching

ICF Code of Ethics; ICF Team Coaching Competency 1
Also in the guide
The idea

Confidentiality across members and sponsors, multiple loyalties, and the boundary between coaching and other modalities.

In team coaching

See the ethics section.

Watch

Agree confidentiality layers before the first interview.

Evaluating impact: Kirkpatrick’s four levels and ROI

Donald Kirkpatrick; Jack Phillips (ROI)
New in the library
Kirkpatrick levels5 · ROI (Phillips)4 · Results3 · Behaviour2 · Learning1 · Reaction
The idea

Four levels: reaction (how members found the sessions), learning (what they understood), behaviour (what changed in how the team works) and results (business outcomes). Phillips adds a fifth level: return on investment.

In team coaching

Agree at contracting which levels you will measure. For team coaching, levels 3 and 4 — observed behaviour change and stakeholder-visible results — matter most to sponsors.

Watch

ROI estimates involve assumptions; agree them with the sponsor upfront.

Quick reference: all 69 frameworks

AreaFrameworkIn one lineMethods
1Six conditions for team effectivenessJ. Richard Hackman and Ruth WagemanMost of a team’s effectiveness comes from its design.2635
1Five disciplines of systemic team coachingPeter HawkinsHigh-value-creating teams master five disciplines: commissioning (what the team is asked to deliver), clarifying (its own purpose, goals and roles), co-creating (how members work together), connecting (with stakeholders) and core learning (at the centre).6164746
1CID-CLEAR engagement processPeter HawkinsA process for a whole engagement: Contracting, Inquiry, Diagnosis and design (the first phase), then Contracting again with the whole team, Listening, Exploring, Action and Review.1874348
1Five dysfunctions of a teamPatrick LencioniA pyramid of five dysfunctions: absence of trust at the base, then fear of conflict, lack of commitment, avoidance of accountability, and inattention to results at the top.2627364140
1The “real team” definitionJon Katzenbach and Douglas SmithA real team is a small group with complementary skills, committed to a shared purpose, shared performance goals and a common approach, for which members hold themselves mutually accountable.2
1PERILL modelDavid ClutterbuckSix interacting influences on team performance: Purpose and motivation, External systems and processes, Relationships, Internal systems and processes, Learning, and Leadership.635444632
1GRPI modelRichard BeckhardTeams fail mostly from unclear Goals, then unclear Roles, then poor Processes, and only then Interpersonal problems.6393527
1Drexler-Sibbet Team Performance ModelAllan Drexler, David Sibbet and Russ ForresterSeven stages, each with a key question: Orientation (why am I here?), Trust building (who are you?), Goal clarification (what are we doing?), Commitment (how will we do it?), Implementation (who does what, when, where?), High performance (wow!), and Renewal (why continue?).42633354046
2Belbin Team RolesMeredith BelbinNine roles in three clusters.263910
2Team Management WheelCharles Margerison and Dick McCannEight work preferences around a wheel — Reporter-Adviser, Creator-Innovator, Explorer-Promoter, Assessor-Developer, Thruster-Organiser, Concluder-Producer, Controller-Inspector, Upholder-Maintainer — with Linking skills at the centre, which everyone needs.3926
2Team versions of DiSC, Insights Discovery and MBTIVarious publishersPersonality-style tools adapted for teams.2629
2CliftonStrengths team reportsGallupEach member’s top talent themes (from 34) are grouped into four domains — Executing, Influencing, Relationship Building and Strategic Thinking — and combined into a team grid.2026
3Team Diagnostic Survey (TDS)Ruth Wageman, J. Richard Hackman and Erin LehmanA research-based survey that measures the six team conditions and indicators of team effectiveness.82
3Team Diagnostic AssessmentTeam Coaching International (Phillip Sandahl, Alexis Phillips)Measures team strengths on two dimensions: productivity (task-related) and positivity (relationship-related), with comparisons between members’ views.8
3High-Value Creating Team questionnairePeter HawkinsA questionnaire based on the five disciplines, often completed by team members and stakeholders, comparing how the team sees itself with how others see it.81647
3Five Behaviors assessmentWiley, based on Lencioni (with DiSC)Measures the team on trust, conflict, commitment, accountability and results, combined with members’ DiSC styles.82627
3Aston Team Performance InventoryMichael West and colleagues, Aston UniversityA research-based inventory covering team inputs (such as task design and resources), processes (such as communication, decision-making and leadership) and outputs (performance, wellbeing, innovation).8
3Team Climate InventoryNeil Anderson and Michael WestMeasures four aspects of team climate linked to innovation: vision, participative safety, task orientation (commitment to excellence) and support for innovation.825
3Team Development MeasureAs listed in many curricula (attributed to Stroebel)A short questionnaire that tracks how far a team has developed, used for before-and-after comparisons.848
4Tuckman’s stagesBruce Tuckman (1965); adjourning added with Mary Ann Jensen (1977)Forming, storming, norming, performing and adjourning.4273541483
4Punctuated equilibriumConnie GersickProject teams often do not move through gradual stages.43740
4Basic assumptionsWilfred BionGroups can work on their real task (“work group”) or fall into unconscious basic assumptions: dependency (waiting for a leader to rescue them), fight/flight (attacking or avoiding an enemy) and pairing (hoping two members will produce a solution).9191314
4Systems psychodynamics (Tavistock tradition)Tavistock Institute, group relations conferencesCombines systems thinking with psychoanalytic ideas.35321314
4FIRO-B and Element BWill SchutzThree interpersonal needs — Inclusion, Control and Affection (later Openness) — each with an expressed and a wanted dimension.53526
4Lewin’s equation B = f(P, E)Kurt LewinBehaviour is a function of the person and their environment.212216
4Groupthink, social loafing and informal rolesIrving Janis; Bibb Latané and colleagues; Kenneth Benne and Paul SheatsGroupthink: cohesive groups under pressure suppress dissent.3427401015
5The team as a nested systemSystems theory; Peter Hawkins; Peter SengeThe team is a living system made of members and relationships, and itself part of larger systems — the organisation, customers, the market, society.16647
5Systemic constellations and ORSCBert Hellinger and organisational adaptations; ORSC by Faith Fuller and Marita Fridjhon (CRR Global)Constellations use spatial representation to reveal hidden dynamics.122816
5Feedback loops and circular causalityGregory Bateson; systems thinking (Peter Senge)In systems, A affects B and B affects A.102218
5Stakeholder mapping and systemic pattern awarenessStakeholder theory; systemic team coachingMap who depends on the team, who influences it and what each needs.61647
6Edmondson’s research and seven-item scaleAmy Edmondson (1999 onwards)Team psychological safety is a shared belief that the team is safe for interpersonal risk-taking.258
6Google’s Project AristotleGoogle People Analytics (2012–2015)Google studied 180 of its teams and found that who was on a team mattered less than how the team worked together.25356
6Vulnerability-based trustPatrick LencioniTrust that comes from members being willing to admit weaknesses, mistakes and needs for help, confident that others will not use them against them.262532
7Thomas-Kilmann conflict modesKenneth Thomas and Ralph KilmannFive modes on two axes — assertiveness and cooperativeness: competing, collaborating, compromising, avoiding and accommodating.2731
7Lencioni’s conflict continuumPatrick LencioniA line from artificial harmony (no conflict) to mean-spirited personal attacks.27425
7SCARF modelDavid RockFive social domains the brain treats like threats or rewards: Status, Certainty, Autonomy, Relatedness and Fairness.222531
7Karpman Drama TriangleStephen KarpmanVictim, persecutor and rescuer roles that keep conflict going.19
7Transactional AnalysisEric BernePeople communicate from Parent, Adult or Child ego states.32191
7Nonviolent Communication (NVC)Marshall RosenbergFour components: observations (without evaluation), feelings, needs and requests.29313930
7Ladder of inferenceChris Argyris; popularised by Peter SengeThe steps from observable data to beliefs and actions.22
7Kantor’s four-player modelDavid KantorMove, follow, oppose and bystand.10
8Appreciative InquiryDavid Cooperrider and Suresh SrivastvaDiscovery, dream, design and destiny: studying what works to create more of it.20
8Liberating StructuresHenri Lipmanowicz and Keith McCandlessA collection of 33 simple microstructures that include everyone.538412815
8Open Space and World CaféHarrison Owen; Juanita Brown and David IsaacsOpen Space: participants create the agenda themselves and move freely between conversations (“the law of two feet”).16746
8Force-field analysisKurt LewinList the driving forces pushing towards a change and the restraining forces holding it back.184038
8Consensus and gradients of agreementSam Kaner and colleaguesScales that show real levels of support rather than yes/no.362837
8Team charters and working agreementsTeam effectiveness and facilitation practiceExplicit documents covering purpose, goals, roles, norms and decision processes.4635
8Decision-rights tools (RACI, DACI)Project management practiceRACI: Responsible, Accountable, Consulted, Informed.353937
9Schein’s levels of cultureEdgar ScheinThree levels: artefacts (what you can see and hear), espoused beliefs and values (what people say they value), and basic underlying assumptions (taken-for-granted beliefs that really drive behaviour).131822
9Kotter’s and Lewin’s change modelsJohn Kotter; Kurt LewinLewin: unfreeze, change, refreeze.334044
9Bridges’ Transitions modelWilliam BridgesChange is the external event; transition is the inner psychological process.1153345
9Polarity ManagementBarry JohnsonInterdependent pairs that must be managed over time rather than solved.17
10Action LearningReg RevansLearning comes from programmed knowledge plus questioning (L = P + Q).41942
10Kolb’s experiential learning cycleDavid KolbLearning moves through four stages: concrete experience, reflective observation, abstract conceptualisation and active experimentation.40434642
10Double-loop learningChris Argyris and Donald SchönSingle-loop learning changes actions to reach the same goal; double-loop learning questions the assumptions and goals behind the actions.461822
10After-action reviewsUS ArmyIntended, actual, why, next time.4342
10Coaching the team leader alongside the teamLeadership team coaching practiceLeaders often receive individual coaching in parallel with team coaching, so they can reflect on their impact and practise new behaviours.32
10Shared and distributed leadershipCraig Pearce and Jay Conger and othersLeadership as a set of functions (direction, coordination, challenge, support) that can be shared across members rather than held by one person.41483542
10Theory U and the learning organisationOtto Scharmer; Peter SengeTheory U describes moving from downloading old patterns to sensing, presencing (connecting to what wants to emerge) and prototyping.9334624
11Hofstede’s cultural dimensionsGeert HofstedeDimensions on which national cultures differ on average: power distance, individualism versus collectivism, motivation towards achievement (originally called masculinity–femininity), uncertainty avoidance, long-term orientation and indulgence.264
11The Culture MapErin MeyerEight scales for workplace behaviour: communicating (low to high context), evaluating (direct to indirect negative feedback), persuading, leading (egalitarian to hierarchical), deciding (consensual to top-down), trusting (task-based to relationship-based), disagreeing (confrontational to avoids confrontation) and scheduling (linear to flexible time).26429
11Inclusion and power dynamicsInclusion research; Deep Democracy; group relationsRank, role, identity and majority status shape who speaks, who is heard and whose ideas are adopted.28532915
11Virtual, hybrid and global teamsRemote and hybrid team research and practiceDistance reduces informal communication, increases misunderstanding and creates in-room/remote inequality.444123
11Agile and self-managing teamsScrum (Ken Schwaber and Jeff Sutherland); Lyssa Adkins’ “Coaching Agile Teams”Agile teams work in short cycles with built-in reflection (retrospectives).4344403
12Seven-eyed model of supervisionPeter Hawkins and Robin ShohetSeven perspectives in supervision: (1) the client team, (2) the coach’s interventions, (3) the relationship between coach and team, (4) the coach themselves, (5) parallel process — the coach–team dynamic showing up in supervision, (6) the supervisor’s own reactions, and (7) the wider context.932
12Co-coachingTeam coaching practice; ICF Team Coaching Competency 5Working in pairs, with agreed roles (lead and observe, content and process).91
12Use of self and parallel processGestalt and psychodynamic traditions; supervision literatureThe coach’s own reactions are data about the system.91314
12Ethics specific to team coachingICF Code of Ethics; ICF Team Coaching Competency 1Confidentiality across members and sponsors, multiple loyalties, and the boundary between coaching and other modalities.1832
12Evaluating impact: Kirkpatrick’s four levels and ROIDonald Kirkpatrick; Jack Phillips (ROI)Four levels: reaction (how members found the sessions), learning (what they understood), behaviour (what changed in how the team works) and results (business outcomes).184748

The team coach’s inner game

Everything above describes the team’s material. This part turns the same attention onto the coach. In a group, the coach’s own nervous system, preferences and blind spots are amplified: seven people are reading your face, and every nod is a signal about whose view you favour. ICF’s team competencies ask coaches to stay objective about team dynamics, to use supervision, and to move in and out of the dialogue. These six practices are disciplines you practise on yourself, in real time.

Practice 1

Staying multi-partial

The momentYou find yourself agreeing more with one member, one faction or the leader.
The practiceNotice whose side you are drifting to; deliberately get curious about the person or view you least understand.
Self-check prompts
  1. Whose words am I nodding at?
  2. Whom have I not looked at in ten minutes?
  3. What would the quietest person say about my last intervention?
  4. Is my question serving the team or a subgroup?
Multi-partiality is not neutrality. You are on everyone’s side — and on the side of the team as a whole.
Practice 2

Coaching the space between

The momentYou notice yourself coaching one member in front of the others.
The practiceTurn the question outward to the team: “What do others make of what Sam just said?”
Self-check prompts
  1. Am I having a one-to-one in public?
  2. What is happening between people right now?
  3. How could this question involve the whole team?
  4. What pattern is this person’s comment part of?
The team learns most when members respond to each other, not to the coach.
Practice 3

Moving in and out of the dialogue

The momentThe team is working well — and you feel the urge to add something.
The practiceStep out physically or verbally; let the team own the dialogue. Step in only when the pattern needs naming.
Self-check prompts
  1. Would the team get there without me?
  2. Am I intervening for them or for my sense of usefulness?
  3. What would happen if I said nothing for five minutes?
  4. When did I last step back?
A coach who is always in the dialogue becomes the team’s centre of gravity.
Practice 4

Holding the field

The momentTension rises, a member is upset, the room goes silent — and your own anxiety spikes.
The practiceBreathe, slow down, describe what is happening, and trust the team to survive the moment.
Self-check prompts
  1. What am I feeling, and whose feeling might it be?
  2. What does the team need from me now — space, structure or a pause?
  3. Am I rushing to smooth this over?
  4. What would a calm version of me say?
The team borrows your nervous system. Calm is an intervention.
Practice 5

Resisting the leader’s pull

The momentThe leader looks to you for agreement, or asks you privately for help managing the team.
The practiceAcknowledge the leader’s need, return to the contract, and coach them to raise it directly.
Self-check prompts
  1. Am I becoming the leader’s ally or messenger?
  2. What does the team see when I agree with the leader?
  3. How can I support the leader without colluding?
  4. What did we agree about my role?
Collusion feels like rapport while it is happening.
Practice 6

Using yourself as an instrument

The momentYou feel bored, confused, irritated or protective during a session.
The practiceTreat your reaction as possible data about the team; offer it tentatively if useful.
Self-check prompts
  1. What am I feeling, and when did it start?
  2. Could this be something the team is feeling but not saying?
  3. How could I offer this without imposing it?
  4. What should I take to supervision?
Your reactions are data, not truth. Offer them as questions.
Taking it to supervision. The seven-eyed model helps you look at a session from seven angles — the team, your interventions, the relationship, yourself, parallel process, your supervisor’s reactions and the wider context. Eyes 3 to 5 are where team coaches most often find what they missed. See also use of self and parallel process.

Coach Presence and Self-Supervision Lab

The coach is an instrument in the room. With a team, that instrument picks up a lot of signals at once: seven nervous systems, a leader’s authority, a sponsor’s expectations, and your own history with groups. This lab is a practical toolkit for working with yourself — before, during and after a session. It complements the inner game and the seven-eyed model.

1 · Body signals in the room

Your reactions are data — about you, about the team, or both. Notice, hypothesise, then choose a move. Don’t assume the signal is about the team; check it.

What you noticeWhat it might meanA move to try
Tight chest, shallow breathingAnxiety — yours, or the room’s fear of conflict or judgment.One slow exhale; feel your feet; slow your next sentence.
Sudden sleepiness or boredomThe team may be avoiding something; energy is being held back.Name it lightly: “I notice the energy has dropped. What’s happening?”
Strong urge to rescue or fixPull into the expert or rescuer role; the team may be in helplessness.Ask the team what they think before you offer anything.
Irritation with one memberYou may be picking up what the team feels but won’t say — or your own trigger.Get curious about that person; check for projection in supervision.
Racing thoughts, talking moreYour anxiety about being useful; possibly the team’s urgency.Pause. Ask one question. Let the silence work.
Feeling excluded or invisiblePossibly what some members feel; or the team closing ranks.Ask: “Who else might feel outside this conversation?”
Heaviness, sadnessUnacknowledged loss or disappointment in the system.Make room: “It feels heavy in here. What are we carrying?”
Excitement, urge to speed upEnthusiasm — or a flight from something difficult.Slow down and check: “Is everyone with us?”

2 · Projection and counter-transference with teams

Teams put coaches into roles — expert, ally, rescuer, scapegoat — and coaches unconsciously accept them. In therapeutic language this is transference (the team’s projection onto you) and counter-transference (your reaction). You don’t need the theory to use the idea: notice which role you are being pulled into, and choose whether to accept it.

Being made the expert

Signs The team asks you for answers and goes quiet when you don’t provide them.

Move Name the pull, offer input only by agreement, return ownership.

S10.3 Coach pulled into expert role

Becoming the leader’s ally

Signs Private chats, shared looks with the leader, members watching you both.

Move Return to the contract; coach the leader to speak directly.

S7.3 Leader wants the coach as ally

Siding with a subgroup

Signs You warm to the members who agree with you or who seem “reasonable”.

Move Get curious about the person or view you least understand.

S10.4 Coach colluding with a subgroup

Mirroring the team’s helplessness

Signs You leave sessions feeling stuck and hopeless, just like the team.

Move Treat it as data (parallel process); take it to supervision.

S2.6 Collective cynicism

Rescuing the underdog

Signs You protect a quiet or criticised member and lose multi-partiality.

Move Support the pattern change, not the person against the team.

S3.7 A scapegoat

Becoming the scapegoat

Signs The team blames the coaching for its difficulties.

Move Stay calm; explore what the team is protecting itself from.

S1.8 Cynical about coaching (“been here before”)

3 · Real-time self-regulation

One long exhale

A slow out-breath longer than the in-breath settles the nervous system within seconds.

Feet and seat

Feel your feet on the floor and your weight in the chair. It brings you back to the room.

Widen the lens

Look at the whole room, not the person speaking. You will notice the pattern instead of reacting to the content.

Name it silently

“I’m feeling rushed.” Naming a feeling to yourself reduces its pull.

Slow your voice

Speak more slowly and more quietly than you want to. The room follows.

Return to the contract

“What did we agree this session is for?” is an anchor for you and the team.

Pause the room

“Let’s take a breath before we go on.” A pause helps everyone, including you.

Lean on your co-coach

Agree a signal in advance for “take over for a moment”.

4 · Seven-eyed prompts for team coaching

Use after a session, alone, with a co-coach or in supervision. Eyes 3–5 are where team coaches most often find what they missed.

1 · The team
  • What was the team’s pattern today? Which situation was it in?
  • Whose voice was missing?
2 · My interventions
  • Which methods did I use, and why?
  • What did I not do that might have helped?
3 · The relationship
  • What role did the team put me in today?
  • How did my relationship with the leader show?
4 · Me
  • What did I feel, and when?
  • Where did I lose presence?
5 · Parallel process
  • Is something happening between me and my supervisor (or co-coach) that mirrors the team?
  • What am I avoiding saying?
6 · My supervisor
  • (For the supervisor) What do I notice in myself as I listen?
  • What image or hunch comes up?
7 · The wider context
  • What is the organisation asking of this team right now?
  • How are the sponsor and stakeholders shaping the work?

5 · Post-session self-supervision template

Twenty-minute self-supervision

  1. What was the team’s situation and pattern today?
  2. What was my best moment as a coach, and my weakest?
  3. Where did I feel a strong reaction, and what might it tell me?
  4. What role did the team (or the leader) pull me into?
  5. Where did I stay in content when process needed naming?
  6. Whose voice did I under-hear?
  7. What might be a parallel process here?
  8. What do I need to raise with the sponsor, leader or co-coach?
  9. What will I take to supervision?
  10. What will I do differently next time?

6 · Sustaining yourself

Prepare

Ten minutes before: read your contract, set an intention, breathe.

Decompress

Twenty minutes after: notes, a walk, no back-to-back meetings.

Limit load

Know how many team days a week you can do well; full-day team sessions tire more than one-to-ones.

Debrief

Debrief with your co-coach every time; with your supervisor regularly.

Boundaries

Hold the contract with sponsors and leaders kindly and firmly; ambiguity drains energy.

Learn

Keep a practice journal; one learning per session.

A note on limits. These are reflective practices for professional coaches, not therapy. If a session stirs up strong personal material, take it to supervision, and to your own therapist or support if needed. ACTC requires coaching supervision; it is also simply good care.

Working with a co-coach

ICF’s team competencies explicitly mention using a co-coach when the team and sponsors agree. Two coaches can hold more of a complex system: one leads the dialogue while the other observes process, tracks energy and notices who is being left out. But co-coaching also adds a relationship the team will watch closely — and copy.

Contract between coaches first

  • Who leads which parts of each session?
  • How will the observer intervene — signal, time-out, or only at breaks?
  • How will you disagree in front of the team, if at all?
  • Who holds which stakeholder relationships?
  • How will you debrief after each session?

Common divisions of labour

  • Lead / observe — swap roles by session or half-session.
  • Content / process — one tracks the topic, one tracks the pattern.
  • Inside / outside — one works with the team, one with stakeholders.
  • Mirror — co-coaches talk openly to each other about what they see while the team listens (a “reflecting team”).

What goes wrong

  • Competing to be the “real” coach.
  • Parallel process: the coaches start mirroring the team’s conflict.
  • Splitting: members bring different issues to each coach.
  • Unresolved disagreement leaking into sessions.

See S10.5 Co-coach disagreement.

Across the engagement

Each session follows the spine. The whole engagement has its own shape too — usually six to twelve months. Most problems at this level are easier to prevent with clear multi-party contracting than to repair later. The cycle below is a common pattern, close to Peter Hawkins’ CID-CLEAR model.

The lifecycle of a team coaching engagement1Explore andchemistryMeet sponsor and leader;check fit2Multi-partycontractPurpose, roles, reporting,confidentiality3InquiryInterviews, survey,stakeholder voices4Feedback anddesignTeam makes meaning;co-designs focus5Team sessionsSession contract; the sixfamilies6BetweensessionsExperiments, peer pairs,leader coaching7Mid-pointreviewWith team, leader andsponsor8Evaluate andendHarvest, hand over, closethe loopA team coachingengagementtypically 6–12 months

The same cycle in Hawkins’ CID-CLEAR terms

CContractingwith sponsor and leader
IInquiryinterviews, data, observation
DDiagnosis and designmake sense, design the work
CContractingwith the whole team
LListeningto the team’s story
EExploringpatterns and possibilities
AActionexperiments and commitments
RReviewlearning and next steps

See also CID-CLEAR in the Knowledge Library.

1

Explore and chemistry

Meet the sponsor and the leader separately and together. Understand why now, what they hope for, and what they fear. Explain what team coaching is and isn’t. Decide whether this is a coaching need at all — it might be a structural, training or performance issue.

2

Multi-party contract

Agree purpose, success measures, roles (coach, leader, team, sponsor, any co-coach), confidentiality layers, reporting, logistics, review points and how the engagement will end. Ratify it with the whole team in the first session.

3

Inquiry

Individual interviews with every member (and often key stakeholders), a team effectiveness survey, observation of a real team meeting. Agree in advance that interview content will be reported only as anonymised themes.

4

Feedback and design

Present themes to the team as a mirror. Let the team decide what the data means and what it wants to work on. Prepare the leader beforehand if the data concerns them.

5

Team sessions

Typically every four to eight weeks, half a day to a full day. Each has its own contract and follows the spine of a team session. Observe at least one ordinary team meeting along the way.

6

Between sessions

Experiments owned by members, peer coaching pairs or triads, optional individual coaching for the leader (with clear boundaries), and short check-ins.

7

Mid-point review

Repeat a short version of the survey or ask stakeholders what they notice. Review the contract with the team, leader and sponsor; re-contract if needed.

8

Evaluate and end

Compare against the baseline and the agreed measures, harvest learning, hand coaching functions to the team, close the loop with stakeholders and mark the ending.

Evaluating impact: agree it at the start

1 · ReactionDid members find sessions useful?Short check-out ratings
2 · LearningWhat does the team understand now?Learning harvest, reflections
3 · BehaviourWhat does the team do differently?Repeat diagnostic, observed meetings
4 · ResultsWhat changed for stakeholders and the business?Agreed measures, stakeholder pulse

Based on Kirkpatrick’s four levels — see the library card. Sponsors care most about levels 3 and 4, so agree how you will evidence them in the multi-party contract.

The Between Sessions Toolkit

Most change happens in the two to four weeks between coaching sessions, not in them. This toolkit gives the team and its leader small, practical things to do in that gap: ten-minute rituals, leader moves, observation prompts, ready-made experiments and “one thing to notice” cards. Pick a few; don’t try them all.

A rhythm for the gap

Day 1Within 24 hours

The team (not the coach) sends a short summary: decisions, experiments, owners, dates.

Week 1Start

Experiments begin. Buddies check in once. Pick one “notice” card.

Week 2Midway

Weekly pulse and commitment traffic light. Leader tries one leader move.

Week 3Adjust

Short peer coaching or action learning set. Adapt experiments that aren’t working.

Before next sessionReflect

Each member notes: what changed, what we noticed, what we want to work on next.

Ten-minute team rituals

Two-minute wins

Start one meeting a week with each member naming one win — theirs or someone else’s.

Weekly pulse

Each member posts a number (1–5) and one word on how the team is working. Discuss the spread, not the average.

Commitment traffic light

Every owner gives a green, amber or red on their experiment. Ambers and reds get help, not blame.

Five-minute process check

End one meeting a week with: what helped us today, and what would we change?

Appreciation and request

Pairs swap one thing they appreciated and one thing they’d like more of this week.

Decision recap

Close every meeting by reading back the decisions, owners and dates — and checking real agreement.

Risk minute

One minute: what could go wrong this week that nobody has mentioned?

Learning minute

Friday: one thing each of us learned this week that the team should know.

Leader moves for the fortnight

Speak last

In at least one meeting, share your view only after everyone else has spoken.

Ask “What am I missing?”

Before responding to any concern, ask this once — and wait.

Thank the first dissent

When someone disagrees with you, thank them publicly before you respond.

Delegate one decision

Hand one decision you would normally make to the team, with clear limits.

Share one mistake

Tell the team about one thing you got wrong and what you learned.

Check real agreement

End decisions with a fist-to-five or “any objections?” rather than “OK?”

Notice who hasn’t spoken

Keep a quiet tally in one meeting; invite those voices next time.

Ask a stakeholder

Ask one stakeholder what they have noticed about the team recently.

Observation prompts for the leader

Jot answers down and bring them to the next session or to leader coaching.

  1. When did the team do something we agreed in coaching without being reminded?
  2. Who stepped up this fortnight, and how did you respond?
  3. Where did an old pattern return, and what triggered it?
  4. What did you do that made candour easier — or harder?
  5. Which decision stuck, and which was reopened?
  6. What did a stakeholder notice?

Ready-made team experiments

Meeting experiment

Change one thing about one recurring meeting for two weeks.

Decision experiment

Use consent or fist-to-five on every decision in one meeting.

Voice experiment

Use 1-2-4-All for one important question.

Feedback experiment

Each member asks two colleagues for feedforward on one behaviour.

Stop experiment

Stop one report, meeting or habit for a month and see who notices.

Connection experiment

Each member has one 20-minute conversation with a stakeholder.

Pair experiment

Pair on one piece of work normally done alone.

Learning experiment

Run a 15-minute after-action review after one piece of work.

“One thing to notice” cards

Each member draws one card for the fortnight and simply notices — no fixing. Bring observations to the next session. They also work as prompts for process observers.

Notice card 1

Who speaks first in our meetings?

Notice card 2

What happens in the minute after someone disagrees?

Notice card 3

Which topic makes the room go quiet?

Notice card 4

When do we look at the leader before answering?

Notice card 5

What do we talk about in the corridor that we don’t say in meetings?

Notice card 6

Who gets interrupted most often?

Notice card 7

Which decisions get reopened?

Notice card 8

When did we last celebrate something?

Notice card 9

What do we say about other teams?

Notice card 10

Who is carrying more than their share?

Notice card 11

When did someone admit a mistake — and what happened next?

Notice card 12

Which of our agreements did we quietly break?

Notice card 13

Where did a remote colleague get left out?

Notice card 14

What did we decide by not deciding?

Notice card 15

What are we proud of never being?

Notice card 16

What would a newcomer notice about us this week?

Related methods: 40 · Team Experiments and Commitments 41 · Peer Accountability and Peer Coaching 44 · Redesign the Team Rhythm 45 · Team Rituals and Ceremonies 42 · Action Learning Sets for Intact Teams

Ethics and professional practice in team coaching

The ICF Code of Ethics applies in full. Team coaching adds particular challenges around confidentiality, multiple roles and power. Several situation cards go deeper: S10.1 Sponsor asks for a report on individuals S7.7 Leader asks coach about individuals S4.10 Disclosure of bullying or harassment in session S10.2 Member asks for private coaching mid-engagement S10.12 Interview data tempting to use S4.5 Trust breach / leak

The team is the client

Keep the team-as-entity as the client throughout. Individual members, the leader and the sponsor are stakeholders with legitimate needs, but none of them is the client alone.

Layered confidentiality

Agree three layers at the start: what members say in one-to-one interviews (themes only, never attributed), what is said in team sessions (stays in the team unless agreed), and what goes to the sponsor (agreed measures and themes, shaped with the team).

Distinct modalities

Explain how team coaching differs from training, facilitation, consulting, mentoring and team building. If you step into another mode, say so and ask permission.

Multiple roles

If you also coach the leader or a member individually, or work elsewhere in the organisation, declare it, agree boundaries and keep information separate. When in doubt, refer individual coaching to a colleague.

Assessment and data

Psychometrics and surveys must be used with consent, by qualified people, for development not selection. Individual results belong to individuals.

Not performance management

Team coaching is not a route to assess or remove individuals. Performance issues belong to the leader and HR processes. Say this clearly in contracting.

Safety and referral

Harassment, bullying, discrimination, risk of harm and clinical distress are not coaching topics. Pause, support the person, and follow agreed procedures.

Supervision

Team coaching stirs strong group dynamics in the coach. Regular supervision is an ethical requirement, not a luxury — and is required for ACTC.

Working across cultures and in virtual teams

Every method carries assumptions about directness, hierarchy, emotion, silence and the individual versus the group. In multicultural teams these assumptions differ between members, not just between coach and team. These notes are prompts for curiosity, not rules about any culture: always ask the team what fits. See also S8.3 Multicultural team S4.7 Cross-cultural misunderstanding S8.2 Hybrid friction.

#MethodWhat to adjust
5Check-in RoundsRounds can feel exposing where speaking without being asked by a senior person is unusual. Allow passes, use writing first, or start with pairs.
9Process Observation in Real TimeDescribing the team’s behaviour publicly may cause loss of face in some contexts. Ask permission, describe the pattern not the person, and consider raising it with the leader first.
13Name the UndiscussableSome cultures place high value on harmony and indirect communication. Use anonymous methods and third-person framing (“What might someone worry about?”).
25Build Psychological SafetyWhat counts as “speaking up” differs widely. Ask the team what safety and voice look like for them, rather than importing one norm.
27Make Conflict ProductiveOpen debate may feel aggressive in some cultures and normal in others. Agree explicitly how the team wants to disagree; use structured roles.
29Team Feedback RoundsPublic peer feedback may be uncomfortable where feedback is normally private or hierarchical. Start with appreciation, use written forms, or work in pairs.
32Coach the Leader in the RoomExpectations of the leader vary: in high power-distance contexts, asking the leader to speak last may need careful explanation and the leader’s visible endorsement.
36Gradients of AgreementShowing disagreement openly (e.g. fist to five) can be uncomfortable; use anonymous polls.

Virtual and hybrid team coaching

Cameras and presence

Agree norms together. “Cameras on for check-in and decisions” is a common compromise.

One remote, all remote

If anyone joins remotely, everyone joins from their own device, so access is equal.

Use the chat deliberately

Silent writing in chat before discussion gives quieter and second-language members a voice.

Shorter, more frequent

Virtual attention fades after about 90 minutes. Split full days into shorter sessions.

Visual collaboration

Online whiteboards make sculpting, timelines and polarity maps possible remotely.

Time zones

Rotate meeting times so the same members don’t always carry the inconvenience.

Practice

Spot the situation: practice exercises

Read each scenario and decide for yourself before opening the answer: which situation is this, what would you try first, and what would you avoid?

1The polite launchIn the first session, everyone agrees with everything. Interview data showed strong frustrations.Which situation, and what would you try?Show suggested answer

S1.3 Polite, flat and “fine”. Share anonymised interview themes as a mirror (Method 8) or use anonymous cards (Method 13). Avoid pushing for honesty before any safety exists.

2“It’s really about Raj”In the contracting meeting, the leader says the team would be fine if one member changed.What do you contract for, and what do you avoid?Show suggested answer

S1.4 Wants the coach to fix one person. Contract for team patterns and state that individual performance is the leader’s to manage (Method 1). Avoid adopting the leader’s diagnosis.

3The eyesBefore answering any question, members glance at the CEO.What is happening, and what is your first move?Show suggested answer

S7.5 Team defers to leader. Agree with the leader to speak last; name the pattern neutrally (Methods 32, 9). Avoid exposing the leader without preparation.

4The same argumentFor the third session running, the team debates centralising versus local freedom.What might this be, and what would help?Show suggested answer

S3.9 The same debate on loop — probably a polarity. Map both poles (Method 17). Avoid picking a side or forcing a decision.

5Seven yesesThe team agrees a new process in four minutes; nobody asks a question.What would you check before moving on?Show suggested answer

S9.2 Agreeing too easily. Use fist to five (Method 36) and a quick pre-mortem (Method 34). Avoid accepting the yes at face value.

6The corridorYou hear after the session that members “didn’t really agree” with the decision.What pattern is this, and what could you try next time?Show suggested answer

S3.3 The meeting after the meeting. Ask what will be said in the corridor; use anonymous surfacing (Method 13) and minority voice (Method 28).

7The sharp remarkA senior member says “That’s a junior idea.” The person who proposed it goes red and silent.What do you do in the next thirty seconds?Show suggested answer

S4.4 Disagreement turns personal. Pause, separate idea from person, give both space (Method 31), and refer back to working agreements (Method 4).

8The sponsor’s emailThe sponsor emails asking which members are “resistant”.How do you respond?Show suggested answer

S10.1 Sponsor asks for a report on individuals. Restate the contract and offer team-level themes and measures (Method 1). Never share individual information.

9Monday morningSessions are energising, but each new session starts with “we didn’t get to the actions”.What would you change?Show suggested answer

S9.1 Great session, nothing changes. Shrink to one owned experiment (Method 40), embed it in an existing meeting (Method 44) and open each session by reviewing it.

10Them upstairsEvery problem the team raises is caused by head office.What could open this up?Show suggested answer

S1.11 Talks only about other teams. Empty chair for head office (Method 16), then the drama triangle (Method 19) to find the team’s sphere of influence.

11Four of sevenIn the check-in, four people say “distracted”. You learn a colleague resigned yesterday.Do you keep to the plan?Show suggested answer

S2.4 Grief after a loss (or S2.2). Re-contract live (Method 7): acknowledge the loss first, then return to the plan if the team wants to.

12Teach us somethingMembers ask for a model and some slides instead of “all these questions”.How do you respond while staying in role?Show suggested answer

S10.6 Team wants training, not coaching. Name the modality shift, offer brief input with permission, then return to coaching on how it applies.

13Everyone loves each otherThe team scores 9/10 on trust and has missed three quarterly targets. Nobody can say why.What situation might this be, and where would you start?Show suggested answer

S4.11 The team that is “too nice”. Show the safety × accountability picture and let the team place itself (Method 25); introduce feedforward (Method 30) and peer accountability (Method 41). Avoid shaming the warmth.

14The indispensable oneOne member answers every technical question, works every weekend and is praised by the leader in every meeting.What pattern is this, and how would you approach it?Show suggested answer

S6.11 Star performer or hero culture. Make it systemic: what does the team gain and lose (Method 14)? Spread capability through pairing and peer coaching (Method 41). Speak to the star privately first.

15The CEO drops inThe CEO joins your session unannounced. The team’s answers become polished and short.What do you do in the first two minutes?Show suggested answer

S7.11 Sponsor or senior stakeholder in the room. Name the change, re-contract the session and agree the CEO’s role (Method 1, Method 7). Protect confidentiality from earlier sessions.

Self-assessment

Rate your confidence with each method. Your answers stay only in this browser. The summary suggests where to focus next — useful when planning your ACTC education hours.

Rate a few methods to see your summary.

Contract and Convene

2 · Test for Team-ness
3 · Teaming for Fluid Teams
5 · Check-in Rounds
7 · Contract the Session Live

Surface the System

10 · Map Interaction Patterns
13 · Name the Undiscussable
14 · Collective Shadow
15 · Liberating Structures

Trust, Conflict and Voice

27 · Make Conflict Productive
28 · Hear the Minority Voice
29 · Team Feedback Rounds

Future and Decisions

33 · Shared Preferred Future
34 · Team Pre-Mortem
35 · Clarify Decision Rights
36 · Gradients of Agreement

Reflection and supervision prompts

Use these after a session, alone, with your co-coach or with a supervisor. Pick two or three, not all of them.

About the team

  • What situation was the team in? Was there more than one?
  • Where was the energy at the start, middle and end?
  • Who spoke, who didn’t, and how did that change?
  • What did the team say that was new?

About my choices

  • Which method did I use, and why that one?
  • When did I stay in content when process needed naming?
  • Where did I change level, and where should I have?
  • Did I coach one person in front of the team?

About me

  • Whose side did I drift towards?
  • When did I fill a silence that the team needed?
  • How did the leader’s presence affect me?
  • What was I feeling that might belong to the team?

About the system

  • How did the contract hold up? Who else needs to be in it?
  • What does the sponsor need to hear, and from whom?
  • What would the team’s stakeholders have noticed?
  • What should I bring to supervision?

Team health check (interactive)

A quick, informal self-rating to start a conversation — not a validated diagnostic. Score your team from 1 to 10 on each dimension, or ask each member to score it privately and compare. The radar updates as you move the sliders and saves in this browser. Low scores point to methods that may help.

5
5
5
5
5
5
5
5

Toolkit

Cheat sheets

Four one-page summaries to keep beside you. The print button prints only these sheets.

The six families

Which kind of move does this moment need?

Contract and ConveneIs everyone clear what this team is here to do together, and who the client is?Contract with the Three Clients, Test for Team-ness, Teaming for Fluid Teams, Co-create Working Agreements, Check-in Rounds, Purpose and Stakeholder Expectations, Contract the Session Live
Surface the SystemDoes the team see its own patterns, or only its stories about them?Diagnostic and Data Feedback, Process Observation in Real Time, Map Interaction Patterns, Team Timeline / Journey Line, Sculpt the Team (Constellations), Name the Undiscussable, Collective Shadow, Liberating Structures
Shift the Team FrameIs the team locked into one meaning of its situation?Zoom to the Ecosystem (Stakeholder Chairs), Polarity Map for Teams, Team Immunity to Change, From Drama to Empowerment, Appreciative Inquiry: What Is Working, Externalize the Team Problem, Walk Down the Ladder of Inference, Clean Language for Teams, Theory U and Presencing Practices
Trust, Conflict and VoiceCan the team say true things to each other and stay a team?Build Psychological Safety, Personal Histories and User Manuals, Make Conflict Productive, Hear the Minority Voice, Team Feedback Rounds, Feedforward and Start / Stop / Continue, Repair a Rupture in the Room, Coach the Leader in the Room
Future and DecisionsDoes the team share a picture of where it is going and how it decides?Shared Preferred Future, Team Pre-Mortem, Clarify Decision Rights, Gradients of Agreement, Consent-Based Decision Making, Prioritize and Stop Doing, Role Negotiation (Give and Get)
Land, Learn and SustainHas enough opened that it must become something the team does?Team Experiments and Commitments, Peer Accountability and Peer Coaching, Action Learning Sets for Intact Teams, After-Action Review / Retrospective, Redesign the Team Rhythm, Team Rituals and Ceremonies, Harvest Team Learning, Close the Loop with Stakeholders, Fade the Coach and End Well

The spine of a team session

Where is the team now?

ContractWhose agenda? What does the team want today?
SurfaceMake patterns visible; let the team interpret.
ShiftZoom out, both/and, hidden commitments.
ConnectSafety, real conflict, every voice.
ChooseDirection, decision rights, real support.
CommitOne owned experiment, a way to know.
In the moment: Notice → Name → Choose a family → Ask the team → Wait → Shift level

Six levels

If nothing new is coming, change level, not wording.

Content“What exactly is happening?”
Process“What do we notice about how we’re talking?”
Climate“What’s the mood in here?”
Assumptions“What are we assuming must be true?”
Identity“Who do we want to be in this?”
System“What around us keeps this going?”

End most sessions at Experiment.

Eight questions for any team

When in doubt, ask the whole team

  1. 1 What does this team need from today?
  2. 2 What do you notice about how we’re talking right now?
  3. 3 Who sees this differently?
  4. 4 What are we not saying?
  5. 5 What would our stakeholders say?
  6. 6 Is this a problem to solve or a tension to manage?
  7. 7 What would it take for everyone to come along?
  8. 8 What will we try, who owns it, and how will we know?

Templates

Checklists and agendas you can copy into your own notes.

Multi-party contracting checklist

  1. What does the sponsor need from this team, in their words?
  2. What does the leader want, and what are they willing to change themselves?
  3. What does the team want? (ratify in session 1)
  4. What is team coaching here, and what is it not (training, consulting, facilitation)?
  5. Who is the client? (the team as one entity)
  6. Confidentiality layers: interviews, sessions, sponsor reporting
  7. What will be reported, by whom, how often?
  8. Success measures and baseline
  9. Roles of leader, coach, co-coach, sponsor
  10. Number, length and format of sessions; between-session work
  11. Review points and how the engagement ends
  12. What happens if someone asks for individual information?

Team session plan

  1. Check-in round (5–15 min)
  2. Review experiments from last session
  3. Session contract: topic, outcome, team-level test
  4. Surface: data, observation or exercise
  5. Explore and shift: levels, models, reframes
  6. Decide: level of agreement, decision rights
  7. Commit: experiments, owners, success signs
  8. Process review: how did we work today?
  9. Check-out round: one word / one commitment

Individual interview guide (pre-engagement)

  1. What is this team for? Who depends on it?
  2. What is the team doing well?
  3. What gets in the way of the team performing at its best?
  4. How are decisions made? How is conflict handled?
  5. What is not discussed in the team that should be?
  6. How would stakeholders describe this team?
  7. What would you like this coaching to achieve?
  8. What would make it safe for you to speak openly in sessions?
  9. Anything else I should know? (remind: themes only, no attribution)

Working agreements starter

  1. What do we need from each other to think well here?
  2. How will we disagree?
  3. How will we treat what is said here? (confidentiality)
  4. How will we treat people who are absent?
  5. Devices, cameras, chat?
  6. How will anyone raise a broken agreement?
  7. How and when will we review these agreements?

After-action review

  1. What did we intend to happen?
  2. What actually happened?
  3. Why was there a difference?
  4. What will we keep doing?
  5. What will we change?
  6. Who needs to know what we learned?

End-of-engagement evaluation

  1. Compare with the baseline: what has changed?
  2. Which agreed measures moved? Which didn’t?
  3. What do stakeholders notice?
  4. What has the team learned about how it learns?
  5. Which coaching functions will the team now run itself?
  6. What will we review, when, and who will lead it?
  7. How do we want to mark the ending?

Quick reference: all 48 methods at a glance

#MethodFamilyCore moveICF
1Contract with the Three ClientsContractAgree outcomes with the team, the leader and the sponsor before the first session13
2Test for Team-nessContractCheck whether the group really needs to work as a team before coaching it as one137
3Teaming for Fluid TeamsContractBuild enough trust, shared purpose and a shared picture of the work — fast — when the team won’t stay together long348
4Co-create Working AgreementsContractLet the team write the rules of its own coaching space34
5Check-in RoundsContractHear every voice early, before the loudest voice sets the tone456
6Purpose and Stakeholder ExpectationsContractAsk why the team exists and who it serves before asking how it should behave378
7Contract the Session LiveContractAgree what this group wants from this session, and whose agenda it really is35
8Diagnostic and Data FeedbackSurfaceShow the team its own data and let it make the meaning37
9Process Observation in Real TimeSurfaceName what is happening between people, here and now2567
10Map Interaction PatternsSurfaceMake the team’s conversational moves visible: who moves, follows, opposes, bystands267
11Team Timeline / Journey LineSurfaceWalk the team’s history together to see where today’s patterns come from47
12Sculpt the Team (Constellations)SurfacePut the team’s relationships into space so members can see what words hide257
13Name the UndiscussableSurfaceMake it safe to say what everyone knows but nobody says47
14Collective ShadowSurfaceGently notice what the team habitually leaves out, pushes away or puts onto others27
15Liberating StructuresSurfaceUse simple, ready-made structures that include every voice and reduce the coach’s talking468
16Zoom to the Ecosystem (Stakeholder Chairs)ShiftBring the voices outside the room into the room78
17Polarity Map for TeamsShiftTurn either/or arguments into both/and management78
18Team Immunity to ChangeShiftFind the hidden commitments that keep the team from doing what it says it wants78
19From Drama to EmpowermentShiftHelp the team step out of victim, persecutor and rescuer roles47
20Appreciative Inquiry: What Is WorkingShiftBuild on the team’s best moments rather than diagnosing its worst478
21Externalize the Team ProblemShiftTurn a blamed person or vague malaise into a shared opponent7
22Walk Down the Ladder of InferenceShiftSeparate what happened from the story the team tells about it67
23Clean Language for TeamsShiftUse the team’s own words and metaphors to unlock stuck or polarised language67
24Theory U and Presencing PracticesShiftMove the team from reacting with old patterns to sensing what the situation really needs578
25Build Psychological SafetyConnectMake it safe to speak up, admit mistakes and ask for help45
26Personal Histories and User ManualsConnectBuild trust by letting members know each other as people4
27Make Conflict ProductiveConnectTurn avoided or destructive conflict into useful debate about ideas47
28Hear the Minority VoiceConnectGive voice to dissent and unspoken views before they go underground46
29Team Feedback RoundsConnectGive and receive feedback as a team, safely and specifically468
30Feedforward and Start / Stop / ContinueConnectHelp members ask for future-focused suggestions instead of judgments about the past468
31Repair a Rupture in the RoomConnectWhen trust breaks between members in session, slow down and repair before moving on45
32Coach the Leader in the RoomConnectWork with the leader’s dual role — inside the team and above it12346
33Shared Preferred FutureChooseBuild one picture of “better” that every member can see themselves in78
34Team Pre-MortemChooseImagine the plan failed, then work out why — before it does78
35Clarify Decision RightsChooseAgree who decides what, and how38
36Gradients of AgreementChooseReplace the yes/no vote with a scale that shows real levels of support68
37Consent-Based Decision MakingChooseDecide when full agreement isn’t possible: ask not “do you agree?” but “is it safe enough to try?”38
38Prioritize and Stop DoingChooseHelp the team choose fewer things — and agree what it will stop78
39Role Negotiation (Give and Get)ChooseMake expectations between members explicit and negotiate them348
40Team Experiments and CommitmentsCommitTurn insight into a small, owned experiment the whole team can see8
41Peer Accountability and Peer CoachingCommitHelp members hold each other accountable without the leader as enforcer48
42Action Learning Sets for Intact TeamsCommitStructured peer problem-solving: questions first, action between meetings, reflection on learning78
43After-Action Review / RetrospectiveCommitMake learning from experience a routine, not an accident78
44Redesign the Team RhythmCommitChange the team’s meetings and routines so new behaviours have a home8
45Team Rituals and CeremoniesCommitDesign how the team marks beginnings, endings, transitions, wins and losses48
46Harvest Team LearningCommitHelp the team notice what it has learned about how it learns78
47Close the Loop with StakeholdersCommitShare progress with stakeholders and bring their feedback back in38
48Fade the Coach and End WellCommitTransfer the coaching role to the team and close the engagement deliberately138

Quick reference: all 113 situations at a glance

Every situation on one line: what is happening, the recommended coach move, and the methods that handle it. Hover over a number to see the method’s name.

CodeSituationWhat is happeningCoach moveMethods
S1 How the team arrives 11 situations
S1.1Sent by the sponsorThe team attends because someone above asked; low ownership of the agendaName the three clients; find the team’s own stake in the work176
S1.2The leader’s agenda dressed as the team’sThe leader frames the topic; members nod but energy is elsewhereTest the agenda with the whole team before working on it7321
S1.3Polite, flat and “fine”Everyone is pleasant; nothing real is said; energy is lowName the pattern lightly; use anonymous or individual ways to surface the real material513815
S1.4Wants the coach to fix one personThe team or leader frames the problem as one memberContract for team patterns; widen from person to system1219
S1.5Too many topics at onceThe team arrives with a long list; everything feels urgentHarvest, prioritise, and test which topics need the whole team738
S1.6Firefighting / crisis modeUrgent operational issues hijack every sessionAcknowledge the crisis; separate what needs solving now from what the crisis reveals about the team7385
S1.7A group, not a teamMembers report to the same leader but rarely depend on each otherTest for team-ness; find the few genuinely collective tasks26
S1.8Cynical about coaching (“been here before”)The team has had away-days and consultants; expects another oneMake past experience into design input; promise less, deliver more1420
S1.9Newly formed teamMembers are new to each other and to the taskBuild working agreements, purpose and relationships early42663
S1.10Merged team (“us and them”)Two former teams now one; old identities persistHonour both histories, then build a shared story and purpose11262045
S1.11Talks only about other teamsEvery problem is located outside the teamZoom to the ecosystem, then explore the team’s part16192214
S2 The team’s emotional climate 11 situations
S2.1Low trustMembers protect themselves; candour is rareBuild safety in small steps; start with understanding each other25264
S2.2Fear after layoffs or restructuringMembers are anxious about their jobs; survivor guilt; silenceAcknowledge the fear; make space for what happened before moving on25511
S2.3Exhausted / burnoutMembers are depleted; coaching feels like another demandMake load visible; decide what to stop; protect energy38544
S2.4Grief after a lossA colleague has died, left suddenly or been seriously illPause the agenda; create space to acknowledge the loss5113145
S2.5Anxiety about changeUpcoming change creates worry and speculationSeparate known from unknown; build a shared preferred future; manage polarities331725
S2.6Collective cynicismThe team believes nothing will improveFind exceptions; test assumptions; start very small201840
S2.7Anger at the organisationThe team is angry about decisions made aboveAcknowledge the anger; separate venting from influence; connect to the system16195
S2.8Overconfidence / euphoriaAfter success, the team feels invincible and ignores risksCelebrate, then test with pre-mortem and outside views34816
S2.9Shame after a public failureThe team failed visibly and members feel embarrassedMake learning safe; separate identity from event; review without blame432120
S2.10Disengaged / going through the motionsMembers show up physically but not mentallyReconnect to purpose and to what each person cares about653345
S2.11Tension you could cutSomething unnamed is creating tension in the roomName the tension neutrally; ask permission to explore13931
S3 Patterns in the conversation 12 situations
S3.1One or two voices dominateA few members do most of the talkingStructure participation; make the pattern visible591015
S3.2Silent membersSome members rarely speakUse structure and invitation; understand the silence5282515
S3.3The meeting after the meetingReal conversations happen outside sessionsBring the corridor conversation into the room13436
S3.4GroupthinkThe team agrees quickly; dissent is absentLegitimise dissent; use pre-mortems and red teams34271024
S3.5Interrupting and talking overMembers cut each other offUse agreements and process observation4910
S3.6Subgroups and factionsThe team splits into campsMake the factions visible; explore their positions and needs121728
S3.7A scapegoatOne person carries blame for team problemsExternalize the problem; explore the team pattern21192214
S3.8Joking to deflectHumour shuts down serious discussionNotice the pattern lightly; invite what’s under the joke9135
S3.9The same debate on loopThe team repeats the same argument without resolutionMap the pattern or polarity; change the structure of the conversation1710923
S3.10Advice-giving instead of thinkingMembers jump to solutions for each otherSlow down; ask questions; use structured thinking954142
S3.11Remote members invisibleHybrid meetings favour those in the roomAgree hybrid norms; equalise participation4544
S3.12Innovation or creative stucknessThe team needs new ideas but keeps producing variations of old onesChange the quality of attention: sense the system freshly, include every voice, then prototype small241520
S4 Conflict and trust 11 situations
S4.1Open hostility between two membersTwo members clash openly; the team watchesSlow down; separate positions from needs; negotiate specific agreements313927
S4.2Covert conflict / passive aggressionConflict shows up as sarcasm, delays, missed deadlinesName the pattern; make it discussable; explore underlying conflict13272214
S4.3Conflict avoided at all costsThe team avoids any disagreementBuild safety and structures for productive conflict272534
S4.4Disagreement turns personalA task disagreement becomes an attack on a personPause; separate the idea from the person; restore norms27314
S4.5Trust breach / leakSomething said in confidence was shared outsideRevisit agreements; repair; rebuild confidentiality43125
S4.6Old history resurfacesPast conflicts shape current interactionsMap the history; acknowledge; decide what to carry forward113122
S4.7Cross-cultural misunderstandingDifferent cultural norms lead to misinterpretationsExplore cultural assumptions; build shared norms26224
S4.8Venting about an absent colleagueThe team criticises someone who isn’t presentRefer to agreements; refocus on the team’s part4219
S4.9Silo war with another teamConflict between this team and anotherZoom to the ecosystem; negotiate the interface16391915
S4.10Disclosure of bullying or harassment in sessionA member raises a serious allegation in the roomPause; protect the individual; follow ethical and organisational procedures31132
S4.11The team that is “too nice”Warm relationships, low challenge — and quietly declining performanceName the cost of harmony; make challenge a form of care27143025
S5 Purpose, goals and direction 10 situations
S5.1No shared purposeMembers can’t say why the team existsExplore stakeholders and purpose; create a shared statement6332
S5.2Competing prioritiesMembers pull in different directionsMake priorities visible; decide together; manage polarities38176
S5.3Goals imposed from aboveTargets set without team input; low ownershipExplore what the team can own; test assumptions; connect to stakeholders18616
S5.4Strategy unclearThe team doesn’t understand the organisation’s directionClarify what is known; connect to stakeholders; build preferred future6163324
S5.5Individual goals beat team goalsIncentives reward individuals; collaboration suffersClarify collective goals; manage the individual/team polarity2176
S5.6Disagree on what success meansMembers use different definitions of successBuild a shared preferred future; use data338623
S5.7Short-termism / always urgentThe team focuses only on immediate issuesManage the short/long polarity; protect strategic time173844
S5.8Purpose drift after successAfter achieving goals, the team loses directionRevisit purpose; harvest learning; set new goals61146
S5.9Purpose conflicts with valuesMembers feel the team’s goals clash with their valuesHear the minority voice; explore values and purpose28617
S5.10A good team that wants to become greatNo crisis, solid results — the team wants to raise its gameStart from strengths, find the next level of value for stakeholders, and stretch with small, ambitious experiments863046
S6 Roles, decisions and accountability 12 situations
S6.1Role confusionMembers are unsure who does whatNegotiate roles; clarify decision rights3935
S6.2Turf warsMembers compete for territory and authorityNegotiate roles; zoom to the ecosystem; clarify decisions391635
S6.3Decisions don’t stickDecisions are reopened repeatedlyClarify decision rights; test real agreement; hear dissent35362837
S6.4Everything escalates to the leaderThe team doesn’t decide without the leaderClarify decision rights; coach the leader to step back353241
S6.5Consensus paralysisThe team insists on consensus for everythingChoose decision styles; use gradients of agreement363537
S6.6Free ridersSome members contribute lessPeer feedback; peer accountability; role negotiation29413930
S6.7Nobody owns actionsActions are agreed but no one follows throughNamed owners; experiments; peer accountability404142
S6.8Meeting overloadToo many meetings, too little valueAudit and redesign rhythms; stop doing4438
S6.9Matrix / dual reporting tensionMembers serve two bosses; conflicting demandsNegotiate roles; manage polarities; map the system391716
S6.10Handoffs keep failingWork stalls at interfacesRole negotiation; AAR; interaction patterns39431015
S6.11A star performer or hero cultureOne person carries critical work; others defer, or resent; the system depends on a heroMake the pattern systemic rather than personal; spread capability and recognition14413929
S6.12Knowledge loss and key-person dependencyCritical knowledge lives in a few heads; departures cause crisesMake knowledge flow a team responsibility: map dependencies, pair, document and hand over by design3423944
S7 The leader and the team 11 situations
S7.1Leader dominatesThe leader talks most; the team defersContract leader role; structure participation; observe3259
S7.2Leader absent or abdicatingThe leader delegates coaching and doesn’t engageRecontract; clarify leader’s role13235
S7.3Leader wants the coach as allyThe leader tries to align the coach with their viewHold the contract; coach the leader132
S7.4New leader inherits teamA new leader takes over an existing teamTimeline; personal histories; leader role contracting11263245
S7.5Team defers to leaderMembers wait for the leader’s opinionLeader speaks last; interaction patterns; decision rights321036
S7.6Leader defensive under feedbackThe leader reacts badly to team feedbackPrepare the leader; model curiosity; safety32825
S7.7Leader asks coach about individualsThe leader asks for information about membersHold confidentiality; redirect132
S7.8Leader is the issue no one namesThe team’s problem centres on the leader’s behaviourAnonymous data; leader preparation; name the undiscussable13328
S7.9Leader leaves mid-engagementThe leader exits during coachingRecontract; timeline; transition11148
S7.10Leader wants to be “one of the team”The leader avoids authorityCoach the leader’s role; clarify decisions3235
S7.11The sponsor or a senior stakeholder is in the roomA powerful person attends; the team performs; real issues disappearContract the visitor’s role in advance; make the power visible and the purpose clear13297
S8 Change, context and the wider system 14 situations
S8.1Reorganisation or mergerStructural change disrupts roles, identity and relationshipsHonour the past; build a shared future; manage the tensions of change113317
S8.2Hybrid frictionHybrid working creates unequal access and misunderstandingsAgree hybrid norms; redesign rhythms; map the team in space44412
S8.3Multicultural teamMembers from different cultures bring different normsSurface norms; build shared agreements; treat difference as resource26224
S8.4Rapid growth / many new membersThe team is growing fast; culture is dilutingExplicit norms; onboarding rituals; rhythms426443
S8.5Key member leavingAn important member is leavingAcknowledge; redistribute roles; capture knowledge5391145
S8.6External crisisA sudden external event threatens the teamContract the session around the crisis; plan; support7345
S8.7Stakeholders unhappyStakeholders complain about the teamZoom to stakeholders; close the loop; revisit purpose16476
S8.8Resource cutsBudget or staff reduced; same expectationsPrioritise; test assumptions; engage stakeholders381816
S8.9Change fatigueRepeated changes exhaust the teamTest assumptions; appreciate stability; prioritise182038
S8.10Team of teams / cross-team coordinationSeveral teams must deliver together; nobody owns the wholeCoach the system of teams: shared purpose, explicit interfaces, liaison roles and regular cross-team learning16315392
S8.11Generational or neurodiversity frictionDifferent ways of thinking, communicating and working cause misunderstandingMake differences in style explicit and design working norms that let different minds contribute2642328
S8.12AI or new tool adoption changes how the team worksNew AI or digital tools change roles, decisions and expertiseTreat adoption as a team change: explore hopes and fears, agree principles, and run small experiments with review24374017
S8.13A purely virtual teamMembers have never (or rarely) met; all work happens onlineDesign connection, communication and rituals deliberately — nothing happens by accident online345415
S8.14Fluid membership: the team keeps changingPeople join and leave constantly; the team never settlesShift from building a stable team to building teaming routines that survive turnover3454
S9 From insight to action 9 situations
S9.1Great session, nothing changesInsight in sessions; no change in daily workSmall experiments; redesign routines; review40444345
S9.2Agreeing too easilyCommitments are made quickly without real buy-inTest agreement; pre-mortem; hear dissent363428
S9.3Action list too longMany actions; little focusPrioritise; small experiments4038
S9.4Reverting under pressureNew behaviours disappear when stress risesImmunity to change; rhythm; peer support184441
S9.5Experiment fails and team gives upA failed experiment leads to abandonmentAAR; reframe failure as learning; adapt434020
S9.6Waiting for permissionThe team waits for approval to actDrama to empowerment; decision rights; test assumptions19351815
S9.7Learning stays in the roomTeam learning isn’t shared with stakeholdersClose the loop; harvest; rhythms474644
S9.8Breakthrough momentA significant insight landsHarvest; land in experiments4640
S9.9Can’t agree the next stepThe team agrees on the issue but not the actionGradients of agreement; decision rights; experiments36354037
S10 The engagement and the coach 12 situations
S10.1Sponsor asks for a report on individualsThe sponsor wants information about team membersHold contract; offer team-level reporting147
S10.2Member asks for private coaching mid-engagementA member wants individual coaching from the team coachClarify roles; refer if needed14
S10.3Coach pulled into expert roleThe team wants the coach to give answersReturn ownership; process observation; fade the coach9748
S10.4Coach colluding with a subgroupThe coach aligns with one factionSelf-awareness; supervision; observation928
S10.5Co-coach disagreementCo-coaches disagree on approachContracting between coaches; review143
S10.6Team wants training, not coachingThe team asks for contentClarify modalities; contract17
S10.7Member discloses personal crisisA member shares a personal difficultySupport; refer; manage team impact314
S10.8Scope creepThe engagement expands without agreementRecontract17
S10.9Ending the engagementThe coaching is endingHarvest; handover; close the loop48464745
S10.10Coach’s own anxiety in the groupThe coach feels overwhelmed by the groupSelf-regulation; supervision; process95
S10.11Cameras off on videoRemote members turn off camerasNorms; check-in; rhythms4544
S10.12Interview data tempting to useThe coach knows individual information from interviewsHold confidentiality; feed back only themes81

Where the methods come from, and further reading

Each method page ends with a short “Where it comes from” note. These books are good next steps, and many are commonly used in ACTC education programmes. For the standards themselves, use ICF’s Team Coaching Competencies, Core Competencies and Code of Ethics.

Team coaching

  • Leadership Team Coaching Peter HawkinsThe five disciplines and systemic team coaching; CID-CLEAR.
  • Coaching the Team at Work David ClutterbuckA practical and research-informed guide; the PERILL model.
  • The Practitioner’s Handbook of Team Coaching David Clutterbuck, Judie Gannon et al. (eds)Broad survey of approaches and contexts.
  • High Performance Team Coaching Jacqueline Peters and Catherine CarrA research-based team coaching model.
  • Group and Team Coaching Christine ThorntonGroup-analytic perspectives for coaches.

Team effectiveness

  • Leading Teams J. Richard HackmanThe enabling conditions for team effectiveness.
  • Senior Leadership Teams Ruth Wageman, Debra Nunes, James Burruss and J. Richard HackmanWhat it takes to make top teams great.
  • The Wisdom of Teams Jon Katzenbach and Douglas SmithWorking groups versus real teams.
  • The Five Dysfunctions of a Team Patrick LencioniA popular fable and model; easy for teams to engage with.

Safety, conflict and voice

  • The Fearless Organization Amy EdmondsonPsychological safety in practice.
  • Reading the Room David KantorStructural dynamics and the four-player model.
  • Inside the No Myrna LewisDeep Democracy and the wisdom of the minority.
  • Overcoming Organizational Defenses Chris ArgyrisUndiscussables, defensive routines and the ladder of inference.

Facilitation and process

  • Humble Consulting / Process Consultation Edgar ScheinHelping groups see their own process.
  • The Skilled Facilitator Roger SchwarzGround rules and mutual learning.
  • Facilitator’s Guide to Participatory Decision-Making Sam Kaner et al.Gradients of agreement and divergent/convergent thinking.
  • The Surprising Power of Liberating Structures Henri Lipmanowicz and Keith McCandlessSimple structures that include every voice.

Change and development

  • Immunity to Change Robert Kegan and Lisa LaheyCompeting commitments and big assumptions, including collective immunity.
  • Polarity Management Barry JohnsonManaging tensions that can’t be solved.
  • Appreciative Inquiry: A Positive Revolution in Change David Cooperrider and Diana WhitneyBuilding on strengths.
  • Managing Transitions William BridgesEndings, the neutral zone and new beginnings.
  • Organizational Culture and Leadership Edgar ScheinThe three levels of culture.
  • Theory U C. Otto ScharmerPresencing and levels of listening.

Roles, culture and the coach

  • Team Roles at Work Meredith BelbinThe nine team roles.
  • The Culture Map Erin MeyerEight scales of cultural difference at work.
  • Supervision in the Helping Professions Peter Hawkins and Robin ShohetThe seven-eyed model.
  • Coaching Agile Teams Lyssa AdkinsTeam coaching in agile settings.
  • Nonviolent Communication Marshall RosenbergObservations, feelings, needs and requests.

My favourites and notes

Star any method or situation (look for the ☆ button) and write private notes on method pages. Everything is saved only in this browser on this device.

Nothing saved yet.

Principles to carry

Coach the team, not the people in it. Every question, observation and measure is about the team as a whole. Individual stories matter as part of the pattern.
Describe, don’t diagnose. Offer what you see as observable behaviour. The team supplies the meaning, and owns the change.
Hold every relationship in the contract. Team, leader, sponsor and stakeholders each need clarity. Most crises in team coaching are contracting problems that arrived late.
Safety before candour; candour before commitment. Don’t ask a team for conflict it can’t yet survive, or for commitment it hasn’t debated.
Make yourself unnecessary. The best measure of team coaching is a team that keeps coaching itself after the coach leaves.
Know the edge. Harassment, risk of harm, clinical distress and performance management are not team coaching topics. Pause, support and refer.