Goals, key results and check-ins
Vision, pillars, objectives and key results, with progress that rolls up and confidence check-ins.
The Goals view is a tree: the vision at the top, pillars under it, objectives under each pillar, and key results, outcomes or KPIs under each objective.
- Time-bound or ongoing. An objective with a period (a quarter, a year) can be finished. An ongoing one - a standard the company keeps, like response time - has a cadence and a target band instead, and never reads as done.
- Progress rolls up, and the card says how: the average of its key results, the progress of the work linked to it, or its child objectives. If somebody typed a number by hand, the card says it is a manual figure.
- Check-ins. The owner sets their confidence - high, medium or low - with a note. It goes on the goal's updates, so the history of how sure people were is kept.
- Execution plan. Every objective has a panel listing the programs and projects that serve it. *Propose execution* drafts programs, projects and milestones for the owner to review; each item is accepted or declined on its own, and nothing is created until somebody presses Accept.
On the new Strategy page, Goals & OKRs opens this view - objectives and key results live in one place. On the earlier page it is still its own extension page.
A dated checkpoint on one project - "beta shipped", "pilot complete" - is a milestone on that project, not a company goal. On the new Strategy page, Autopilot and meeting notes write those as milestones, and project milestones that Autopilot or a meeting had filed as goals are moved to their projects so the Goals view lists strategy. A meeting's objective without a date is not filed anywhere: the meeting says how many were mentioned so you can add the real ones here.