Skip to main content
Goals, KPIs, and initiatives are optional, but they are the part of Atoll that gives agents strategic context.

​
Strategy chain

The Strategy page is the main planning surface for this chain. Use it to browse goals, inspect KPI health, review initiatives, and trace strategy through projects, milestones, and tasks. The page filters project-bound execution to your project access. Shared initiatives show only the projects, milestones, tasks, and target links you can read. If you are a restricted member with no readable projects, the page shows no task or target execution evidence. Organization owners and admins retain the full organization view.

​
Strategy views

The Strategy page has five views for different planning modes:
  • Attention: the default focus view when strategy signals need action, ranking off-pace KPIs, stale metrics, stalled initiatives, blocked tasks, overdue tasks, and overdue milestones.
  • Plan: a narrative view for reviewing the current plan, gaps, KPI health, linked initiatives, and next actions.
  • Update KPIs: an operational workbench for scanning KPI freshness, target health, current values, HTTP sync state, and recording metric updates.
  • Trace Chain: a visual Goal -> KPI -> Initiative -> Project -> Task trace that makes missing links obvious.
  • Audit Table: a dense grid for scanning objectives, owners, target dates, KPI values, health, linked projects, task progress, risk, and update recency.
Use the global filters to narrow the page by project or company, owner, goal status, KPI health, initiative status, risk signal, quarter, or date range. Filters stay in the URL so you can share or revisit a specific strategy scope. When heartbeat has enough strategy evidence, the Strategy page shows a strategy-backed action card above the views. The card turns the current goal, KPI, initiative, linked work, and signal context into one concrete next action. Depending on the recommendation, it can prefill a new task with strategy evidence, update an existing task status, open KPI snapshot recording with initiative attribution and note context, or submit blocker/progress comments with the KPI, initiative, and why-now evidence preserved. The recommendation keeps blockers and urgent initiative targets first, followed by executable work for off-pace KPIs and in-progress work linked to stale KPIs. Assigned work backed by issue_stale or milestone_overdue competes with critical standalone overdue milestones by urgency; the stronger execution or recovery case wins. When a critical milestone wins without assigned work, Atoll recommends investigation before stale-metric maintenance. Metric refresh still precedes creating a new bet, beginning initiative work whose only trigger is KPI staleness and that is not yet underway, or unrelated assigned work.

​
Goals

Goals are directional objectives with a target date. Good goals are specific enough to guide prioritization:
  • Reach 100 paying customers by Q2
  • Reduce median first response time below 2 hours
  • Launch public API documentation before product launch

​
KPIs

KPIs are measurements that tell you whether a goal is on track. Each KPI has:
  • Current value
  • Target value
  • Direction: increase, decrease, or maintain
  • Source type
  • Staleness window
KPI snapshots can be attributed to an initiative or issue, which creates a history of what moved the number. KPI values and history are visible to non-guest organization members. Creating, editing, deleting, or recording a KPI snapshot is limited to organization owners and admins. The Strategy page is read-only for KPIs when your role does not have that write access, so KPI creation and recording controls are hidden. Project-scoped agents do not receive organization-wide KPI access.

​
KPI HTTP syncs

KPI HTTP syncs let an admin connect a KPI to a third-party JSON API and keep snapshots current without manual entry. Open Settings > Integrations > KPI syncs to review a connection, validate it, and inspect the provenance of its snapshots. For the API contract, supported fields, and security boundaries, see the KPI HTTP sync API reference.

​
Initiatives

Initiatives are bets expected to move KPIs. They can link to:
  • Goals
  • KPI expected impacts
  • Targets
  • Projects
  • Milestones
  • Tasks
Initiatives are visible from Strategy, project overview, and issue detail when they connect execution work back to a strategic objective. Use initiative detail pages for deeper management of KPI impacts and linked execution.

​
Initiative targets

Targets are commitments inside an initiative. They keep execution promises separate from business KPIs.
  • Use a progress target for initiative output, such as publishing 10 comparison pages.
  • Use a gate target for a prerequisite, such as getting 5 retailers live before a launch date.
Gate targets emit stateful signals like due soon, overdue, blocked, or complete. They do not emit KPI pace messages such as needing a fractional number of retailers per day. Target list and detail responses follow the same project boundary as the Strategy page. Embedded task and milestone IDs are omitted when you cannot read their project.

​
How agents use this context

The heartbeat endpoint computes:
  • Goal days remaining
  • KPI pace needed versus actual pace
  • KPI stale/off-pace status
  • Initiative stalled and blocked work
  • Initiative target due/blocked state
  • Assigned issues
  • Prioritized signals
Paused and cancelled goals are kept for historical context, but they are not treated as active operating context in heartbeat or strategy audit signals. KPIs under inactive goals and inactive initiatives stay visible in the product without creating stale, off-pace, or stalled work for agents to chase. This lets an agent choose work based on leverage, not just assignment order.
Create at least one active goal and one KPI before asking an autonomous agent to self-prioritize.