Decision Velocity: Definition, Formula, and How to Measure It

Decision velocity is the speed at which a product team moves an idea from capture to a recorded decision. It is measured by four sub-metrics: time to decision (TTD), decision throughput (decisions made per sprint), decay queue size (ideas waiting beyond a target threshold), and reopen rate (percentage of decisions revisited within 90 days). Healthy product teams hit TTD under 14 days, throughput at or above intake, decay queue under 5 items, and reopen rate under 5%. Below those, the roadmap is stuck and the team is paying the cost of decision decay.

Your product team probably tracks sprint velocity, feature velocity, and deployment velocity. Decision velocity is the upstream metric that constrains all three. If decisions take 30 days, no amount of engineering velocity makes the roadmap go faster.

This post defines decision velocity, walks through the formula and the four sub-metrics, and shows how to measure each. For the broader context on why slow decisions cost product teams roughly $250,000 per year, see the decision decay pillar. For decision velocity in product management specifically, this post is your starting point.

At a glance

Question	Short answer
What is decision velocity?	The speed at which a team moves an idea from capture to a recorded decision.
What's the formula?	Decisions resolved per period ÷ ideas captured per period. A ratio of 1.0 means the team is keeping up; below 1.0 means the backlog is growing faster than decisions.
Four sub-metrics	Time to decision (TTD), throughput, decay queue size, reopen rate.
Healthy TTD	Under 14 days.
Healthy throughput	At or above intake rate.
Healthy decay queue	Under 5 ideas pending past the target threshold.
Healthy reopen rate	Under 5%. Above 15% means decisions aren't sticking, often because the rationale wasn't captured.
Why measure it	Slow decisions kill roadmap momentum. Every idea waiting in limbo is a customer waiting for an answer plus the cognitive load on whoever is supposed to decide.
Where it fits	Decision velocity is the leading indicator. Decision decay is the lagging cost. Reopen rate is the bridge.

What Is Decision Velocity?

Decision velocity is composed of several key metrics:

Time to Decision (TTD)

Average days from when an idea is captured to when a decision is made.

Healthy: < 14 days Warning: 14-30 days Critical: > 30 days

Decision Throughput

Number of decisions made per week/sprint. This measures your team's capacity to process ideas.

Healthy: Throughput ≥ intake Warning: Backlog growing slowly Critical: Backlog growing faster than decisions

Decay Queue Size

Number of ideas waiting for a decision longer than your target threshold.

Healthy: 0-5 items Warning: 6-20 items Critical: > 20 items

Reopen Rate

Percentage of decisions that get revisited within 90 days. High rates indicate poor initial decision quality.

Healthy: < 5% Warning: 5-15% Critical: > 15%

Why Decision Velocity Matters

Slow Decisions Kill Momentum

Every idea waiting in limbo is:

• A customer waiting for an answer
• An opportunity getting stale
• A team member wondering "did anyone see my suggestion?"
• Cognitive load on whoever is supposed to decide

When decisions take 30+ days, stakeholders lose faith that feedback matters.

Fast Decisions ≠ Reckless Decisions

Decision velocity isn't about saying yes to everything quickly. It's about resolving ideas quickly:

• "Yes, let's build this"
• "No, here's why not"
• "Not now, but we'll revisit when X changes"

A fast "no" is better than an eternal "maybe." At least "no" provides closure.

Velocity Compounds

Teams with high decision velocity:

• Ship faster (less time debating, more time building)
• Have higher morale (people see their input matters)
• Make better decisions (practice improves judgment)
• Attract better feedback (customers engage when they see responsiveness)

Teams with low decision velocity enter a doom loop: slow decisions → disengaged stakeholders → fewer quality inputs → worse decisions → even slower decisions.

How to Measure Decision Velocity

Step 1: Define Your Decision States

Every idea should have a clear status:

• New - Just captured, needs triage
• Under Review - Someone is evaluating
• Decided: Approved - Will be built
• Decided: Rejected - Won't be built (with reason)
• Decided: Deferred - Not now, conditions for revisit defined

Step 2: Track Timestamps

For each idea, record:

• When it was captured
• When it entered review
• When a decision was made
• Who made the decision

Step 3: Calculate Your Metrics

Time to Decision: Average(Decision Date - Capture Date) for all decided items

Throughput: Count(decisions) per week

Decay Queue: Count(items where Today - Capture Date > 30 days AND status ∈ {New, Under Review})

Reopen Rate: Count(reopened decisions) / Count(all decisions) over 90-day window

Step 4: Set Targets and Review Weekly

Put decision velocity on your weekly metrics dashboard:

• Are we meeting our TTD target?
• Is the decay queue growing or shrinking?
• Are we reopening too many decisions?

The Decay Queue Problem

The decay queue deserves special attention. Every idea sitting undecided for 30+ days represents:

Customer Frustration

Someone suggested something. They're waiting. The longer they wait, the less they'll engage in the future.

