What a team actually receives

A plain description of what's in a psychological safety report from this instrument — and a full specimen you can read, built from fabricated data by the identical pipeline a real team's report goes through.

Read the specimen report Back to the instrument

Distributions, not averages

Most psychological safety surveys hand back a number. A team scores 4.1 out of 5, and everyone nods, and nothing happens — because 4.1 is the average of a team where four people feel safe and two feel silenced, and it is also the average of a team where everyone feels roughly fine. Those are completely different teams with completely different problems, and the mean erases the difference.

So every item in this report is shown as a distribution: how many people picked each point on the scale. You can see the shape. A cluster with two outliers looks nothing like an even spread, and the report shows you which one you have.

Disagreement is the finding, not noise

When a team splits on an item — half saying it's easy to raise problems, half saying it isn't — the instinct is to treat the split as measurement error to be averaged away. It's the opposite. A split means the team is not one habitat. Something differs by role, by tenure, by how close someone sits to whoever holds power, and the people at the quiet end are experiencing a different workplace from the people at the loud end.

The report says this in as many words when it sees a split, and points at it as the most interesting thing on the page.

Why people hold back — and what makes speaking up possible

Knowing that people stay quiet is not much use on its own. What helps is knowing why. When someone reports finding it hard to speak up, the survey asks a short follow-up: is it that you can't predict how it'll land, that you expect it to go badly, or that you don't think it'll change anything? Ambiguity, valence, futility. Those three have different remedies, and treating one as another is how well-meaning interventions fail.

Where power is involved, it asks what kind: formal authority, informal influence, expertise, or who's in the room. A team whose voice depends on the most senior person present needs something different from a team where it depends on who is considered the expert.

The report also probes the high scores, not only the low ones. When something is working, it asks what makes it possible — because a team that knows why speaking up is easy on Tuesday has something to protect and repeat, and most instruments only ever ask what's broken.

Not knowing is data

If a lot of people answer "I don't know" to whether it's clear what the team's priorities are, that is not a gap in the data. It is the finding. The report treats not-knowing as a signal in its own right rather than discarding it or folding it into a midpoint.

What people wrote, verbatim and shuffled

Comments come back exactly as written, unedited and unsummarised. They are never processed by AI, never paraphrased into themes, and they arrive shuffled and detached from the ratings their author gave, so no one's set of answers can be reassembled from the page.

Suggested experiments, matched to what the team said

The report ends with a small number of concrete things to try, chosen by fixed rules from the pattern in the answers — not a generic list of best practice, and not an AI's impression of the team. If the picture is one of futility, the suggestions are about closing loops. If it's ambiguity, they're about making reactions predictable. The point of the whole exercise is the conversation the team has next, so the report is built to hand them a starting place rather than a verdict.

What the report deliberately doesn't do

There is no overall score. There is no benchmark against other teams, other organisations, or an industry index — a team's only meaningful comparison is with its own past. And there is no view anywhere that lets someone above the team read one team's report: the administration tools are structurally incapable of it, not merely discouraged from it. A psychological safety score used to appraise a manager corrupts the measurement within one cycle, because everyone learns the number is a weapon and answers accordingly.

How anonymity holds up

Responses carry no name, no email, no IP address, and no receipt — a receipt would be a handle, and a handle is an identifier. Only the date of submission is kept, never the time. Results stay sealed until the survey closes and at least four people have answered, then release once to everyone together; that threshold and that sealing exist to stop anyone reading the report at four responses, then again at five, and deducing what the fifth person said.

The honest limit, which the survey states above every comment box: in a team of four or five, a colleague who knows you well may recognise your writing. Architecture can protect the data; it cannot protect a turn of phrase. Full detail is on the privacy page.

Read the specimen

The specimen report describes a team called Meridian Crew. Meridian Crew doesn't exist — the six responses were written to show a team with real disagreement in it, because a sample where everyone agrees would demonstrate nothing. Everything else is real: the same report builder, the same rules, the same layout your team would receive.

Read the specimen report Set up a survey for your team

The individual self-check is free and always will be. Team surveys are free during the current preview. If you'd like to talk about using this across an organisation, get in touch.