Psychological safety has become one of those phrases that gets used so often it has stopped meaning anything specific. Teams talk about it in retrospectives. Managers put it in their leadership principles. Consultants build frameworks around it.
Most of what gets said about it focuses on the same thing: are people willing to speak up? Will they admit mistakes? Will they disagree with someone senior in a meeting without fear of consequences?
Those things matter. But they are not the most useful signal.
The most useful signal of psychological safety on an engineering team has nothing to do with what happens in the meeting. It has to do with what happens before it.
The Thing That Tells You Everything
Pull up a story in refinement. Watch what happens.
In a team without psychological safety, the story appears on the screen and the room waits. Nobody has seen it before. The scrum master reads it aloud. Silence. A clarifying question gets asked. Another one. The conversation starts from zero because everyone is starting from zero — nobody looked at it before they walked in.
In a team with psychological safety, something different happens. Someone has a question ready. Someone else has already identified a dependency. A third person has a concern about the approach that they formed before the meeting started. The conversation begins in the middle rather than at the beginning because people came prepared to have it.
That preparation is the signal.
An engineer who looks at the sprint board before a refinement session has made a bet. They invested time and mental energy before anyone asked them to. That investment only makes sense if they believe it will pay off — if they believe the meeting is going to be a real conversation, that their preparation will matter, that showing up ready is going to be worth something.
That belief is psychological safety expressed as behavior.
It is not “I feel safe to speak up.” It is something more fundamental: “I believe this environment is worth investing in.”
The Misconception Worth Naming
Most managers think psychological safety means being nice. No conflict, no critical feedback, no hard conversations. A team where everyone feels comfortable and nothing is ever uncomfortable.
That is not psychological safety. That is conflict avoidance dressed up in better language.
Real psychological safety is not the absence of discomfort. It is the presence of trust — trust that the discomfort is worth it, that engaging with a hard problem will produce something useful, that a mistake will be treated as information rather than evidence of failure.
A team with genuine psychological safety can have a sharp disagreement in refinement about the right approach and leave the meeting aligned and energized. A team without it will have no disagreement at all — and leave the meeting having agreed to something nobody actually believed in, because the cost of saying so felt too high.
The silence that looks like harmony is often the most dangerous thing in the room.
How Preparation Becomes Self-Reinforcing
Engineers do not show up prepared because you tell them to. They show up prepared because they have seen that preparation works.
Here is what that looks like in practice.
A refinement session with five stories on the agenda. Everyone has looked at the board before the meeting. The first story gets pulled up and someone already has a question. The question gets answered. The next story. Someone has identified a dependency. It gets discussed. The story gets refined. Third story, fourth story, fifth story — the meeting moves.
With twenty minutes left on the clock, you are done.
That twenty minutes is the return on investment. It is immediate, tangible, and felt by everyone in the room. Not in the abstract — in their calendar. They have twenty minutes back in their day that they did not expect to have.
Engineers are rational. When preparation produces time back, they prepare. Not because it is the professional thing to do. Because it works.
The next refinement session, a few more people show up having looked at the board. The session moves faster. More time back. The session after that, a few more people. The behavior compounds because the reward is real and it is immediate.
You do not have to manufacture the incentive. The meeting itself is the incentive. Your job is to make sure the meeting is worth preparing for.
What Makes a Meeting Worth Preparing For
An engineer will look at the stories before a refinement session if they believe the following things are true:
Their preparation will be used. If they come in with a question and nobody engages with it — if the scrum master plows through the agenda and the questions get deferred or dismissed — they will not prepare next time. Preparation has to produce something in the room.
The meeting will be a real conversation. If refinement is a walkthrough where the scrum master reads stories and engineers nod, there is nothing to prepare for. The meeting is not asking anything of them. Preparation only matters if the meeting requires thinking.
The stories will be ready to refine. If the team consistently pulls up stories that are not ready — vague requirements, missing context, no clear definition of done — preparation becomes frustrating rather than rewarding. You can think about a story all you want before the meeting and still not be able to do anything useful with it in the room.
All three of these conditions are in your control. The stories you bring to refinement, the way you run the meeting, the way you respond to preparation when you see it — these are the conditions that make preparation rational or irrational for your engineers.
How to Signal That It Matters Without Making It Weird
You do not need to call out preparation explicitly. You do not need to praise the engineer who had a question ready or single out the one who clearly looked at the board. Making it feel like a gold star undermines the point — preparation should be the norm, not a performance.
What you do instead is let the meeting speak for itself.
When refinement moves well — when stories get refined efficiently, when the conversation is substantive, when the team gets out early — that outcome is its own signal. Everyone in the room knows why it happened. They felt the difference. The engineer who prepared knows their preparation contributed to that. The engineer who did not prepare knows it too.
The meeting that finishes early because everyone was ready feels completely different from the meeting that drags because nobody was. The energy is different. People leave with momentum instead of exhaustion. That feeling is more powerful than any recognition you could give.
And then — simply, genuinely, without ceremony — you tell the team you appreciate getting the time back.
Not “great job preparing everyone.” Not a performance review moment. Just: I noticed, I appreciated it, thank you.
That is enough. It lands because it is real. Engineers can tell the difference between a manager performing gratitude and a person acknowledging something that actually mattered to them.
The Environment That Produces This
Preparation before a meeting is a downstream effect. It does not happen because you ask for it. It happens because the environment has taught engineers that engagement is worth it.
That environment has a few consistent characteristics.
Stories arrive at refinement ready to be discussed — not vague, not missing context, not half-formed ideas that need another meeting before they can be refined.
Questions get real answers. When an engineer asks something in refinement, the answer is substantive — not “we’ll figure that out in the sprint” or “let’s take that offline.” The question gets engaged with in the room.
The meeting requires something from the engineers. Not passively watching a scrum master read stories — actively thinking, asking, proposing, deciding. The meeting asks for their judgment and uses it.
And when the meeting goes well because everyone showed up ready — when the team gets time back because the preparation paid off — that outcome is acknowledged. Not effusively. Just honestly.
Build that environment consistently and the preparation will follow. It is not a culture initiative. It is not a values exercise. It is a rational response to a meeting that is worth preparing for.
That is what psychological safety actually looks like in practice. Not the absence of fear. The presence of a belief that the work is worth investing in.
If this resonated, the thinking behind it goes deeper in my book — Getting Engineers to Give a Damn: A Manager’s Guide to Building Ownership Inside Broken Systems. Written for managers inside large, constrained organizations who are tired of meetings that nobody prepared for.
Top comments (0)