Why Your Team Won't Step Up (And What Your Leadership Has to Do With It)

Why Your Team Won't Step Up

You hired capable people. You trust them. You give them real work and real responsibility.

So why does everything still come back to you?

The client escalation that should have been handled two levels below you. The decision your Head of Production has been sitting on for three days waiting for your input. The deliverable that went out under your name because, by the time you'd revised it to the standard it needed to be at, it effectively was yours.

You've told yourself the story that your team just isn't ready yet. That they need more experience. That the standard isn't there.

Here's what I'd ask you to consider instead: what if they're not failing to step up, but responding perfectly rationally to the system you've built around them?

What the system is actually teaching

Every leadership behaviour creates a signal. The problem is that the signal being received is rarely the one being sent.

When you solve a problem your senior leader brings to you, you believe you're modelling good thinking. What they learn is: bring problems upward, they get resolved faster.

When you jump into a difficult client situation to support your account director, you believe you're backing them up. What they learn is: wait for backup before handling anything difficult.

When you revise work before it goes to a client, you believe you're protecting standards. What they learn is: their judgment isn't trusted, and someone will fix it anyway.

None of this is malicious. Most of it comes from genuine care for the work and the client. But repeated consistently, it builds a team that has been trained out of ownership -- not because they lack capability, but because the system has made dependency the rational choice.

This is one of the patterns I see most consistently in creative and events agencies after a leadership transition. A new MD, a restructure, a merger -- the leader is focused on getting the new configuration to function, and in the process of holding everything together, quietly builds a team that cannot hold itself.

The three patterns worth examining honestly

You coach by solving. A senior leader brings you a problem. You ask a few questions, identify the issue, tell them how to fix it. Efficient, clean, done in five minutes. But they just watched you solve a problem rather than solving one themselves. The next time a similar situation arises, the path of least resistance is the same: bring it to you.

The shift is not complicated but it is slower, at least initially. "What options have you considered?" "What do you think is the right call?" "What would happen if you went with that?" The first few times this takes longer than just answering. After ten times, they stop bringing you that category of problem entirely.

You delegate the task but keep the decision. You hand something over but check in multiple times before it lands. You suggest the approach. You review the draft before it goes anywhere near the client. You step back in the moment it gets difficult. This is not delegation -- it is you doing work through someone else's hands. And it teaches them that ownership is nominal, because the real owner never actually let go.

You hold a standard they cannot hit. There is a difference between work that is client-ready and work that is exactly how you would have done it. If your team consistently produces the former but you only accept the latter, you are not raising standards. You are making the gap between their judgment and yours permanently visible, and permanently discouraging them from trying to close it.

Why this matters beyond the MD's workload

The obvious cost of a team that won't step up is the MD's time. Decisions that should be made at director level. Conversations that should never reach your desk. The strategic headspace you cannot find because you are still in the operational detail.

But the less visible cost is what it does to the people beneath you.

Capable leaders who are not given real ownership do not stay and improve. They stay and become frustrated, or they leave. Either way, the agency pays. In creative and events agencies specifically -- where the work demands judgment, initiative and the confidence to hold a client relationship independently -- a team trained into dependency is not just an MD problem. It is a commercial and retention problem.

What actually changes things

The shift from solving to coaching is not a personality change. It is a decision about what your role is. Are you the person who holds the standards, or the person who builds the people who hold the standards?

Above-the-line leadership in this area looks like: asking questions instead of providing answers, letting your senior team arrive at the solution and own it, tolerating an approach different from yours when the outcome is sound, and creating enough distance from the day-to-day that your team has space to actually lead.

It is uncomfortable at first. There will be a period where things feel slower, where you bite your tongue more than you speak, where you let something go out that you would have done differently. That discomfort is not a sign it is not working. It is the system adjusting.

The leaders who come through the other side of that adjustment describe the same thing: a team that brings solutions instead of problems, that holds its own standards when the MD is not in the room, that can be trusted with a client relationship that does not need to be propped up from the top.

That is not an accident. It is what happens when someone stops being the answer to every question long enough for other people to become the answer instead.

Suzy Malhotra is the founder of The Leadership Line, leadership coaching and consultancy for MDs and founders of creative, events, experiential and exhibition agencies. She co-founded and ran 4D Design for nearly 30 years. Book a discovery call or download the white paper to find out more.