Why founders become the routing layer, even in companies that swear they're not hierarchical

Plenty of founders will tell you their company is flat. No org chart, no title inflation, everyone empowered to just decide things. Then you watch how work actually moves, and the founders are in every meaningful path anyway. Not because they inserted themselves. Because the company built no other way for a decision to get made.

How does this happen without anyone deciding it should?

It starts small and reasonably. Early on, the founders genuinely do have the most context, so it makes sense that they weigh in on most things. Nobody writes this down as a rule, because at ten people it does not feel like a rule, it feels like normal collaboration.

Then the company grows and nothing replaces it. New hires arrive into roles that were never given explicit decision rights, only responsibilities. Faced with a real call, the reasonable move for a new hire is to check with whoever clearly has context and authority, which is still the founders, because nobody told them otherwise. Each individually sensible check-in becomes, in aggregate, a company where every meaningful decision still funnels through the same one or two people, five years and two hundred people later than when it was actually appropriate.

What does it look like from the inside?

The calendar fills up with decisions that are, on paper, someone else's job. The founders start to feel like a bottleneck without being able to point to the moment they became one, because there wasn't one moment. It was hundreds of small, individually reasonable defaults, none of which anyone chose on purpose.

Meanwhile the people whose job the decision technically is stop believing it is actually theirs. This is the quiet cost: talented hires who came in expecting ownership discover the ownership is nominal, and either shrink to fit the role or leave.

What actually breaks the pattern?

Not a mandate to "delegate more." Vague instructions to empower people do not survive contact with an undesigned system, because the underlying mechanics have not changed: nobody has explicitly said which decisions belong where. What breaks the pattern is writing the decision rights down, by category, in a way specific enough to actually be tested. Not "the head of product owns product decisions," but the actual list: which calls they make alone, which they make with input, which still escalate, and why.

Once that list exists, two things happen. People stop defaulting upward, because there is finally something more specific than habit to route by. And founders can see, in writing, exactly which decisions they are still holding that the design says should sit elsewhere, which is a much easier problem to fix than a vague sense of being overloaded.