When Every Decision Finds Its Way Back to You
If everything still runs through you, the issue may not be your team—it may be your decision structure.
A founder I worked with recently told me about a week that will sound familiar to a lot of service-based businesses.
It was a peak weekend: big events in town, every property booked, and the kind of demand that’s great for revenue but unforgiving operationally. The kind of week where things don’t just get busy, they get unpredictable.
Customer issues started popping up throughout the day, and a maintenance situation needed quick coordination across multiple properties. These were just a couple of last-minute changes layered on top of an already full schedule. And not surprisingly, messages were coming in from everywhere (customers, vendors, team members) all at once…and all needing some level of response.
None of this was unusual on its own, though it was the volume and timing that made it feel chaotic. But what really stood out wasn’t just how much was happening, it was where everything went. A significant portion still routed through the founder.
This wasn’t because her team wasn’t capable, and they weren’t dropping the ball. Rather, in many cases, the team was doing exactly what you’d want — flagging issues, asking thoughtful questions, trying to move things forward responsibly.
But when things got even slightly messy, time-sensitive, or unclear, she became the default point of decision-making. And once you start to see that pattern, it’s hard to unsee it.
The Pattern Isn’t Just About Busy Weeks
What made this more interesting is that it wasn’t entirely limited to high-pressure moments like that weekend.
Even in normal day-to-day operations, some of her teammates would occasionally check in on relatively small decisions like
how to respond to a customer’s question,
whether to approve a request, or
how to handle a situation that didn’t perfectly match a past example.
Most of these came through as quick messages that were easy to respond to at the moment. In fact, individually none of these moments felt overly significant. They were easy to respond to and easy to justify. But taken together, they started adding up to something bigger: a system where decisions consistently routed back to one person (and more than they really needed to in a scaling organization).
Over time, that doesn’t just affect efficiency — it changes the experience of running the business.
The founder mentioned that even when she’s technically off (evenings, weekends, even while on vacation), she doesn’t fully disconnect. There’s a constant, low-level awareness that if something comes up, she’s still the most reliable escalation point. Not always because she needs to be, but because that’s how the system has evolved to function.
This Isn’t a Training Problem (or a Tools Problem)
It would be easy to look at a situation like this and assume the issue is training. Maybe the team needs more guidance, or more confidence, or more time in their roles.
But that wasn’t what was happening here. This was a thoughtful, capable team with people who could handle many of these decisions on their own. The instinct to escalate wasn’t coming from a lack of ability.
It also wasn’t a tool issue. They already had a solid digital management system implemented, with messaging, task tracking, and automation features available. There wasn’t a shortage of places to communicate or document work. And yet, decisions and context were still living in people’s heads or scattered across messages, rather than anchored in a shared, consistent system.
So if it’s not training, and it’s not tools, what’s actually going on?
The Real Gap: Decision Clarity
In this case, and in many growing organizations, the gap is decision clarity. More specifically, I’m talking about a lack of clearly defined decision boundaries.
When those boundaries aren’t explicit, people are left to interpret them in real time. And when the stakes involve customers, quality, or brand experience, most people will default to the safest option: they ask the original expert.
It’s not because they don’t want ownership, but because they don’t want to get it wrong.
If you zoom in on those moments, you can almost hear the internal questions running in the background:
Am I supposed to decide this, or check first?
Is this within the “normal” range (and “eek…what’s normal?!?”), or is it an exception?
What does “good” actually look like here?
Where’s the line between handling it and escalating it?
When those answers aren’t clear ahead of time, escalation becomes the most efficient and least risky path…even if it slows the organizational system down overall.
When Strength Creates Dependency
There’s another layer here that’s important to name. In this case, the founder is highly detail-oriented and deeply committed to quality. She notices things, and cares about the customer experience. After all, she’s built a business that works because she’s been willing to stay close to the details and maintain a high standard.
That’s not a flaw, and it’s absolutely a strength. It’s also part of what makes this pattern harder to spot.
When a leader has a strong internal standard — even if it’s not fully documented — the team can feel that. They know there’s a “right” way to handle things, even if it hasn’t been explicitly defined. Over time, that creates a subtle but powerful cultural dynamic: people check not because they have to, but because they want to align.
Because the founder often does have the best answer…or at least the fastest one…the system reinforces itself. The more that decisions route through one person, the more that person becomes the source of truth. And the more that happens, the harder it is for others on the team to confidently decide without looping them in.
In many ways, this is what it looks like when a business has been built with a high level of care: the challenge is simply evolving the system to match that standard.
What Actually Helped
What she and I worked on together wasn’t adding more tools or retraining the team from scratch. It was something simpler, but more foundational: defining decision boundaries and thresholds in a way the team could actually use in real time. That meant making implicit expectations more explicit.
For example:
What decisions does the team fully own without needing to check?
Where are the thresholds that should trigger escalation?
What constraints matter most (cost, guest experience, brand standards) and how should those be weighed in a decision?
In some cases, that looked like setting clear parameters. For example, if a situation falls within a certain range, the team can make the call. If it crosses a specific threshold, that’s when it gets escalated.
To take it to the next level, it’s important that leaders plan opportunities to talk and walk through real scenarios together. This might include periodically looking at recent situations and asking questions like, “Should this have been escalated?” or “What would you need to feel comfortable deciding this on your own next time?”
These mini “after action reviews” will make a difference to the team because decision clarity isn’t just about policies. It’s about building shared understanding through examples.
Know that the goal isn’t to eliminate escalation entirely. There will always be situations that require executive input or collaboration. However, the goal is to reduce the number of decisions that default to escalation simply because the boundaries aren’t clear.
A Simple Place to Start
If you’re seeing a similar pattern in your own organization where decisions keep flowing back to you, it’s worth pausing before jumping to conclusions about performance or capability.
More often than not, people are responding to the system they’re operating within.
A simple place to start is by looking at your own recent experience. Think about the last handful of decisions that came to you. Don’t just look at the big, strategic ones, but also the smaller, day-to-day questions.
Which of those could someone else have handled with the right context?
What would they have needed to make that decision confidently?
And, where could a clearer boundary or guideline have changed the outcome?
Because if everything still runs through you, it’s usually not just about delegation. It’s a signal that decision ownership hasn’t been fully designed yet. Once you start designing for that — even in small, practical ways — the system begins to shift into something much more sustainable for everyone.
