Team health

The best teams aren't the nicest. They're the ones where it's safe to say the hard thing.

Psychological safety is the shared belief that you can take an interpersonal risk — ask an obvious question, admit a mistake, challenge a decision, float a half-formed idea — without being punished or made to feel small. It's the single biggest differentiator between teams that learn fast and teams that hide problems until they explode (Amy Edmondson's research; Google's Project Aristotle). And it's the most misunderstood idea in team health: it is not comfort, not niceness, and not lower standards. This tool takes your team's temperature — and shows where the truth is getting stuck.

01 — The thermometer

Take your team's temperature.

Seven statements, adapted from Amy Edmondson's team psychological-safety scale. Rate each one for the team you're on right now — honestly, as it actually is, not as you wish it were. The thermometer fills as you go, and the panel below points at the one or two things dragging it down — and the leader behaviour that would move each.

1 — Strongly disagree 3 — Neutral 5 — Strongly agree
Mixed
50/100
Team safety index

Three statements are negatively worded (marked reverse) — agreeing with them lowers the reading, because they describe an unsafe climate. Scoring them in reverse is what lets you answer every item honestly on the same scale and still get a true reading.

02 — What it is, and isn't

It's candour, not comfort.

Almost every team that gets this wrong makes the same swap: they hear "safety" and think "be nice, keep the peace, don't rock the boat." That's the opposite of the idea. Real safety is what lets a team disagree out loud, name the problem in the room, and admit a mistake early — the candour that niceness quietly suppresses.

What psychological safety IS What it is NOT (the common myth)
Candour — people say the hard thing Niceness — people avoid the hard thing to keep the peace
A demanding bar, held honestly Lowering the bar so nobody feels bad
Mistakes surfaced early and examined No mistakes — or no consequences for anything
Productive disagreement and dissent Consensus, harmony, everyone comfortable
A shared, team-level climate One-to-one personal trust or friendship
Built by leaders, daily, in the moment An offsite, a values poster, or an HR perk

Safe is not the same as nice

Nice teams protect feelings. They smooth over conflict, leave the awkward question unasked, and read the silence as agreement. It feels good, and it hides the truth until the truth becomes a crisis.

Safe teams protect the truth. Precisely because no one gets punished for it, people can disagree, challenge the boss, and name the problem while it's still small. Candour, not comfort — that's the whole point.

Team safety is not personal trust

Trust is my judgement about you: will this specific person do what they said? It runs one-to-one, person to person.

Psychological safety is our shared belief about the group: if I take a risk in this room, will the team have my back? You can trust individuals and still not feel safe to dissent in the meeting — which is why safety is a climate you build, not a relationship you have.

Safety on its own isn't the goal either. Pair high safety with a low bar and you get mere Comfort — pleasant and stagnant. Pair it with a high bar and you get the Learning zone, where high performance actually lives. Those are two of Edmondson's four zones — explore all of them in the two dials below.
03 — The two dials

Safety is one dial. Standards are the other.

Psychological safety doesn't stand alone — it multiplies whatever standards you hold. Plot your team on Edmondson's two axes: how safe it feels to speak up, and how high and how honestly the bar is held. Where the two dials land tells you which zone you're in — and which dial to turn next.

72
38

Zone

04 — When it breaks

What low safety actually costs you.

It rarely shows up as an argument. It shows up as silence, hidden mistakes, and questions that never get asked — small omissions that compound into expensive surprises. Four scenes a leader will recognise, and what the same moment looks like on a safe team.

The meeting

Silence that ships a bad decision

The plan has a hole and three people in the room can see it. Nobody says anything — the last person who pushed back got talked over. Heads nod, the decision ships, and the hole becomes a quarter of rework.

The tells

  • Decisions pass with zero dissent, fast.
  • The same one or two voices do all the talking.
  • "Any concerns?" is met with silence and nods.
With safety: the leader asks "what's the strongest case against this?" and thanks whoever makes it. Silence is treated as missing data, never as agreement.
The post-mortem

Blameful versus blameless

An outage happens. In one version, the meeting hunts for who to blame — so next time people cover their tracks and the real cause stays buried. In the other, the team asks what in the system let a competent person make that move.

The tells

  • The first question is "who did it?"
  • People go quiet or defensive when the incident comes up.
  • The same class of failure keeps recurring.
With safety: a blameless post-mortem assumes good people hit a flawed system. It gets the honest timeline — because telling the truth is safe — and fixes the system so it doesn't repeat.
The newcomer

The junior who won't ask

A new engineer isn't sure what the ticket means. Asking feels like admitting they don't belong, so they guess — and build the wrong thing for two weeks before anyone notices.

The tells

  • New people stay quiet through their first months.
  • Questions get asked in DMs, never in the open.
  • Rework traces back to an unasked question.
With safety: senior people ask "dumb" questions on purpose, and "I don't understand this yet" is normal from anyone. The cheap question gets asked before the expensive mistake gets built.
The star

The mistake that hides until it's a crisis

A strong performer makes a costly error. Admitting it risks the reputation they've built, so they quietly try to patch it — until it grows past hiding and lands on your desk as an emergency.

The tells

  • Problems surface late, fully formed, as crises.
  • Your best people never bring you bad news.
  • "I made a mistake" is a sentence no one says.
With safety: early bad news is welcomed and never punished, so a small mistake gets raised while it's still small. Your reaction to the first admission sets the price of the next one.
Notice the through-line: every failure is a problem that existed but stayed hidden because surfacing it felt unsafe. Safety doesn't create fewer problems — it gets them on the table while they're still cheap to fix.
05 — Go deeper

A reading is a start. Changing the climate is the work.

The thermometer tells you where you stand; it doesn't move the needle. That happens in a hundred small moments — most of all in how a leader reacts the instant someone brings bad news. That's the work we do with the leaders and teams we coach: turning a candid read of the climate into the habits that raise it, without ever lowering the bar.

Talk to us about coaching
TAKE ONE

Safety is candour, not comfort

The goal isn't a team that feels nice. It's a team that can tell you the truth — admit the mistake, ask the question, name the risk. Comfort is a side effect at best, and often the opposite.

TAKE TWO

High safety AND high standards = learning

Safety isn't a substitute for a high bar; it's what makes a high bar survivable. Demand a lot and make it safe to fall short, and the team learns its way up. Either dial alone underperforms.

TAKE THREE

Leaders set it by how they react to bad news

The climate is decided in the seconds after someone brings you a problem. Curiosity keeps the channel open; blame closes it — and everyone watching learns whether the truth is safe here.