Authority · How-To
How to Improve Decision Velocity
Decision velocity is one of the highest-leverage organizational improvements available to a leader - and it requires no additional headcount, technology, or budget.
Organizations with high decision velocity move faster, adapt more readily, and retain better people. The research on this is consistent: Bain & Company found that decisions made at the right level, with clear decision rights, are made five times faster than decisions in organizations without that clarity. Five times. No additional resources. No new technology. Just structural clarity about who decides what.
Definition
Decision velocity is the speed at which decisions move from identification to resolution in an organization - after eliminating the unnecessary latency produced by unclear ownership, excessive approvals, missing information, and escalation loops.
Why Decisions Take Too Long
In the Four A's framework, decision velocity is the primary output metric for the Authority dimension. When decision velocity is low, one of four structural problems is almost always present:
No one knows who is empowered to decide
The most common cause of decision stall. When ownership is ambiguous, everyone defers, hedges, or escalates. The fix is explicit decision rights - documented, communicated, and honored.
The person with knowledge lacks authority
The person closest to the decision - with the most relevant information - escalates because they lack the authority to act. Senior leaders make decisions with less context and slower response times. Both quality and velocity suffer.
Too many required sign-offs
Approval chains expand over time to manage risk. Many persist long after the original risk is gone. Each additional approval layer adds latency. The question for each layer: what specific risk does this manage, and is that risk real at the current organizational context?
The needed information is not available
Decisions stall while waiting for data that is held in another function, behind a reporting cycle, or inside a system with no current access. Better information architecture - not more approval - is the structural fix.
Four Structural Interventions
1. Map decision rights explicitly
Use a decision rights framework (RACI, RAPID, or a simple owner/approver/informed matrix) to map the most common and highest-impact decisions in your organization. For each: who decides? Who must be consulted? Who must be informed? Publish it. Honor it. The value is not the document - it is the behavioral commitment it creates.
2. Define explicit escalation criteria
Escalation should be the exception, not the default. Define, in writing, the specific conditions that require escalation: dollar threshold, strategic precedent, cross-functional impact above a defined level. Everything below that threshold should be decided by the role-owner without upward request. This requires leaders to genuinely honor the boundary - including when they would have decided differently.
3. Audit approval chains for risk relevance
For every required approval in your organization: identify the specific risk it is designed to manage. Estimate the probability and cost of that risk. Estimate the cost of the approval (not just time, but the decision-velocity tax across all decisions in that chain). If the approval cost exceeds the risk-management value, eliminate it.
4. Redesign information flows around decision cadences
Identify the ten most common decisions in your organization and map what information each requires. For each, ask: is that information available to the decision-maker when they need it, without a request process? If not, redesign the information flow. The decision waits for the data, not the other way around.
The Leader's Role
Improving decision velocity requires something counterintuitive from leaders: genuine delegation that is honored even when they disagree with a decision made within the delegated authority. Leaders who say they want faster decisions but continue to override, revisit, or require sign-off on decisions they delegated are the primary source of escalation behavior in their organizations. The structural intervention is behavioral, not just architectural.
Research basis: Blenko, Mankins, and Rogers, Decide and Deliver(Bain & Company, 2010); Rogers and Blenko, "Who Has the D?" (Harvard Business Review, 2006); McKinsey Global Survey on organizational speed and decision-making quality (2019).
Frequently Asked Questions
What is decision velocity?
The speed at which decisions move from identification to resolution, after eliminating unnecessary latency from unclear ownership, excessive approvals, missing information, and escalation loops.
What causes slow decision making?
Unclear ownership, authority concentrated too high, excessive approval chains built for past risks, and information that is siloed rather than available to the decision-maker.
How do you improve decision velocity?
Map decision rights explicitly, define escalation criteria in writing, audit approval chains for actual risk-management value, and redesign information flows around decision cadences.
Diagnose Your Authority
Where are your decisions slowing down?
The Executive Diagnostic identifies which of the Four A's - including Authority conditions that drive decision velocity - is the primary constraint on your organization's performance.