Psychological safety shows up in small moments. It’s the second after someone asks a basic question, or the meeting where a missed deadline comes up. Amy Edmondson defined it as “a shared belief held by members of a team that the team is safe for interpersonal risk taking” (Edmondson 1999). Below are 12 everyday moments, each with what it looks like when people feel safe and what happens when they don’t. Read them as a checklist and see which ones you noticed on your team this week.
What the research links it to
Edmondson studied 51 work teams at a manufacturing company. Team psychological safety was linked to learning behavior, and learning behavior in turn linked it to team performance (Edmondson 1999). Google’s re:Work guide describes a study of 180 teams and puts psychological safety first in its list of five team dynamics. It reports that how a team worked together mattered more than who was on it (Google re:Work). A meta-analysis by Frazier and colleagues pooled 136 samples, with more than 22,000 people and nearly 5,000 groups, to map what comes before psychological safety and what follows it (Frazier et al. 2017).
On teams high in psychological safety, the guide says, members trust that nobody will shame or penalize them for admitting a mistake, asking a question, or offering a new idea. People on those teams were less likely to leave and were rated effective twice as often by executives. The moments below start with those three acts.
1. Someone asks a question the room thought was obvious
On a safe team, the answer comes without a sigh, and someone else says they wondered the same thing. Where safety is missing, someone says “we covered this,” and the next question arrives as a private message after the call. In one engineering forum thread, a commenter described a whole career of staying quiet out of fear of looking dumb.
2. A mistake gets mentioned by the person who made it
The person posts “I sent the wrong file to the client” in the team channel, and the replies are about the fix. On a team that doesn’t feel safe, the same mistake surfaces weeks later in a review, and nobody remembers who knew first. Edmondson studied patient care teams in two hospitals and found that teams differed in how often errors happened and in how likely members were to catch them and learn from them (Edmondson 1996).
3. Bad news reaches the manager early
A project is going to miss its date. On a safe team, the manager hears it from the person doing the work, while there’s still time to change the plan. On an unsafe one, the manager hears it from someone else, close to the deadline.
4. A junior person disagrees with a senior one in a meeting
A new hire says the senior engineer’s estimate looks too short. On a safe team, the senior engineer asks why, and the estimate changes or the reasons get clearer. On an unsafe one, the junior person says it to a peer after the meeting instead. The Thesis rule card has a line for this: “Every view is welcome, especially one that differs from yours.”
5. Someone gives feedback upward
An employee tells a manager that the new process slows their reporting down. On a safe team, the manager says thanks and later reports back on what changed. Where safety is missing, the cost shows up later. In a forum thread on honest feedback, one commenter wrote that even softened feedback to leadership got him ignored for a while, or marked for good.
6. A new idea gets raised in a meeting
The re:Work guide includes a scenario about a long-time manager who had grown intolerant of mistakes and challenges. He publicly dismissed an experienced team member’s well-researched idea and criticized that person to the team. After that, the team stopped offering ideas, and the proposal he drove was rejected by executives for lacking creativity. On a safe team, a half-formed idea gets a follow-up question before it gets a verdict.
7. Someone says “I don’t know”
In a stand-up or a client call, a person admits they don’t know the answer and says when they’ll find out. On a safe team, that’s a normal sentence. On an unsafe one, people guess and correct it later.
8. Someone asks for help early
A person stuck on a task asks a colleague while there’s still time to recover. On a safe team, asking reads as good planning. Where safety is missing, people work late to hide the gap, and the problem shows up at the deadline.
9. The manager names a mistake of their own
The re:Work guide passes on Edmondson’s tips, and one of them is to admit your own fallibility. A manager who says “I scheduled this too tight, that one’s on me” makes the next admission easier for everyone else.
10. A quiet person gets the floor and can pass
Someone who hasn’t spoken all meeting gets asked for their view by name. On a safe team, they can give a full answer, a short one or a pass, and all three are fine. The Thesis rules start the same way: “Before you start, agree together how passing works.” An invitation that can’t be declined works as an order.
11. Someone names a limit on their workload
A person says they can take the new project only if something else moves. On a safe team, the talk turns to what moves. On an unsafe one, they say yes in the meeting and miss deadlines later.
12. The retro talks about the process
After a release goes wrong, the team asks what made the problem hard to catch. On a safe team, the answers name steps, tools and handoffs. Where safety is missing, the retro looks for one person, and the next retro is quieter.
Questions to check the moments on your team
Each question below turns one or more moments into a topic. Use one or two in a retro or a one-on-one:
- When did someone last ask a question in a meeting that others were also wondering about?
- What happened the last time someone here admitted a mistake?
- How early do we hear about a slipping deadline?
- When did someone last change a senior person’s mind in a meeting?
- What feedback have we given upward this quarter, and what came of it?
- Which idea from the last month got a follow-up question before a decision?
- When is it fine to say “I don’t know” here?
- What would make it easier to ask for help sooner?
Practicing the moments with a word
The moments above are small risks taken out loud, and a card round gives a team a low-stakes place to take them. Each Thesis card has an idea on one side and an everyday thing on the other. A word on a sticky note works too.
Trust has Window on its back. A team might read Trust as the colleague they’d hand a project to without checking, or the first time a manager backed them in public. The Window side gives an easier way in: a desk by the window, a glass-walled office, a screen everyone can see.
Courage has Bicycle on its back. On a team, Courage can bring out the first time someone spoke up in a meeting, or pushed back on a plan. The bicycle side leads to learning to ride, or a commute in the rain.
Failure has Washing machine on its back. It sits close to moment 2: people talk about a launch that flopped and what they did next. The washing machine gives a lighter version of the same story: a shirt that came out pink, the first month living alone.
Each turn follows the same steps. Draw a card, choose the idea or the thing, roll the die and look at the word from that side. The die has six plain words: MEMORIES · BODY · PEOPLE · VALUES · CHILDHOOD · FUTURE. The only instruction is “Look at the word from that side.” The others ask what they’re curious about, and the rule card gives three examples of good questions: What did that feel like? Who else was there? Has it always meant that to you?
Pick one of the twelve moments and watch for it in your next team meeting: who spoke, and what happened next. For a short opener to start that meeting, see check-in questions for team meetings. Word pages: Trust, Courage and Failure. For more on running it at work, see Thesis for teams and classes. The online table is free. For the studies, see the research behind the deck. See the rules and the box. Related: how to build psychological safety in teams: 7 research-backed steps. Related: psychological safety in the classroom: what instructors can borrow from team research.