Quick answer: A roadmap slide communicates where the product is heading and the order in which value will arrive. It appears in three places — the investor pitch, the sales deck, and the customer update — and each version needs a different level of detail.

The three-state structure

The most reliable roadmap slide divides work into three visible states:

  1. Shipped. Done, available, or in use.
  2. In progress. Confirmed and under construction.
  3. Planned. Directional, not committed.

The visual distinction must be obvious: solid color for shipped, half-filled for in progress, outline or muted for planned. Anything less than three states forces the audience to read the dates to understand status.

The time bands

The common formats:

  • Quarters. Q1–Q4 for a one-year view; the standard investor choice.
  • Now / Next / Later. For a twelve-to-eighteen-month product view without dates.
  • Half-years. H1/H2 for an audience that needs to see the broad arc, not the sprint.

Do not put month-level detail on a roadmap slide. Months belong in the internal product plan, not the external deck; a slide with exact dates is a slide that will embarrass you twice.

The content

Each roadmap item should be a short, user-facing phrase:

  • "SSO and SCIM" not "Auth refactor phase 2."
  • "Mobile app" not "React Native parity work."
  • "Marketplace" not "Partner integration framework."

Name the capability, not the project. A roadmap of five to seven items per band is the maximum; more items make the slide a backlog.

The layout patterns

The horizontal track

A single left-to-right line with the bands marked on top and cards beneath it. Best for a single product line and a strong narrative.

The swimlanes

Horizontal tracks grouped by theme: Product, Platform, Ecosystem, Business. Best for an audience that needs to see investment across areas, such as a Series A investor deck.

The three-card stack

Three cards: Shipped, Building, Planned. Best for a customer update deck where precise dates are deliberately absent.

The rules of the visual

  • One color for the state, not for the priority.
  • The same card size and the same icon weight across all items.
  • No more than two lines of text per item.
  • Keep the current band visually emphasized; the rest is context.
  • A subtle arrow or line connects the bands; the direction is the whole point.

What to show investors versus customers

Audience Detail Dates
Investors Thematic swimlanes, platform bets, market position Quarters, with a clear "this year"
Customers Capabilities, user-facing names, benefits "Now / next / later," not hard dates
Internal team The actual plan Months and owners

The customer update guide uses the customer version; the internal version never leaves the company.

The honesty rules

  • Mark exploratory work as "planned" or "exploring."
  • Do not put a customer's requested feature on the roadmap without an owner and a band.
  • Do not remove a missed item silently; show it in the next band with a note.
  • Keep the shipped column populated — it proves the team can execute.

Making the slide

  1. List the last two releases worth showing.
  2. List the three to five things in flight.
  3. List the three directional bets after that.
  4. Translate each item to user-facing language.
  5. Choose the track, swimlane, or card layout.
  6. Apply the three states and the color system.
  7. Check the slide against the deck consistency rules and the slide typography guide.

An AI deck generator can draft the slide from a product brief; a tool such as Neatico lays out the three-state structure and leaves the dates and the item wording to the team.

The timeline slide is the companion when the story is historical rather than forward-looking.

What to avoid

  • A roadmap that is actually a wish list with no shipped items.
  • Month-level dates on a public slide.
  • More than three states rendered in five different colors.
  • Roadmap items named after internal tickets.
  • Competitor-reactive roadmaps with no underlying theme.
  • Promising a date to a customer on the slide and then missing it.

Frequently asked questions

What is the difference between a roadmap slide and a timeline slide? A roadmap is forward-looking and grouped by product states; a timeline shows events in chronological order, often with the past included. Use the roadmap for the future, the timeline for the journey.

How many items should a roadmap slide have? Roughly ten to fifteen items total, with at least three in the shipped column. Anything more becomes a feature list, which belongs in an appendix.

Can I show exact dates? Investors can see quarters; customers should see "now, next, later." Months are an internal commitment.

What if the roadmap changes? The slide changes with each deck version; keep the source and the published version identical so the narrative in the roadmap slide never outruns the plan.

Show the shipped work, the in-flight work, and the direction. The best roadmap slide is one the team can defend a quarter later.

Related guide: the slide design guide.