Systemic Team Coaching — The Field Guide

Every principle, framework, method and tool from the Team Development Essentials course, on one page. Organised around Peter Hawkins' Five Disciplines, module by module, with the working detail of each model.

TEAM DEVELOPMENT ESSENTIALS (TDE) · MODULES 1–6 · A PERSONAL QUICK-REFERENCE

The Five Disciplines Model

The spine of the whole course. Peter Hawkins' model holds that to create real value a team must master five disciplines — and coach the connections between them. The four outer disciplines sit on two axes: Task ↔ Process and Inside the team ↔ the Outside / changing world. Core Learning sits at the centre, running through all four.

Systemic Team Coaching (Hawkins, 2014): coaching a whole team, together and apart, to improve both its collective performance and how it works together, developing its collective leadership to engage all key stakeholders and jointly transform the wider business — "team coaching at scale," worked outside-in and future-back.
TASK PROCESS INSIDE THE TEAM OUTSIDE / CHANGING WORLD Clarifying THE WHAT Commissioning THE WHY Co-Creating THE HOW Connecting THE WHO Core Learning

The Extended Team Coaching Continuum — by breadth of focus

Team FacilitationProcess focus at events
→
Performance CoachingTask + process
→
Leadership Team Coaching+ stakeholder
→
Transformational LTC+ organisation
→
Systemic Team Coaching+ the wider system

No matches — try a different word, or reset the filters.

1

Foundations & the Coach-Leader

Leading & Developing Teams

Why teams matter now, what "good" looks like, and how the coach-leader needs to show up. The groundwork the other five disciplines are built on.

Principle

IQ → EQ → WeQ

The leadership challenge has evolved from individual logical intelligence, to emotional intelligence, to collective intelligence.

  • IQ — logical intelligence of the individual
  • EQ — emotional intelligence & self-awareness
  • WeQ — collective intelligence of a team that is more than the sum of its parts
  • The age of the heroic individual leader is "passed and gone"
Framework

Teamwork vs Teaming

Two complementary lenses: the quality of working together (Hoegl) and the active behaviours of teaming (Edmondson).

  • Teamwork Quality (Hoegl) — 6: Communication · Coordination · Balance of contributions · Mutual support · Effort · Cohesion
  • Teaming behaviours (Edmondson) — 4: Speaking up · Collaboration · Experimentation · Reflection
Questionnaire

HVCTQ — High Value Creating Team Questionnaire

