A KPI review template exists to stop the weekly meeting from improvising. Without one, the same three numbers get discussed from scratch every week, the same opinions get repeated, and the meeting ends with no decision anyone remembers on Thursday. With one, the review takes twenty minutes, every metric gets the same four questions, and the output is a short list of decisions and owners. This template is built for small teams that review five to ten KPIs weekly.
The Four Questions Every Metric Gets
Every metric on the dashboard gets exactly four questions, in order. What is the number, compared to last week and the threshold? What changed, in one sentence of cause? What decision does this change suggest? And who acts on it before the next review? The discipline is in the order: number first stops storytelling before it starts, cause second keeps the explanation accountable to the data, decision third forces the metric to justify its place on the dashboard, and owner fourth is what makes the review a management tool instead of a report.
If a metric survives four weeks without suggesting a decision or an owner, that is a finding. Either the threshold is wrong, the metric is decoration, or the team has not agreed what the number is for. The template has a row for exactly this situation, because unnoticed decoration is how dashboards grow to thirty charts that nobody uses.
Kpi Review Template KPI Decision Table
Fill one row per KPI during the meeting. Keep entries short — this table is read aloud, not archived for posterity.
| KPI | Number vs threshold | One-sentence cause | Decision or none | Owner and due date |
|---|---|---|---|---|
| Weekly qualified leads | 14 vs target 12 | Referral spike from partner webinar | Raise webinar cadence test to monthly | Sam, by Oct 9 |
| First response time | 7.1h vs max 4h | Tuesday inbox overflow, one person out | Temporarily re-route Tuesday tickets | Support lead, immediate |
| Monthly churn | 2.1% vs 2.0% guardrail | One large account downgrade | None — within noise, watch next month | Review owner, next review |
| [Decoration candidate] | No movement 4 weeks | — | Remove or re-threshold | Dashboard owner, this week |
Notice the third row: a decision of “none” is a valid, useful output. The template’s job is not to manufacture action every week; it is to make inaction a conscious choice with a revisit date. Rows that end in “none, watch” stop the debate that would otherwise eat the meeting.
Running The Meeting Around The Table
Sequence matters. Send the prefilled table — numbers and thresholds only — the day before, and open the meeting with five silent minutes where everyone reads it. Then walk the rows top to bottom, spending time in inverse proportion to how well a row is going. Rows at target get thirty seconds of confirmation; rows breaching threshold get the discussion time. This inverts the natural meeting dynamic, where comfortable numbers get talked about because they are easy to talk about.
Close by reading the decision column aloud. That list — decisions and owners, nothing else — is the entire output of the review. Post it where the team works, and open the next review by reading last week’s list first. A review that does not check its own follow-ups is theatre; this one habit is what makes the template compound. For the layer above this meeting, the monthly business review template aggregates the weekly decisions into trends, and the KPI owner guide defines who the “owner” column actually names.
Common Failure Modes And How The Template Handles Them
The first failure mode is the metric that arrives pre-explained. Someone walks in with a polished story about why a number moved, and the meeting nods along without checking the data. The template counters this structurally: the cause column gets one sentence and must be written after the number column, so the explanation follows the measurement instead of replacing it. If the one-sentence cause needs a paragraph, the honest entry is “cause unknown — investigate,” which is a legitimate decision with an owner.
The second failure mode is threshold drift: targets quietly loosened after a bad month so the dashboard looks green again. The template has no special defense except habit — but the habit is strong. Because every row states the threshold in writing every week, changes to thresholds become visible edits rather than silent memory shifts. Teams that keep last quarter’s filled tables can diff them, and a threshold that moved without a decision row explaining why is exactly the kind of finding a monthly review should catch.
The third failure mode is the review that outgrows its own follow-ups. Decisions get made, owners get named, and nobody checks whether anything happened. The closing ritual of reading last week’s decision column first is deliberately unskippable: it converts the template from a meeting agenda into a management system. For the wider goal-setting context that these weekly reviews serve, Measure What Matters remains the standard readable reference on why cadence and visible scorecards beat annual planning, and its ideas map directly onto the decision column’s owner-and-date discipline.
When The Review Says The Metric Is Wrong
Sometimes the template’s most valuable output is the discovery that a KPI itself is broken — measured unreliably, defined ambiguously, or tracking something the business no longer cares about. Handle this as a formal decision, not a quiet deletion. The decision row records “retire or redefine,” the owner names who proposes the replacement, and the next review includes a row for the candidate metric so the team compares old and new honestly for a few weeks before the swap. Retired metrics leave a note in the table’s history, because six months later someone will ask “why did we stop tracking that?” and the answer should be a decision, not a shrug.
This is also where the template protects against metric inflation. New numbers get proposed constantly — a tool ships a new report, a manager reads an article, a client asks for a chart. The template’s cost is visible: every new KPI takes meeting minutes every week forever. Requiring a proposal to name the decision the metric will inform, and then survive four weeks on the “watch” treatment, filters most additions before they calcify into permanent ceremony.
Adapting The Template Without Breaking It
The template flexes on purpose. A team reviewing three KPIs can drop the decoration row and meet in ten minutes; a team with fifteen needs it more, not less. What should never flex is the four-question order and the owner column — those two are the mechanism. Everything else, including this article’s exact table columns, is a starting point you may reshape once you have run six honest reviews and know where your own meetings leak time.
Start this week with the table above, copied into whatever the team already uses. The first two reviews will feel mechanical. By the fourth, the meeting will run itself — and the dashboard will be three charts smaller.