Organizational Indecision

If something has been sitting for 30+ days, that's a signal. Either:

• No one owns the decision (accountability problem)
• The decision is hard (needs escalation)
• The idea lacks information (needs research)

Opportunity Cost

While you're not deciding, competitors might be shipping.

Target: Decay queue should be zero.

If you have 20+ items in your decay queue, you have a systemic decision-making problem—not an individual item problem.

How to Improve Decision Velocity

1. Assign Decision Owners

Every idea needs a clear owner responsible for the decision. Not "the product team"—a specific person with a name.

2. Set Decision SLAs

Every idea gets a decision within 14 days. Period. This forces prioritization of decision-making itself.

3. Make "No" Easy

Many decay queues are full of ideas no one wants to reject. Create:

• Clear rejection categories (out of scope, insufficient demand, technical constraints)
• Templates for rejection rationale
• A culture where "no" is respected, not punished

4. Batch Decision Sessions

Instead of ad-hoc decisions, schedule weekly "decision inbox" sessions:

• Review all new items
• Process decay queue
• Record decisions with rationale

5. Escalate Stuck Items

If an idea has been in review for 14+ days, it needs escalation—not more time. Either:

• Escalate to someone with authority to decide
• Gather missing information
• Accept that "defer" is a valid decision

Decision Velocity as a Leading Indicator

Feature velocity tells you how fast you're building. Decision velocity tells you how fast you're learning.

Teams with high decision velocity:

• Process customer feedback faster
• Course-correct before building the wrong thing
• Maintain stakeholder trust
• Keep roadmaps dynamic, not stale

If you're only measuring output velocity, you're missing half the picture. Start measuring decision velocity.

Start Tracking Today

Calculate your current state:

1. How many ideas are waiting for a decision?
2. What's the oldest undecided item?
3. How many decisions did you make last week?

If the answers are uncomfortable, you've found your problem. Decision velocity isn't a vanity metric. It's a health check for your product organization.

FAQ

What is decision velocity?

Decision velocity is the speed at which a product team moves an idea from capture to a recorded decision (accepted, rejected, deferred, or shipped). It is the upstream constraint on every other product metric. Engineering velocity, feature velocity, and deployment velocity are all bounded by how fast the team can decide what to build.

What is the decision velocity formula?

Decisions resolved per period ÷ ideas captured per period. A ratio of 1.0 means the team is keeping up with intake. Below 1.0 means the backlog is growing faster than decisions are being made, which compounds into decision decay. Above 1.0 means the team is processing the backlog faster than new ideas are arriving (rare; usually a leading indicator that intake is too narrow).

How is decision velocity different from feature velocity?

Feature velocity measures shipping speed (features delivered per sprint). Decision velocity measures decision speed (ideas moved through the decision pipeline per sprint). The two are not substitutes. A team can have high feature velocity by shipping the wrong things fast. Decision velocity is the metric that catches that. Both matter; decision velocity is the leading indicator and feature velocity is the lagging output.

What is a healthy time to decision?

Under 14 days from idea capture to recorded decision. Above 30 days, ideas start to decay (context fades, requesters move on, the situation changes) and the decision either gets made on stale information or gets skipped entirely. The Decision Half-Life of 23 days is roughly the inflection point.

What is decay queue size?

Decay queue size is the count of ideas waiting for a decision longer than your target threshold (typically 14 days). It's the leading indicator that decision velocity is slowing. A growing decay queue means decisions are accumulating without being made, which compounds into decision decay and re-litigation cost.

What is a good reopen rate?

Under 5%. Reopen rate is the percentage of decisions that get revisited within 90 days of being made. High reopen rate (above 15%) usually means decisions aren't sticking because the original rationale wasn't captured, so when a new stakeholder raises the same question, the team starts the debate from scratch. Capturing the rationale at the moment of decision (see ambient decision detection) is the primary fix.

How do I measure decision velocity in Jira or Linear?

Both tools expose status transitions in their APIs. Define an "idea captured" status and a set of "decision made" terminal statuses (Won't Do, Done, Deferred, Cancelled). Time to decision = time between those two events. Throughput = count of items reaching a terminal status per sprint. Decay queue = count of items in non-terminal statuses past your TTD threshold. Reopen rate = items that left a terminal status and re-entered an active status within 90 days. IdeaLift computes all four automatically across Jira, Linear, GitHub, and Slack.

How does decision velocity relate to decision decay?

Decision velocity is the leading indicator. Decision decay is the lagging cost. Slow decision velocity (high TTD, growing decay queue) compounds into high decision decay (lost context, re-litigated decisions, $250K/year for a typical team). Improving decision velocity is the prevention; capturing the rationale at the moment of decision is what makes the velocity sustainable. See the decision decay pillar for the full cost model.

---

IdeaLift tracks decision velocity automatically. See your time to decision, decay queue, and throughput in real-time. Know exactly where decisions are getting stuck. Start your free trial.