Operations = process + people (and you need both to be right)

Operations = processes + people (and you need both to be right)

Most operational problems aren't mysterious.

When a business is firefighting constantly, when delegation keeps failing, when the senior leadership team is busy but not effective — there's usually a straightforward explanation.

The operation wasn't built around how people actually work.

Operations, at their core, are two things: processes and people. The systems, structures, and workflows that move work through a business — and the individuals responsible for running them. Get both right, and things flow. Get either one wrong, and you spend a significant portion of your time managing the friction that creates.

That's not necessarily a leadership failure, more likely It's a design problem.

Here's what I see consistently, working with CEOs and their senior teams.

The business has grown, often quickly, and the processes that worked at an earlier stage are still in place. They weren't wrong then. But they weren't built for where the business is now. So the team spends time working around them, compensating, fixing things that shouldn't need fixing, and the leader at the top absorbs the fallout.

That's what firefighting actually is. It's not a people problem disguised as a crisis. It's usually a process problem disguised as a people problem.

When you address the process side properly, a few things can happen fairly quickly.

Decisions that used to land on the CEO's desk stop arriving there, because the structure exists to make them elsewhere. The SLT stops being a group of capable individuals operating in parallel and starts functioning as a team with clear accountability and then the day-to-day noise reduces, not because problems disappear, but because the business has the infrastructure to handle them without escalating everything upward.

That's when delegation starts to work properly.

Delegation doesn't fail because leaders hold on too tightly, though sometimes that's part of it. It fails because the thing being delegated doesn't have a clear enough process around it. Without that, the person receiving it either does it differently every time, comes back for guidance constantly, or quietly absorbs a level of ambiguity that shouldn't be theirs to manage. None of that is their fault.

Fix the process, and delegation becomes a practical option rather than a leap of faith.

The people side is where things get more nuanced.

Good process doesn't automatically mean an empowered team. The Senior Leaders need to understand not just what they're responsible for, but how decisions get made, where their authority starts and ends, and what success actually looks like for their function. When that clarity exists, something shifts in how people show up. They're less reactive. More confident and genuinely more engaged.

Morale in senior teams is rarely about pay or perks. It's almost always about autonomy, clarity, and the sense that their contribution matters. You get those things right, and you don't need to work particularly hard on culture. It follows naturally.

What I'm describing isn't a transformation programme with a twelve-month timeline and a complex delivery plan.

It's usually a relatively focused piece of work looking at how the operation is structured, where the friction is, what the team actually needs to perform well, and building something that fits the business as it is now, not as it was three years ago.

The businesses I work with aren't broken. They're capable teams operating in systems that haven't kept pace. The opportunity isn't starting again, it's closing the gap between the people you already have and the structure that lets them do their best work.

If your senior team is stretched, your own time is dominated by things that shouldn't need you, and delegation feels more complicated than it should, it's worth having a conversation.

Not because something is wrong. Because something better is available.

Amy Wray April 2026