Progress

The Progress tab answers a question that is hard to answer from memory: what changed on this roadmap, and when.

What it does

Progress keeps an automatic change log. As you edit the roadmap — statuses, priorities, owners, target periods, blockers, added and removed items — Roadmap Flow records each meaningful change. You never start a tracker; it is always on.

You read the log through five time windows: Session, Today, This week, This month, and All. A label below the selector shows the active window and the total number of changes, so you always know what the tiles and log are summarising.

Summary tiles count the signals that matter — items added, completed, blocked, delayed, priority changes, owner changes, decisions added, and total changes. Clicking a non-zero tile jumps to those items on the canvas. The change log groups by day and each day can be collapsed.

Section order

When to use it

• Before a stakeholder meeting, to prepare an honest "here is what moved".
• In a weekly update, to summarise the week without trusting memory.
• To save a milestone snapshot before a review starts.
• To export a progress report.

When not to use it

• When you need to compare the roadmap against a specific past commitment — that is a milestone, not the rolling log.
• For per-person attribution on a single-user workspace. The log records what changed; the "By [name]" label only appears when a Display name has been set in Account → Display name.

Reading change log rows

Each row shows:

• A bold item title and what changed (before → after).
• A category label (Blocker, Completed, Delayed, Priority, Owner, etc.) and the relative time the change happened. Hover the time to see the full date and clock.
• A left-edge stripe indicating severity: red = critical, amber = major, blue = minor, gray = observation. Severity is calculated automatically.
• Clicking a row (for item changes) opens the item detail view.

Summary tile drill-down

Each summary tile with a non-zero count has a chevron icon and is clickable. Clicking switches to Canvas, highlights the changed items with a blue ring, and auto-scrolls to the first one. A banner above the filter bar shows the count and a Clear button.

Who changed what (Team)

There is one change log. On the Team plan each entry also shows who made the change, and Show changes for narrows the whole log to a single item.

There used to be a second section called Team attribution listing the same edits again in different words. It is gone; attribution is now a column on the one log rather than a feed of its own.

A person appears by name when they had a Display name set at the time of the change. Changes made before that appear unnamed and cannot be renamed retroactively — ask people to set one in Account → Identity → Display name.

Before a review

Two roll-ups that answer questions you would otherwise have to open items one at a time to answer:

• Open feedback (Team) — every item with unresolved review comments, busiest first. Export sends the whole roadmap's open feedback to Markdown.
• Handover readiness — every item at the tech-readiness gate, marked Ready or with the number of gaps still to fill.

Both link straight to the item.

3-minute flow

1. Open the Progress tab.
2. Pick a time window — This week is the usual choice for an update.
3. Check the summary tiles for the shape of change.
4. Expand a day in the change log to read the detail.
5. If you are about to run a review meeting, scroll to Milestones and save a snapshot now so you can compare before and after.
6. Export the window to Markdown, PDF, or PowerPoint for your audience — or export the raw change log itself as Markdown or CSV.
7. Before the meeting, check Before a review for open feedback and anything at the handover gate that is not ready yet.

Best use cases

• "What changed this week" updates.
• Reviewing roadmap movement before a meeting.
• A written progress report drawn from real history.
• Saving and comparing milestones around a review cycle.

Common mistakes

• Forgetting to check the window label. A quiet log often just means the window is too short — switch to This week or All.
• Saving a milestone after the meeting instead of before — the comparison loses the pre-meeting baseline.

Related guide pages

• Milestones
• Saved views
• Executive update
• Change history (Team)

Availability

Free. The change log and Markdown export are free; PDF and PowerPoint progress reports and attributed change history are Pro / Team.