Teams are often told that psychological safety is a feeling to create. It is far more useful to treat it as a set of conditions you already control and are already setting, deliberately or by accident. Every recurring meeting has an order of speaking, a tolerance for silence, a way that a late objection gets handled, and a rule about what goes in the notes. None of those arrive from the department. A supervisor sets them.
The conditions matter most for the observations that are hardest to raise: that a notice will not work for the people who receive it, that a measure counts the wrong thing, that a decision was made before the meeting, that a process burdens one group of staff more than another. Those observations rarely arrive as finished arguments. They arrive as a half-formed sentence at the end of a long agenda, from the person with the least standing in the room.
What you do with that sentence is the whole lesson. If a question becomes homework for the person who raised it, questions stop. If it is treated as a challenge to the plan rather than information about the plan, only the confident keep speaking. If it disappears into “good point, let's take that offline,” the team learns that the meeting is for reporting and not for thinking. None of this requires anyone to be unkind. Warm, well-run meetings produce silence all the time.
This is also where a careful team settles into Minimization: the belief that because everyone is treated the same, everyone experiences the same thing. It sounds fair, and it removes exactly the differences that matter — who can read the agenda in the format it arrived in, who gets interrupted, whose files take longer, who is asked to explain themselves. Moving toward Acceptance means letting those differences back into the conversation and treating them as information about the design rather than as a complaint about the team.
