Applied business architecture · Recipe 19

Capability Assessment & Heat Map: Method & Excel Template

A capability heat map helps decide where further attention is justified. Keep strategic importance, observed performance, and confidence visible as separate judgments. Once a capability is selected, investigate the conditions limiting its performance before choosing an intervention.

  • Free · No registration
  • Editable Excel
  • Instructions and blank worksheets

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.

  1. Define the decision the heat map must support and exclude dimensions that cannot influence it
  2. Keep strategic importance, current performance, change urgency, risk, investment exposure, and evidence confidence separate unless a documented decision rule combines them
  3. Define each dimension, scale, threshold, evidence requirement, and treatment of missing data before scoring begins
  4. Assess capabilities at the lowest consistent level that can change the decision and avoid mixing scores from uneven levels
  5. Record the source, date, rationale, assessor, and confidence for every material score
  6. Calibrate scores across business units and assessors using common examples, challenge sessions, and reconciliation of outliers
  7. Normalize only where comparison requires it, preserve significant variation, and avoid averages that conceal a critical weakness
  8. Present layered views that distinguish observed condition from strategic judgment and make uncertainty visible
  9. 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.

Northstar · Apply the method

Assess confidence before assigning a color.

Evidence: E-001 reports approximately 82% promise adherence from inconsistent local definitions. E-006 finds recorded part and skill confirmation for 68 of 180 reviewed commitments, while explicitly separating that sample from a later eligible cohort.

Apply the method: Record the source, denominator, period, and uncertainty alongside the assessment. Agree the scoring rule before using a color to direct attention.

Keep this boundary: This is an evidence preview, not a completed scored heat map. Missing recorded confirmation may reflect missing action, recording failure, or infeasibility; the percentage does not resolve the cause.

Inspect the source evidence · Follow the guided lessons

Archive: earlier workbook example

Worked example · Northstar v1.1

Inspect the evidence before assigning a color.

Northstar v1.1 provides different kinds of initial investment 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.

Northstar v1.1 · Evidence available before the first investment decision
IDClaim supportedAuthority / confidenceLimitation
E-001M-01 is approximately 82%; promise failures and customer escalations are materialHigh directionallyRegional definitions and cancellation handling differ
E-003Promises often precede part, skill, and capacity confirmation; exception practices varyMedium-high as convergent observationNot a controlled measure; participant incentives may affect accounts
E-006M-04 is approximately 38% under the provisional definitionMediumSmall 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.

Explore the relationships in the Atlas

Reusable Excel template

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

Use it with your own evidence

  1. Use Recipe 19 to select capabilities requiring attention.
  2. Register evidence before assigning condition or importance scores.
  3. Use Recipe 41 only after selection to diagnose limiting conditions.
  4. 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.

Start with the blank worksheets and your own evidence. Northstar’s worked examples are available separately and contain the case answers.

Optional: work through this method with AI

Describe your question in SCALE, the AI-assisted business architecture approach, and copy a complete starter into your chosen AI. Supply the source evidence there and add this method when useful. Check the evidence, challenge the explanation, and correct the result.

Use SCALE with your own question

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

Find this method in the full library