Skip-Level Leadership: When Senior Leaders Bypass Their Managers

Early in El Hassane Ben Ahmed’s career, a senior leader repeatedly bypassed the management layer. He stopped at desks, drew junior colleagues into direct conversations, and redirected priorities. The managers responsible for those teams often learned of the changes later, if at all.

At the time, the author noticed the discomfort it created but could not explain it. Over time something became clear. The managers under this leader became progressively less confident, less decisive and less trusted by their own teams. Chapter III.2 of The Lessons That Stayed traces that cause and effect.

“The leader who goes around people is not simply taking a shortcut. They are disrupting the system through which authority, information, and accountability flow.”

A pattern more common than acknowledged

When senior leaders bypass the chain of command, the effects are rarely neutral. The chapter’s central argument is balanced: senior leaders have a legitimate interest in operational reality, but habitually going around the management layer carries high costs for managerial authority, team cohesion and organisational accountability.

What hierarchical bypass is

The book defines it precisely: a leader at one level communicating with, directing or extracting information from people below their direct reports, without the knowledge or involvement of the intermediate managers.

That definition matters, because not every contact between senior leaders and frontline staff is bypass.

Why hierarchy exists in the first place

Corporate governance rests on a simple principle, set out by Robert Monks and Nell Minow: accountability is meaningful only when there is a direct, transparent link between authority, responsibility and consequence. A manager who is accountable for a team’s results but whose priorities are regularly rewritten from above has responsibility without authority. The link is broken.

Three motivations for bypass

Bypass rarely reflects malicious intent. The chapter identifies three common motives.

1. Distrust of the management layer

The most psychologically complex motive. The senior leader does not trust what managers are telling them, so they go to the source. Sometimes the distrust is justified. Bypass does not fix it. It confirms it.

2. A desire for direct control

Some leaders prefer to stay directly involved in day-to-day decisions. In a growing organisation, this treats a structural challenge as if it were a personal one. What is needed is to develop the organisation’s collective capacity, not to add one more set of hands.

3. The belief that formal structures slow things down

Sometimes they do. But the answer is to fix the structure, not to route around it. Every workaround teaches the organisation that the official process is not the real one.

What it does to the management layer

Robert Kahn and colleagues identified role ambiguity, not knowing clearly what you are responsible for or what authority you have, as a significant predictor of job strain, reduced performance and intention to leave. Habitual bypass creates exactly that. Managers stop knowing whether their decisions will stand, so they stop making them. Teams learn that the real decisions come from above, so they stop bringing problems to their manager. The senior leader then sees weak managers and concludes that bypass is necessary. The cycle feeds itself.

Presence without disruption

The chapter returns to Grant as the clearest model. His after-action notes from battlefield visits recorded what he had observed and what it revealed about conditions. Direction, when needed, went back through the commanders. The book draws two disciplines from this.

Separate listening from directing

The most important discipline for senior leaders on operational visits is to keep listening and directing apart. When you hear something that needs action, resist the instinct to give an instruction on the spot. Note it, then take it to the manager. This is hard for action-oriented leaders, which is why it needs to be a deliberate habit.

Keep managers informed

Make sure managers know when you are meeting their teams, what was discussed and what follow-up is expected. A skip-level conversation that the manager knows about strengthens the structure. The same conversation behind the manager’s back weakens it.

Practical guidelines for senior leaders

1. Tell managers before you visit their teams, and invite them if appropriate.
2. Ask questions: what is getting in your way, what would you change, what am I not hearing?
3. Do not reassign work or change priorities during the visit.
4. Debrief the manager afterwards with what you heard, framed as information rather than verdict.
5. If you find yourself bypassing a particular manager often, address the underlying issue with that manager directly.

Ronald Heifetz and colleagues describe this as getting “on the balcony”: stepping back to see the whole system rather than diving onto the dance floor to fix one part of it.

Presence without appropriation

The lesson of Napoleon is not that senior leaders should be remote. The lesson of Grant is that they can be closely connected to operational reality without disrupting the structure that makes that reality sustainable.

“Strong leaders remain accessible and curious about what happens throughout the organisation. But they also protect the integrity of the management structure that allows organisations to function effectively at scale.”

The challenge, the author concludes, is not visibility. It is what you do with what you see.