What is decision drag, and how do you measure it?
By Brendan Levin. 20+ years scaling businesses, from teams of 8 to 600 and budgets from startup to $100m.
Key takeaways
- Decision drag is measured in time, not effort. It is the total delay work spends waiting on a call only you are allowed to make.
- It is not decision fatigue. Fatigue is your depletion. Drag is the business stalling, and you can have high drag even on a day you feel fresh.
- It has three structural causes: no decision rights, ambiguous Direction, and escalation you have accidentally trained. None of them is a discipline problem.
- Hiring senior people without assigning them authority raises drag, not lowers it. The bigger the hire, the bigger the calls they bounce back to you.
- You can measure your own drag in one week with an escalation log, and cut the recurring part of it within a fortnight.
Decision drag, defined
Decision drag is the lag between the moment a decision becomes necessary and the moment it actually gets made, when the reason for the lag is that the call has to come through you. A quote needs sign-off and sits until you surface from a client call. A hire is ready to be offered and waits for your nod. A supplier needs an answer and the account lead holds off because they are not sure it is theirs to give. None of that time is spent deciding. It is spent waiting.
The unit that matters is time in the queue, not how hard you are working. This is why drag is easy to miss. On a busy, productive day you can clear twenty escalations and feel effective, while the business quietly lost hours of throughput waiting for you to get to them. The effort was real. The drag was real too, and they are not the same measurement.
Two things get confused with decision drag. The first is decision fatigue, which is the personal cost of making too many calls: your judgment degrades as the day wears on. That is about you. Drag is about the organisation, the stalled work sitting behind you. You can have low fatigue and high drag, especially if you happen to enjoy being the person everything runs through. The second is delegation. Delegation moves tasks off your plate. Drag is about who holds the authority to decide. You can delegate every task in the business and still hold every decision, which is the exact trap most founder-run firms are in.
How to measure your decision drag this week
You do not need software. For five working days, keep a running log of every decision that came to you, wherever it came from: a message, a hallway question, a raised hand in a meeting. For each one, write down two things and nothing else. First, the wait, meaning roughly how long the thing had been sitting before it got resolved. Second, a plain yes or no to the question: did this genuinely need me, or could a named person with a clear boundary have made the same call.
At the end of the week two numbers fall out. Your drag hours are the total wait time attached to the decisions that did not need you. Your drag ratio is the share of your escalations that did not need you. A founder who logs forty escalations in a week, finds that thirty of them did not need her, and adds up eleven hours of work that sat waiting on those thirty, has an 11-hour drag week and a 75 percent drag ratio. The exact figures do not matter. The pattern does, and it tends to be worse than founders expect.
The yes or no column is where the honesty lives. Most calls that route to you feel important in the moment, which is why they reached you. The test is not whether the decision mattered. It is whether it needed you specifically, or whether it needed someone with clear authority and a defined limit to act inside.
- The decision (one line is enough)
- The wait: how long it sat before it was resolved
- Needed me: yes or no, judged honestly
- If no: who could have owned it, and what boundary would have let them
What causes decision drag?
Decision drag has three structural causes: no decision rights, ambiguous Direction, and escalation you have accidentally trained. None of them is a sign that your team is weak or that you are bad at letting go, and that matters, because a general push to "just decide without me" fixes none of them. Each gap has a different cause and a different fix, so the first move is to name which one is generating a given call.
| Source | Why it creates drag | The fix |
|---|---|---|
| No decision rights | Nobody knows where their authority ends, so when a call feels significant the safe move is to ask you. The escalation is rational. | Write decision rights with real thresholds: a named owner and the number or risk line below which they act without you. |
| Ambiguous Direction | Even a capable person cannot make a confident call if they do not know what the business is optimising for this year. So they check. | Make Direction explicit in one sentence with the numbers that prove it moved, so people can weigh a call themselves. |
| Trained escalation | You answer fast and well, so asking you is the cheapest, safest path for everyone. You have quietly rewarded the behaviour. | Install a standing act-and-log rule: sub-threshold calls get made on the spot and dropped in a shared decision log you review once a week, so asking first is slower than acting. |
Why decision drag gets worse as you grow
The intuition is that hiring senior people reduces drag. Bring in an experienced operator and the calls stop coming to you. In practice it often runs the other way, and this is the part founders get caught by. A senior hire without assigned decision rights does not stop escalating. They escalate bigger. They handle the small stuff, then bring you the larger, riskier calls that they can see matter but are not sure they are allowed to own. You end up more on the hook, not less, and you conclude that even good people cannot take this off you.
They can. The problem is not the person. It is that you gave them a role without giving them the authority the role implies. Headcount adds decisions to the business faster than it removes them, unless authority is assigned alongside each seat. This is the mechanism behind the founder who says, honestly, that they hired great people and the business still runs through them. The hires were fine. The structure around them was never built.
This is also why drag compounds rather than growing in a straight line. Every new person makes more calls, and without a boundary each of those calls has some chance of routing to you. More people, more calls, same single point of resolution. The queue behind you lengthens quietly until a fortnight away from the business becomes unthinkable.
How to remove decision drag
The fix is not to delegate more or to care less. It is to close the three gaps directly. Assign decision rights with real thresholds, because a decision right without a number is just a title. For spend it might read like this. Under two thousand and inside an approved budget, the owner acts and tells you afterwards. Above that, or outside budget, it comes to you first. Make Direction explicit enough that a capable person can weigh a call without you in the room. And change the escalation economics with a standing act-and-log rule, where sub-threshold calls get made immediately and logged for a weekly async review, so that asking you first is genuinely slower than acting.
Do it in that order and the recurring, low-risk routing, which is the bulk of most founders' drag, can fall within a couple of weeks. The structural pieces take longer, but the relief comes fast because most of what reaches you is not high-stakes. It is just unassigned. This is the same underlying problem as owner dependency, seen through the specific lens of decisions rather than the whole business.
One caution. The goal is not zero drag. You want the rare, high-stakes, hard-to-reverse calls to reach you, because those are genuinely yours. What you are removing is the recurring routing of calls that a clear boundary would have settled. Aim the fix at the pattern in your log, not at every escalation. Getting decisions to stop routing back to you is a matter of degree, done deliberately.
If you want to see exactly which decisions still route to you and what it is costing in stalled work, the free Founder Dependency Diagnostic maps it in about ten minutes.
Take the free diagnosticCommon questions
What is the difference between decision drag and decision fatigue?
Decision fatigue is the personal cost of making too many calls: your judgment gets worse as the day goes on. It is about you. Decision drag is the business cost: work stalling in a queue behind you while it waits for a call only you are allowed to make. It is about the organisation. You can feel sharp and rested and still be running a high-drag business, because drag is measured in the time work spends waiting, not in how tired you are.
Is decision drag just a delegation problem?
No, and this is the distinction that matters most. Delegation is about moving tasks. Decision drag is about who holds the authority to decide. You can delegate every task in the business and still keep every decision, which is exactly what most founder-run firms do without realising it. The work is off your plate but the calls still route to you. The fix is decision rights, not more delegating.
Can you actually measure decision drag?
Yes, roughly but usefully. Keep an escalation log for one week: every decision that came to you, how long it had been waiting, and an honest yes or no on whether it needed you. Two numbers fall out, your drag hours and your drag ratio, and the trend over a few weeks tells you whether the structure you are building is working. It is directional, not precise, and directional is enough to act on.
Will hiring a COO or a senior operator fix decision drag?
Only if you assign decision rights along with the role. A senior hire without clear authority tends to escalate bigger, riskier calls to you rather than fewer, so the drag can go up before it goes down. The hire is not the fix on its own. The fix is the authority you build around the seat. This is worth thinking through before you hire, not after.
How quickly can you reduce decision drag?
The recurring, low-risk routing, which is usually most of it, can drop within a couple of weeks once thresholds are written and actually communicated to each person directly. The deeper pieces, particularly making Direction clear enough that people can decide without you, take longer. But the early relief is real and fast, because most of what reaches a founder is not high-stakes. It is simply unassigned.