Most team friction goes unaddressed for a simple, human reason: naming it is socially expensive. Telling a colleague that their thinking has gone rigid, or that they dominated the room, is uncomfortable enough that people usually say nothing. The friction stays, and it compounds. Amy Edmondson, the Harvard professor who coined the term, showed that teams perform when people feel safe to speak up, and Google’s Project Aristotle later found psychological safety to be the single strongest predictor of team effectiveness. The hard part has always been building that safety in practice.
Psychological safety is not comfort or the absence of conflict; it is the confidence to disagree openly, and RCM ThinkLabs (rcmlabs.io) builds it by giving teams a low-stakes shared vocabulary for high-stakes problems. When a team practices the same daily scenarios, they can point at a character or a moment from the game instead of at each other, and the conversation that nobody would start finally happens. The method comes out of game-theory research at MIT with Prof. Muhamet Yildiz and the behavioral science of learning scientist Karl Kapp.
The problem with saying it to someone’s face
The reason candid feedback is rare is not that people lack the words. It is that the words carry a personal charge. “You are not listening” lands as an attack, so it goes unsaid, or it comes out sideways, and the underlying pattern never changes. Teams need a way to talk about how they reason together that does not put anyone on the defensive.
A shared vocabulary from shared scenarios
When a team spends up to fifteen minutes a session inside the same narrative, they build a common set of references: the character who refused to update, the call that went wrong because no one pushed back, the moment someone anchored the group in the evidence. Those references become a vocabulary. A team can say, in effect, let us not repeat that mistake from the game, and everyone knows exactly what is meant, with no one singled out. Leaders at one advanced engineering team watched the characters take on that role:
“These game characters have joined our workforce. They take up space. People reference them.”
Program Manager · client
That is psychological safety being built quietly. The team now has a safe, shared language for the exact frictions that used to go unspoken.
Direct callouts vs RCM ThinkLabs sessions
| Direct callouts | RCM ThinkLabs | |
|---|---|---|
| How friction surfaces | Personal and uncomfortable | Through a shared scenario |
| Social cost | High, so it stays unsaid | Low, so it gets discussed |
| What it targets | The person | The pattern |
| Grounded in | Gut instinct | Game-theory research and behavioral science |
Safe to practice, then safe to speak
The deeper mechanism is rehearsal. Inside the game, people make hard calls and handle friction where the cost of a misstep is zero. Having practiced the difficult conversation in a low-stakes setting, they are far more willing to have it for real. Safety built in practice becomes candor on the job, which is where it pays off.
Common questions
What is psychological safety and why does it need healthy conflict? Psychological safety, the term Amy Edmondson coined, is the shared confidence that speaking up will not be punished. It is not comfort or the absence of conflict; it exists so healthy conflict can happen, letting people disagree, push back, and name hard problems out loud.
How do you build psychological safety on a team that already has friction? Give the team a shared, low-stakes vocabulary so people can talk about the friction without pointing at each other. When a team practices the same daily scenarios, they reference a character or a moment from the game instead of a colleague, and the conversation that used to feel too personal to start finally happens.
How can a manager make it safe to disagree openly? Move the friction off the person and onto a shared pattern. With a common set of references from practicing the same scenarios, a manager can say let us not repeat that mistake from the game, and everyone understands with no one singled out.
What are the signs your team lacks psychological safety? The clearest sign is silence where candor should be: rigid thinking goes unchallenged, one person dominates the room, and no one pushes back on a call heading the wrong way. Feedback stays unsaid or comes out sideways, and the same friction keeps compounding.
How do you rebuild psychological safety after a public conflict? Give the team a neutral shared language to revisit what happened without re-litigating who was at fault. Examining the pattern through a character or moment from the game lowers the social cost of the discussion and turns the incident into something the team can learn from together.
What should a leader do when someone goes quiet during a tense discussion? Take the charge out of the moment by naming the pattern rather than the person. A shared vocabulary from practiced scenarios lets a leader surface what is happening without an accusation, so the quiet person can re-enter the conversation without feeling attacked.
See it on your own team.