Healthy
Inside the green boundary.
OKRGoal holds your KPIs and your OKRs in one place, connected. Build driver trees down to the numbers a team can move this week. Give every KPI a health band. When one turns unhealthy, the Champion tells its owner and drafts a recovery OKR from the drivers that are falling short.
| KPIs | OKRs |
|---|---|
| A number you watch every period, whether or not anybody is trying to change it | A deliberate change, for a quarter or a year |
| Describe the health of the business | Describe what you are changing about it |
| Live as long as the business does | Close, get scored, and feed the next cycle |
They connect in three ways. A key result can be measured by a live KPI. An unhealthy KPI can start a recovery OKR. And every KPI's baseline is an input to planning.
A tree has one root, usually a lagging number such as revenue or operating margin. Its leaves are leading drivers a team can act on this week. A link is either a formula, where the child is part of the parent's calculation, or an influence, where the child is believed to move the parent.
Set green and red boundaries in the KPI's own units: stay at or above, stay at or below, increase to, decrease to, or stay within a range. No boundaries? It falls back to how close the reading is to its target.
Inside the green boundary.
Between the boundaries. Watch the leading drivers.
Past the red boundary. Decide a response.
Enter a value and a target.
A KPI under recovery is shown as recovering beside its real band, never instead of it. You can see the fix working without anyone mistaking it for the number having recovered.
Treat it as day-to-day work, with an owner and a date.
Put it under an objective you already have.
A committed objective, drafted for you, to restore a level the business relies on.
The draft is ready the moment the KPI turns unhealthy. The Champion proposes it after two unhealthy periods in a row, or at once if the KPI falls straight from healthy to unhealthy.
The objective names what the KPI protects, in words, not numbers.
The first key result is the KPI itself, from where it is to where it is healthy.
Up to three more, one per leading driver at the edge of the failing branch that is below its own target, each owned by whoever owns that driver.
Drivers already on target are skipped.
When the reading is healthy again, the Champion proposes closing the recovery OKR.
The draft is built by rules, so it works with the AI switched off. With an AI provider connected, a model can word the objective better, and the KPI page narrates the trend.
Every KPI in the workspace that is unhealthy or under recovery: its real band, its recovery objective and progress, and the three responses for the ones nobody has answered yet. A To do list, for numbers.
Write a formula over other KPIs. Change a source and everything that depends on it recomputes.
Daily numbers roll into monthly ones with their own aggregate, so a ratio stays a ratio of sums.
Periods across, KPIs down. Enter a month of readings without touching the mouse.
A key result can read its value from a live KPI, so nobody types the same number twice.
With an AI provider connected, a plain-language narration of the trend under every chart.
Bring KPIs and their history from a spreadsheet.
In the live demo, Northwind's operating margin goes unhealthy in the summer, and Hugo, the CFO, runs a recovery OKR. Sign in as Hugo and follow it.