Decision Velocity examines reported delays in making decisions. It asks about approvals, reviews, handoffs, escalation, and the coordination needed to reach a decision.
The diagnostic records the participant’s account of this work, including time estimates where asked. It does not assume that a faster decision is always better or that each review step is unnecessary.
A useful decision process balances timely action with the information, review, and authority the decision requires.
What the diagnostic asks about
The questions cover how decisions are referred, reviewed, and completed from the participant’s selected perspective. They can reveal uncertainty or repeated follow-up in that account, but they do not independently verify elapsed time or identify a cause.
Topics covered
Four aspects of decision-making
The question path adapts to the submitted answers and selected perspective: people doing the work, managers, or senior leaders.
Four distinct diagnostic lenses
Q²-SODI’s four diagnostics cover different aspects of work. Each result reflects the submitted answers and selected role, not a complete assessment of the organization.
| Diagnostic | Business focus | What it examines |
|---|---|---|
| Structural Clarity | Clear responsibilities and decision authority | Whether people know who is responsible for work, who can make decisions, and how responsibilities pass between roles. |
| Operational Systems | Unnecessary process work | Recurring processes, reporting, coordination, and repeated data entry that may create unnecessary work. |
| Decision Velocity | Delays in making decisions | Reported delays associated with approvals, escalation, review steps, and routing. |
| Institutional Performance | Reliable delivery and response to change | Participants' reports of reliable delivery, responses to changing demands, and the effort needed to maintain results. |
Why decision delays deserve attention
A decision may wait for information, review, or an authorized person. These possibilities should be checked against a concrete example instead of treating every delay as a process defect.
Timing matters differently for different decisions. The next step may be to clarify what was needed, where the decision waited, and which requirements still apply.
From one response to a wider view
One participant can complete more than one Diagnostic. Each run is a separate result; additional runs do not add participants. Depth Synthesis summarizes eligible responses to the same Diagnostic. Cross-Lens Synthesis compares eligible results from different Diagnostics while retaining each measure. The Workspace checks scope, timing, versions, participation and other requirements before combining results.
Read the methodology, participation guidance and financial-scenario limits. A single-run score does not establish organizational exposure, recoverable savings or ROI.
What one completed run can show
The Decision Velocity report presents a score and band from the structured answers, the participant’s selected perspective, recorded strengths and concerns, and evidence-linked next steps where supported. A single run does not establish organization-wide conditions or change over time.
Inside the report
A participant’s view of decision-making
Open the Decision Velocity response comparison →
Recorded findings. A reading of the participant’s answers about decision-making in the stated work context.
Reported strengths and concerns. Conditions the participant describes as helpful or difficult, without assuming which one causes delay.
Practical next steps. A focused question or review that respects the decision’s existing approval requirements.
This guide describes an individual report. The Decision Velocity response-comparison sample compares responses from several people. Its scores, supporting evidence and report text use realistic example responses, not customer results.
Decision-making issues to investigate
Repeated follow-up
If a participant reports repeated follow-up, a review can ask what information or approval was needed. It should not presume that another person’s involvement was unnecessary.
Informal coordination
Informal arrangements may help people complete a decision. The account should be checked before concluding that the formal process is ineffective.
The purpose of review
A review step may address a real risk. Proposed changes need the responsible owner’s approval and should preserve required controls.
Unresolved decisions
A participant may describe decisions arriving late or being reopened. Follow-up should establish what happened in the relevant case and whether circumstances changed.
How Q²-SODI approaches decision velocity
Q²-SODI organizes submitted answers around practical questions: What decision was needed? Where did it wait? Which information and approvals were required? What could a responsible person check next?
Use the report to choose a specific question to investigate, not to remove approvals automatically. Measure the effects of any change; the report does not promise a shorter decision time.
When this diagnostic may be useful
Consider a run when decisions involve repeated follow-up, unclear referral requirements, or difficulty obtaining needed information. The result can also record what the participant says works well.
Request an invitation