10 · Project — A Team Development Plan

Level 2's project built a plan for one person. This one operates at the level this track has been building toward: a whole team, using the diagnostic and structural tools from this level rather than a single coaching conversation. A team development plan is not an org chart with aspirations attached — it is a diagnosis of what's actually constraining the team (Module 5), the structural lever behind it (Module 3), and a set of committed changes with a way to know if they worked (Module 9). The test of completion is the same kind as Level 2's: can you point to one thing the team can now do in six months that it could not do today, and would the team describe the plan as an accurate diagnosis of themselves, not a document written about them.

1. The brief

Choose your actual current team — not a hypothetical one. Produce a written plan with the seven sections below, built from real data you gather over one to two weeks, not from your own assumptions about what's wrong.

Plan section	Module
Diagnostic baseline	05 · Team Diagnostic
The structural loop behind the lowest score	03 · Loop Diagram
The culture gap, if relevant	01 · Culture Audit
The one structural change	03 · systems thinking
Individual development threads	Level 2 coaching plan, applied per person
What I will change about how I run the team	05, 06 · rituals and structure
Measurement plan	09 · Signal Set

Two hard rules, matching Level 2's discipline. Diagnose before you design — do not write the plan until the Team Diagnostic has been run as an actual anonymous pulse, not your own guess at the scores. And name one structural lever, not five — a plan that tries to fix psychological safety, dependability, clarity, meaning, and impact simultaneously fixes none of them with the attention any one requires.

2. The plan template

TEAM DEVELOPMENT PLAN
Team: ______________  Size: ______  Written: ______
Diagnostic run: [ ] anonymous pulse  [ ] leader estimate only (flag this)

1. DIAGNOSTIC BASELINE
   Team Diagnostic scores (1-5, from Module 5):
     Safety: __  Dependability: __  Clarity: __  Meaning: __  Impact: __
   Lowest score and gap from leader's own estimate of it:
   Evidence beyond the score (specific instances, dated):

2. THE STRUCTURAL LOOP
   Trigger:
   Response (and the incentive making it locally rational):
   Downstream effect:
   Feedback (reinforcing or balancing):
   The lever — which step, changed structurally:

