There’s a particular kind of leader who is widely admired.
They’re responsive, available and close to the work. When something wobbles, they step in. When a client escalates, they make the call. When two people in the team fall out, they smooth things over.
They’re the person everyone knows they can rely on.
They’re also often exhausted.
If you lead an agency or consultancy, you probably know how this happens. The client changes the brief on Thursday, the creative needs sharpening on Friday, the margin is already looking a little too interesting, and you know you can make the proposal better in half the time it would take someone else.
So you do.
The job gets done, the client is happy, and everyone moves on.
Until you find yourself doing something remarkably similar next week. And the week after that.
And that’s when being helpful starts to cost you.
If you'd prefer to listen rather than read, I explore this in more detail in the How to Lead mini-series: Why your voice isn't being heard, Part 1.
When helpful becomes the operating model
Being helpful isn’t a leadership flaw. Most of the time, it comes from competence and care.
You step in because you can see what needs doing and you know how to do it. Clients appreciate your responsiveness, your team knows you’ll support them, and senior stakeholders know they can rely on you.
The problem comes when the short-term fix becomes the way the organisation operates.
You rewrite the proposal because it’s quicker. You step into the scope conversation because you know how to handle the client. You smooth over the disagreement because you can sort it out in ten minutes.
None of those decisions is particularly alarming on its own.
But do it often enough and you can end up with a senior leader spending a surprising amount of time doing work that someone else should be learning to own.
Strategic conversations get pushed back. People who need to develop their commercial or leadership judgement get fewer opportunities to practise it.
And you spend your days being incredibly useful while wondering why you never seem to have time to think.
There’s a certain irony in being promoted into senior leadership and then becoming the most expensive pair of hands in the business.
The problem with being indispensable
If you’ve built your reputation on being the reliable one, stepping back can feel surprisingly uncomfortable.
You’ve spent years being the person who solves the difficult problem, calms the client, stays late to get the proposal out or steps in when nobody else quite knows what to do.
Those qualities probably helped you get where you are.
But the habits that make you successful as a high-performing operator don’t automatically help you at the next level.
At some point, being the person who can fix everything becomes less useful than building a team that can fix more things without you.
That sounds obvious.
It is considerably less obvious when someone is standing in your doorway saying, “I just wanted to check something…”
Linda knows this feeling well. She encourages everyone to take ownership, as long as they remember to check with her first.
The trouble is, helpfulness can create dependency without anyone intending it.
An Account Director is struggling with a client who wants another round of work without another penny of budget. You step in and sort it out. Everyone is relieved.
But what has the Account Director learnt?
Perhaps that when a commercial conversation gets uncomfortable, it goes upwards.
Or a Creative Lead brings you work that’s good but needs sharpening. You rework the narrative in the meeting, and the end result is better.
But they haven’t had the opportunity to work out how to make it better themselves.
Do that often enough and you can end up with a team that’s very capable of bringing problems to you.
That isn’t quite the same as building a team capable of solving them.
Helpful or replacing?
One of my favourite questions to ask when you feel the instinct to step in is:
Is my involvement building their judgement, or replacing it?
There’s a big difference between helping someone think and doing the thinking for them.
Instead of rewriting the proposal, you might ask, “Where do you think this is weakest?”
Instead of taking over the client conversation, “How are you planning to handle their objection?”
Instead of resolving the tension yourself, “What outcome are you both trying to achieve?”
You’re still involved. Your experience is still available. Standards still matter.
What changes is who owns the problem.
And yes, this can take longer.
There is something deeply satisfying about taking a problem away, fixing it and moving on. You've solved it, everyone can stop talking about it, and you can get back to the other 47 things in your inbox.
Helping someone work through it takes more patience, especially when you can already see the answer.
Unfortunately, leadership has an irritating habit of caring more about what works six months from now than what saves ten minutes on a Thursday afternoon.
The career cost of staying helpful
The more time you spend fixing, refining, smoothing and absorbing, the less time you have for the work that increasingly needs your attention.
Your judgement should go into things like direction, strategy, commercial decisions, relationships, developing people, and where the business is going next.
If your diary is still full of everyone else’s immediate problems, there isn’t much room left for any of that.
And this is where being extremely useful can become a career trap.
You’re so good at solving the problems in front of you that the organisation has very little reason to move you away from them. You become indispensable in the role you’ve created for yourself, and then wonder why nobody seems particularly keen to let you escape it.
What happens when you stop rescuing?
This isn’t about never stepping in.
A major client issue may genuinely need you. A difficult commercial decision may require senior judgement. Sometimes the quickest and best thing to do really is to take control.
The useful question is whether that’s the exception or simply how things work around you.
For the next week, just notice the moments when you rescue something.
You don’t need a complicated leadership tracker, although if you’re anything like some of the leaders I work with, you may now be wondering whether this could be colour-coded.
When you feel the instinct to fix, refine, smooth or absorb, pause and ask:
Am I helping this person develop their judgement, or am I replacing it?
Then see what happens.
You might discover that the person in front of you has considerably more judgement than you’ve been giving them the opportunity to use. Or you might discover something genuinely needs your involvement.
Either way, you know more than you did before.
When you stop automatically rescuing, people have to form their own view before escalating. They start handling more complexity themselves, and you get something increasingly valuable back: capacity.
Capacity to think about where the business is going, develop people, strengthen client relationships and make better commercial decisions.
More time, essentially, to do the work your role actually requires of you.
Being helpful feels good. It makes you useful and keeps things moving.
But if you’re always the safety net, people will keep looking for you when they fall.
And perhaps the most helpful thing you can do this week is resist being helpful for long enough to let someone else have a go.
Leave the proposal alone. At least until they’ve had a chance to think about it themselves.
If this pattern feels familiar, I explore it in more detail in the How to Lead podcast episode, The Hidden Cost of Being the Helpful Leader, including some practical ways to recognise when helpfulness has tipped into dependency.
You’ll also find more practical leadership insights and resources at waterfallhill.co.uk.
