Everything still comes back to you

It is the tiredness of being the point every decision must pass through before it can move. By the time you notice it, your calendar has already told the story: fifty small approvals a week, three of which actually needed you.

Most founders read this as a people problem. They think: my team is not senior enough, or my hires were wrong, or I need to trust more. Some of that may be true. But if you have been through two or three team rebuilds and the same pattern comes back, the problem is not the people. It is the shape of the business. You have built a system that routes to you by default, and no amount of hiring will change what the system is asking for.

The routing is structural, not personal

Every business runs on a set of implicit decisions about who decides what. In a small operation those decisions live in the founder's head, which is efficient at the start. Twenty people, two products, one office. You can hold the whole map. When someone needs an answer, they walk to your desk, and the answer is faster than any process would have been.

Then the business grows. The map gets bigger than one head can hold, but the routing habit stays. Nobody wrote down when to escalate and when not to. Nobody named the decisions that no longer need you. So the team keeps walking to the desk, and the desk keeps saying yes, and the pattern hardens.

By the time the business is doing real revenue, the founder is the switchboard. The team is doing what the wiring tells them to do. That wiring was laid when the business was small enough for one head to hold, and it was never rebuilt when the business outgrew that size.

This is the first thing to notice: the bottleneck is not a character flaw. It is a design that worked at one size and stopped working at the next size, and nobody redrew the diagram.

The three signals

There are three signals that tell you the routing is broken, and they are worth watching for separately.

The first is the quiet Sunday check. If you find yourself opening the laptop on Sunday evening to read messages that came in Friday afternoon, and none of them are strictly urgent, you are the fallback for problems the team could have solved. They copied you because copying you is the safe move. That is a routing signal, not a work-ethic signal.

The second is the returning question. A question you have answered before, from someone who has heard the answer before, arriving again in a slightly different form. When this happens once, it is a memory issue. When it happens repeatedly across the team, the decision does not have a home. Nobody owns it, so it keeps coming back to the person who last said something about it, which is you.

The third is the meeting that cannot start without you. Look at the agenda of the one you are thinking of. If it reads as a list of items waiting for your yes, that meeting exists because you exist. If more than one of your weekly recurring meetings looks like that, the business has quietly organised itself around your availability.

Why hiring senior does not fix it

The natural move, once you notice the pattern, is to hire someone senior. A GM, a chief of staff, a head of operations. The idea is that this person will absorb the decisions and give you back your calendar. Sometimes it works. Often it does not, and it is worth being honest about why.

A senior hire inherits the same undefined decision rights the previous team had. Nobody wrote them down for the new person either. So the senior hire tries to make decisions and quickly discovers that half of them get overturned or second-guessed, because the founder still holds the final word on things the founder never explicitly kept. After a few of those, the senior hire learns to check first, and the routing pattern reasserts itself around a more expensive salary.

The fix is not the person. The fix is the map. Until the decisions the business runs on are named, sorted by who owns them, and separated into ones that need the founder and ones that do not, the next senior hire will end up doing the same thing the last one did.

What the map actually looks like

The exercise is duller than founders expect. It is not a strategic offsite. It is a two-column list.

On the left, write the decisions your business made in the last thirty days. All of them. Pricing exceptions. Vendor changes. Hiring calls. Refund approvals. Small policy calls. Which meeting to move. Whether to accept a client with a difficult brief. It runs longer than you think.

On the right, name who owned each one. Not who signed off. Who owned it from problem to answer. If the honest answer for most of the list is "me, eventually", the map is telling you the truth. If a decision needed you but did not need you at the resolution stage, that is a decision that can be redrawn with a boundary and handed off.

Most founders find, when they do this properly, that between a third and half the decisions on the list did not need them. They just kept passing through them because that was the path of least resistance. The team was not overstepping. The team was following the well-worn trail.

The cost is not what you think

The obvious cost is your time. It is also the least important one.

The real cost is that decisions the founder does not need to make are still being made at the founder's pace, which is always slower than the pace of the person closer to the work. A refund decision that could have been made by the customer service lead in ten minutes waits three days for the founder to look at it. In those three days, a customer who would have stayed becomes a customer who told two other people about the wait. Multiply that across a year of small delays.

The second cost is that the team's judgement never gets used. If every decision passes through the founder, the team learns to bring problems rather than solutions. They stop practising the muscle of deciding. Over time you end up with senior people who behave like coordinators, because that is the only role the system left them. This is not a failure of the people. It is a failure of the design, and the people notice.

The third cost is the founder's own attention. Every small decision you make is a slot you did not spend on the two or three big ones only you can make. If the calendar is full of fifty small approvals, the big call about which market to enter next year is being made on scraps of time, at the end of long days, while the small stuff crowds it out.

What changes when the routing is redrawn

The founders who do this work well tend to describe the shift in the same way. The business feels quieter. The team stops copying them on everything. Meetings that used to require them get run by someone else, and the outcomes are usually within a few percent of what they would have been with the founder in the room. The founder still holds the decisions that genuinely need to be theirs, and those decisions get more room.

None of this happens because the team suddenly got better. It happens because the map was drawn. Once decision rights are named, the team can act on them without checking, and the checking-in traffic drops. The Sunday laptop closes. The switchboard is retired.

The work of redrawing takes a few weeks of careful thinking. It is structural engineering. You look at where the load is landing, you look at where the load should land, and you rebuild the joints that carry it. The building stops leaning on the one column that was never meant to hold the whole roof.

The honest picture

If you are the founder and everything still comes back to you, it is not a moral failing. It is a design problem you inherited from your earlier, smaller self, and that earlier self was right to build it that way at the time. What is required now is not more effort. It is a different kind of thinking about who owns what, written down, agreed, and honoured.

Most founders can do this work if they know what they are looking at. The ones who struggle are usually not struggling with the concept. They are struggling with the discipline of not stepping back into the switchboard the first time someone asks them a question they could have answered.

That is the real test. Not whether you can draw the map. Whether you can let the team use it.