Goals
Goals, with the work underneath them
Goals: the task lands on the goal's Effort card, and the ring moves with the KPI reading.
The screen
This is the real product surface
One Tuesday
What happened at 4:45.
The same day the home page tells, read from this block.
4:45
Every task moves a goal.
Done at 4:45, and on the goal's Effort card. The KPI reading is recorded by its owner, and the ring moves with it.
With Work.
The wires
What Goals connects to
A block is a neighbour here because one stop of Tuesday puts the two of them on the ends of the same wire.
- Goals and WorkThe task is linked to the KPI
The whole map, with every node and every edge, is on how it connects.
Inside it
What is inside Goals
- OKRs
- KRAs
- KPIs
- the on track verdict
- KRAswhat a role owns, not what a person remembers.
- KPIstargets, readings and the weight each one carries.
- Goals and OKRscascade, rollup and the on track verdict.
Not built yet
Listed because the story above describes the day they will make possible, and the narration you have read is the version that is true today.
Completing the task writes the KPI record, which moves goal progress, with the Effort card and the on track verdict beside it. The Effort card from linked KRA tasks, goal rollups and the deterministic on track verdict all ship. Completing a task writes no KPI record: every KPIRecord in the repo comes from a person or an external door, so the ring does not move by itself.
On every tier, including the free Starter plan.
The point is what it connects to
Goals is one of eight, and the whole day is at one Tuesday.