Project Roadmap Template for PowerPoint: Layout, Build Steps, Example
9 min read ยท 2026-10-25
A good project roadmap template PowerPoint slide fits the whole project on one 16:9 slide: workstreams as horizontal swimlanes, months as columns, phases as colored bars, milestones as diamonds and a dashed line for today. A sponsor should understand where the project stands and what comes next in under a minute, without reading a task list.
This guide describes that layout precisely, then shows how to build it in PowerPoint step by step with tables, shapes and alignment tools. It includes a six-month project roadmap you can copy into the slide, a filled-in example for a customer portal launch, and how to present and update it for a steering committee or leadership review.
The roadmap at a glance
Goal: A six-month project moves from kickoff to launch and handover, with every phase, milestone and owner shown on one slide that the sponsor reviews every two weeks. Duration: 24 weeks (about 6 months)
Initiate (Weeks 1-2)
Agree on why the project exists, what is in scope and who decides.
- Write a one-page project charter with goal, scope, out of scope, budget owner and success measures.
- Name the sponsor, project manager and workstream leads.
- Hold the kickoff meeting and share the first draft of the roadmap slide.
Milestone: Charter signed by the sponsor and kickoff held with all workstream leads.
Plan (Weeks 3-5)
Turn the charter into a schedule, a RACI and a risk log.
- Break the work into workstreams and phases, and estimate each with the people who will do it.
- Build a RACI for key deliverables and decisions.
- Start a risk and dependency log with an owner for each item.
- Set the governance rhythm: weekly team meeting, steering committee every two weeks.
Milestone: Baseline schedule and roadmap slide approved at the first steering committee.
Design (Weeks 6-9)
Define what will be built or changed in enough detail to start.
- Run requirement workshops with business users and document decisions.
- Produce designs, process maps or specifications for each workstream.
- Review designs with stakeholders and log change requests.
Milestone: Design sign-off by the business owner.
Build (Weeks 10-17)
Deliver the solution in increments that can be shown and checked.
- Build in two-week cycles and demo progress to business users at the end of each one.
- Prepare data, integrations and environments in parallel.
- Draft training material and the communication plan.
- Update the roadmap slide every two weeks with status colors.
Milestone: Feature complete: all in-scope items built and demoed.
Test (Weeks 18-21)
Prove the solution works for real users and real data.
- Run system and integration tests and fix critical defects.
- Run user acceptance testing with business users against agreed scenarios.
- Write the go-live runbook and the rollback plan.
Milestone: UAT sign-off and go/no-go decision by the sponsor.
Launch and handover (Weeks 22-24)
Go live, support users and hand over to the team that will run it.
- Go live following the runbook and send launch communications.
- Run a hypercare period with daily issue reviews.
- Hand over support, documentation and open items to the operations owner.
- Hold a lessons-learned session and close the project.
Milestone: Go-live complete, handover signed by the operations owner and project closure report sent.
What goes on a project roadmap slide
The layout below works for most projects of three to twelve months. It reads left to right in time and top to bottom by workstream, which is how most stakeholders scan a slide. Keep it to five or six swimlanes. If you need more, the slide is turning into a Gantt chart and belongs in your scheduling tool.
Pick one color per phase or one color per status, never both on the same slide. Phase colors help when you present the plan for the first time. Status colors (green, amber, red) help in progress reviews. Many project managers use phase colors for bars and add a small status dot at the end of each swimlane.
- Title bar (top): project name, one-line goal and a version date such as Updated 14 March.
- Time header: one column per month, with a lighter row underneath for weeks or sprints if needed.
- Swimlane labels (left column, about one fifth of the width): one per workstream, such as Design, Build, Data, Testing, Change and training.
- Bars: rounded rectangles placed in each swimlane from start month to end month, labeled with the phase or deliverable.
- Milestones: small diamonds on a top milestone row or inside the swimlane, labeled with a short name and date.
- Today line: a thin dashed vertical line with a small Today label at the top.
- Legend and status (bottom): colors used, plus a status dot and owner initials per swimlane.
How to build it in PowerPoint, step by step
Building the grid with a table keeps your columns even, and placing shapes on top keeps the bars easy to move. Work on a blank slide so nothing from the theme gets in the way.
Once the slide is built, save it as a template slide in your project folder, or add the layout to your company's Slide Master (View, then Slide Master) so every project manager starts from the same structure. Export a PDF for people who read on their phones (File, then Export, then Create PDF/XPS).
- Set the slide to 16:9 under Design, then Slide Size, then Widescreen, and choose the Title Only layout from Home, then Layout.
- Insert a table with Insert, then Table: one column for labels plus one per month, and one row for the header plus one per swimlane.
- Widen the first column for labels, color the header row, and use light alternating fills on swimlane rows from the Table Design tab.
- On the View tab, tick Guides and Gridlines so you can line bars up with month edges.
- Draw each bar with Insert, then Shapes, then Rectangle: Rounded Corners, type its label inside, and set the fill to the phase color.
- Add milestones with the Diamond shape, and line up groups of shapes with Shape Format, then Align, then Align Middle or Distribute Horizontally.
- Draw the today line with a straight line set to a dashed style, and name objects in the Selection Pane (Home, then Arrange, then Selection Pane) so they are easy to find later.
- Keep a clean, empty copy of the finished slide at the end of the file, so each new version starts from the same grid.
Example: a filled-in roadmap for a customer portal launch
Picture a six-month project from January to June to launch a self-service portal where business customers can track orders and view invoices. The slide has five swimlanes and four milestones. The project manager owns the slide. Each workstream lead updates their lane before the steering committee.
On the progress version of this slide, the today line sits in mid-April. Build is amber because the invoice integration slipped by a week, and the slide notes the recovery plan in one line under the legend.
- Design (owner: UX lead): discovery and prototypes January to mid-February. Milestone: design sign-off, end of February.
- Build (owner: development lead): portal features in two-week sprints, March to April. Milestone: feature complete, end of April.
- Data and integration (owner: integration architect): ERP order and invoice feeds, February to April, migration of customer accounts in May.
- Testing (owner: QA lead): system tests in early May, user acceptance testing with ten pilot customers mid-May. Milestone: UAT sign-off, end of May.
- Change and launch (owner: customer success manager): help articles and training in May, launch emails and hypercare in June. Milestone: go-live, mid-June.
Project roadmap vs Gantt chart vs project plan
A project roadmap is a high-level visual: workstreams, phases and milestones on one page. It is built for sponsors, steering committees and teams who need the big picture. A Gantt chart shows every task with start and end dates and dependencies, and lives in a tool like Microsoft Project, Smartsheet or a Jira timeline. A project plan is the full document: scope, schedule, budget, RACI, risk log, communication plan and governance.
Keep the three linked but separate. The roadmap slide is updated from the Gantt chart, not the other way around. If a stakeholder asks for more detail, show the Gantt chart for that workstream rather than adding rows to the roadmap. The roadmap stays readable only if it stays high level.
How to present it to a steering committee
Open with the roadmap slide and say three things: where we are (point to the today line), what changed since last time and what decision you need. Do not walk through every bar. Executives read the slide faster than you can describe it. Spend your time on amber and red lanes, the next milestone and any request, such as a scope decision or extra testers.
Put the details in backup slides: the RACI, the risk log top five, and a Gantt view of any workstream at risk. Use Slide Show, then Hide Slide, so backup slides do not appear unless you jump to them. Leave out task lists, sprint numbers and internal jargon on the main slide. Always show the version date so nobody argues from an old copy.
How to adapt the template
For a portfolio of projects, swap workstreams for projects: one swimlane per project, quarters as columns and one bar per major phase, with a status dot on each lane. PMO leads often use this version in quarterly business reviews. For an agile team, replace months with three columns, Now, Next and Later, and show outcomes or epics instead of dated bars when dates are uncertain.
For a long project over a year, use quarters as columns and add a separate slide per quarter with month detail. For an external client, remove internal owners and effort, keep milestones and deliverables, and add the decisions you need from the client on each date. Whatever the version, keep the same colors, fonts and legend across all roadmap slides in your organization so readers learn the format once.
Common mistakes to avoid
- Cramming every task onto the slide makes it unreadable, so keep five or six swimlanes with phases and milestones and leave tasks in the Gantt chart.
- Drawing bars freehand leaves them misaligned with the month columns, so use a table grid with guides and the Align tools.
- Mixing phase colors and status colors confuses readers, so pick one color meaning for bars and show status with a separate dot.
- Forgetting the version date lets people argue from old copies, so put an Updated date in the title bar every time you edit it.
- Showing a static plan with no today line hides progress, so add a dashed today marker and move it before every review.
- Presenting the roadmap without an ask wastes the steering committee's time, so end every review with the decision or support you need.
Frequently asked questions
How do I make a project roadmap in PowerPoint?
Start with a blank 16:9 slide and insert a table with one label column and one column per month. Add a row per workstream, then draw phases as rounded rectangles and milestones as diamonds on top. Align them with the guides and Align tools, and add a dashed today line and a legend.
Does PowerPoint have a built-in roadmap template?
PowerPoint includes SmartArt graphics such as Basic Timeline in the Process category, and Microsoft offers timeline designs you can search for when creating a new presentation. These work for simple timelines. For a project roadmap with swimlanes and milestones, a table grid with shapes gives you more control.
What should a project roadmap include?
It should include the project goal, workstreams, phases with start and end dates, key milestones, owners and the current status. Add a today marker and a version date. Keep detailed tasks, budgets and risks in the project plan.
How often should I update a project roadmap slide?
Update it before every steering committee or status meeting, usually every one or two weeks. Move the today line, update status colors and note any changed dates. Keep older versions so you can show how the plan changed.
What is the difference between a project roadmap and a timeline?
A timeline shows events in date order, often on a single line. A project roadmap shows several workstreams in parallel, with phases, milestones, owners and status. It is a planning and communication tool, while a timeline is mostly a record of dates.