A CEO said something to me recently that I have heard in some form from almost every CEO I have ever worked with.

"Vijay, I have a team of experienced, capable people. They are not junior. They are not new. They have been doing this for years. So why do they wait to be told? Why do they not just lead?"

— CEO, professional services firm, £12M turnover

What I said next made him go quiet.

I said: "They do not wait to be told because they cannot lead. They wait to be told because your system trained them to."

That was not easy for him to hear — because it meant the problem was not sitting in his team. It was sitting in the system he had built around them. And that system started with him.

"Your team is not waiting because they cannot lead. They are waiting because the system taught them that leading is risky and waiting is safe."

— Vijay Mistri

What follows are three revelations about why capable people stop taking initiative. Each one goes deeper than the last. By the end, you will see your leadership team — and your own role — in a completely different light.

Three Revelations. Each One Deeper Than the Last.

Revelation 1

Your System Taught Them to Wait

Think about what happens in your business when a leader makes a decision independently. In most leadership teams, one of three things occurs:

  • The CEO questions the decision after the fact — "Why did you not run that past me first?"
  • The CEO overrides the decision publicly — "Actually, I think we should go a different direction"
  • The CEO quietly redoes the work, sending the message that the original decision was not good enough

Each one of these moments teaches the same lesson: deciding alone is risky. Waiting for the CEO is safe.

It only takes two or three of these moments for an intelligent leader to recalibrate their behaviour permanently. They stop deciding. They stop initiating. And within months, the CEO is wondering why nobody is taking initiative — when the system has been systematically removing every incentive to do so.

This is not a character flaw in the team. This is classical conditioning. The system trained them. Not deliberately. Not maliciously. But the system trained them. And now the system needs to untrain them.

Empty boardroom — a leadership team that defers all decisions upward is a symptom of system design, not personal failure
A team that always defers is not a people problem — it is a system design problem. The architecture of how decisions are made determines how much initiative the team will take.
Revelation 2

Learned Helplessness — The Psychology Behind the Passivity

There is a concept from psychology that every CEO needs to understand: learned helplessness.

It was first observed in research where subjects were placed in situations where their actions had no effect on the outcome. They could act or not act — and the result was the same. Over time, they stopped acting entirely. Even when the situation changed and their actions could have made a difference, they had learned that action was pointless. So they did nothing.

Your leadership team can develop the same condition.

A leader brings an idea and it goes nowhere. They raise a concern and it is acknowledged but never addressed. They set a goal and it is quietly abandoned without consequence. They make a commitment and nobody tracks whether it was delivered. They learn, over time, that their actions do not change the outcome. The system does not respond to their effort.

So they stop putting in the effort. Not visibly — they still attend meetings, send emails, look busy. But their discretionary effort, their initiative, their genuine leadership? That has been extinguished by a system that taught them it does not matter.

From the outside, the team looks functional. They are present. They are compliant. But they have checked out internally. And the CEO cannot understand why a room full of talented people produces so little.

"The system you ignore will become the system that defines you."

— Vijay Mistri

Revelation 3

The Inverted Consequences — When Passivity Becomes the Rational Choice

This is the deepest revelation — and the most uncomfortable. In many leadership teams, the consequences are inverted. The system punishes the behaviour it should reward, and rewards the behaviour it should punish.

What Gets Punished

Taking Initiative

A leader makes a bold decision and it does not land perfectly. They get questioned. They get second-guessed. In some cases, they get publicly corrected. The consequence of acting is risk.

What Gets Rewarded

Waiting and Deferring

A leader does nothing, defers everything, never acts independently. Nothing happens to them. They are often seen as reliable — because they never make mistakes. The consequence of inaction is safety.

When initiative is punished and passivity is rewarded, what do intelligent people choose? They choose safety. Every time. Not because they are weak — because they are rational. The system has made passivity the logical choice.

The fix is to invert the consequences back. Initiative must be visibly rewarded, even when the outcome is imperfect. Passivity must be visibly addressed. A leader who waits for permission when they had the authority to act must be asked — consistently, without blame — "Why did you wait?"

That question, asked consistently, rewires the system faster than any training programme ever will.

Because accountability is not about catching people. It is about freeing them.

Leadership team session — redesigning decision rights and accountability architecture
Rebuilding initiative in a leadership team requires both a structural redesign of decision rights and a simultaneous shift in the behavioural architecture — both must happen together, not in sequence

The Five-Minute Test That Reveals Your System's True Architecture

This challenge takes five minutes, but it will reveal more about your leadership system than any assessment or away day you have ever commissioned.

The 5-Minute Leadership System Test

Pick a decision. Delegate it. Watch what happens.

