Definition, roadmap vs. project plan and Gantt chart, a filled swimlane example, six steps, four roadmap types, team examples, and a free template.

What changed (Nov 14, 2026): Rewrote the guide around one filled help center relaunch roadmap with dependency, risk, and change logs; added comparisons with project plans, Gantt charts, product roadmaps, and charters, four roadmap types, team examples, common mistakes, executive tips, and Markdown and CSV templates; replaced decorative images with original diagrams; removed unverified tool claims, the PMBOK section, and duplicated promotional paragraphs.
A project roadmap is a one-page visual summary of a project: the goal, the main workstreams, the milestones, and roughly when each will happen. It shows stakeholders where the project is going and why. It leaves out the task-level detail that belongs in the project plan. A good roadmap can be read in two minutes and answers four questions: what are we trying to achieve, what are the big pieces of work, when will the key milestones land, and what could get in the way?
Key takeaways
Disclosure: AFFiNE publishes this guide and makes a workspace for docs, whiteboards, and databases. The template and example below work in any doc or spreadsheet tool. The section on tools explains where AFFiNE fits and where a dedicated project tool is the better choice.
Atlassian describes a project roadmap as "a visual and strategic tool that clearly outlines a project's key components, milestones, and timelines and gives a high-level overview of the project's goals, deliverables, and progress indicators." ProductPlan adds that it should explain the strategic reasoning for the project, the "why" behind it.
In practice, a project roadmap is the page you show a sponsor, an executive, or a partner team when they ask "what is this project, and when will it be done?" It usually covers:
A roadmap is created early, ideally before the detailed plan. ProductPlan recommends developing it before the project plan and using it at the kickoff meeting. It stays useful only if someone keeps it current.
Not every project needs one. A two-week task for one team is fine with a to-do list. A roadmap pays off when:
If none of these apply, skip the roadmap and go straight to a task list or a simple project timeline.
These five documents get mixed up because they all describe the same project. The difference is the level of detail and the audience.
| Project roadmap | Project plan | Gantt chart | Product roadmap | Project charter | |
|---|---|---|---|---|---|
| Question it answers | What and when, at a high level, and why | How, by whom, and with what budget | Which task happens on which day | What the product should do next, and why | Should we do this project at all? |
| Level of detail | Workstreams and milestones | Tasks, resources, budget, risks | Tasks, durations, dependencies | Outcomes, themes, initiatives | Purpose, scope, sponsor, constraints |
| Time scale | Months or quarters | Weeks and days | Days | Now / Next / Later or quarters | Start and target end |
| Main audience | Sponsors, executives, other teams | Project team | Project team, PMO | Product team, company | Sponsor, approvers |
| Lifespan | The whole project, updated monthly | The whole project, updated weekly | Updated as tasks move | Ongoing, no end date | Approved once at the start |
A few rules of thumb:
A useful project roadmap has seven parts. Most fit on one screen.
Resources and budget usually stay in the project plan. If the sponsor needs to see them on the roadmap, add one line per workstream with headcount or budget, not a full breakdown.
The content stays the same; the layout changes with the audience. Pick the one your readers can understand fastest.
| Type | What it looks like | Best for |
|---|---|---|
| Timeline roadmap | Milestones and phases on a single time axis | Simple projects, executive updates |
| Swimlane roadmap | One row per team or workstream, bars across months | Cross-team projects with dependencies |
| Now / Next / Later roadmap | Three columns instead of dates | Agile projects where dates are uncertain |
| Portfolio roadmap | Several projects stacked on one timeline | PMOs and leaders comparing projects |
The swimlane layout is the most common for projects with more than one team, because it shows at a glance who is busy when and where handoffs happen. The example below uses it.
Here is a complete roadmap for a fictional project: relaunching a company's customer help center. The numbers are illustrative.
| Workstream | Initiative | Window | Milestone | Owner | Depends on | Status |
|---|---|---|---|---|---|---|
| Content | Audit 600 articles | Jan to Feb | M1 Content audit approved | Content lead | None | Done |
| Content | Rewrite top 150 articles | Mar to May | Content lead | Legal review of billing articles | Green | |
| Content | Migrate content | Jun to Jul | Content lead | Platform setup and SSO | Green | |
| Design | Navigation and search research | Jan to Feb | Design lead | Content audit | Done | |
| Design | Page templates and style guide | Mar to Apr | M2 Templates and style guide signed off | Design lead | None | Done |
| Engineering | Platform setup and SSO | Mar to May | Engineering lead | SSO security review by IT | Amber | |
| Engineering | Search and analytics | Apr to Jun | Engineering lead | Search vendor contract | Green | |
| Engineering | Beta hardening | Jul | M3 Beta for 10% of visitors | Engineering lead | SSO security review by IT | Amber |
| Support ops | Agent training | Jul to Aug | M4 Public launch | Support ops lead | Beta feedback | Green |
| Support ops | Ticket deflection reporting | Aug to Sep | M5 Old help center retired | Support ops lead | Analytics live | Green |
Dependencies log
| Item | Depends on | Owner | Needed by | Status | Mitigation |
|---|---|---|---|---|---|
| Beta for 10% of visitors (M3) | SSO security review by IT | Engineering lead | End of Jun | Late, two weeks | Beta moved to mid-Jul; launch date held |
| Migrate content | Legal review of rewritten billing articles | Content lead | End of May | On track | Legal reviews in weekly batches of 30 |
| Search and analytics | Search vendor contract signed | Project manager | Mid-Apr | Done | None needed |
Top risks
| Risk | Level | Owner | Trigger | Response |
|---|---|---|---|---|
| SSO review slips again and delays the public launch | Amber | Engineering lead | Review not passed by Jul 1 | Launch without SSO for the public site; keep SSO for agent tools |
| Writers cannot finish 150 rewrites by May | Amber | Content lead | Fewer than 60 done by end of Mar | Cut to the top 100 articles by ticket volume |
| New search returns poor results for billing questions | Green | Design lead | Beta search success below 70% | Add synonyms and pin answers before launch |
Change log
| Version | Date | Change | Reason | Approved by |
|---|---|---|---|---|
| v1.0 | Jan 8 | First approved roadmap | Kickoff | Sponsor |
| v1.1 | Jun 3 | Beta moved from end of Jun to mid-Jul | SSO security review needs two more weeks | Sponsor and Engineering lead |
What this example shows:
The first version takes a few hours of preparation and one review meeting. After that, an update takes under an hour a month.
Write one sentence that says what the project will change and how you will measure it. Agree on it with the sponsor before you draw anything. If the sponsor and the team describe the goal differently, the roadmap will not fix that. Collect the inputs you will need: the approved charter or business case, known deadlines, budget limits, and the teams involved.
Group the work into three to six workstreams, usually one per team or major deliverable. Under each, list two to four initiatives in plain language, such as "migrate content" rather than "Phase 2b." Write down what is out of scope at the same time.
Pick four to eight milestones that a stakeholder would recognize as progress. Place each initiative in a time window of a month or a quarter. Estimate effort and resources with the team leads at this step, because a window without people behind it is a wish. Keep exact dates in the project plan unless they are fixed by a contract, a regulator, or an event. If you want the months on one page, a monthly Gantt chart template gives you 12 columns and phase rows to start from.
For each milestone, ask what you need from another team, a vendor, or an approver, and when. Give each dependency an owner and a "needed by" date. Then list the three to five risks that could move a milestone, each with a trigger and a planned response. A RAID log or a risk register can hold the full list; the roadmap shows only the top items.
Share the draft before the review meeting so people come with questions. Use the meeting to confirm the goal, the scope boundaries, the milestone windows, and the dependency owners. Record every decision, and leave with a named owner for each open question.
Publish the approved roadmap as v1.0 in a place everyone can find. Set a review cadence, usually monthly with the team and quarterly with the sponsor. Each time a milestone moves, raise the version number and add one line to the change log with the date, the change, the reason, and who approved it.
The structure above works for any project. These filled examples show how the workstreams and milestones change by team. Copy the one closest to your project, then use the full template or the blank CSV to fill in the rest.
| Workstream | Initiative | Window | Milestone | Owner |
|---|---|---|---|---|
| Data | Clean and map customer records | Q1 | Data mapping approved | Data lead |
| Platform | Configure new CRM and integrations | Q1 to Q2 | Integrations tested | IT lead |
| Migration | Trial migration, then full cutover | Q2 | Cutover weekend complete | IT lead |
| Adoption | Train sales and support teams | Q2 to Q3 | Old CRM switched off | Sales ops |
| Workstream | Initiative | Window | Milestone | Owner |
|---|---|---|---|---|
| Positioning | Messaging and pricing page | Month 1 | Messaging approved | Product marketing |
| Content | Launch blog post, video, and email series | Month 1 to 2 | Assets ready for review | Content lead |
| Channels | Paid ads and partner announcements | Month 2 | Launch day | Growth lead |
| Sales | Sales deck and training | Month 2 | Sales team certified | Sales enablement |
| Follow-up | Webinar and case study | Month 3 | Pipeline review | Product marketing |
| Workstream | Initiative | Window | Milestone | Owner |
|---|---|---|---|---|
| Venue | Shortlist, visit, and sign venue | Months 1 to 2 | Venue contract signed | Event lead |
| Program | Call for speakers and agenda | Months 2 to 4 | Agenda published | Program lead |
| Registration | Ticketing site and early-bird sales | Months 3 to 5 | Early-bird closes | Marketing |
| Operations | Catering, AV, and staffing | Months 4 to 6 | Run of show final | Operations lead |
| Workstream | Initiative | Window | Milestone | Owner |
|---|---|---|---|---|
| Design | Layout and approvals | Q1 | Permits approved | Architect |
| Procurement | Furniture, IT hardware, and long-lead items | Q1 to Q2 | Orders placed | Procurement |
| Build | Demolition, electrical, and finishes | Q2 to Q3 | Practical completion | Site manager |
| Move | IT setup and staff move | Q3 | First working day | Facilities |
A roadmap that is two months out of date does more harm than no roadmap, because people make decisions from it. Three habits keep it honest.
A fixed review cadence. Review the roadmap monthly with team leads to update status and dependencies, and quarterly with the sponsor to confirm the goal and milestone windows. Put the next review date in the header.
Version numbers. Use v1.0 for the first approved version. Raise the minor number (v1.1, v1.2) when a milestone window moves or a workstream changes. Raise the major number (v2.0) when the goal, the scope, or the end date changes. Keep old versions in an archive so you can see how the plan evolved.
Light change control. Anyone can propose a change, but a moved milestone needs the sponsor's approval. A short change request is enough:
| ID | Date | Requested by | Change | Impact on scope, time, cost | Decision | Approved by |
|---|---|---|---|---|---|---|
| CR-004 | Jun 3 | Engineering lead | Move beta two weeks later | Time: beta moves two weeks; launch unchanged | Approved | Sponsor |
Send a two-line summary to stakeholders after each approved change. Say what moved, why, and whether the end date is affected.
To check whether the roadmap is working, track a few simple measures: milestones hit within their window, the number of unplanned changes per quarter, and whether stakeholders actually open the roadmap before status meetings. If nobody reads it, simplify it.
Executives usually want three things: is the project on track, what decisions do you need from them, and what could go wrong. Structure the update that way.
Keep the full swimlane view in an appendix for questions.
You can build a good project roadmap in a spreadsheet. A dedicated tool helps when many people update it, or when you want the roadmap to stay in sync with tasks.
| Tool type | Examples | Good for | Watch out for |
|---|---|---|---|
| Spreadsheets and docs | Excel, Google Sheets, Word, Google Docs | Small projects, quick drafts, sharing with anyone | Manual updates; no link to tasks |
| Whiteboards | Miro, AFFiNE Edgeless, FigJam | Workshops and visual swimlane roadmaps | Hard to keep in sync with the plan |
| Work management tools with timeline views | Asana, monday.com, Wrike, Smartsheet | Teams that want the roadmap and tasks in one place | Seat costs; roadmap can drift into task detail |
| Jira and other agile tools | Jira (Atlassian offers a project roadmap template) | Software teams already tracking issues | Less friendly for non-technical stakeholders |
| Dedicated roadmap tools | Aha! Roadmaps, ProductPlan, Tempo Strategic Roadmaps (formerly Roadmunk) | Multiple roadmaps, portfolio and executive views | Built mainly for product roadmaps; extra cost |
| Project and portfolio tools | Microsoft Project, Smartsheet | Large projects with detailed schedules and resources | Steeper learning curve |
The examples are illustrations of each category, not ranked recommendations. For more template options across these tools, see our list of project planning templates and timeline templates.
AFFiNE combines docs, an Edgeless whiteboard, and databases in one workspace. For a project roadmap, that means you can keep the roadmap page, the swimlane drawing, and the dependency and risk tables side by side:
Where AFFiNE is not the right tool: it has no Gantt chart or automatic timeline view today (the docs list a Timeline view as planned), and it does not schedule tasks from dependencies or balance resources. If you need those, use a work management or project scheduling tool and keep AFFiNE for the roadmap narrative and workshops, or skip it.
The template has the seven parts described above: header, goal and success measure, scope, roadmap table, milestones, dependencies and risks, and change log. Download the version that suits your tool:
The roadmap table uses these columns:
| Workstream | Initiative | Window | Milestone | Owner | Depends on | Status |
|---|---|---|---|---|---|---|
| [Team or theme] | [Big piece of work] | [Month or quarter] | [Checkpoint, if any] | [One person or role] | [Team, vendor, or approval] | [Green / Amber / Red] |
A project roadmap is a one-page picture of a project that shows the goal, the main pieces of work, the key milestones, and roughly when each will happen. It gives stakeholders the big picture without the task-level detail of a project plan.
Include a header with the owner and version, a measurable goal, the scope, three to six workstreams with time windows, four to eight milestones with owners, the key dependencies and risks, a status for each workstream, and a change log.
A project roadmap is a high-level summary for stakeholders that shows what will happen and roughly when. A project plan is the detailed document for the team that lists tasks, owners, dates, resources, and budget. Create the roadmap first, then build the plan behind it.
No. A Gantt chart is a detailed schedule that shows every task as a bar with start and end dates and dependencies. A project roadmap shows workstreams and milestones by month or quarter. Many teams draw their roadmap as a simplified Gantt chart, but the two serve different readers.
Write the goal and success measure, break the scope into workstreams, set milestones and time windows, map dependencies and risks, review the draft with stakeholders, then publish it as version 1.0 and review it on a fixed schedule.
The common types are the timeline roadmap, the swimlane roadmap with one row per team, the Now / Next / Later roadmap for uncertain dates, and the portfolio roadmap that shows several projects together.
Update the status monthly with team leads and review the goal and milestones quarterly with the sponsor. Update it right away when a milestone moves, raise the version number, and record the change and the reason in the change log.
How this guide was prepared: Allen first published this guide in December 2025. In November 2026 we rewrote it around a single worked example, added the comparison with Gantt charts, product roadmaps, and charters, the roadmap types, team examples, common mistakes, and downloadable templates, and removed tool claims we could not verify. The help center example is fictional and its numbers are illustrative. AI tools assisted with research and drafting, and the AFFiNE team reviewed and edited the content.