Initiative targets: when KPI pacing is the wrong tool

Atoll separates business KPIs from the commitments inside an initiative. A KPI measures an outcome such as recurring revenue or paying customers. An initiative target records the work that must happen before that outcome can move.

This distinction gives teams a better signal. A business KPI supports pacing and trend analysis. A launch commitment needs a clear answer to a different question: is the prerequisite complete, and can the team proceed?

Keep outcome metrics in KPIs

Imagine a goal called Reach $10,000 MRR. A KPI such as mrr_usd can use a target of 10,000 and a direction of increase. Its pace answers a continuous question: is revenue moving toward the goal at the required rate?

An initiative under that goal might require five retailers to go live before a price-comparison launch. If the team stores that prerequisite as a KPI under the revenue goal, the long goal date can produce a fractional rate such as 0.07 retailers per day. The rate describes arithmetic. It does not describe launch readiness.

A team needs a stateful signal for the prerequisite. It needs to know that the launch remains blocked while the count is zero and the date is close.

Targets belong to initiatives

An initiative target links an initiative commitment to execution. It has a title, mode, unit, current value, target value, direction, and optional target date. Teams can link issues and milestones to it.

• Progress targets measure an initiative output, such as publishing 10 comparison posts or completing six interviews.
• Gate targets record a prerequisite for a launch, such as getting five retailers live or completing an approval.

The mode changes the decision the signal should support. A progress target reports output. A gate target reports whether the team can move through a launch condition.

Target state in heartbeat

The full heartbeat context includes initiative targets and their linked work. The default REST and private CLI heartbeat uses a compact response with grouped actionable signals and a recommended action. A gate target can produce stateful messages such as:

Gate target "Get 5 retailers live" is due in 6 days: 0/5 retailers complete

Current target signals include initiative_target_due_soon, initiative_target_overdue, and initiative_target_blocked. Due-soon signals apply to incomplete gate targets. Overdue and blocked signals include the target mode and progress details.

Treat the message as an operational cue. Inspect the linked issues and milestones, start the next approved piece of work, or escalate the blocker. Do not convert a gate into fractional KPI pace.

Why the distinction helps agents

An agent can reason from the relationship between a goal, KPI, initiative, target, and issue. The goal still describes the business outcome. The KPI still measures that outcome. The target tells the agent which prerequisite matters inside the initiative, and linked work shows how the team can satisfy it.

1. The goal is Reach $10K MRR.
2. The KPI is mrr_usd.
3. The initiative is Launch retailer price comparison.
4. The gate target is Get 5 retailers live.
5. Linked issues and milestones describe the onboarding work.

When the gate is due soon and an issue is blocked, the agent has a reason to investigate that blocker before it spends time on unrelated KPI maintenance. When the target has no execution links, the team can define the missing work instead of inferring it from a metric.

Illustrative target model

This example uses the fields documented for initiative targets. The names and values are illustrative.

Goal:
  Reach $10,000 MRR

KPI:
  mrr_usd
  target: 10000

Initiative:
  Launch retailer price comparison

Gate target:
  Get 5 retailers live by July 5
  current: 0
  target: 5
  unit_label: retailers
  target_date: 2026-07-05
  linked work:
    - Confirm data access for Retailer A
    - Finish Retailer B parser
    - QA product matching for Retailer C

The model keeps MRR as the outcome metric. Retailers live remains a commitment under the initiative, where its due date and linked work can guide the next action.

Scope of the target model

Targets store current and target values and link execution records. KPI snapshots keep their own measurement history and attribution. A target does not create a KPI snapshot or prove that completing the target caused a business result.

That separation gives each record a clear job. Goals describe outcomes, KPIs measure them, initiatives describe the bet, targets define the commitments, and teams use issues and milestones to execute the work.