I gave them room. Nothing moved.

A founder once told me, a few weeks into an engagement, that he had done everything the books say. He had stopped approving every decision and told the team, more than once, that they could push back. The meetings had only got quieter.

He took it personally. Most founders do, and I did too.

When I was leading a company myself and gave a team more room, the silence that came back felt like a verdict on me. Either I had hired the wrong people, or I was still in the way somehow. My reflex was to take control again: step into the decision, write the plan myself, show how it could be done. That felt safe for about a week. Mostly it confirmed what the team already suspected, that the room I offered came with conditions.

What I learned then, and see in almost every company I walk into now, is that neither explanation is usually right. The team is reacting to the company they have been working in for years. That company has been teaching them something different from what the leader is now saying.

Behaviour that once made sense

The behaviour that frustrates a leader during a change (people waiting, hedging, agreeing in the meeting and doing the old thing afterwards) rarely comes from bad will. Mostly it is protection. People learned at some point what was safe here, and they are still acting on it.

Maybe a previous leader didn't listen, or the last person who took the initiative got corrected in front of the team. People don't forget that because someone at the top says the rules have changed.

One team member put it to me very plainly: "I'll take the initiative once I know it's safe. Let's first see if this one stays."

That sentence is completely logical, and it keeps the company stuck. A leader starting from trust meets people still running on the old logic, and both sides are being reasonable.

Five patterns I keep running into

I call these employee styles. They are smart, mostly unconscious adaptations to a place where clarity or trust was missing for a while. Each has a real strength, and each turns into a brake when the pressure goes up.

The peacekeeper keeps the team together and calms things down. Under pressure he avoids the hard conversation for so long that problems simmer for months.

The soloist delivers high quality on her own, with little fuss. Under pressure she withdraws and does everything herself, and the information the rest of the team needs stays in her head.

The sceptic sees the risks nobody else wants to name and protects what works. Under pressure he answers every new idea with "yes, but", and the energy drains out of the room before anything is tried.

The controller keeps track of details, planning and quality. Under pressure nothing is allowed to go wrong, which leaves no room to try something new or to learn from it.

The chameleon adapts and builds bridges between people. Under pressure she moves along with everyone so well that nobody knows any more what she actually thinks.

None of these are character traits. They grew in a context that has since changed, and the habit hasn't caught up yet.

Why pressure makes it worse

When things are stable, people experiment a little. When a company is under pressure (growth that stalls, a founder who leaves, a restructuring) the whole system falls back on what it knows. Initiative turns into waiting, and roles get divided up tightly again.

That is self-protection, and it makes sense. It also means that the moment you most need people to move is the moment they are least inclined to. You offer room and people reach for something to hold on to.

What helps

More pressure rarely does. What I have seen work is slower and more specific.

Say out loud why the old behaviour made sense. Something like: "I understand this was the safe way to work here." It sounds small. People can only let go of a habit once they feel someone sees why they held on to it.

Be very clear about what is needed now. Room without a frame feels like a trap to someone who learned to be careful. Say where the company is going and what behaviour helps get there, in plain words, and say it more often than feels necessary.

Make the first steps small. One decision taken in the team instead of upstairs, or one meeting where the uncomfortable topic gets ten more minutes. When it works, make sure people notice it worked.

Slow down when you hit resistance. The reflex is to push harder, and I know that reflex well. It usually helps more to stop, ask a question without judgement and listen to the answer.

When it doesn't move

Sometimes a pattern sits so deep that nothing you do gets through. Then it is fair to admit that your leadership has limits here. It might need a different conversation, and sometimes a different person in the role. Sometimes it needs help from outside, when what is being touched goes deeper than work.

Saying that clearly is part of leading. It gives the person and the team something to stand on.

Where to start

If you recognise the silence, a few questions are worth taking to your next leadership meeting:

• What did people need to do here to get by, a few years ago?
• Which behaviour was rewarded then, and do you still see it now?
• What happens in this team when the pressure goes up?
• Which of the five patterns do you recognise, and what are they protecting?
• Is your own leadership adapting to the system: pushing harder, or holding back?

That last one matters most to me. I still walk into companies whose way of working goes against how I work, and I notice the system pulling at my old reflex to take control. A leader is part of the system they are trying to change, so I look at myself as carefully as at the team.

You don't have to work this out alone. If this sounds like your company, tell me what's going on.