When everything comes to you: How to avoid becoming the Ops bottleneck
In scaling businesses, effective Ops leadership often means being hands-on. It’s (quite literally) rolling up your sleeves and getting things done. You dip into all sorts of areas, jump in to solve problems, put out fires, run cross-team projects, and unblock people when they get stuck. Being this close to the action, and keeping a pulse on what’s really going on, is what makes Ops leaders valuable. It’s also something many of us take pride in. I know I do.
At the same time, hands-on Ops doesn’t mean doing all the work yourself or being involved in every decision. When too much relies on one person, friction and risk creep in. It’s no different for Ops leaders: if too much depends on us, we can become a bottleneck.
How do we avoid it?
By shifting our focus from doing all the work ourselves to making it clear how the work can move forward without us. Here are everyday behaviours that can help you change where decisions, knowledge, and ownership sit.
Clarify what belongs with Ops and where requests should land
Many of the headaches we deal with in Ops start with one of two things: unclear ownership or grey areas. When ownership isn’t clear, work tends to be sent to Ops by default. And if Ops is loosely defined, or just accepts whatever comes its way, you can expect that pattern to stick. So, the first step is to be clear about what Ops owns, what Ops supports, and what definitely isn’t Ops work. A simple list is often enough; the goal is to set the boundaries quickly.
Grey areas will always exist, and that’s fine. You should still be helpful and get involved when needed, but that doesn’t automatically mean Ops takes the work on. Sometimes it’s enough to help decide where it actually belongs.
The next step is making sure Ops work doesn’t come straight to you. People naturally feel that Ops leaders need to be kept in the loop. That makes sense; you do want visibility. But there’s a big difference between visibility and becoming the entry point for everything Ops-related. A single place for Ops requests to land helps avoid that. You still get visibility, but work can be picked up by the right level in your Ops team without waiting for your direction or approval.
Document as you go
Ops leaders often have access to information and context that no one else has, simply because the role is so varied and cross-functional. Quite often, that knowledge lives only in our heads, emails, or scattered notes. Documentation is hardly a priority when there’s so much else going on. It’s easy to tell yourself you’ll do it later (or not at all) because as long as you know, things feel safe. But that safety is just an illusion.
First, it creates risk. If information only lives with you, what happens when someone needs it urgently and you’re not available? A simple example: you’re away, a contractor needs to be onboarded urgently, and no one knows the exact process. Onboarding slows down, is not done correctly or stalls completely, and missing documentation can have real consequences for the business. Second, it creates dependency. You get the same questions coming back over and over again, when documented answers would allow people to move forward on their own.
Documenting as you go is a habit worth building. Not later. Not tomorrow. Straight away, while the context is still fresh. With the tools available today, capturing knowledge is quicker and easier than ever.
Delegate and coach
How tempting is it to say “I’ll just do it”, even when there are others who could handle the task, perhaps with a bit of guidance and time? Doing things yourself feels quicker and easier. It can also seem safer, especially when nothing is documented and also, you know it’ll be done exactly how you want it. But that’s a short-term perspective. One small task here, another there, and suddenly you end up with a growing to-do list, while others wait for you to make progress. Just like that, you’re becoming the bottleneck you didn’t mean to create.
Delegation is not only powerful, but also absolutely necessary in scaling businesses. But it only works if it’s done properly. That means putting time and effort into coaching and training, so others are genuinely equipped to handle the work you pass on. This approach helps you build a team that’s confident, capable, and ready to take on new responsibilities and challenges. It also wins you a lot of your own time back.
Escalate based on expertise, not hierarchy
There’s a common assumption in many businesses that escalation automatically means going up the management chain. Something feels challenging, important, or bigger than someone’s role, and it gets sent straight to a manager (or even a director), simply because they’re more senior. We often equate escalation with seniority. But is that really the most effective escalation path?
There are only so many leadership roles in a business, and quite often those individuals aren’t the ones closest to the challenge. In practice, they may end up passing the issue on to someone with the right knowledge, or helping identify who can actually unblock it. Think about your own role. How many times does something get escalated to you, only for you to pass it on to someone in your Ops team or another department who actually has the right knowledge?
Encourage escalation based on expertise, not hierarchy. Help people understand who is best placed to handle different types of issues, and make that visible. In some businesses that might mean mapping out areas of responsibility or key skills, so it’s easier to identify the right person. It’s faster and more efficient.
And yes, some issues will still come to you, like business decisions, key approvals, and sensitive matters. But with time, you’ll notice that when something reaches you, it’s usually because it genuinely belongs with you.
Be clear about who decides what
Just as escalation often follows hierarchy, decision-making tends to do the same. People are naturally cautious. They may not want to make “important” decisions, they don’t want to overstep, and they certainly don’t want to be responsible for something that isn’t theirs to decide in the first place. So even when a decision could move things forward, waiting for someone else to make it feels like the safer option.
Focus on spreading decision-making. Not every decision needs top-level sign-off, and not every decision needs you. Be explicit about what can be decided at different levels of the business. Clear guardrails help a lot. They help people understand what they can decide independently, what needs input, and what genuinely requires approval. Over time, clarity and support reduce uncertainty, build confidence, and decisions start moving faster.
Next steps
Reflect & take action: When was the last time something got stuck because it needed you? What’s one small change you could make this week to reduce that dependency?
Join the conversation: What's your experience of staying hands-on without becoming a bottleneck? Have you experimented with any of these habits, or found other approaches that have helped you? Let us know in the comments. Your experience might help someone else.
Subscribe to Opsi Monthly: One email a month with practical ideas, habits, and reflections to help you lead through imperfect, real-world operations with clarity and confidence.