progress

When to use

• Parallel workstreams at a glance. When the audience needs to scan five to eight workstreams and immediately spot the ones in trouble. The bar length carries the magnitude; the status pill carries the verdict.
• Percent-complete is the natural unit. Readiness, OKR progress, capacity utilization, rollout coverage. Any series where each row is a 0–100% completion against its own scale fits the layout. Mixed units belong in kpi.
• Status framing matters as much as the number. Use the on-track, at-risk, blocked, deferred, done vocabulary — the engine tints the bar fill to match. A 68% bar reads very differently when it is at-risk than when it is on-track.

When not to use

• Comparing unrelated metrics. Revenue % of target, latency vs SLO, and headcount fill aren't comparable on a shared bar scale. Use kpi for value/target/status tiles or stats for an independent metric row.
• More than eight rows. Past eight workstreams the bars compress and the labels truncate. Split the view by owner or workstream group; the audience can't scan twelve bars at once anyway.
• Decorative status pills. Don't invent new status words for tone. on-track, at-risk, blocked, deferred, done are the vocabulary the engine recognises; everything else renders as a plain pill and breaks the at-a-glance read.

Common mistakes

• Writing the fill value without the % sign, assuming the bar won't fill correctly. The % sign is cosmetic for the bar fill itself — a bare number and a %-suffixed one drive the same fill. It DOES matter for the displayed chip text, though: omit it and the chip shows a bare number with no percent sign, which reads wrong even though the bar fills correctly. Always include % for a clean label.
• Writing the status pill before the percent chip. Trailing chips are read percent first, status second (` 68% then at-risk `) — reversing the order is a genuine break, not graceful tolerance: the bar renders at 0% fill and the percent/status text swap positions in the row.

Authoring

<!-- _class: progress -->

`Eyebrow · context`

## Progress by item.

- First item `80%` `on-track`
- Second item `55%` `at-risk`
- Third item `30%` `blocked`

Slots

Anatomy

┌─────────────────────────────────────────┐
│  header                                 │
│  Progress heading.                      │
│                                         │
│  Goal A   ▓▓▓▓▓▓▓▓▓▓▓▓▓▓70%░░░░░░       │
│  Goal B   ▓▓▓▓▓▓▓▓▓▓50%░░░░░░░░░░       │
│  Goal C   ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓90%░        │
│                                         │
│  footer                           1/19  │
└─────────────────────────────────────────┘

Related

• kpivalue + target + status tiles, not a single percent
• statsindependent headline metrics, no completion scale
• ganttthe rows are time-bound and need a date axis
• checklistbinary done / not-done across a flat list
• timeline-listthe workstreams complete in sequence, not in parallel