Can Roadmap Reports Show Progress by Team? KPIs and Sample
9 min read ยท 2026-10-31
Can roadmap reports show progress by team? Yes, they can. Every roadmap item needs one owning team, a status and a progress measure that all teams calculate the same way. Once those three fields exist, any tool can produce the report: a spreadsheet, Jira, Notion or a visual roadmap. You can show one line per team, a page per team, or a map of who waits on whom.
Progress by team is only part of the picture. It tells you whether teams deliver what they committed to. Good roadmap KPIs cover three layers. Delivery KPIs show whether the work ships. Outcome KPIs show whether it changed user or business behavior. Health KPIs show whether the roadmap itself is stable and trusted. This guide gives you a setup plan, rules for calculating progress, a way to handle work that several teams share, and a sample team report you can reuse.
The roadmap at a glance
Goal: Build a roadmap report that shows progress by team, backed by outcome, delivery and health KPIs, for next quarter. Duration: 2 weeks of setup, then a 3 month reporting cycle
Assign Owners and Fields (Days 1 to 3)
Make every roadmap item traceable to one team.
- Give each roadmap item exactly one owning team, even when several teams contribute.
- Add six fields to every item: team, status, percent complete, target date, risk level and blocker.
- Agree on three status values only: on track, at risk, blocked.
- List every dependency between teams next to the item that waits on it.
Milestone: Every item on the roadmap has an owning team and all six fields filled in.
Agree on How Progress Is Calculated (Days 4 to 5)
Make sure 50 percent in one team means the same as 50 percent in another.
- Choose one calculation method for the whole roadmap: items done, effort done or milestones reached.
- Write down what "done" means, for example released to users rather than code merged.
- Decide who updates the progress field and on which day of the week.
- Test the method on two past initiatives to see whether it matches what really happened.
Milestone: A written progress rule, signed off by every team lead.
Attach Outcome KPIs (Days 6 to 8)
Connect each theme to the result it should produce.
- Write the user or business behavior each roadmap theme should change.
- Choose one primary metric per theme, such as activation, retention or conversion.
- Add one guardrail metric per theme to catch side effects, such as error rate or support load.
- Record today's baseline for every metric.
Milestone: Every theme has a primary metric, a guardrail and a recorded baseline.
Build the Team Report (Days 9 to 10)
Put team progress and KPIs on one page.
- Create a summary with one line per team: initiatives, status, percent complete, risk and next step.
- Draw the dependencies between teams so the steering group sees who waits on whom.
- Note release dates next to each outcome metric so changes can be linked to launches.
- Fill the report with one real week of data and fix any field that is empty or unclear.
Milestone: A working report that any stakeholder can read in a few minutes.
Review Every Two Weeks (Months 1 to 3)
Use the report to make decisions, not just to inform.
- Review team progress, risks and blockers in a roadmap sync every two weeks.
- Review outcome KPIs monthly, once releases have had time to produce data.
- For each theme, decide to continue, iterate or stop, and record why.
- Escalate any blocker that has stayed on the report for two reviews in a row.
Milestone: Every review ends with recorded decisions and named owners for each blocker.
Score the Quarter (Final week)
Judge the quarter across all three KPI layers and improve the system.
- Compare each outcome metric with its baseline and target.
- Summarize delivery per team and name the biggest cause of slips.
- Count mid quarter roadmap changes and carryover items as health signals.
- Drop any metric that did not inform a single decision.
Milestone: A quarter scorecard per team and per theme, with changes for next quarter.
Three Report Formats for Showing Progress by Team
The right format depends on who reads it. The data stays the same in all three: owning team, status and percent complete on every item. If you need help laying out the team structure of the roadmap itself, the team roadmap guide covers it. This section is about reporting on that roadmap.
Write the status as a word (on track, at risk, blocked), even if you also use a color. Words survive printing, screenshots and color blind readers.
- One line per team: initiatives, status, percent complete, risk and next step. In a spreadsheet, that is one row per team on a summary tab. In Jira or Notion, it is a short table you update by hand from the team field. Best for steering committees and monthly updates.
- One page per team: the items one team owns, with their status, target date and blocker. You can build it with a saved filter in your ticket tool, a separate tab in a spreadsheet or a section of a shared document. Best for team reviews and sprint planning.
- Dependency map: boxes for each team's key items, and arrows showing which team waits on which. Best for spotting the one late item that holds back three teams.
How to Calculate Percent Complete per Team
There are three common methods. Each one can mislead you in a different way. Pick one, write it down and use it everywhere.
Whatever the method, show status next to the number. A team at 80 percent with a blocker is in more trouble than a team at 40 percent that is on track.
- Items done: completed items divided by total items. It is quick to update, but a two day task counts as much as a two month epic.
- Effort done: completed estimate (points or days) divided by total estimate. It is closer to real work, but only reliable if teams estimate the same way.
- Milestones reached: reached milestones divided by planned milestones. It is the easiest for executives to read, but it moves in steps and can look stuck between milestones.
When Several Teams Work on the Same Initiative
Shared work is where team reports usually break. If three teams each claim the same initiative, it gets counted three times. If nobody owns it, it disappears from every team's report.
There are two clean options. The first is a single owner: one team owns the initiative and reports its overall progress, and the other teams appear as dependencies with their own dates. The second is a split: break the initiative into parts, give each part to one team, and roll the parts up into the parent item. Use the split when the parts are large enough to track on their own. Either way, list each dependency with the team that waits, the team that delivers and the date it is needed.
Step 1 of the KPI Set: Delivery KPIs
Delivery KPIs show whether teams ship what they committed to. Keep to three, with definitions written once and shared by all teams.
Never turn milestone hit rate into a target for a team. Teams judged on it start committing to less. Treat it as a signal of planning accuracy, and pair it with an outcome metric so speed and impact are judged together.
- Milestone hit rate: milestones delivered on time against milestones committed.
- Cycle time: time from work started to released, for roadmap epics.
- Unplanned work share: the part of team capacity lost to work that was not on the roadmap.
Step 2 of the KPI Set: Outcome and Health KPIs
Delivery says nothing about whether the work mattered. Outcome KPIs answer that: feature adoption, activation, retention, conversion, or support tickets for a problem area. They lag behind releases, so read them monthly and use leading signals, such as first use of a feature, for an earlier read.
Health KPIs show whether the roadmap process holds up. Track how often the roadmap changes mid quarter and why, how many items carry over to the next quarter, and how useful stakeholders find the roadmap in a short pulse survey. If teams deliver but outcomes do not move, read health and outcome data together. They usually tell you why.
A Sample Team Progress Report You Can Copy
The figures below are made up to show the format. Replace them with your own data.
The report fits on one screen, states a dependency in plain words and ends with a decision leadership must take. That last point is what makes it useful in a steering meeting.
- Platform team: 2 initiatives, on track, 60 percent of milestones reached, low risk, next step: release the new import tool.
- Growth team: 1 initiative, at risk, 35 percent of milestones reached, medium risk, next step: finish onboarding tests, waiting on Platform for the import tool.
- Mobile team: 2 initiatives, blocked, 20 percent of milestones reached, high risk, next step: decision needed on the offline mode scope.
- Outcome line: import tool usage among new users, baseline recorded, first reading due one month after release.
Building This Report on a Visual Roadmap
If your steering committee reads pictures faster than tables, you can draw the same report on a visual canvas with four basic elements.
Then share the roadmap with your team, or export it as an image for the steering committee deck. The numbers still follow your written progress rule. The canvas only makes them easier to read.
- One Goal node per team: Platform, Growth, Mobile. Write the team's status and percent complete in its description, and update it on your weekly update day.
- Milestone elements under each Goal: one per planned milestone, so anyone can count reached against planned.
- Decision nodes for open questions: in the sample, "Offline mode scope" sits under Mobile as a Decision, so the blocker is visible, not buried in a note.
- Links for dependencies: connect the Growth onboarding tests to the Platform import tool. The arrow shows the dependency without a word of explanation.
Adapting the Report for Leadership, Teams and Stakeholders
The same data serves different audiences. Leadership wants strategic goals, status per team, risks and the decisions they need to make. Delivery teams want releases, capacity, dependencies and blockers. Marketing wants scope, dates and milestones it can plan launches around. Sales and support want to know what is coming for customers and when.
Send leadership the one line per team summary. Give teams their own page. If your ticket tool cannot group work by team, keep the six fields in a shared spreadsheet or a visual roadmap and update them on a fixed day each week.
Common mistakes to avoid
- A percentage without a status hides risk. Always show on track, at risk or blocked next to the number.
- If each team calculates progress its own way, you cannot compare teams. Write one rule and apply it everywhere.
- Counting a shared initiative in every contributing team inflates progress. Give each item one owner or split it into parts.
- Showing leadership every item buries the message. Give them one line per team and the decisions needed.
- Measuring only features shipped rewards output over impact. Pair every delivery KPI with an outcome KPI.
- Judging outcomes the day after release leads to false conclusions. Wait for enough data or use leading signals.
Frequently asked questions
How do I measure roadmap delivery performance?
Track milestone hit rate, cycle time and unplanned work share, with one written definition for all teams. The delivery KPIs section above explains each one and why it should never become a team target.
How do I track roadmap performance metrics?
Track delivery, outcome and health KPIs on one page, grouped by roadmap theme. The two KPI sections above list what to measure in each layer and how often to read it.
What is a KPI roadmap?
A KPI roadmap links each roadmap theme to a measurable result, with a baseline and a target. It shows which metric each piece of work should move, not just which features ship.
How do I report progress when several teams share one initiative?
Give it one owning team and list the others as dependencies, or split it into parts owned by one team each and roll them up. For every dependency, name the team that waits, the team that delivers and the date.
How often should I report roadmap progress to leadership?
Most leadership groups do well with a monthly summary, one line per team, plus an alert as soon as an item becomes blocked. Delivery teams usually need a shorter rhythm, such as a review every two weeks.