KPI tracking software, and where it stops being a dashboard.
KPI tracking software holds a short list of numbers, each with a named owner and a target, updated on a fixed rhythm and read together as a group. It is a meeting input rather than a reporting tool. The working test: someone can read the whole list in five minutes and say which numbers are off target and who is already doing something about each one.
What does KPI tracking software actually do?
It keeps a fixed list of measures with an owner and a target for each, records a value every period, shows the trend beside the current number, and marks what is off target. The value comes from the list staying the same week to week, so a number falling out of range is visible as a change rather than as noise.
Do we need KPI tracking software if we already have a BI tool?
Frequently not. If your BI tool can pin a small set of measures to one page with a target line on each, and a person is accountable for reading it every week, you already have the thing that matters. The rhythm and the ownership do the work, not the software. A dedicated tool helps when the list keeps getting longer, when nobody owns individual numbers, or when the weekly read needs assembling by hand.
How many KPIs should a team track?
Small enough to read aloud in a meeting, which in practice lands somewhere between five and fifteen per team. Above that, nobody reacts to any single number and the list becomes a report. The count is a symptom: a long list usually means the team has not decided which measures would actually change a decision.
Should KPI values be entered automatically or by hand?
Automation is obviously better for anything already in a system, but manual entry has an underrated property: the owner has to look at the number. Teams that automate everything often stop noticing their own measures. Where a number is hand-entered, the act of entering it is part of the accountability, not just data collection.
What to look for
One name against every number
A measure owned by a department is owned by nobody. Scan the list and count how many rows have a person rather than a team beside them; anything under all of them is a gap. The owner is not the person who produces the number, it is the person who is expected to have a view when it moves.
A target set in advance, not a color set afterwards
Red and green mean nothing unless the threshold was agreed before the period started. Check whether the tool stores a target per measure per period, and whether changing that target leaves a trace. A system where the goal can be edited after the result is known produces a scorecard that is always mostly green.
Weekly granularity, not monthly rollups
A number reported monthly gives you eleven chances to react in a year, and the reaction arrives weeks after the cause. Weekly is the rhythm most operating frameworks assume, because it is short enough that a miss is still recoverable. Check that the tool stores a value per week rather than aggregating up to a monthly figure.
Trend beside the current value
A single number tells you almost nothing: 62 is good or bad depending on last quarter. Look for at least thirteen weeks of history shown inline, not on a separate detail page. If seeing the trend takes a click per measure, nobody will do it during the meeting, and the meeting is the only place it matters.
An off-target number produces a decision
The point of the review is not the list, it is what happens to the rows that are off. Check whether a missed measure can become an owned, dated item without leaving the tool. If flagging a problem and deciding what to do about it live in different systems, the second half quietly stops happening.
KPI tracking vs. business intelligence and dashboards
Business intelligence is built for exploring: many measures, slice-and-dice, questions you did not know you had. KPI tracking is built for deciding: a short fixed list, the same one every week, each row owned and each with a line it is supposed to stay above. The formats look similar on screen, which is why they get conflated, but the failure modes are opposite. A BI tool fails when it cannot answer a new question. A KPI review fails when the list changes so often that nobody notices a number slipping. Most companies need both, and the mistake is using one where the other belongs.
Where GoalCadence sits
GoalCadence is being built around a weekly scorecard read inside the meeting it belongs to, for teams running OKRs, Scaling Up or 4DX — or a blend. It is currently in development, so signing up joins a waitlist rather than creating an account.