There is a particular kind of morning. The calendar is full, the team is visibly busy, and the founder is at their desk choosing a coffee supplier or debating the colour of new office chairs. Not because the strategic paper doesn’t matter more. Because the strategic paper requires uninterrupted thought, and uninterrupted thought is the first thing a full decision pile takes away.
The pile rarely looks like a crisis. It looks like a few extra items on the list. A code review waiting for sign-off. A budget line needing one more approval. A hire that could have been made two levels down but somehow needed the founder’s read first. Each item, on its own, seems small enough to justify keeping.
What is easy to miss is where these items came from. They were not created by the founder. They were routed there, by a structure that never quite assigned the decision to anyone else, or assigned it in name but not in practice. The org chart says the decision belongs to a manager. The daily reality says it lands back on the same desk it always has.
This is the part that stays invisible longest. It doesn’t look like a bottleneck from the top. It looks like a bit more work, a bit more context-switching, a bit more “let me just handle this one, it’s faster.” What it actually is: thinking time and deep work time, spent instead on decisions that were never meant to require the founder’s attention in the first place.
The cost does not stop at the desk. Every decision sitting in that pile has people on the other end of it, waiting. A team that can’t ship until the review comes back. A department that can’t hire until the number is confirmed. Those people don’t wait quietly. They stop, they start something else, they come back, they stop again. Context-switching has a cost of its own, and it is being paid by people who did nothing to cause the delay.
So the pile is doing two things at once. It is stopping the founder from moving the needle on the work only they can do. And it is stopping entire teams from moving on the work only they can do. Neither of these costs shows up on a dashboard. Both compound, week after week, long before anyone names what is happening.
The instinct, once this is noticed, is to look at the people. The manager who keeps escalating. The team that keeps waiting instead of deciding. But the pattern rarely traces back to a person. It traces back to where a decision actually sits versus where the structure says it sits, and how much information, trust, or authority was actually transferred along with the responsibility. Escalation is not a character flaw. It is what happens when a structure quietly makes escalation the safer choice.
None of this is solved by working faster, delegating more forcefully, or asking people to “just decide.” The pile is not a motivation problem. It is a structural one, and structural problems are visible only once someone stops asking who is slow.