The call always comes.

Three days before a large exhibition opens, something goes wrong. A graphic panel with a last-minute colour change. A structural element that doesn't fit the space as built. A client who has just walked the hall and decided the messaging needs to change.

It doesn't matter what it is. What matters is who the call goes to.

In most of the agencies I work with, it goes to the MD. Not because the project manager can't handle it. Not because the account director doesn't know the client. But because somewhere along the way, the agency learned that when things get difficult enough, the MD picks up. And the MD because they're good at their job, because they can see the solution clearly, because the client is standing in the hall  fixes it.

The stand opens on time. The client is reassured. Everyone goes home.

And the following month, at a different venue, with a different client, the call comes again.

Why does your team keep escalating to you?

This is the question most MDs are asking. It is the wrong question.

The right question is this: why are you making yourself available for them to do that?

Every time an MD steps in on the difficult client, the pressure decision, the moment a project goes sideways the agency absorbs a lesson. Not through a conversation or a policy. Through repetition. The lesson is that escalation works. That when something gets hard enough, the right move is to pass it upward. The MD will carry it. The MD always does.

Escalation works because you make it work. And the culture you have built is doing exactly what it was designed to do.

This is not a people problem. It is not a delegation problem, despite what most of the advice on this topic will tell you. It is a leadership infrastructure problem. The system is producing the results it was built to produce. The question is whether those are the results you want.

Is it really your team that's the problem  or is it a belief system?

When I name this pattern with MDs, the response is almost always the same. "But if I don't step in, things go wrong. The client suffers. I can't afford that."

And my question back is always the same: do you have evidence of that? Or is that a belief system, one you have confirmed, every single time you stepped in before your team had the chance to find out what they were capable of?

Think about what actually happens when you rescue. The client is fine. The stand opens on time. The belief is reinforced — without me, it would have gone wrong. But you never let it get to the point where your team had to navigate their way through it. So you don't know what they are capable of. And neither do they.

The rescue creates the evidence for the rescue. That is the mechanism. And it runs quietly, beneath the surface of every well-intentioned intervention, compounding over time into a senior team that is technically excellent and operationally dependent.

"The agency can only grow as far as what the MD can personally carry until the leadership layer is built."

An agency whose output is capped by the MD's personal bandwidth is not a scalable business. It is a well-run job. The two look identical from the inside, right up until the moment someone tries to value it, exit it, or step back from it.

What does above the line leadership actually look like here?

It does not look like stepping back and hoping for the best. It does not look like a new accountability framework or a restructure. It starts in one conversation, in one moment, when something lands on your desk that belongs on someone else's.

Instead of fixing it, you ask one question: what would you do here?

You give the power back. You stay in the room. You just stop being the answer in it.

That is the shift. Not dramatic. Not a management overhaul. One question, repeated consistently, until the team learns a different lesson. That the expectation is that they will solve it. That their judgment is what is wanted. That the call doesn't have to go upward because the capability to handle it is already there.

"The ceiling lifts when you stop being it."

Above the line leadership is not about doing less. It is about being present in a completely different way as the person who sets the standard and builds the capability, rather than the person who steps in when the standard isn't met.

The agencies that grow without getting heavier have one thing in common. The MD is busy above the line, not below it. Not less involved. Differently involved. The week still moves at pace. The decisions still get made. The clients are still looked after. But none of it requires the MD to be the one doing it.

Where to start

If this pattern is familiar, the place to start is not with the team. It is with one honest question asked at the end of this week: of the hours I worked, how many went to work that only I could do?

Not work that was quicker because I did it. Not work that felt safer because I was across it. Work that genuinely required my judgment, my relationship, my decision  at the level I am supposed to be operating at.

For most MDs, the first time they ask that question honestly, the answer is clarifying. And that clarity is usually enough to know where to start shifting.

I have made a short video on what above the line leadership looks like in practice across a leadership team  and where to start shifting it. Watch it at leadershipline.co.uk/atl_video

Suzy Malhotra is a leadership adviser to MDs and founders of creative, events, experiential and exhibition agencies. She ran an agency inside this industry for nearly thirty years. The Leadership Line — leadershipline.co.uk