00 The Compounding Flywheel
High performing teams are not built by chance, and they're not built once. They're the result of six conditions working together, each one reinforcing the others. Get one spinning, and it nudges the rest. Let one degrade, and the whole system slows.
Six conditions that high performing teams share. None of them are optional. Each can be actively designed, measured, and improved.
Click any node to explore its elements
01 The Compounding Effect
The six pillars aren't independent. Each one actively enables the others. This is the mechanism that turns a good team into a high performing one, and keeps it there.
Fuels Trust
Connected teams communicate more honestly and assume positive intent. Social bonds make candid feedback feel safe. A joyful team epitomises trust.
Unlocks Purpose
When people trust each other, they are more likely to collaborate effectively. When people trust leadership, they believe in the mission. Transparent organisations build trust and attract people who align with their purpose.
Enables Safety
A clear purpose gives people the confidence to challenge and apply critical thinking, because they know the goal is outcomes not appearances, and a clear purpose creates alignment and a drive to safely promote doing the right thing.
Drives Ownership
People only take genuine ownership when they feel safe to fail. Without safety, ownership becomes performative rather than real. If people feel safe, they'll own the quality of their work and impact.
Accelerates Growth
Teams that own outcomes seek the skills to deliver them better. Ownership creates natural pull for learning and mastery. People who own their impact will invest more deeply in their work and their growth.
Deepens Joy
Progress and mastery are deeply joyful. Teams that grow together build stronger bonds and joyful relationships, and the cycle accelerates.
02 The HPT Runbook
Eight repeatable steps to build and sustain high performing team conditions. Run the full cycle quarterly. Check in on individual steps as needed between cycles.
Baseline
Run the Team Health Audit
Score all six pillars honestly, as a team, not as an individual. Use the audit in Section 03. Give each person a chance to score independently before sharing, to avoid anchoring on whoever speaks first.
- Schedule a 60-minute session, separate from sprint ceremonies
- Everyone scores independently first (use sticky notes, anonymous polls, or a shared doc)
- Share and discuss: the gaps between individual scores are as useful as the averages
- Be especially attentive to Safety scores, as low safety means low candour in the session itself
- Output: six pillar scores, a team health score, and a shared view of current state
Diagnosis
Identify Your Flywheel Friction Points
Your lowest-scoring pillar is costing the others. Find it, name it, and explore why, not who. The goal is to surface conditions, not assign blame.
- Identify the 1-2 lowest-scoring pillars from the audit
- For each, ask "why is this low?" and aim for three levels of depth
- Look for patterns: is it structural (how the team is organised) or behavioural (how people interact)?
- Check for compounding drag: which low pillar is pulling down others?
- Output: a root-cause hypothesis for each friction point, agreed by the team
Focus
Choose One or Two Pillars to Target
Distributed effort across all six pillars simultaneously produces slow, invisible results. Focused investment in one or two at a time compounds faster. This is the equivalent of the debt avalanche method: highest friction first.
- Agree as a team which 1-2 pillars to prioritise this quarter
- Use the compounding map from Section 01: which pillar, if improved, would most enable the others?
- Don't neglect pillars at 4-5; maintain them even while building others
- Write the focus areas down and make them visible in the team space
- Output: named priority pillars for the quarter, agreed and visible
Design
Design One Experiment Per Targeted Pillar
Experiments, not initiatives. Small, time-boxed, observable. The goal is to create a feedback loop between the intervention and the pillar score, not to commit to a six-month culture change programme.
- For each targeted pillar, agree one specific, observable experiment
- Define what success looks like before you start: what would you see if it worked?
- Keep experiments to 2-4 weeks. Longer timescales reduce learning velocity.
- Examples: a weekly 15-minute connection ritual (Joy), a team decision log (Ownership), anonymous retro questions (Safety)
- Output: one experiment card per targeted pillar, covering name, hypothesis, duration, and success signal
Ownership
Name an Owner for Each Experiment
Shared ownership of team health experiments is no ownership. A named person makes the experiment happen, tracks it, and raises blockers. They don't have to do it alone, but they have to make sure it moves.
- Assign one named owner per experiment, not the leader by default
- Owner is accountable for: running the experiment, observing the signals, and reporting back
- Rotate ownership across team members over time; everyone should lead at least one improvement
- Leader's role: remove blockers and provide support, not take over
- Output: named owners per experiment, written into the team's sprint or working agreement
Transparency
Share Progress Openly
Team health work is most powerful when it's visible. Sharing progress builds the trust it's designed to create. It also signals to the broader organisation that this team takes its conditions seriously, which is itself a form of gravitas.
- Share experiment progress at each sprint retrospective, even a two-sentence update
- Track the pillar scores over time; even a simple table in Confluence or Notion works
- Share successes beyond the team when something works, to model the behaviour for others
- Don't hide struggles; acknowledging a low safety score publicly takes courage and builds it
- Output: a simple visible tracker that the team owns and updates
Celebration
Recognise and Reward Progress
Recognition tied to team health improvements reinforces the behaviours you're building. This is itself a growth intervention, rewarding impact over task completion, and making the invisible visible.
- Celebrate when a pillar score improves, even by a point
- Name what changed and why, making the causal link explicit
- Recognise the owner of the experiment, and the team for making it possible
- Keep rewards proportionate: a team shoutout and a shared retrospective on what worked is often enough
- Output: a standing agenda item for "what improved and why" in each quarterly cycle
Quarterly Reset
Re-run the Audit and Set New Focus
The flywheel doesn't maintain itself. Re-audit every quarter. Some pillars will have improved; others may have drifted as the team's context changes. The goal is a sustained, improving trajectory, not a one-time perfect score.
- Re-run the full health audit, following the same process as Step 1
- Compare scores to last quarter: what moved? What didn't? Why?
- Archive completed experiments, celebrate closures, learn from what didn't work
- Set new priority pillars for the next quarter based on current scores
- Output: updated audit, new experiment cards, and a shared sense of where the team is heading
03 Team Health Audit
Score your team against each pillar right now. Be honest. The audit is only useful if it reflects reality, not aspiration. Run it quarterly.
HPT Health Audit
04 Intervention Tiers
Depending on where your team sits on the health score, the right level of investment changes. These tiers frame how much focused effort to apply, and when.
05 Quick Wins to Start This Sprint
Before you run the full audit, get momentum. These are actions that take minutes to hours, not a quarter. Small moves on the flywheel still move the flywheel.
Run a 30-minute connection session this sprint
No agenda, no updates, no tasks. Just the team, together. Swap stories, share something non-work. Joy is the most neglected pillar because it feels optional. It isn't.
Write your team's purpose in one sentence
If you can't, that's the gap. "To ship features" is not a purpose. "To make it easier for nurses to access patient records under pressure" is. The difference matters.
Ask one person: "Do you feel safe to challenge decisions here?"
Not in a group setting. One-to-one. Listen to the answer. The most important signal about safety in your team will never come from a survey.
Map one recent decision: who actually owned it?
Was the right person making it? Did they have the context? Would they own the outcome? Ownership gaps are usually invisible until a decision goes wrong.
Give one piece of specific, actionable feedback today
Not "great job." Something with a what, a why, and a so-what. "The way you framed that risk in the planning session gave the stakeholders exactly what they needed to decide quickly. That's a skill worth using more."
Name one learning opportunity your team doesn't currently have
A conference, a book, a pairing session, a workshop. Then ask: what would it take to create it? Growth rarely happens without someone advocating for it.
Find one place where work is invisible and make it visible
A decision that was made without documentation, a dependency that's managed in someone's head, a risk that isn't on the board. Transparency is a habit, not a project.
Find one team win from the last month and celebrate it publicly
In Slack, in the all-hands, in the retro. Name what happened, name who made it happen, and name why it mattered. Recognition that's specific and public compounds just like the rest of the flywheel.
∞ The Golden Rule
High performing teams are not destinations. They're practices. The teams that sustain high performance aren't the ones that hit a perfect score once. They're the ones who make tending these conditions a habit, not an event. They audit honestly. They experiment deliberately. They celebrate visibly. And they keep going.