One Page Roadmap: Layout, Filled-In Example and How to Present It

The layout that fits on one page

Use a landscape page or a 16:9 slide. Put a header strip across the top with the roadmap name, the period it covers, the owner and the date of this version. Under it, one line with the business goals the roadmap serves. The goals are the reason the page exists, so do not hide them in a footer.

The body is a grid. Columns are time: four quarters, or Now, Next and Later. Rows are swimlanes: three to five lanes for teams, products or strategic themes. Each cell holds one to three short bars or cards, each a theme of work in five words or fewer, with the owner's initials. Use one color per lane and a separate marker, such as a diamond, for milestones. At the bottom, add a strip with two to four outcome metrics and their targets.

• Header: name, period, owner, version date.
• Goals line: one or two business goals with numbers.
• Columns: Q1 to Q4, or Now, Next, Later.
• Swimlanes: three to five rows, one color each.
• Cards: themes, not tasks, with owner initials.
• Milestones: diamonds on the date they are due.
• Footer: outcome metrics and a small legend.

How to build it in PowerPoint or Google Slides

A slide is the best home for a one page roadmap, because it gets presented, pasted into decks and printed. Build it with simple shapes so anyone on the team can edit it later.

Keep text at a size people can read when the slide is shared on a call. If you cannot fit a theme in five words at that size, it is too detailed for this page.

• Start a blank 16:9 slide. Add a text box at the top for the header and one below it for the goals.
• Insert a table for the grid with Insert > Table in either tool: one column for lane names plus one per quarter, and one row per lane plus a header row.
• Fill the lane name cells with a light tint of each lane's color and leave the time cells white.
• Add rounded rectangles for each theme with Insert > Shapes in PowerPoint or Insert > Shape in Google Slides. Color them to match the lane.
• Stretch each card across the quarters it spans, then line them up with Shape Format > Align in PowerPoint or Arrange > Align in Google Slides.
• Add small diamond shapes for milestones and a footer text box for metrics and the legend.

Example: a filled-in one page roadmap

Here is how the 12-month roadmap above reads on the page for a B2B software company of about 80 people. Goals line: grow revenue from existing customers and win the first customers in a new segment.

Notice what is not on it: sprint plans, ticket numbers, exact launch days and a list of 30 features. Those live in the product backlog and the project plans. The page shows only themes, owners and outcomes.

• Product lane (blue): Q1 new onboarding, Q2 top two workflow features, Q3 plan for smaller teams, Q4 review and next bets. Owner: product manager.
• Customer lane (green): Q1 account health score, Q2 business reviews with top accounts, Q3 support for the new segment, Q4 renewal push. Owner: head of customer success.
• Operations lane (orange): Q2 faster ticket resolution, Q3 self-serve billing. Owner: operations lead.
• Platform lane (gray): Q1 one reporting data source, Q4 hardening for growth. Owner: engineering lead.
• Footer metrics: net revenue retention, time to first value for new customers, paying customers in the new segment.

What to leave out

The hardest part of a one page roadmap is deleting things people care about. Use a simple test for every item: would an executive or a partner team change a decision because of it? If not, it belongs somewhere else.

Exact dates are the most common trap. Once you put "March 14" on a roadmap, people treat it as a promise. Use quarters or months for most items, and keep exact dates only for fixed external events such as a contract deadline or a trade show.

• Individual tasks and user stories.
• Exact dates for work that is not fixed.
• Every feature request, ranked or not.
• Detailed dependency arrows between cards.
• Resource and budget breakdowns.
• More than five lanes or more than three cards per cell.

Quarters or Now, Next, Later?

A quarter-based layout works when leadership plans in quarters, when you have fixed external dates, or when other teams need to line up their work with yours. It is the easiest format for executives to read. The risk is that every card looks like a commitment.

A Now, Next, Later layout works better when priorities change often, such as in an early-stage product team. Now means work in progress, Next means what starts once capacity frees up, and Later means ideas you plan to come back to. It sets expectations about certainty without promising dates. Many teams use quarters for the next two quarters and a single Later column for the rest of the year.

How to present it to leadership

Open with the goals, not the grid. Say the two business goals and how the roadmap serves them in one sentence each. Then walk the page lane by lane or quarter by quarter, whichever tells the story better. Spend most of the time on the next quarter, because that is where decisions are still open.

End with what you need: a decision, a hire, a budget call or help from another team. Bring the backlog and project plans as backup, but do not show them unless asked. Send the page as a PDF after the meeting with the version date in the header, so nobody works from an old copy.

How to keep it current

A one page roadmap goes stale fast if nobody owns it. Name one owner, often the product manager, head of operations or PMO lead, and review it once a month with the lane owners. Move cards, mark finished themes, and update the version date.

Rework it properly once a quarter, when you review results against the outcome metrics. Keep old versions in a shared folder. Being able to show what changed and why builds trust with leadership far more than a page that never changes.