An 18-item self-scoring instrument built on the Five Disciplines to rate where a team is and where it needs to get to.

  • 18 items grouped by the 5 disciplines (Commissioning, Clarifying, Co-creating ×6, Connecting, Core Learning)
  • Scored 1 (doesn't do it) → 5 (world-class role model)
  • Three columns: rating now · where it needs to be · the shift needed in me & the team

Use it toSpot the biggest gap, then pick 1–2 priorities plus what connects them.

Tool

Leadership Gravitas — Authority · Presence · Impact (API)

Unpacks "gravitas" (personal power) into three aspects that build a coach-leader's confidence and executive presence.

  • Authority — comes from the past: what & who you know, experience held as a resource (not imposed)
  • Presence — in the moment: full immediacy, rapport, meta-awareness
  • Impact — into the future: making a live shift — of thinking, mood or energy — in the room
  • 21-item self-assessment; "Personal Power" at the centre
Principle

The Reflective Coach-Leader

Building an "internal supervisor" so responses become intentional rather than habitual reactions.

  • Schön's two modes: reflection-on-action & reflection-in-action
  • 4 aspects: External · Introspective · Relational · Systemic
  • Practices: journaling (Kolb cycle) · daily pausing · "fast-forward rehearsals"
Principle

Systemic Thinking · Being · Doing

How the coach-leader "uses self as instrument" across three registers.

  • Thinking — seeing beyond the individual to team, culture & wider system
  • Being — presence; tuning in with the whole emotional, physical, intuitive self
  • Doing — acting on the systemic reading (e.g. working a conflict as a pattern in the room)
Framework

The Team Leader Development Journey

The progression from doing it all yourself to growing a future-fit team — each step a systemic shift.

  • Manager — spins all the plates; becomes exhausted
  • Leader — steps back to what the team must achieve collectively
  • Orchestrator — manages the connections between members & stakeholders
  • Coach — grows the team's core learning & future-fitness

Signature move"Radical weeding" — quarterly, cut 5–10% of least-value time.

Principle

Partnerships Are Not Created By Partners

A partnership is created not by the partners but by a third element — a shared, evolving collective purpose.

  • Move from transactional bartering → true partnering
  • The "third point of the triangle" = collective purpose
  • Purpose keeps changing → revisit it at regular intervals

Key question"What can we do together that we cannot achieve in parallel?"

Method

Team Alliance for Psychological Safety

A process for building psychological safety in any team — distinct from trust.

  • Trust = individual/dyadic ("can I count on you?"); Psych safety = group-level ("is it OK to speak up / be wrong here?")
  • 5 steps: each shares what they need → co-create behavioural commitments → experimental phase → review with a "quality failure" → revise the agreements

Sentence stem"One thing I need to feel safe to learn here is…"

Method

Wide-Angled Empathy

Expanding awareness to hold empathy for all parts of a story or system, instead of taking sides.

  • Centre with the breath; notice where you're "lining up"
  • Expand to hold empathy for every person & party in the story
  • Practise on everyday judgements (e.g. watching the news)
2

Commissioning & Clarifying

Are You a Real Team or Just a Meeting?

The first two disciplines: discovering why the team exists (Commissioning) and turning that into what it must deliver — objectives, charter and KPIs (Clarifying).

Principle

Team vs Group

"Team" is used loosely — real teamwork needs collaboration a group doesn't. A group may become a team.

  • Shared purpose needing collaboration & coordination
  • Higher interdependence of tasks
  • More mutual support
  • Shared responsibility for the collective endeavour
Model

Real Team vs Pseudo Team (West)

Michael West's NHS-research test: only ~40% who say they're in a team actually are.

  • Do you have a few clear team objectives?
  • Do you work together to achieve them?
  • Do you meet regularly to review progress & improve?
  • Real teams → better performance, satisfaction & lower mortality
Tool

Do You Need to Be a Team?

A work-group ↔ real-team continuum to decide whether becoming a team is worth the investment.

  • Distinguishes advisory / information-sharing / decision / task groups from real teams
  • 9 paired poles scored 1–5; a collective average >3–4 = worth investing

Acid-test question"What can we do together that we cannot do working in parallel?"

Method

Gawande's Check-in

The surgical-team practice (from aviation) that gets every voice into the room in the first two minutes.

  • Each member states their name
  • …their role
  • …one thing they're concerned about
  • Start every meeting with a check-in so people speak up when it matters
Framework

Purpose vs Mission vs Vision

"A mission captures ambition, a vision shows what success looks like, but purpose defines who you serve and the value you create."

  • Mission — what we want to achieve (roots in warfare / conquest)
  • Vision — what it will be like when we succeed
  • Purpose — what the world needs from us; our big WHY, head and heart
Principle

The Purpose-Led Team

The team is defined by its purpose — discovered, not invented.

  • "The purpose creates the team, not the team their purpose"
  • Discovered outside-in (what stakeholders need) & future-back
  • Purpose keeps changing → must be continually rediscovered
Principle

Collective Team Objectives

Clear team-level priorities drawn from the purpose that can only be met by collaborating.

  • 3 (min) – 5 (max) priorities — no one remembers more
  • Require collaboration; collectively created, owned & reviewed
  • Not the sum of individual/functional objectives
  • Take them to every team meeting
Tool

The Team Charter

A living "scaffolding" document, kept on the wall and updated as the world changes.

  • Commission, mandate & purpose · strategic focus & narrative
  • Key stakeholders · objectives & goals · team KPIs
  • Vision of success · members · core values
  • Working agreements: green-card (encourage) / red-card (discourage)
Method

Team Collective Build + Dot Democracy

A generative-dialogue process so priorities belong to no single person and beat the individual.

  • Each writes 3–5 bullets alone (independent thinking first)
  • A quieter member reads one point; others build on it
  • Repeat with different members → ~6–8 built-up points
  • Dot democracy: 3 sticky dots each → ranked top 3–5
Model

Transformational Team KPI

A measurable objective that forces the team to change, not just perform.

  • Achievable only through collaboration
  • Collectively created, owned & committed to
  • Cannot be met by the current way of thinking, behaving or partnering
Framework

Collective Responsibility for Regular Improvement

The third real-team essential: meet to close the gap between required and actual performance.

  • Review the performance gap — learn from successes & quality failures
  • Collective & mutual accountability — replace "hub & spoke" with horizontal accountability
  • Regular feedback — framed as "what I need to do my job"
Model

C.O.R.B.S. Feedback

A mnemonic for feedback that can actually lead to change.

  • Clear — specific about what the feedback is
  • Owned — your perception ("I find…"), not the truth
  • Regular — close to the event, not saved up
  • Balanced — positive & negative over time
  • Specific — usable, not "you're irritating"
Framework

Kipling's Drumbeat

The "six honest serving-men" as a recurring sequence to re-align every meeting.

  • Why we are a team → What we focus on → How we organise
  • Who leads / connects → When we review → Where we're heading
  • A continuous cycle, not a one-off
Method

Outcome-Based Meetings

Make every agenda item purpose- and outcome-led, and show the connections between items.

  • Why am I bringing this? What's its purpose?
  • What must we finish having achieved together?
  • What do I need from everyone in the room?
  • What issues is this connected with?
Method

Coaching in Pairs (Co-Coaching)

Co-leading with a co-coach — modelling teamwork and reading the system through parallel process.

  • Gains: extra eyes/perspectives; models teamwork; less likely both caught by the same "hook"
  • Parallel process: tension between co-coaches often mirrors the team's unspoken dynamic — name it
  • Contract on purpose, roles & how you'll handle conflict; debrief & learn afterward
3

Co-Creating

Becoming a Co-Creative Team

The how: team dynamics, generative meetings and psychological safety — helping a team become "more than the sum of its parts" (1 + 1 = 5).

Principle

The Co-Creative Team

What makes a team genuinely co-creative rather than merely agreeable — "being nice is not enough."

  • Balance of support & challenge (healthy dissent)
  • Shift from hub-and-spoke → web; the leader orchestrates, not directs
  • Generative dialogue that creates new thinking
  • Goal: more than the sum of its parts (the "team quotient")
Model

The CLEAR Team Meeting

Hawkins' five-phase structure for co-creative meetings. Teams most often skip Listen and Review.

  • Contract — what does success look like today?
  • Listen — get all perspectives, hopes & fears heard
  • Explore — brainstorm 1–2 issues; generate new thinking
  • Action — who does what, by when, with what support?
  • Review — what worked? what could be even better?
Model

Kantor's Four-Player Model

The four roles members take in conversation — and how to transform each into a co-creative version.

  • Mover (proposes) → Challenge Framer
  • Opposer (challenges) → Inquirer
  • Follower (supports) → Implementer
  • Bystander (observes) → Contributor
Model

Tuckman Team Maturity

The lifecycle stages, used to find a team's "centre of gravity." A 32-item questionnaire scores it.

  • Forming · Storming · Norming · Performing · Adjourning
  • Most teams have too little healthy storming — bring "pinches" in early
  • Sticky-note exercise: each posts the stage they see, then dialogue on the difference
Tool

Team Function Analysis

Assesses how a team spends its meeting time across seven functions — revealing over/under-use.

  • Coordinating · Briefing · Informing · Decision-making
  • Planning · Generative thinking · Nurturing & bonding
  • Rate % time now vs % needed, then what to increase/decrease
Method

Meetings Bloody Meetings

Seven leader practices for a "meeting revolution."

  • Radically weed the meetings you attend
  • Make meetings outcome-focused (~80% of time)
  • Separate info-sharing / creative dialogue / decisions
  • Weed the agenda · set a climate to challenge · use time-outs · sharpen the saw
Framework

Common Team Dynamics & Derailers

The patterns coaches learn to notice — don't memorise, recognise them in your own words.

  • 6 dynamics: hub & spoke · internal competition · sub-group factions · the "identified problem member" · common enemy · the consigliere
  • Derailers: elephants / "the dead elk" · groupthink · silo-ism · in/out-groups · either/or debates · only today, not the three horizons
Method

From Grumble to Gratitude

Four steps to move from complaint ("BMW" = Blame, Moan, Whine) to agency and learning.

  • Reframe the problem as a challenge
  • Relocate it in a relationship/connection, not a person
  • See it as the latest generous lesson life has sent
  • Find gratitude for the lesson
Principle

Psychological Safety (Edmondson)

Being able to show and use yourself without fear — the #1 factor in Google's Project Aristotle.

  • Without it, the diverse challenge needed for good results collapses
  • Build it via team agreements & "containers for safety"
  • Naming psychological safety directly does not reduce it
Method

The Secrets Exercise

Surfaces the unspoken issues most inhibiting the team — anonymously, as shared issues.

  • Each writes the key issue on paper → folded into a pot
  • Each draws one & claims it as their own ("on our team it's hard to…")
  • Coach groups similar issues; team votes the first to address → actions
Questionnaire

Collective Psychological & Relational Maturity

A 17-item team self-assessment scored onto a maturity scale.

  • Covers speaking up, challenging the leader, balanced participation, feedback, generative dialogue, healthy conflict, learning from mistakes
  • Bands: 15–30 Unhealthy Immaturity · 30–45 Dysfunctional Storming · 45–60 Growth · 60+ Collective Maturity
4

Connecting

Who and What Does the Team Serve?

The who: moving from a high-performing team to a high-value-creating one by engaging all stakeholders — and turning them from demands into partners.

Principle

High-Performing → High-Value-Creating

The core reorientation: from internal performance to co-creating value with and for the whole stakeholder system.

  • Stakeholders: separate demand → resource → partner
  • Relationship: face-to-face (transactional) → shoulder-to-shoulder
  • "Success never belongs to a system" — the system creates it
Principle

Parsifal & the Holy Grail

The Grail legend as the discipline of always asking whom an activity serves.

  • Parsifal forgets to ask the question — and loses the Grail
  • Only when mature enough to ask may he stay

The question"Who and what does the Grail serve?" → "And who else? And who else?"

Model

The Six Stakeholder Groupings

A hexagram of the major stakeholder categories every team serves — the frame for an annual review.

  • Investors / funders · Customers / clients · Suppliers
  • Employees / contractors · Communities · Ecology (more-than-human world)
  • For each: what have we received? what value have we given back?
Tool

Stakeholder Mapping + the 13th Fairy

Map every stakeholder — then deliberately hunt the one you've overlooked.

  • Put yourself/the team at the centre; spidergram "who do we serve?"
  • 13th Fairy — the uninvited stakeholder brings the curse (cf. BP / the fishermen)
  • 7th Generation — add future stakeholders too

Key question"Which stakeholder will you regret not having included in 2–3 years?"

Framework

Bringing the Stakeholder Into the Room

A progression from mapping stakeholders to genuinely owning them.

  • 1. Data — interviews, 360 feedback
  • 2. Voice — step into their shoes; empty chairs
  • 3. Relationship — invite real stakeholders into meetings
  • 4. Own them collectively — look at the connections between stakeholders
Method

Empty Chairs

A quick meeting intervention that interrupts internal argument with stakeholder perspectives.

  • Label spare chairs: customers, employees, investors, future generations, the ecology
  • When argument flares, call "time-out"
  • Members sit in a stakeholder chair & speak from that seat
Tool

6 Questions to Ask Your Stakeholders

Balancing what the team delivers (1–3) with how it engages (4–6); appreciation with future needs.

  • 1 · What do we do that creates the most value for you?
  • 2 · What could we do that would create more?
  • 3 · What will you need different in 3–5 years?
  • 4 · What do you appreciate about how we engage?
  • 5 · What do you find most difficult about it?
  • 6 · How could we improve how we partner?
Method

Discovering Stakeholder Needs

A co-inquiry process so purpose is unearthed with stakeholders, not imposed.

  • Team members interview key stakeholders (best in pairs)
  • Bring data back by role-playing the stakeholder they met
  • Role-players share what they'd say "out of hearing" too
  • The "six board" exercise sorts all feedback by stakeholder group
Method

Stepping Into the Stakeholder's Shoes

A Gestalt empty-chair enactment that builds empathy for a difficult stakeholder (John Leary-Joyce).

  • Position 1 — speak to them ("I…/You…"), not about them
  • Position 2 — sit in their chair; sense & respond as them
  • Position 3 — observer; name the dynamic & a way forward
  • Deeper emotion → deeper resolution
Principle

Win-Win-Win (Shoulder-to-Shoulder)

Extending "win-win" with a third win — a benefit for a third entity both parties serve.

  • Western "win-win" tends to become transactional
  • A shared third entity moves parties from face-to-face to shoulder-to-shoulder

Turning a stakeholder into a partner"What can we do together that we cannot do apart?"

5

Core Learning

Unlocking Team Potential — Being a Learning Team

The discipline at the centre — building conscious, ongoing learning into the team's day-to-day work so it becomes future-fit, not just better at yesterday's game.

Principle

Core Learning (the discipline)

The most-neglected discipline; it integrates and runs through the other four.

  • Learning at 3 levels: each individual · project teams · the whole organisation
  • Without it a team "gets better at playing yesterday's game"

Core questions"What are we learning? What do we need to learn?"

Principle

Future-Back & Outside-In Learning

Expanding learning beyond the team's immediate, internal needs.

  • Future-back — start from the world of tomorrow, work back (vs present-forward)
  • Outside-in — bring stakeholder & world voices in (vs inside-out)
  • Aim: grow the capacity to be "future-fit"
Framework

Three Horizons (Sharpe)

Managing today and preparing for the future concurrently — the antidote to short-termism.

  • H1 — manage the present / business as usual
  • H2 — innovate for tomorrow
  • H3 — future foresight; what's emerging
  • Work the sequence 1 → 3 → 2 so you don't innovate from yesterday's frame
Model

The Team Learning Cycle

Kolb's action-learning cycle, simplified by Hawkins. You can start anywhere.

  • Thinking → Planning → Doing → Reviewing → repeat
  • Reviewing is the stage teams most often short-circuit
  • Time-box each stage to keep moving round the whole cycle
Model

Action-Learning Shortcuts

Five ways teams short-circuit the cycle and get stuck — each with a remedy.

  • Fire-fighting — plan-do, plan-do (→ slow down, do an AAR)
  • Post-mortemising — do-reflect (→ take a balcony view)
  • Navel-gazing theorists — reflect-theorise (→ commit to an action)
  • Paralysis by analysis — over-analyse (→ break the trance)
  • Totalitarian — decide in theory & impose
Tool

After & Pre-Action Reviews

Structured learning reviews — looking back, and looking forward ("pre-flection").

  • AAR: What happened? What did we expect? What can we learn? Even better next time?
  • Pre-Action: What do we expect to learn? What could go well / not? How do we prepare?
Tool

Timeline Learning Review

An embodied timeline exercise reviewing the journey, then looking future-back.

  • Lay a timeline on the floor; above = positive, below = negative emotion
  • Walk from the start to now, placing key events & lessons
  • Stand at a point 3–5 years out; look back: what must we learn now?
Method

Seven Embedded Learning Methods

Practices that build learning into the flow of work rather than bolting it on.

  • 1 · Team Facilitator alongside the Chair
  • 2 · Mid-Action Reviews (pause during the work)
  • 3 · "Be-brief, de-brief" in transition time
  • 4 · Team pre-flections before big events
  • 5 · Five Disciplines review (stand in 5 places)
  • 6 · Learning check-ins to open meetings
  • 7 · Quarterly team reviews
6

The Process & Your Next Steps

Team Coaching Journey — Review & Next Steps

Putting it together: the end-to-end coaching process, the design tool that maps a team's journey, and how to keep growing as a practitioner.

Framework

SIDER — The STC Process

The five-stage journey (pronounced "cider") a coach takes a team through — typically over 9–12 months.

  • Scoping & agreement — tune in, build relationships, contract
  • Inquiry & discovery — stakeholder mapping, interviews, 360, observation
  • Developing the agenda — team co-creates its own development agenda
  • Execution & engagement — interventions across all five disciplines
  • Review — review progress; hand the role back to the team
Tool

The Fishbone Method

A visual co-design tool (Ishikawa) that maps a team's journey from now to a future required state.

  • Tail = now: 1a current strengths · 1b current challenges
  • Head = the future required state (≈ 1 year out)
  • Spine & ribs = key activities to bridge the gap
  • Place priorities on a timeline: now / 1 / 3 / 6 / 9 months / 1 year
  • Use the five disciplines as "five lenses" to order them
Principle

A Journey, Not a Series of Events

Why development must be embedded in the flow of work, not delivered as off-sites.

  • Only 0–30% of off-site commitments ever get actioned
  • Embed via bridging activities, mid-meeting time-outs & review cycles
  • "If the change doesn't happen in the room, it won't happen outside it"
Method

Co-Inquire & Co-Design

The coach helps the team lead its own inquiry and design its own journey — for maximum ownership.

  • Start: "Who and what does your team serve?" → discover collective purpose
  • Members interview stakeholders & bring data back experientially (role-play)
  • Team works its own data via the fishbone; agrees 3–5 priorities
  • Close the loop back to stakeholders
Tool

Questions for the Start of the Journey

A question bank grouped by who's being asked, to open a rich inquiry.

  • Sponsor: "What would have to happen for you not to worry about this team?"
  • Leader: "What legacy do you want to leave?"
  • Team: "What are this team's under-used strengths?"
  • Both: "If this team didn't exist, why would it have to be created?"
Tool

Finding a Team to Practise With

Guidance for securing a (often pro-bono) team — plus the red flags for when not to coach one.

  • A team = 3+ people with a joint purpose needing collaboration
  • Soft entry: offer a "Team Health Check"; ~12 team hours over 6 sessions
  • Walk away if: too large (>12) · only the leader wants it · the team expects rescuing · you're a stakeholder (conflict of interest) · deeply unhealthy team
Tool

Learning Integration & Development Plan

Two worksheets to consolidate your own philosophy and plan your growth.

  • Integration: my definition of a team · my framework · my top five tools · how I'll describe my offering
  • Development Plan: Do differently · Shift in relation · Experiment with · Get feedback on · Keep learning
  • Apply the fishbone to yourself: strengths, challenges, vision, learning