Search for psychological safety exercises and you get lists of workshop games and psychological safety activities: anxiety parties, empathy flashcards, circle drawings. Some are fine. But games run once at an offsite change nothing by Thursday, and as a CEO I never saw an offsite transform a team for longer than a week.
What worked were rituals: small, repeated structures inside the meetings and one-on-ones we already had. These are the ones I ran for years across ten countries, with the time each costs and what visibly changed, plus the popular exercises I would skip.
The psychological safety exercises that work are recurring rituals, not one-off games: a win round that alternates personal and professional openers, a meeting rating closed by asking what would raise it one step, leader-first failure sharing, a high five round, and stating the why behind every ask. Each takes minutes, and repetition is the active ingredient.
A psychological safety exercise is a recurring team practice that makes speaking up, admitting mistakes, and giving honest feedback feel routine instead of risky. A ritual that runs weekly beats a workshop that runs once, because safety is a price people re-check constantly, not a lesson they learn.
The win opener: 2 minutes per person, weekly
Every team meeting starts with a win, and the round doubles as a true check-in on where people actually are. The mechanic that makes it an exercise instead of a warm-up: alternate the type. One week the win is professional, the next it is personal, and I change the pattern up now and then so nobody arrives with a rehearsed answer.
The alternation is diagnostic. A group that only ever shares professional wins is telling you something, and a person whose personal wins are always fluff that does not matter is usually not really present. Over months, the personal weeks teach a team to be personal in a professional context, which is the exact zone where safety lives. Watch for the shift when people start referencing each other's wins; that is belonging becoming visible.
The meeting rating: 5 minutes at the close
I end weekly leadership meetings, staff meetings, and anything L10-shaped (the Level 10 format from the Entrepreneurial Operating System) with a rating round. Everyone scores the meeting, and I ask the top rater and the bottom rater the same thing: what needs to be true for that score to hold, or to go up one step?
Then the anti-gaming layer, because every rating ritual gets gamed by politeness. If everyone rates a nine forever, I do not let them off the hook: OK, what needs to be true for it to be a ten? They have to say something.
And when someone declares it the best meeting ever once too often, I throw the curveball: great, you run it next week. Rotating the facilitation ends the era of reflexive tens, because now everyone knows what running it takes. Leave the full five minutes before the meeting ends; feedback squeezed into the last thirty seconds is theater.
Leader-first failure sharing: 3 minutes, before new work starts
I celebrate wins and I celebrate failures, and I go first. Before we start something I have attempted before, I tell the team: I have done this before, and last time I really messed up by doing the following. So if I react a certain way during this project, you know why, and you know what I am worried about.
This does two jobs at once. It models vulnerability and normalizes admitting mistakes at the exact moment stakes are forming, and it decodes my future behavior so nobody has to guess what my reactions mean. The deeper story of what leader-first admission unlocks, including the best failure celebration my company ever held, is in psychological safety examples.
The high five: 2 minutes, any meeting
Simplest one on the list. Give yourself a high five for something you did that you are proud of, then give a high five to someone else on the team for something they did. Self-recognition trains people to own their contribution out loud, and peer recognition spreads the habit of noticing. It feels slightly silly, which is partly the point: a team that can be slightly silly together has already relaxed its guard.
Say the why: zero extra minutes, every ask
The exercise hiding inside every delegation. People are good at saying who should do something and when it is due, and micromanagers add the how, which is a recipe for failure. What I coach instead: say what needs to be done and what the definition of success looks like, say why it matters, and ask the person to come back with the when.
The why is the safety component, because people are often afraid to ask for it, and working without it turns every task into compliance. Simon Sinek built a book on starting with why; the EOS habit of framing discussions around a named issue does the same work. Great leaders say the why unprompted. If your rituals run well but delegation still feels tense, the sequencing problem usually lives upstream, in how to create psychological safety at work.
The two popular exercises I would skip
First, soliciting feedback you will defend. Asking openly for feedback and then arguing with what comes back is the cardinal sin of this entire discipline. One defensive response converts every future request into a trap people politely sidestep. If you are not ready to change, do not ask yet.
Second, ratings and surveys nobody acts on. A meeting rating you collect and ignore trains cynicism with perfect efficiency, and the corporate version is worse: employee surveys built to make leadership look good, measuring nothing but their own vanity. Almost any exercise works if you truly listen, truly care, and people have a purpose and a direction; almost none survives being visibly performative. That distinction, safety theater versus the real thing, is the core of what people get wrong about psychological safety, and the research base from Amy Edmondson says the same: the response to honesty, not the format, is what teaches teams whether speaking up pays.
Common questions about psychological safety exercises
What are the best psychological safety exercises for teams?
Recurring rituals beat one-off workshop games: a win opener alternating personal and professional, a closing meeting rating where the top and bottom raters explain what would raise the score, leader-first failure sharing before new projects, a high five round for self and peer recognition, and stating the why behind every delegated task. Each costs minutes inside meetings you already run.
How do you start meetings to build psychological safety?
Open with a win round, two minutes per person, alternating weekly between professional and personal wins. The alternation matters: personal wins teach people to bring who they are into a professional room, and consistently fluffy or rehearsed answers are an early signal that someone is not feeling safe or present. Change the pattern occasionally so it stays honest.
How often should psychological safety exercises run?
Weekly, inside existing meetings, indefinitely. Safety is a price people re-check every time they consider speaking up, so a ritual that lapses reads as a policy change. One-off workshops or offsites can open a conversation, but behavior resets within weeks unless a repeating structure catches it. Think habit, not event: small, boring consistency outperforms dramatic interventions.
Which psychological safety exercises do not work?
Any exercise that collects honesty and then punishes or ignores it. The two most common failures: leaders who ask for feedback and then defend themselves against it, and ratings or employee surveys that never produce visible change. Both convert future honesty into politeness. The format is rarely the problem; the response to what the format surfaces is what decides everything.
How do you get honest meeting feedback from a team?
End with a rating round and put names on the numbers: ask the highest and lowest raters what would move the score one step. Refuse permanent nines by asking what a ten requires, and rotate facilitation to whoever claims the meeting cannot improve. Protect five real minutes for the round; feedback compressed into the final seconds signals you never wanted it.
Rituals are the exercise
The pattern across every one of these psychological safety exercises: repetition inside real work, a leader who goes first, and a visible response to what surfaces. Pick two rituals, not five. Run them for a quarter without skipping, and let the team catch you acting on what they said. That consistency is the exercise; everything else is formatting.
The full ritual library
My book, the AI Leadership Mastermind, documents the complete meeting and delegation system these rituals come from, including the scripts and the one diagnostic I have never published. It is $29.99, here. Or start by seeing how your team actually experiences your meetings with the free leadership assessment.
