Advanced leadership: balancing strategic thinking with operational pressure

Some weeks, I look at my calendar and barely recognise the plan I set out to follow. Meetings I didn’t schedule appear between the ones I did. A decision I delegated finds its way back to my desk. By Friday, I’ve solved a dozen problems and made almost no progress on the three priorities I told my team mattered most.

I don’t think this happens because I’m disorganised. I think it happens because operational pressure is patient. It doesn’t announce itself as a threat to strategic thinking — it arrives as one reasonable request after another, each one easy to justify in the moment. Say yes enough times, and the job quietly becomes reactive management, even for someone whose actual mandate is to look further ahead than anyone else in the room.

That’s the paradox of advanced leadership. The more senior I become, the more operational noise finds me, and the less time I seem to have for the thinking that senior roles actually exist to do. Innovation, workforce planning, capability building — none of it competes well against a problem that needs an answer today. Given the choice between urgent and important, urgent wins by default, not by design.

But you don’t need to fall into this trap. Let’s dig in further so you don’t.

Why the drift happens

I’ve noticed it rarely feels like a decision. It’s death by a thousand small ones. I answer the question myself because it’s faster than explaining it to someone else. I sit in on the meeting because I’ve always sat in on that meeting. I keep making calls that no longer need me, and my team learns, correctly, that escalating to me works. Every one of those choices is defensible on its own. Together, they add up to a leader who has stopped leading strategically without ever meaning to.

Deciding what actually needs me

The shift starts with an honest audit of where my time goes, not where I assume it goes. I’ve found it useful to sort decisions into three groups:

• Things only I can decide because of risk, authority or relationships
• Things my team is capable of deciding but hasn’t been given the confidence or framework to own
• Things that shouldn’t reach me at all, because they belong somewhere else entirely.

Most operational load sits in that middle category, and that’s where delegation earns its keep — not as offloading tasks, but as building the judgement in others that lets decisions get made well without me in the room.

Building structure around attention

Advanced leadership, done properly, is closer to designing a system than personally supervising one. A few things have helped me protect it. I run a regular decision-making rhythm — a short, recurring forum where operational issues are resolved as a batch rather than trickling in throughout the week. I’ve been clearer with my team about which questions warrant an immediate escalation and which can wait for that forum. And I now block time for genuine strategic thinking the same way I’d protect a client meeting, because if it’s negotiable, it will always lose to something louder.

None of this removes operational leadership from the role — it’s still there, and it still matters. But it stops being the whole role. The aim isn’t to disappear from day-to-day delivery; it’s to be deliberate about where I show up and why, so the space for long-term thinking survives contact with a busy week.

If you’re finding your own calendar tells a similar story, it might be worth stepping back and asking which of this week’s decisions genuinely needed you — and which ones simply found you, because no one had built a better way for them to land.

Looking for more helpful advice? You can build this capability further in our Advanced Leadership Skills program.