Leaders measure a lot of things. Revenue, margin, customer retention, project completion, employee turnover, and dozens of operational KPIs can tell us whether the business is moving in the right direction.
What most leadership teams do not measure is how long it takes the organization to make a decision once a decision is clearly needed.
That time matters more than it may seem. A project can have the right people, adequate resources, and a reasonable plan, then lose weeks waiting for someone to approve a change, resolve a disagreement, choose between two options, or clarify who has the authority to move forward. The delay rarely appears on a dashboard as a leadership problem. It gets absorbed into a longer project timeline or explained as normal organizational friction.
Decision velocity gives leaders another way to look at that friction. It asks how effectively an organization can move from a question that requires a decision to a clear, owned decision that people can act on.
That does not mean faster is always better. It means the time a decision takes can tell us something important about how well the organization is functioning.
Decision velocity is not the same as deciding quickly
The easiest way to misunderstand decision velocity is to treat it as a mandate to make every decision faster.
Some decisions should take time. An acquisition, restructuring, major investment, or strategic change deserves more analysis than a routine operational call that can easily be reversed. Good leadership is not about shortening every discussion until people start making careless choices.
The better question is whether the amount of time and effort being spent matches the importance and risk of the decision.
Research from McKinsey on decision making found that speed and quality do not have to work against each other. In its survey, faster decisions tended to be higher quality, suggesting that strong decision-making practices can improve both. The appropriate balance still changes depending on the type of decision being made.
That distinction matters. Decision velocity should not reward a leader for making a serious decision in an hour. It should help identify when a decision that reasonably should have taken a day has been sitting unresolved for three weeks.
Slow decisions often reveal problems somewhere else
A slow decision is not always a decision-making problem.
Sometimes it is an ownership problem. I have written before about how unclear ownership slows teams. When several people can provide input but nobody knows who has the final call, even straightforward decisions begin moving upward or sideways through the organization.
Sometimes the issue is information. Leaders hesitate because the numbers do not match, the latest document is difficult to locate, or different departments are working from different versions of the same information. That is one reason information integrity has operational value. People move differently when they trust what is in front of them.
In other cases, the organization has simply accumulated too much process. A decision moves through three meetings, four approvals, two committees, and an executive review because that is how the process evolved over time. Nobody designed it to be inefficient, but nobody has stopped to ask whether all of those steps are still necessary.
That is what makes decision velocity useful as an organizational health measure. The number itself is only the beginning. The real value comes from asking why the number is what it is.
Start by measuring the decisions that matter
I would not recommend trying to calculate one average decision time across the entire company. That could create a neat-looking number without telling leaders very much.
Start with a few recurring types of decisions instead.
A leadership team might track how long it takes to approve a customer exception, resolve a budget request, authorize a hiring decision, choose between competing project priorities, approve a contract change, or settle a cross-functional issue.
For each category, leaders can look at several measures:
- Decision cycle time: How long passes between the point when a decision is formally needed and the point when the decision is made?
- Execution lag: Once a decision is made, how long does it take for meaningful action to begin?
- Escalation rate: How often does a decision move higher in the organization than it should?
- Reconsideration rate: How frequently are completed decisions reopened?
- Approval touches: How many people, meetings, or approval stages does the decision pass through?
- Decision quality: Did the decision produce the intended result, or did speed create avoidable rework?
There is precedent for looking at decision effectiveness this way. Bain has evaluated decision-making through four dimensions: decision quality, speed, execution, and effort. Bain also describes companies tracking decisions that were delayed, revisited, or escalated to someone higher in the organization. Those measures help turn a vague complaint about slow decisions into something leaders can actually examine.
Look for the distance between authority and the work
Once leaders begin tracking decision velocity, one pattern deserves particular attention: decisions that repeatedly travel upward.
Escalation is appropriate when risk, investment, regulation, or enterprise strategy requires senior involvement. It becomes a problem when capable people consistently need executive approval for decisions that should sit closer to the work.
That creates two forms of drag. Employees wait longer for answers, and senior leaders fill their calendars with decisions that do not require their level of authority.
The solution is not simply telling people to be more decisive. Leaders have to clarify decision rights. Teams should know which decisions they own, where consultation is required, what thresholds trigger escalation, and when they are expected to move without another layer of approval.
When responsibility and authority do not match, decision velocity usually exposes it.
The process around the decision matters too
A surprising amount of decision delay happens before the person with authority ever gets the issue.
Information has to be gathered. Documents have to be routed. Someone waits for an email response. Another person discovers that a required approval was never requested. The issue gets added to next Tuesday’s meeting because there is no other defined path for resolving it.
This is where leadership and workflow design meet.
Daida has written about how manual approvals and unclear handoffs create workflow bottlenecks. In document-heavy processes, better routing and automated workflows can reduce the administrative waiting that surrounds approvals. The same principle applies more broadly. If a decision consistently takes too long, leaders should inspect the entire path around it rather than assuming the person making the final call is the only source of delay.
Recent McKinsey research makes a similar point at a larger scale. Its 2026 organizational research identifies redundant governance, repeated reopening of decisions, fragmented information, and unclear accountability as common process problems. McKinsey reports that end-to-end process redesign can increase decision-cycle speed as much as threefold in its experience.
The answer is not always another leadership workshop. Sometimes the workflow itself needs to change.
A decision is not finished when someone says yes
There is another part of decision velocity that leaders can miss.
A decision can happen quickly and still create slow execution.
The meeting ends. Everyone agrees. Two days later, people disagree about what was actually approved. Someone remembers a condition differently. The person responsible for implementation was not in the room. A month later, the original question gets reopened because nobody can reconstruct why the decision was made.
That is why I think decision memory belongs alongside decision velocity.
A simple decision log that preserves the reasoning behind important decisions can help teams capture what was decided, who owns the follow-through, what information shaped the choice, and when the decision should legitimately be revisited.
The goal is not to document every judgment an organization makes. It is to keep completed decisions from repeatedly becoming unfinished ones.
If the same decision keeps returning to the table because context disappeared, the organization may appear busy while its real decision velocity is much slower than leadership realizes.
Improve the system before telling people to move faster
Once leaders see slow decision velocity, the temptation will be to push.
Make the call. Stop overthinking. Move faster.
Sometimes people do need that encouragement. But pressure will not repair an unclear authority structure, fragmented information, redundant governance, or an approval process that requires too many people to touch the same issue.
Leaders should instead examine where the time is actually going.
Is the delay before the decision reaches the owner? Is the owner unclear? Are people waiting for information? Does the decision repeatedly move through meetings without a final call? Are leaders involved who do not need to be? Does the team reopen decisions because the reasoning was never preserved?
Those questions move the conversation away from blaming individuals and toward improving the operating system around them.
McKinsey’s 2026 research also points to the cost of excessive governance. The firm reports that simplifying governance can free a meaningful amount of management time for more strategic work, while highlighting accountability gaps and repeated decision reopening as sources of organizational dysfunction.
That is why decision velocity can be more useful than a simple productivity metric. It helps show leaders where the organization is making work harder than it needs to be.
Good decision velocity is a sign of organizational clarity
The healthiest organizations are not necessarily the ones making every decision fastest.
They are the ones where decisions move at an appropriate pace because people understand the system around them. Authority is clear. Reliable information is available. The right people contribute without turning every decision into a committee. Escalation happens when it adds value, not because nobody feels safe making the call.
That is what decision velocity can reveal.
If routine decisions move slowly, leaders should be curious about why. If decisions repeatedly escalate, reopen, or wait for information, those patterns are telling us something about ownership, trust, workflow design, or organizational structure.
Most of those problems already exist before anyone starts measuring them. Decision velocity simply makes them harder to ignore.
Leaders do not need another metric for the sake of having another dashboard. They need measures that help them understand how the organization really works.
Decision velocity can be one of them.