Good people, clear strategy — and yet decisions take weeks, loop back endlessly, or get escalated for safety rather than need. A decision bottleneck is rar
Good people, clear strategy — and yet decisions take weeks, loop back endlessly, or get escalated for safety rather than need. A decision bottleneck is rarely about intelligence; it's about an unclear operating system: who decides, with what authority, against what threshold. Installing that clarity as infrastructure turns decision velocity from a constant negotiation into a property of how the organisation runs.
Decision Gravity pulls every consequential call upward and inward, where it loops, waits for a meeting, or gets escalated for cover rather than need. The cost is momentum: good strategy and good people stall not for lack of answers but for lack of a clear right to decide.
Decision velocity is not a matter of working faster or meeting more — it is an operating system: who decides, with what authority, against what threshold, made explicit. You don't program people to be braver; you install clear decision rights so that deciding becomes a defined act rather than a constant negotiation.
Pick your last three stuck decisions: was the blocker missing information, or missing clarity about who gets to decide? For most teams under Decision Gravity, it's clarity, not information. The facts were mostly available, but nobody was confident it was theirs to call, so it escalated or waited for a meeting instead.
How much does slow decision-making actually cost, in real terms? More than most leaders assume. McKinsey Quarterly found 61% of executives say at least half the time spent on decisions is used ineffectively, costing a typical Fortune 500 company an estimated 530,000 managerial days a year, worth roughly $250 million in wages.
Do most organisations actually rate themselves as good at decision-making? No. McKinsey's Global Survey found only 20% of executives say their organisation excels at decision-making, and Gallup separately found only 24% of managers strongly agree their peers make well-thought-out decisions, with just 14% satisfied with decision speed.
Does a matrixed reporting structure make this worse? Measurably. Gallup's research on matrixed organisations found employees with multiple bosses are far less likely to strongly agree they know what's expected of them (versus 60% in non-matrixed roles), and unclear decision authority is a major driver of that gap.
Why does the instinct to 'gather more information' usually not fix a stuck decision? Because most stuck decisions aren't actually short on facts. They're short on clarity about who is allowed to make the call. In that vacuum, escalating is the rational, low-risk move for everyone involved, and the bottleneck compounds.
What does 'installing decision rights' actually look like? Naming the owner for each class of decision, the threshold above which it must escalate, and the standard the owner is accountable to, written down and known rather than implied or renegotiated each time.
Will this slow things down by adding more process? The opposite is the intent: the goal is fewer meetings and less escalation, not more governance. Once people know a decision is genuinely theirs and what 'good' looks like, most decisions get made faster, at a lower level, without a meeting at all.
How would we know if this is actually working? Decision velocity becomes a visible property of how the organisation runs rather than something leaders have to personally push for in every meeting: fewer decisions loop back, and fewer get escalated for safety rather than genuine need.