Decision velocity is the rate at which an organization moves from open question to committed answer. It is the time between when a decision is needed and when the decision is actually made — distinct from the time it takes to implement the resulting work.
Decision velocity is distinct from engineering velocity. A team can execute quickly and still ship slowly because every decision routes through a 48-hour deliberation cycle. Engineering velocity is bounded by decision velocity.
In distributed teams, decision velocity is dominated by authority and asynchrony. The team with clear async decision paths makes ten decisions while the team with synchronous-only paths makes two.
Why Decision velocity Matters for Distributed Teams
Slow decision-making is invisible until you measure it. Once measured, it is often the largest single drag on shipping speed.
Improving decision velocity does not require lowering decision quality. It requires structural change: declared authority, async paths, and a culture that distinguishes reversible decisions from irreversible ones.
Frequently Asked Questions
What is decision velocity?
Decision velocity is the rate at which an organization moves from open question to committed answer. It is distinct from engineering velocity, which measures how quickly work ships once decided. Engineering velocity is bounded by decision velocity.
Related Terms
Engineering velocity
Engineering velocity is the rate at which a team converts decisions and code into shipped outcomes. It is the compound r...
Read definitionDecision making
Decision making is the process of choosing among options under uncertainty. In organizational contexts, it is rarely the...
Read definitionAsynchronous decision making
Asynchronous decision making is the practice of reaching decisions without requiring all participants to be online at th...
Read definitionGet the vocabulary that makes distributed teams work
One email per week on async governance. No spam.
See decision velocity in action.
StandIn is built around these concepts. Engineers publish declared state before going offline. The next shift starts with full context.