Decision-Making & Ownership
It Is Not a Confidence Problem
By Sylvie Cowell 3 min read
When decisions keep returning to the founder, the team may not lack confidence. The operating structure may give them no reliable alternative.
When a founder tells me their team keeps coming back to them for decisions, the instinct is often to frame it as a people issue. The team lacks confidence. They are not taking ownership. They need to step up.
Sometimes that is true. But in most founder-led businesses I work with, the team is not coming back because they are passive. They are coming back because the system gives them no other option.
When priorities are unclear, people default upwards. When accountability is fuzzy, people avoid owning things they are not sure are theirs. When there is no shared view of what success looks like, the safest move is to ask the founder—the only person who can give the definitive answer.
The decisions are not returning because your team cannot think. They are returning because the structure has made you the only reliable source of clarity.
The bottleneck is structural, not personal
I see this pattern in businesses at every stage and across every sector: a capable team, genuine effort on all sides, and yet almost every meaningful decision still defaults to the founder.
It is worth being honest about the cost. Every decision that reaches you creates a context switch. Every moment spent in operational detail is a moment not spent on the things only you can do. And every time the team learns that you will answer the question, you train them to keep asking.
The founder bottleneck is one of the most common constraints on growth I encounter. In almost every case, it is not caused by the team. It is caused by the absence of three things: clear priorities, clear ownership and a consistent operating rhythm.
You have not hired people to think for themselves and then built a system that makes that impossible. You have simply not built the system yet.
What needs to change
Clarity on what matters.
If the team does not have a shared, explicit view of the priorities for this quarter, they have nothing to use as a filter when making decisions. So they come to you.
Clear accountability.
Not accountability as punishment, but accountability as ownership. Who is responsible for which outcome? If the answer is unclear—or nominally everyone’s responsibility—the practical answer is that it belongs to no one, and the founder ends up holding it.
A meeting rhythm that creates alignment.
Most businesses have meetings. Far fewer have meetings that produce clear decisions, clear owners and visible follow-through. When the operating rhythm does this consistently, the team begins to make decisions in the room rather than in the corridor outside your office.
What you can do this week
Take the last five decisions you made that you did not expect to be involved in. For each one, ask whether the person who escalated it had enough information, clear enough ownership and a visible priority framework to answer it themselves.
If the answer is consistently no, the problem is structural and the solution is operational. If the answer is sometimes yes, start there. Those are the decisions you can stop being involved in immediately.
Once you have identified the decisions you should not have been involved in, choose one category and write down who owns it from this point forward. Tell them. That is the beginning of the system.
The goal is not to remove yourself from the business. It is to ensure that your involvement is deliberate, strategic and chosen—not the default outcome of a system that cannot function without you.
If you have completed the Operating System Diagnosis, return to Section 1. This is where the gap will show most clearly. If you have not, it takes about three minutes and gives you a structured view of where the operating system is holding—and where it is not.
The team needs more than encouragement to step up. It needs the clarity, authority and rhythm that make stepping up possible.