3. CULTURE GAP (if applicable — run Module 1's audit)
   Stated value: ______   Gap score: ______
   Real lever (promotion / leader behaviour / incentive / story):

4. THE ONE STRUCTURAL CHANGE
   What, specifically, changes (a ritual, an incentive, a process):
   Why this and not a values statement or an offsite:
   Who else has to agree to it, and have they:
   What could go wrong, decided in advance:

5. INDIVIDUAL THREADS (one per team member, one line each)
   Name — the one thing this structural change should unlock for them:

6. WHAT I WILL CHANGE ABOUT HOW I RUN THE TEAM
   Specific, observable, team may hold me to it:

7. MEASUREMENT PLAN
   Which Signal Set indicator(s), from Module 9:
   Re-run date for the Team Diagnostic:
   Signal the plan isn't working, checked before that date:

3. Worked example

Team. Priyanka Deshmukh leads a nine-person customer implementation team at a mid-size SaaS company. Delivery is acceptable but has been flat for two quarters despite two new hires. She runs the anonymous Team Diagnostic before writing anything.

TEAM DEVELOPMENT PLAN
Team: Customer Implementation   Size: 9   Written: 3 September
Diagnostic run: [x] anonymous pulse (7 of 9 responded)

1. DIAGNOSTIC BASELINE
   Safety: 4.1  Dependability: 2.6  Clarity: 3.8  Meaning: 4.0
   Impact: 3.2
   Lowest: Dependability (2.6). My own guess beforehand was 4 —
     I believed the team followed through reliably; the gap is 1.4,
     which is the real finding here, not the score itself.
   Evidence: three implementation handoffs in the last quarter
     slipped their committed date with no advance flag; two
     different customers escalated to my manager before I knew
     there was a problem, not after.

2. THE STRUCTURAL LOOP
   Trigger: an implementation task starts running behind the
     committed timeline.
   Response (incentive): the owner tries to quietly catch up rather
     than flag it, because the one time someone flagged a slip early
     (Marco, June), the response in the team stand-up was five
     minutes of "what happened" in front of everyone — treated as a
     discipline issue, not information.
   Downstream: the gap grows unseen for one to three weeks until it's
     unhideable, at which point it surfaces as a customer escalation
     instead of an internal flag.
   Feedback: reinforcing — the worse the eventual reveal, the more
     "flagging early is dangerous" gets confirmed for the next person
     watching it happen to someone else.
   Lever: what happens publicly when someone reports a slip — not
     the individuals' discipline or effort.

3. CULTURE GAP
   Stated value: "we surface problems early."
   Gap score: 4 (performative — the value is on the onboarding deck;
     the lived response to early flags punishes them).
   Real lever: my own behaviour in stand-up when a slip is reported —
     I turn it into a public post-mortem in the moment instead of a
     private "what do you need."

4. THE ONE STRUCTURAL CHANGE
   What changes: status in stand-up becomes a single word — green,
     yellow, red — with zero discussion in the room. Any yellow or
     red gets a same-day 1:1 from me, opening with "what do you
     need," not "what happened."
   Why this and not an offsite: the loop diagnosis points at a
     specific public ritual, not a general culture deficit — an
     offsite about "accountability" would not touch the actual
     mechanism.
   Who has to agree: my own manager, since she also attends
     stand-up and has asked "what happened" publicly before too —
     briefed her on 4 September, she agreed to hold the same line.
   What could go wrong: someone reports yellow and I revert to
     public discussion out of habit under time pressure. Decided in
     advance: if I catch myself doing it, I say "let's take that to
     a 1:1" out loud, in the room, so the correction is visible too.

5. INDIVIDUAL THREADS
   Marco — the person actually most likely to test the new norm
     first, since he was burned by the old one in June.
   Deja — newest hire; never learned the old norm, so watch whether
     she flags early by default, as a control for whether it's working.
   (seven more lines, one per remaining team member, omitted here)

6. WHAT I WILL CHANGE
   - Stand-up status is one word. I do not ask a follow-up question
     in the room, ever, for the first two months.
   - Every yellow/red gets a same-day 1:1, not "when I get to it."
   - I tell the team directly, this week, why the format is
     changing — naming my own role in the old pattern, not just
     announcing new rules.

7. MEASUREMENT PLAN
   Signal Set: whether bad news reaches me before it's a customer
     escalation (hard-to-fake, Module 9) — track incidents where I
     learn of a slip via 1:1 flag vs. via external escalation.
   Re-run Team Diagnostic: 1 December (12 weeks).
   Signal it's not working, checked at 6 weeks: any yellow/red still
     arriving to me first through a customer or my manager, not
     through the new channel.

4. The moment that produced the diagnosis

An excerpt from Priyanka's review of the diagnostic results with her own manager, Feld, using the Loop Diagram from Module 3 rather than jumping straight to a fix.

Feld: Your dependability score is a full 1.4 below what you guessed. What's your first reaction to that gap?

Priyanka: Honestly, defensive — I think of myself as someone who hears about problems early.

Feld: Sit with that for a second instead of resolving it. When did you last actually hear about a slip early, versus after it had already become a customer issue?

Priyanka: ...I can't think of one in the last quarter. They've all come to me late.

Feld: What happens in the room when someone does report something going sideways?

Priyanka: I ask what happened. I want to understand it.

Feld: In front of everyone?

Priyanka: ...Yes. Every time.

Feld: So the only data point your team has about reporting a slip early is watching Marco get five minutes of public "what happened" in June. What would you predict they learned from that?

Priyanka: That reporting it early costs you a public conversation, and staying quiet costs nothing until it's unavoidable. I built that.

Feld didn't supply the diagnosis — he refused to let Priyanka skip past her own surprise at the gap, which is where the real loop became visible.

5. Rubric — mark your own plan

Criterion	Weak	Strong
Diagnostic	Leader's own estimate only	Anonymous pulse, gap from leader's guess named honestly
Structural loop	"The team needs to communicate better"	Specific trigger → incentive → effect → feedback, with a named lever
Change count	Multiple simultaneous initiatives	One structural change, specific and checkable
Leader's own change	Absent or vague	Specific, observable, team may hold you to it
Measurement	"We'll see how it feels"	A hard-to-fake signal, a re-run date, and a stated failure condition

How It Actually Works

Building a team development plan against a real team, using the five-conditions framework from Module 5 and the loop-diagram tools from Module 3 together, forces integration of skills that are usually practiced separately — and integration, not isolated repetition, is what distinguishes expert-level judgment from a collection of individually mastered techniques. Cognitive science of expertise (chunking research, following Chase and Simon's classic chess studies) shows that experts don't just know more individual facts than novices — they've built larger, integrated "chunks" that let them recognize a whole situation pattern (here: a team that's dependable but lacks psychological safety, with a specific reinforcing loop driving it) and respond to the pattern as a unit, rather than reasoning from first principles about each module's tools separately every time. A single-topic exercise builds isolated pieces; a whole-team plan is what forces those pieces into an integrated chunk.

Why the rubric-based self-review again matters here, more than in the Level 2 version. As the plans grow more complex (a diagnosis, a loop map, a staged intervention), there are more places for motivated reasoning to quietly smooth over a genuine gap in the diagnosis — a leader drafting their own plan is more likely to describe the team as they hope it is once past the initial audit stage. The rubric's specific, external checkpoints (is the diagnosis backed by the actual audit evidence, does the loop diagram identify a real reinforcing or balancing structure rather than an assumed one) are what catch this at the more complex, more failure-prone integration stage.

Exercise

Run the anonymous Team Diagnostic on your real team this week — not your own estimate of the scores. Where your guess and the real result differ by more than one point on any dimension, treat that gap itself as the most important finding, the way Priyanka's dependability gap was more informative than the score. Build the full plan in section 2, and share it with the team once written — a team development plan the team has never seen is a set of notes about them, not a plan with them.

Stretch goals

• Run the Loop Diagram on a problem you didn't build. Pick a dependability, clarity, or impact gap that predates your tenure on the team, and find the structural cause rather than assuming a predecessor simply managed worse than you do.
• Ask the team to score your own contribution to the lowest metric, anonymously, before you finalize section 4 — the sharpest test of whether your diagnosis matches theirs.
• Re-run the Culture Audit on a value you personally hold most strongly. Leaders are often most blind to the gap on the value they believe in most sincerely.
• Build the plan with a co-leader or peer manager reviewing it, the way Feld reviewed Priyanka's — someone whose job is to stop you from skipping past your own surprise at the data.
• Track whether the structural change survives a bad week. The real test of section 4 is whether it holds under pressure, not whether it works when things are calm — check it specifically during the next crunch, not just at the twelve-week mark.