Why decision velocity, more than talent or budget, sets how fast a company can grow.
Take a week off, and you learn how your company is really built.
For some founders the week is quiet. The team makes its calls, the work moves, and the backlog waiting on return is small and ordinary. For others the week produces a queue. Decisions stack up because they were always going to wait, and the first days back go to clearing a pile only one person could clear.
That queue is worth paying attention to. It's the clearest signal you'll get of where the company's real ceiling sits.
A business can only move as fast as the decisions it's able to make. You can hire brilliant people, raise a strong round, and build a great product, and still grow slowly if every meaningful call routes through one person's judgment and one person's calendar. Talent and capital set your potential. Decision velocity sets your actual speed. When the two diverge, it's usually because the decisions have quietly concentrated at the top.
This one is worth saying plainly, because founders tend to hear it as criticism. The bottleneck is a structural state, and it says almost nothing about how capable the founder is. It's the natural residue of having been right. In the early days you made nearly every important call, and you made most of them well, which is a large part of why the company exists at all. The organization learned, correctly, that decisions go better when they run through you. Then the company grew, the volume of decisions grew with it, and the habit that built the company started to cap it. Nobody designed the ceiling. It accumulated.
Delegating work is not the same as delegating decisions
The move most founders reach for first is delegation, and it's the right instinct aimed at the wrong target. They hand off the work. Tasks, execution, whole functions leave their plate, and the calendar still fills, because the judgment stayed. You can offload every task in the building and keep every decision, and the ceiling doesn't move an inch. Handing off work and handing off decisions are different acts, and the second one is what changes your company's speed. A useful test: if your team does the work but still books time on your calendar to get the call approved, you've handed off the task and kept the decision.
A case where the decisions moved
I watched how much this matters at DDG. Decision-making there had concentrated at the executive team. Calls that shaped the day-to-day waited for a small group at the top, while the people closest to the actual work, the front-line managers who could see each situation directly, waited for permission to act on what they already understood.
The change was to move the decision rights down to those managers. Give the people nearest a decision the authority to make it, with clear boundaries on what was theirs to own. It felt, at first, like giving something up. What it produced was speed.
The organization stopped queuing behind a few calendars and started moving at the pace of the people doing the work. Over that period revenue grew from $44M to $63M, and EBITDA margin climbed from 19% to 30%. The talent didn't change. The location of the decisions did.
The pattern isn't unique to executive teams. It's the same shape whether the decisions pile up at a leadership group or at a single founder. Wherever they concentrate, they set the ceiling.
The fix is a structure, not a feeling
The reason this is hard to fix is that the usual remedy is a feeling. "Empower the team" is a sentiment, and sentiments fade by the next stressful Tuesday. Defined decision rights are a system. When a role clearly owns a class of decisions, with the boundaries written down and understood, the calls get made whether or not anyone feels particularly empowered that morning. A system runs on structure, and that's what makes it hold.
In practice it means naming which decisions belong where, giving each owner the boundaries they operate inside, and resisting the pull to reclaim a call the moment it's made differently than you would have made it. That last part is the hardest. The first few decisions your team owns will be made differently than you'd make them, and a fair share will be better than yours precisely because they're closer to the ground.
What changes when you push the right decisions down
Push the right decisions down, and two things happen at once. The company speeds up, because calls stop waiting on a single calendar. And you get your attention back for the small number of decisions that genuinely need a founder. The business keeps moving whether you're in the room or on a plane, which is the real test of whether you've built a company or a very demanding job.
Find the constraint. Fix it in the right order. When the constraint is decision velocity, the fix is a structure that lets the company make good calls without routing every one of them through you.
If the week-off test doesn't go well right now
That backlog is telling you something useful about where the ceiling sits. I'm happy to spend a short call pointing toward where the real constraint likely lives. No pitch. Just an operator's read.