Template

Decision Quality Scorecard (Template)

A practical, ready-to-use scorecard teams can use to rate past decisions, capture root causes, and convert learning into concrete improvements. Includes field definitions, scoring guidance, a sample filled scorecard, and step-by-step instructions for monthly learning huddles.

Decision Quality Scorecard — Template

Use this scorecard to evaluate the quality of a completed decision, capture why outcomes differed from expectations, and identify measurable improvements to decision processes, roles, or data. Designed for quick use in monthly learning huddles or post‑mortem reviews.

When to use

  • After a decision with significant cost, risk, or strategic impact.
  • When outcomes diverge from expectations and you want to learn, not blame.
  • Regularly, as part of a monthly learning huddle to identify systemic improvements.

Fields and guidance

Score each 1–5 (1 = poor, 3 = adequate, 5 = excellent) and add short evidence-backed notes. Keep entries factual and avoid editorializing.

Field What to capture Scoring guidance
Decision ID Unique identifier linking to your Decision Log e.g., DEC-2026-014
Date Date decision was made
Type Operational, Strategic, Tactical, Safety, Compliance, etc.
Evidence Adequacy (1–5) Was relevant data available, current, and applied appropriately? 1 = No relevant evidence used; 5 = strong, relevant, and tested evidence
Clarity of Criteria (1–5) Were objectives, constraints, and success criteria explicit and measurable? 1 = Criteria absent or vague; 5 = clear, measurable criteria aligned to goals
Stakeholder Alignment (1–5) Were affected stakeholders identified, heard, and accounted for? 1 = Key stakeholders ignored; 5 = alignment and documented buy-in
Follow‑up & Learning Captured (1–5) Was a follow-up plan documented, and were learning mechanisms (logs, huddles) used? 1 = No follow-up; 5 = documented plan, owner, and learning captured
Outcome vs Expectation Short factual comparison: what happened vs what was expected (quantify where possible) Example: Expected 10% cost reduction; achieved 4% increase
Root cause notes Evidence-based causes for gaps between expectation and outcome List 1–3 root causes (data gap, wrong assumption, execution failure)
Actionable improvements Specific, assignable actions to reduce recurrence. Include owner and due date. Example: "Add data checkpoints to project intake — Owner: Ops Lead — Due: 2026-07-15"

Scoring and interpretation

Calculate an average of the five numeric scores (Evidence, Criteria, Stakeholder, Follow-up, plus an optional domain-specific factor). Use the average to prioritize follow-up:

  • 4.0–5.0: Strong decision process — document as a best practice and share.
  • 3.0–3.9: Adequate but improvable — assign 1–2 low-effort experiments to test improvements.
  • <3.0: Problematic process — require a corrective plan, coaching, or changes to governance.

Sample filled scorecard (example)

Field Entry
Decision ID DEC-2026-014
Date 2026-05-11
Type Operational: Vendor selection for component X
Evidence Adequacy 2 — Evidence limited to vendor claims; no independent testing
Clarity of Criteria 3 — Cost and delivery clear; quality acceptance criteria were not explicit
Stakeholder Alignment 2 — Procurement and Ops consulted; Quality team not involved
Follow‑up & Learning Captured 2 — No follow-up test plan; no owner assigned
Outcome vs Expectation Expected: Faster delivery and 8% cost savings. Actual: Delivery late; higher rework — net +6% cost
Root cause notes Missing quality acceptance criteria; assumptions about test coverage; late supplier ramp-up
Actionable improvements
  1. Include Quality lead in procurement evaluations — Owner: Procurement Head — Due: 2026-06-30
  2. Require third-party validation of critical specs before contract — Owner: Engineering — Due: 2026-07-15
  3. Create a 30/60/90 day supplier test plan with go/no-go gates — Owner: Ops — Due: 2026-06-15
Average score 2.25 — Prioritize corrective governance and testing requirements

How to use this scorecard in a monthly learning huddle

  1. Select 2–4 decisions from the Decision Log that had notable outcomes or learning potential.
  2. Assign a facilitator to keep the review factual and time‑boxed (20–30 minutes per decision).
  3. Read the Decision summary and fill the scorecard collaboratively. Encourage evidence citations (data, emails, test results).
  4. Capture root causes and convert them into 1–3 concrete actions with owners and due dates.
  5. Log the completed scorecard entry and update the Decision Log with link(s) to follow-up actions.
  6. At the next huddle, review progress on assigned improvements as a standard agenda item.

Biases and common traps to watch for

  • Hindsight bias: Base scores on information available at decision time, not what you learned later.
  • Outcome bias: Separate quality of the decision process from the outcome — a good process can sometimes lead to a bad outcome and vice versa.
  • Consensus-by-default: Record who participated and what dissenting views existed.

Notes and variations

This template is intentionally compact. If you want to collect scorecards centrally for trend analysis, convert this into an interactive form that stores submissions in your Decision Log database. Tracking averages over time reveals whether governance changes improve decision quality.

Related resources

  • Decision Log template (link your system)
  • Pre‑mortem checklist
  • RACI for decision governance
Discuss Ask the Librarian

Discussion

Comments and conversation will live here.