Goals
Measurable targets that organise trackers, decisions and reports around a shared outcome.
A goal is a measurable target. It's the anchor that ties together the trackers, decisions and answers that move toward it.
Status: in progress. Goals exist as a concept across the product (trackers can be linked to goals with explicit roles), but a dedicated Goals page is part of the active roadmap. Until then, goals show up inline on each tracker and decision's detail page. Confirm scope with your admin if you're rolling this out to a customer.
What a goal looks like
Every goal has:
- A name — "Reach ₹X ARR by Q4", "Lift retention from A% to B%"
- A target value and target date
- An owner
- Linked trackers with explicit roles
- Linked decisions that move toward it
Tracker link roles
When you link a tracker to a goal, you pick how that tracker relates to the goal:
| Role | What it means |
|---|---|
| Primary | This tracker directly measures the goal's outcome. ("ARR" for an ARR goal.) |
| Leading indicator | This moves before the outcome does. ("Pipeline created" leads "ARR".) |
| Lagging indicator | This moves after the outcome does. ("NPS" lags "retention".) |
| Guardrail | What must not break while pursuing the goal. ("Support ticket volume" while increasing usage.) |
The goal page uses these roles to order trackers — primary first, then leading, then guardrails, then lagging.
Creating a goal
In-app today: create a tracker, then on the tracker's detail page set its goal context (name, target, role). The platform creates the goal record implicitly. A dedicated "Create goal" flow is on the roadmap.
Linking decisions to a goal
When you log a decision, you can attach it to a goal. The decision then appears on the goal's page in the decision-history list.
Why goals matter
- Coherence. A team chasing five separate trackers and twenty separate decisions has no narrative. A team chasing one goal with five trackers and twenty decisions tells a story.
- Focus for stakeholders. A stakeholder asking "how's it going?" doesn't want twenty tracker dashboards. They want the goal page.
- Better quarterly reviews. A QBR built from one goal + its trackers + its decisions writes itself.
Tips
- One goal per quarter per team. More than that is unfocused.
- Always set a guardrail. A goal with no guardrail is a goal that breaks something else to make its number look good.
- Pick a primary + at most one leading + one guardrail. Three signals beat ten.