--- name: kpi-tree description: "Goals, the driver metrics that actually move them, and a checkable target with a review cadence for each — a huddle board's metric tree, honestly flagging any goal with no real target yet. Use when: You want a huddle board or daily standup to track something real, not a vague sense of 'how are we doing.' You have goals but haven't broken them into the specific metrics that actually drive them. You want to know honestly which goals still have no real, checkable target. Not for: You don't have real goals yet, just a general sense you should 'track more metrics' — sharpen the goals first. The driver metric would just restate the goal — a real driver metric is something specific enough to move independently. You'd be forcing a target onto a metric with no real baseline yet — leave it open and set the target once you have one." --- # Key performance indicator (KPI) tree Goals, the driver metrics that actually move them, and a checkable target with a review cadence for each — a huddle board's metric tree, honestly flagging any goal with no real target yet. Family: Daily management · Format: .xlsx · Domain: core ## What it is A KPI tree is what a daily or weekly huddle actually tracks: goals, broken into driver metrics that genuinely move them, each with a specific target and how often it's reviewed. State your goals, and a real tree gets drafted — but only with targets the input actually supports, never an invented number to fill the field. ## When to use it Use it when: - You want a huddle board or daily standup to track something real, not a vague sense of 'how are we doing.' - You have goals but haven't broken them into the specific metrics that actually drive them. - You want to know honestly which goals still have no real, checkable target. Not when: - You don't have real goals yet, just a general sense you should 'track more metrics' — sharpen the goals first. - The driver metric would just restate the goal — a real driver metric is something specific enough to move independently. - You'd be forcing a target onto a metric with no real baseline yet — leave it open and set the target once you have one. ## How to fill it in - **goals** — List each goal. Driver metrics and targets are drafted beneath each one. - **coverage** — Computed for you: total goals, driver metrics, and targets, and which goals still have no target — nothing to enter here. - **narrative** — Drafted from the tree and any coverage gaps. ## What good looks like The example below tracks the same renewal-risk support process running through this catalogue's kaizen charter, sustainment audit, work instruction, and ILUO matrix examples — one driver metric even references the ILUO matrix's own coverage number directly. The third goal is honestly left with a driver metric but no target yet. Full worked example, on-screen and as a downloadable .xlsx: https://www.katafacts.com/katas/kpi-tree ## Common mistakes - **Writing a driver metric that's really just the goal restated in metric language.** — A real driver metric can move independently and gives the team something specific to act on — a restated goal gives them nothing to actually do differently. - **Inventing a target to fill the field when there's no real baseline yet.** — A made-up target looks like rigor but isn't — it's better to leave the gap visible and set a real target once the data exists. - **Building the tree once and never revisiting it as goals change.** — A KPI tree is a living huddle artifact, not a one-time analysis — re-run it as goals shift or targets get hit. ## What it connects to Upstream: - **Training matrix with I, L, U, O skill levels (ILUO)** (`iluo-training-matrix`) — A driver metric can directly track something the ILUO matrix already measures, like coverage — the worked example does exactly this. ## Where AI helps Judgement — stays with you: - Deciding whether a drafted target is realistic given real team capacity - Deciding which coverage gap to close first Analysis — AI helps: - Drafting driver metrics and, where supportable, real targets from a stated goal - Drafting the narrative from the tree and any coverage gaps Drudgery — automated: - Counting goals, driver metrics, and targets - Identifying which goals still have no target - Exporting to xlsx in the house format --- Key performance indicator (KPI) tree is licensed [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Attribution: Katafacts (katafacts.com). ## Using this skill Apply this method as part of whatever broader task, instructions, or deliverable you're already working on -- it's a method to use, not a standalone conversation to start. There is no generation tool for this catalogue yet, so draft the artifact's actual content yourself, following the fields above, the same way a person filling this out by hand would. The canonical guide page and a downloadable worked example (.xlsx) are at https://www.katafacts.com/katas/kpi-tree.