Pick one decision that normally comes to you for approval — something in the £5,000 to £20,000 range if you are a £3M business. Something a senior leader in your team should be able to handle independently. Then do this:

1

Go to the relevant leader and say: "This decision is yours. Here are the boundaries. Here is the budget. I trust your judgement. Make the call and tell me what you decided afterwards."

2

Say nothing else. Do not add caveats. Do not hover. Give them genuine authority — not the appearance of authority with a safety net attached.

3

Watch what happens. Their response is not about them. It is a precise diagnostic of the system you built around them.

Reading the Outcome

If They Decide Quickly and Confidently

Your system has more capacity than you realised

You have been holding on to something you did not need to hold. The team is ready. The bottleneck was the architecture, not the people. Start delegating systematically.

If They Hesitate or Come Back to Check

Your system has trained them to wait

That is the signal the architecture needs rebuilding — not the people. The hesitation is not weakness. It is a completely rational response to a system that has taught them that acting alone carries risk.

Either outcome is valuable. One tells you the system works. The other tells you exactly where to start fixing it.

"The moment you change the system, the leadership will follow. Every time."

— Vijay Mistri

Why Both the Structure and the Behaviour Must Change Together

The structural fix is designing clear decision rights — who decides what, in what range, with what boundaries, without needing to escalate to the CEO. That is the architecture work.

But the behavioural shift is equally essential. The learned responses — the instinct to check, to defer, to wait for permission — have been conditioned over months or years. They will not disappear because a decision rights framework was printed and distributed. The human barrier underneath the gap must be addressed at the same time as the structural gap itself.

A structural fix without a behavioural shift reverts within ninety days. Every time. This is why the gap has two layers — the system that needs redesigning, and the conditioned response that needs unconditioning. Both must happen simultaneously. That is the dual fix. And it is what separates a genuine operating system intervention from a framework that looks good on paper and disappears in practice.

Watch the Full Video

Find Out How Deep the Founder Bottleneck Goes in Your Business

The Hidden Value Report maps all 15 gaps — including the founder bottleneck and accountability erosion — across your specific leadership system. 40 questions. 30+ pages. Reviewed personally by Vijay within 24 hours.

Frequently Asked Questions

Q
Why does my leadership team wait for permission before acting?

Capable leaders wait to be told not because they cannot lead — but because the system trained them to wait. When a CEO questions decisions after the fact, overrides them publicly, or quietly redoes the work, it takes only two or three of those moments for an intelligent leader to conclude that deciding alone is risky and waiting is safe. This is classical conditioning. The fix is in the system, not the people.

Q
What is learned helplessness in a leadership team?

Learned helplessness occurs when a leader's actions consistently have no effect on outcomes — ideas go nowhere, concerns are acknowledged but never addressed, goals are set and quietly abandoned. Over time, the leader stops investing discretionary effort or initiative. From the outside the team looks functional. Inside, they have disengaged. The system taught them that their actions do not change outcomes, so they stop trying.

Q
What are inverted consequences and how do they destroy initiative?

Inverted consequences occur when a leadership system punishes initiative and rewards passivity. A leader who acts independently and makes an imperfect decision gets questioned and corrected — initiative is risky. A leader who waits, defers, and never acts independently faces no consequence — passivity is safe. When intelligent people face this system, they choose passivity rationally. The fix is to invert the consequences back: visibly reward initiative even when outcomes are imperfect, and consistently question leaders who wait when they had the authority to act.

Q
How do I know if my system has trained my team to wait?

Run the five-minute test. Pick one decision normally requiring your approval — in the £5,000 to £20,000 range for a £3M business. Go to the relevant leader and tell them the decision is theirs, give clear boundaries and budget, and ask them to report back what they decided. If they decide quickly and confidently, your system has capacity you are not using. If they hesitate, ask "are you sure?", or decide and then check anyway — your system has trained them to wait.

Q
What is the founder bottleneck and why is it so costly?

The founder bottleneck is Gap 8 in the 15 gaps framework — and it is the most seismically connected gap, triggering six others simultaneously. It occurs when 60 to 80 percent of meaningful decisions require CEO approval. Over time, this creates a team conditioned to defer upward. Annual cost in a £3M business: £10,000 to £18,000 tracked — but the full compounded cost across the six triggered gaps is substantially higher.

Q
Why does a structural fix without a behavioural shift always revert?

Because the gap has a human barrier underneath it that built the structural problem in the first place. Print a decision rights framework and the learned responses — the instinct to defer, to wait, to check — remain intact. Within ninety days, the old patterns return because the behaviour was never addressed. Both the structural redesign and the behavioural shift must happen simultaneously. That is the dual fix.