Skip to content
Prolifik
Video creation guide

Make a Product Roadmap Carousel That Separates Planned from Shipped

Show roadmap themes, current status and uncertainty on each carousel card so planned work does not look like a live feature.

Published 2026-11-17Facts checked 2026-11-02
Three rows of blank cards and movable tokens distinguish planned, in-progress and shipped work.
A public roadmap card must show what exists now and what remains tentative.

A roadmap carousel can help customers understand where a product is going. It can also make an unbuilt feature look available if planned, in-progress and shipped items share the same visual treatment. Use explicit status labels and dates that the product team has approved. Keep uncertainty on the card where the promise appears.

The product-launch carousel guide announces something ready to use. This page is for a different situation: a team is communicating priorities while some work is still conditional.

Choose the level of commitment first

Imagine a fictional document app called FleetNote. Its team is considering offline review, building a new role selector and has already shipped an improved comment filter. Those three items cannot all be captioned “new features.”

Ask the product owner to classify each item and its public wording. A planning theme may change direction. In-progress work may be delayed. A shipped feature may be limited to a plan or rollout cohort. The carousel should not compress those realities into a neat timeline with invented dates.

FleetNote item Approved state in this example Safe card treatment
Offline review Planned exploration “Exploring offline review,” with no launch date.
Role selector In progress Name the current test scope and avoid a release promise.
Comment filter Shipped in the example Show current availability and link to the real guide.

FleetNote is fictional. These states demonstrate editorial labels, not an actual company roadmap.

Atlassian distinguishes a roadmap from a detailed delivery plan. That distinction matters here. A roadmap can explain priorities and why they matter without being an unconditional contract for a specific date.

Build the cover around the truth

A cover like “What we are working on next” sets a reasonable expectation. “Three features arriving this month” would be inaccurate if one is exploratory and another has no firm release date. Do not let a strong cover force the later cards into awkward disclaimers.

Keep the status language consistent. If “planned” means under discussion, do not use the same badge for an item already scheduled for a public beta. Define the terms in the caption or first card when readers could reasonably interpret them differently.

Avoid tiny footnotes. A screenshot of the offline-review card may circulate alone, so its uncertainty belongs on that card. A link to a full public roadmap can provide context, but it cannot rescue a misleading image that appears elsewhere.

Give each card an evidence path

For a shipped item, show a real current screen or link to the canonical help page. For in-progress work, use clearly conceptual art or an approved prototype label. For planned work, discuss the user problem without drawing a fake finished interface.

The FleetNote comment-filter card could show a safe sample document with the actual filter action if the app really supports it. The role-selector card should not show a production screenshot unless that version is publicly available. The offline-review card might use a neutral illustration and explain why the problem matters.

The feature announcement video guide applies once a capability is ready to announce. A roadmap carousel should not borrow its confident launch copy for work that is not yet shipped.

Treat dates as product facts

If the team publishes a target quarter or date, record who approved it and what conditions could move it. A simple “coming soon” badge can be as misleading as a precise date if customers interpret it as guaranteed near-term access.

Avoid a decorative progress bar that suggests a percent complete when the product team has not defined one. Status categories are not percentages. Similarly, a card order from left to right need not mean the first item ships first. Use grouping or clear labels to communicate the actual relationship.

If a target changes, update the public post or publish a correction where the platform allows it. Keep an internal record of every exported card and its source approval so a stale version is not reused in a later newsletter or ad.

Use generated visuals only for the concept

Prolifik Image Carousel can turn approved roadmap copy into branded carousel-style video. Supply each item's status, prohibited promises and current source URL. Review every returned panel for altered language. A generated card that upgrades “exploring” to “launching” is not ready.

Use real screenshots only for shipped features. If the format creates a video and still panels, inspect both. A planned label that is readable on a still may vanish too quickly in the timed version. Keep the next action relevant: shipped items can point to a current product guide, while planned themes can invite feedback without implying a purchase entitlement.

Canva's current carousel guidance emphasizes one clear idea per slide and a coherent sequence. Apply that to status as well as design. The reader should be able to tell what exists now after seeing only the card in front of them.

Review the whole set as a customer would

Ask someone outside the product team which FleetNote items they think they can use today. If they name offline review because the illustration looked too real, redesign the card. If they cannot find the currently shipped comment filter, the hierarchy may be hiding useful information.

The final approval should include product, support and legal or communications owners as appropriate. A roadmap is a public statement about intent, even when it is not a guaranteed release schedule. Keep the reviewed source document, exported cards, caption and public URL together for future updates.

Make roadmap status clear on each card

Keep planned, in-progress and shipped wording distinct in the final video.

Explore Image Carousel
Sources and verification

Facts checked 2026-11-02. Worked examples are illustrative unless a real source is identified.