The meeting starts at nine. By nine-oh-four, everyone in the room has already done the same quiet calculation: what does Marcus want to hear? Nobody says it out loud. Nobody needs to. A slide that was blunt on Friday has been softened by Monday. A risk that was “serious” in the hallway has become “something we’re monitoring” by the time it reaches the table.

Marcus, a COO I’ll call by that name, is not a tyrant. He is warm, quick, generous with praise. He would be shocked to learn that his team edits reality before it reaches him. But they do, every week, and they have learned to do it so well that it no longer feels like a choice. It feels like how things are done here.

That is the moment a schema stops being personal. It becomes culture.

From one person’s pattern to everyone’s rules

A schema is an old emotional blueprint. It forms early, usually around a need that was not reliably met: to be safe, to be accepted, to be good enough, to have limits. It works like a pair of tinted glasses. We stop noticing the tint. We simply see the world in that colour and respond to it.

Most of the time, we talk about schemas as something inside one person. In Schemas in Leadership I spend a lot of time there, because that is where change begins. But leaders are not private people. Their reactions set the weather for everyone around them. When a leader with a strong Approval-Seeking or Defectiveness pattern flinches at bad news, the team does not see a schema. They see a rule: don’t bring problems unless you have them solved.

Teams are excellent learners. They watch what gets rewarded, what gets punished, and what makes the air in the room go thin. Within months they adapt. The leader’s private coping style becomes the team’s shared operating system. New hires absorb it in their first few weeks without anyone teaching it. This is how a pattern outlives the person who started it.

How to tell a schema has become culture

You rarely spot it in the values statement. You spot it in the small, repeated moments. A few signs I see often:

• The same silence in different rooms. Different people, different projects, and yet the same topics never get raised. Workload, a struggling peer, a strategy that isn’t working.
• Everyone protects the leader from the same thing. Disappointment, conflict, a missed number. The protection is collective and unspoken.
• The workaround has a name. “Pre-meetings” before the real meeting. A side channel where the honest conversation happens. When a team builds infrastructure around a feeling, the feeling is in charge.
• People who leave say the same thing. In exit conversations, the words repeat: “I never knew where I stood”, or “Nothing was ever enough.” That repetition is the pattern speaking.

What it costs

The cost is not drama. Schema-driven cultures are often polite, busy and productive on paper. The cost is quieter. Information arrives late and arrives filtered, so decisions get made on a version of the truth that has been made comfortable. Capable people spend energy managing the leader’s state instead of the work. The ones with the most options, often your best people, quietly leave for places where they can breathe.

And there is a paradox at the centre of it. The pattern was built to protect something: the leader’s sense of being good, safe or in control. At team scale, it produces exactly what it fears. The leader who most needs to hear the truth becomes the last person to hear it.

Five practices for leaders who want a different culture

Culture built by a pattern can be rebuilt with attention. Not with a new slogan, but with new repeated moments.

• Name your own pattern first. Before you ask the team to be more open, get curious about what you do when you feel disappointed, exposed or out of control. Your reaction in those seconds is the curriculum your team is learning from.
• Reward the first person who brings bad news. Not with a speech. With your face, your tone and your follow-through. The team is watching the first one far more closely than the tenth.
• Ask about the silence directly. “What are we not talking about in this team?” is an uncomfortable question. Ask it anyway, and then wait longer than feels natural.
• Retire one workaround. If the honest conversation happens in a side channel, bring one of those conversations into the main room and make it safe there.
• Look at the team, not only yourself. Your self-awareness matters, but culture lives between people. Ask the team how it experiences recognition, ownership, openness, trust and learning, and listen to the answers as data rather than verdicts.

If you want to go deeper into the personal side, the eighteen schemas and how each one shows up in a leader are the heart of my book Schemas in Leadership: Uncover Your Hidden Power. For the earlier step of spotting your own pattern, this piece on the hidden architecture of leadership is a good place to start.

A question to sit with

If a new person joined your team tomorrow, what would they learn in their first month about what is safe to say here, and whose feeling taught them that?

You don’t need to answer it quickly. The honest answer usually arrives a day or two later, often in the middle of an ordinary meeting.

The pattern is not the person

Marcus did not need to become a different man. He needed to see what his team had been protecting him from, and to show them, one meeting at a time, that the truth would not break him. Culture follows that kind of evidence. Slowly, and then all at once, a room starts telling the truth at nine o’clock instead of in the corridor at eleven.

Schemas start inside one person. They don’t have to end up running the whole team.