The decision
Build a useful capability heat map
A capability map has been colored red, yellow, and green without a clear decision, consistent dimensions, defensible evidence, or any indication of confidence, creating visual certainty without analytical discipline.
- Decision supported
- Which capabilities require attention for a stated decision and how condition, importance, urgency, risk, and confidence should remain distinct.
- Start with
- A governed capability map, decision-specific dimensions, outcome and performance evidence, scoring rules, owners, and confidence criteria.
- Boundary
- Prioritizes capability attention; it does not diagnose root cause, prove investment value, or convert maturity into an unexplained color.
When to use this method
- Leaders need to prioritize capability investment or improvement
- Several assessments use incompatible scoring rules
- Strategic importance and current performance are being collapsed into one color
- Stakeholder opinion is the only visible basis for a portfolio recommendation
Evidence to bring
- Decision, audience, scope, and investment horizon
- Governed capability map and definitions
- Strategic outcomes and value-stream impacts
- Performance, risk, cost, maturity, customer, workforce, and dependency evidence
- Assessment owners, evidence dates, and confidence criteria
The method
Work through the decision.
- Define the decision the heat map must support and exclude dimensions that cannot influence it
- Keep strategic importance, current performance, change urgency, risk, investment exposure, and evidence confidence separate unless a documented decision rule combines them
- Define each dimension, scale, threshold, evidence requirement, and treatment of missing data before scoring begins
- Assess capabilities at the lowest consistent level that can change the decision and avoid mixing scores from uneven levels
- Record the source, date, rationale, assessor, and confidence for every material score
- Calibrate scores across business units and assessors using common examples, challenge sessions, and reconciliation of outliers
- Normalize only where comparison requires it, preserve significant variation, and avoid averages that conceal a critical weakness
- Present layered views that distinguish observed condition from strategic judgment and make uncertainty visible
- Translate the findings into a small set of investment, validation, or ownership decisions and define the reassessment trigger
What the work should produce
- Decision-specific capability heat map
- Assessment dimension and scoring guide
- Evidence and confidence register
- Calibration and exception log
- Prioritized decisions and reassessment plan
When to stop
Stop when each emphasized capability has a defensible score, visible evidence and confidence, and a clear connection to the decision. Do not color unassessed capabilities or use a composite score that decision makers cannot explain.
Worked example · Northstar v1.1
Inspect the evidence before assigning a color.
Northstar v1.1 provides different kinds of Episode A evidence about service promises. This is an evidence-register preview, not a scored heat map: the limitations must inform assessment confidence, and no missing score is inferred from a percentage.
| ID | Claim supported | Authority / confidence | Limitation |
|---|---|---|---|
| E-001 | M-01 is approximately 82%; promise failures and customer escalations are material | High directionally | Regional definitions and cancellation handling differ |
| E-003 | Promises often precede part, skill, and capacity confirmation; exception practices vary | Medium-high as convergent observation | Not a controlled measure; participant incentives may affect accounts |
| E-006 | M-04 is approximately 38% under the provisional definition | Medium | Small purposive sample; definition not yet approved |
A performance report, convergent observations, and a small provisional sample cannot be treated as equally certain. Use the workbook to document the assessment rule and evidence behind each score; use Recipe 41 afterward to diagnose the selected capability’s limiting conditions.
Editable template · Version 1.1
Evidence-based capability assessment and heat-map workbook
First select capabilities that warrant attention using strategic importance, observed performance, evidence strength, and confidence; then diagnose the specific people, process, information, technology, policy, governance, capacity, performance, and dependency conditions that limit a selected capability.
Inside the workbook
- Read me and assessment scales
- Evidence register
- Formula-driven selection assessment
- Heat-map summary
- Limiting-condition diagnosis
- Completed Northstar examples
Use it with your own evidence
- Use Recipe 19 to select capabilities requiring attention.
- Register evidence before assigning condition or importance scores.
- Use Recipe 41 only after selection to diagnose limiting conditions.
- Keep confidence, disagreement, required condition, and evidence gaps explicit.
A heat-map color prioritizes attention; it does not diagnose cause. The improvement assessment structures a diagnosis; it does not prove causation or authorize investment.
Continue the work
Why does a selected capability fail to produce the required outcome and how does investment coverage compare?
Related Field Notes
Reference material
- Business Architecture and Business Performance Analysis ↗Business Architecture Guild · Account required
- Metrics for Evidence-Based Strategy Execution ↗Business Architecture Guild