Goals and KPIs
A goal is an outcome you can measure: “Activation ≥ 50% by December 1”. A KPI is the number behind it, with samples over time. Shipments are not goals: “2.4 on TestFlight by November 15” is a milestone, which may serve a goal.
A goal has:
- a target: a condition on a KPI, such as
activation >= 50; - a deadline, if there is one;
- supporting KPIs, shown with it;
- a status: active, achieved, missed or abandoned;
- a health (on track, at risk, off track), taken from the latest update posted on it.
You see goals on the Overview, each with its KPI’s latest number, and on the goal’s own page. Add one on the Overview, or tell Lea in chat and she creates it.
A KPI has a short ref (K-3), a name and a unit, a direction (up or down is good), a role (input, lagging or health)
and a cadence: hourly, daily or weekly. It belongs to the whole project or to one area.
Every KPI today is recorded by hand or by an agent. KPIs fed by a connector (an analytics tool, a store, a payment provider) are Planned.
Samples and periods
Section titled “Samples and periods”A sample says what the number was for a period, not when someone looked it up. Minga rounds each sample down to the start of its KPI’s period, in UTC: the hour, the day, or the Monday of the ISO week.
- Two samples for the same period are the same data point. The newer one wins on screen, and the history keeps both.
- To correct a number, record the same period again.
- A sample can be marked provisional (for data that is still coming in). Provisional numbers never wake Lea.
Who records numbers
Section titled “Who records numbers”| Who | How | Evidence |
|---|---|---|
| You | Ask Lea in chat, or call record_kpi from your own Claude Code or Codex session over MCP. The app has no sample form yet. |
Optional |
| Lea, or the agent of the KPI’s area | record_kpi in a turn |
Required: a query, a tool call, a link, a run, an output or a note |
| A worker | record_kpi, only for a KPI its item names (through a goal, or the KPI’s ref in the item) |
Required |
The tool answers with the period it stored, for example “K-3 = 42 users for the week of 2026-10-05 (weekly)”.
What Lea does with a new number
Section titled “What Lea does with a new number”When anyone else records a (non-provisional) number for a KPI of an active goal, Lea hears about it in her next turn. She compares it with the goal. If it is off track, she posts an update on the goal and usually starts research first, unless a research item for that goal is already open or closed in the last seven days.