Category: Metrics & Progress

Understand how theme progress rolls up into objectives.

How rollup works

Progress rolls up in this order:

1. Issues — Individual issues are linked to themes
2. Themes — Metrics on themes aggregate linked issue data
3. Objectives — Metrics on objectives aggregate data from all linked issues (across all themes)

Rollup example

Your objective: “Launch marketplace” with 3 themes:

• Theme A: “Seller onboarding” (5 issues)
• Theme B: “Buyer experience” (4 issues)
• Theme C: “Payments integration” (3 issues)

If you add an “Issue completion” metric on the objective:

• The metric counts all 12 linked issues (across all themes)
• Progress shows: “6/12 issues done = 50%”

Theme-level progress

Click a theme to see:

• Linked issues for that theme only
• Metrics specific to that theme
• Progress toward theme goals

Objective-level progress

Click an objective to see:

• All linked issues (from all themes)
• Objective metrics — aggregated from all issues
• Theme metrics — shown per theme

View progress over time

Metrics track a Target date (quarter and year). As time passes, you can look back to see:

• Historical progress
• Which metrics were met
• Which fell short

Rollup for different metric types

Type	Rollup	Example
Issue count	Sum	5 + 4 + 3 = 12 issues
Issue estimation	Sum	13 + 8 + 5 points = 26
Issue completion	Weighted average	Weighted by issue count
Manual	Independent	Each metric tracked separately

Metrics live at two levels: objectives and themes.

Objective metrics

Objective metrics measure progress across all linked work, regardless of theme.

Use objective metrics for

• Overall goal progress
• Cross-theme health
• Company-wide KPIs

Example

Objective: “Improve customer retention” Metric: “Churn reduction” (manual)

• Target: Reduce churn from 5% to 3%
• Updated monthly by the finance team

This metric doesn’t care which theme’s work reduces churn—it’s one company-wide goal.

Theme metrics

Theme metrics measure progress within a specific theme.

Use theme metrics for

• Theme-specific goals
• Work stream milestones
• Discipline-specific initiatives

Example

Objective: “Improve customer retention” Theme: “In-app engagement redesign” Metric: “Issue completion: 8/12 issues done”

• This metric counts only issues linked to this theme
• Other themes’ issues don’t affect it

Combining both

An objective can have:

• Objective-level metric: “Overall churn: -2% (target -2%)”
• Theme A metric: “In-app engagement: 8/12 issues (67%)”
• Theme B metric: “Email campaigns: 5/5 issues (100%)”
• Theme C metric: “Support improvements: 3/6 issues (50%)”

A viewer sees both the objective-wide goal and the breakdown by theme.

Theme metrics don’t aggregate to objective metrics

Theme metrics are independent. An objective metric doesn’t calculate theme metrics—they are separate.

If you want an objective metric that summarizes themes, use an auto-calculated metric like “Issue completion” that counts all linked issues.

Discipline leaders can define metrics on discipline-scoped themes.

What is a discipline-scoped metric?

A discipline-scoped metric is a metric on a theme that is visible only to members of that discipline (and admins).

Create a discipline-scoped metric

1. Go to Planning
2. Click a Discipline-scoped theme
3. Click the Metrics tab
4. Click + Add Metric
5. Define your metric (name, type, target, quarter, year)
6. Click Create

The metric is now visible only to discipline members and admins.

Who can see discipline metrics?

• Discipline members — See metrics for their discipline(s)
• Discipline leaders — See and edit metrics for their discipline(s)
• Project admins / company admins — See all metrics

Metrics on company-wide themes

If a theme has no discipline assigned, its metrics are company-wide and visible to everyone.

If a theme is discipline-scoped, its metrics are visible only to that discipline.

Update discipline-scoped metrics

1. Click the theme
2. Click the Metrics tab
3. For manual metrics, enter the Current Value
4. Click Save

Auto-calculated metrics update automatically from linked issues.

Report on discipline metrics

Discipline leaders can review their metrics in the Planning page:

Share with their discipline team

Filter themes by their discipline

See metric progress

Metrics quantify progress toward objectives and themes.

Add a metric to an objective

1. Go to Planning
2. Click an Objective
3. Click the Metrics tab
4. Click + Add Metric
5. Enter:
   • Name — What you’re measuring (e.g., “User engagement”)
   • Metric type — How you measure it (see below)
   • Target value — Your goal
   • Unit (optional) — e.g., “percentage”, “count”
   • Quarter and Year — When you want to achieve this
6. Click Create

The metric now appears on the objective card.

Add a metric to a theme

1. Click a Theme
2. Click the Metrics tab
3. Click + Add Metric
4. Fill in the same details
5. Click Create

Metric types

Type	What it measures	Example
Issue count	How many issues are linked	“10 issues”
Issue estimation	Total story points of linked issues	“55 points”
Issue completion	% of linked issues marked done	“60% complete”
Custom field	Aggregate of a custom field value	“Revenue target: $500k”
Manual	Manually tracked progress	“User engagement: 8.5/10”

Edit a metric

1. Click the objective or theme
2. In the Metrics tab, click the metric
3. Edit any field
4. Click Save

Update manual metrics

Manual metrics are updated by hand:

1. Click the metric
2. Enter a Current Value
3. Click Save

Manual metrics are useful for KPIs like NPS scores, customer satisfaction, or adoption rates.

Delete a metric

Confirm

Click the objective or theme

In the Metrics tab, find the metric

Click Delete or Remove

Metrics can be auto-calculated from your work, or updated manually.

Auto-calculated metrics

These metrics update automatically based on linked issues:

• Issue count — Recounts linked issues every time you view it
• Issue estimation — Sums story points of linked issues
• Issue completion — Recalculates % of issues marked done
• Custom field — Aggregates custom field values from linked issues

No manual update needed. As you close issues and update fields, these metrics refresh automatically.

When auto-calculated metrics update

Auto-calculated metrics update:

• When you link or unlink an issue
• When you change an issue’s status (marks it done/not done)
• When you change an issue’s estimate
• When you modify relevant custom field values

Example: Issue completion metric

1. You create an “Onboarding redesign” objective with 10 linked issues
2. You set a metric: Issue completion, target 100%
3. As your team marks issues done, the % updates automatically
4. When 10/10 are done, the metric shows 100%

Manual metrics

Manual metrics are tracked outside of issues. You update them by hand.

When to use manual metrics

Use manual metrics for:

• NPS scores — Customer satisfaction surveys
• Market share — Competitive positioning
• Revenue — Financial targets
• Adoption rate — Feature or product usage
• Team velocity — Story points per sprint

Example: NPS metric

1. You create a “Customer satisfaction” objective
2. You add a metric: Manual NPS, target 75
3. Each quarter, you survey customers and update the current value
4. The metric shows progress toward 75

Mix auto-calculated and manual

You can use both on the same objective:

• Auto-calculated: “Issue completion: 60/100 issues done”
• Manual: “NPS score: 72 (target 75)”

Metric rollup

When calculating objective progress:

• Objective metrics roll up from all linked issues
• Theme metrics are specific to that theme’s issues

See Progress tracking and rollup.