Psychological safety, in practice
2026-10-19 · The Scrums team
When Google studied what made its teams effective, the strongest factor was whether people felt safe to take risks in front of each other. Here's what that looks like in a team's ordinary meetings.
In 2015, Google published the findings of Project Aristotle, a study of what made some of its teams more effective than others. The researchers expected the answer to be about who was on the team: seniority, skills, personalities. It wasn't. The strongest factor was psychological safety: whether people believed they could take a risk in front of their teammates, such as admitting a mistake, asking a basic question or disagreeing, without being punished or embarrassed for it.
The term comes from Amy Edmondson, a professor at Harvard Business School, who defined team psychological safety in a 1999 paper. Her earlier research on hospital teams had found something surprising: the better teams reported more errors, not fewer. They weren't making more mistakes. They were more willing to talk about them.
It's built in small moments
Psychological safety isn't created by an offsite or a poster. It's built, or worn away, in ordinary meetings, by small things:
- Who speaks first. When the most senior person gives their view first, everyone else adjusts theirs.
- Whether quiet people get in. Talking-only meetings favour the fast and the confident.
- How bad news lands. The first time someone raises a problem and gets blamed for it is the last time they'll raise one.
- Whether anything happens. Honesty that leads nowhere stops.
Meetings that make it easier
Scrums is designed so that the safe thing to do and the easy thing to do are the same:
- Everyone writes before anyone talks. In a retro, cards are written privately and revealed together.
- Anonymous by default. Retro cards' authors never leave our server, and health checks never show who rated what. In anonymous retros, comments can be anonymous too.
- Votes stay hidden until they're all in. In dot voting and sprint poker, nobody sees which way the room is leaning before casting their own.
- Follow-through is visible. Action items have owners and due dates, and the next retro starts by reviewing them.
None of this replaces a team lead who responds well to bad news. But it lowers the price of speaking up, which is where safety starts.
Run a retro in your browser, no account needed, and notice how different it feels when nobody can see who wrote what.
More on anonymous retrospectives in Scrums.