Reference
Templates and checklists for kpi-architecture
Part of the KPI Architecture skill · loaded on demand from SKILL.md
Read this when you are producing the deliverables and want the copy-ready structures: strategy map, linkage table, scorecard, measure-definition sheet, stage-gate criteria, value ledger, P&L reconciliation, cadence table, board value page, and the pre-delivery checklists. Placeholders in angle brackets are allowed here and nowhere else.
1. Financial anchor
| Line | Baseline FY<0> | Target FY<n> | Change |
|---|---|---|---|
| Revenue | | | |
| Gross margin ($ and %) | | | |
| Operating expenses ($ and % of revenue) | | | |
| EBITDA ($ and %) | | | |
Value gap the plan must close: $<x>M run-rate by FY<n>.
Bridge: baseline + initiative run-rate value + organic contribution - inflation/headwinds = target.
2. Strategy map (text form; render as a diagram with pptx if needed)
FINANCIAL
F1 <outcome the board must see, with number and date>
F2 <productivity objective> F3 <growth objective>
CUSTOMER (value proposition: <lowest total cost | product leadership | complete solution>)
C1 <what the customer experiences, in the customer's words>
C2 ...
INTERNAL PROCESS
I1 <the process the organisation must excel at, stated as an outcome>
I2 ...
LEARNING AND GROWTH
L1 <human capital: which roles, what capability>
L2 <information capital: which data or system, to what standard>
L3 <organisation capital: incentive, culture, leadership behaviour>
Strategic themes (vertical slices): <theme A: L, I, C, F refs>; <theme B: ...>
Rules: 12 to 20 objectives; every objective is an outcome not an activity; arrows in the linkage table below, not more than about 15.
3. Linkage hypothesis table
| Arrow | If ... then ... | Lead measure (tail) | Lag measure (head) | Expected lag | Status at review |
|---|---|---|---|---|---|
| <L1 to I1> | If <lead moves to x> then <lag moves to y> | | | <n quarters> | <holding / not yet testable / failed> |
Linkage test: every objective has at least one inbound and one outbound arrow (bottom row: no inbound; top objective: no outbound). Any arrow without a measure pair is deleted or the measures are added.
4. Scorecard
| Ref | Objective | Measure | Type (lead / lag / health / pairing) | Owner | Baseline | Target FY1 | Target FY<n> | Review frequency |
|---|---|---|---|---|---|---|---|---|
Selection rules to apply row by row: few (about 20 to 25 total), causal (on the map), owned (one person), actionable (owner can move it in the review period), definable (a sheet exists), balanced (lead and lag; a health measure wherever an outcome could be hit by breaking something), gaming-resistant (a pairing measure wherever a cheap route to the target exists).
Also record: measures considered and rejected, with the reason; measures with a retirement rule.
5. Measure-definition sheet
### Measure: <name> (<map ref>, <lead | lag | health | pairing>)
| Field | Definition |
|---|---|
| Formula | <numerator / denominator, period, inclusions and exclusions, in words precise enough to code> |
| Data source | <system, table or report, join keys, version rules> |
| Frequency | <captured>; <reviewed>; <reported> |
| Owner | <accountable person>; data steward: <name> |
| Baseline | <value, period, sample size> |
| Target | <value and date, intermediate and final> |
| Related measure (pairing) | <the measure that would reveal gaming or side-effects> |
| Value link | <which ledger initiative it feeds, and how value is computed from it, if any> |
| Double-count rule | <which initiative gets credit when two touch the same line> |
| Known limitations | <what the measure cannot see; how that is reported> |
| Change control | <who can change the formula; restatement rule> |
6. Stage-gate criteria (adapted from the public McKinsey L0 to L5 description)
| Stage | Meaning | Entry criteria | Evidence required | Sign-off |
|---|---|---|---|---|
| L0 Idea | Logged | Description, rough size, sponsor | One-line entry | TO |
| L1 Validated | Worth pursuing | Owner named; value hypothesis with mechanism and baseline source; feasibility check | Half-page hypothesis | Owner + TO |
| L2 Business case | Finance-approved case | Baseline agreed and frozen; run-rate target and monthly phasing; one-off costs; double-count check; draft milestones; lead measures named | Business case, baseline sheet | Finance |
| L3 In execution | Planned and started | Milestones with dates and owners; lead measure targets; first milestone started | Milestone plan | TO + sponsor |
| L4 Implemented | Work complete | All milestones closed; lead measures at or near target; finance assessment of P&L visibility started | Milestone closure, lead-measure evidence | TO |
| L5 Realised | Value in the P&L | Value identified in management accounts against frozen baseline; sustained <3> months; budget or forecast adjusted | Finance validation memo | CFO or controller |
Rules: value is reported as realised at L5 only; stages can move backwards and the ledger shows it; every stage move is dated.
7. Value-realisation ledger
| ID | Initiative | Owner | Finance validator | Stage | Run-rate target $M | FY<1> in-year target | YTD in P&L | FY<1> forecast | Variance | One-off cost | Next gate and date | Last stage move |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| V1 | | | | | | | | | | | | |
| S | Sand: <n> initiatives each under $<x>M | Various | TO controller | mixed | | | | | | | rolling | |
| | Total | | | | | | | | | | | |
Stage split of YTD in P&L: L5 realised $<a>; L4 assessed $<b>; L3 early value $<c>. Headline = L5 only.
Pipeline by stage (run-rate $M): L5 <> | L4 <> | L3 <> | L2 <> | subtotal L2+ <> | L1 <> | L0 <>
Coverage: L2+ value / required value = <x> percent. Interpretation: <thin / adequate>, given expected attrition of roughly 70 percent from L1 to L5 in the public McKinsey data.
Business-case line for each boulder: one sentence showing the arithmetic (volume x unit effect x realisation factor = run-rate).
8. Ledger-to-P&L reconciliation
| Line | Plan FY<1> | Forecast FY<1> | Comment |
|---|---|---|---|
| Baseline EBITDA (frozen) | | | |
| Initiative value in-year (from ledger) | | | |
| One-off implementation costs | | | shown separately, never netted silently |
| Headwinds / tailwinds independent of the programme | | | |
| EBITDA | | | |
Independent FP&A forecast: $<x>M. Difference: $<y>M, traced to <cause>.
9. Review cadence
| Forum | Frequency | Chair and attendees | Inputs | Decisions it can take | Output document |
|---|---|---|---|---|---|
| TO initiative review | Weekly | CTO; owners in rotation | Milestones, lead measures, blockers | Stage moves to L4; unblocking; owner changes | Action log |
| Value review | Monthly | CFO; controller; CTO; L4/L5 owners | Ledger; management accounts | L5 sign-off; baseline restatements; re-phasing | Updated ledger |
| Scorecard and strategy review | Quarterly | CEO; executive team | Scorecard; linkage status; ledger summary | Confirm or revise hypotheses; add or retire measures | Review minutes |
| Board value page | Quarterly | Board | One page (template 10) | Investment approvals | Board page |
| Strategy map refresh | Annual or on strategy change | CEO; executive team | Map, scorecard | Rebuild or reconfirm | New map |
10. Board value page (one page)
Title (action title, one sentence): <e.g. "Programme is at $6.5M realised against $38.0M in-year plan; two initiatives re-phased, run-rate target unchanged">
Value bars: Realised (L5) | Assessed (L4) | Early (L3) | Forecast (L1, L2) | Target
Pipeline coverage: <x> percent of required run-rate at L2+; refill actions: <list>
Scorecard headlines: <4 to 6 measures with baseline, current, target, trend arrow described in words>
Hypotheses tested this quarter: <holding / failed, one line each>
Decisions requested: <list>
11. Pre-delivery checklist (run before anything goes to the client)
Strategy map
- Every objective is an outcome, not an activity or a project name.
- Every objective has at least one inbound and one outbound arrow, except the bottom row and the top objective.
- Every arrow has a lead-lag measure pair and an expected lag time.
- Fewer than about 15 arrows; an executive is willing to defend each.
- The value proposition is stated in the customer's terms.
Scorecard
- 20 to 25 measures or fewer; no perspective is empty; no perspective has more than 7.
- Every measure has one named owner who can move it within the review period.
- Every measure has a definition sheet with formula, source, frequency, baseline and target.
- Every lag measure has at least one lead measure upstream on the map.
- Every measure that could be hit cheaply has a pairing or health measure.
- Measures that will read 100 percent or zero forever have a retirement rule.
- Rejected measures are listed with reasons.
Ledger
- Every initiative has an owner, a finance validator, a stage with a date, a frozen baseline and a run-rate target.
- Headline value is L5 only; L4, L3 and forecast are shown separately.
- Stage subtotals sum to the ledger total; the ledger in-year value plus costs and headwinds reconciles to the P&L forecast; the difference to FP&A is stated.
- Double-count rules exist wherever two initiatives touch the same P&L line.
- One-off costs are on their own line.
- Sand is tracked, not only boulders.
- Coverage is stated and interpreted against expected attrition.
Cadence
- Each forum has a chair, inputs, decisions it can take and an output.
- The quarterly review has a hypothesis-test agenda item, not only a numbers recital.