Roadmap
Product, technology and programme roadmaps whose arrows are CHECKED against their dates. Lanes for themes or teams; items placed by quarter, month, half, year or on a Now / Next / Later horizon; four statuses (planned, in progress, done, at risk), each with a symbol as well as a colour so the figure survives greyscale; milestones on a band of their own with guide lines, or inside a lane; and a status date that draws the today line. Every dependency is checked: a prerequisite still running when its dependent starts is drawn red and named with the overlap in days, a loop or an unknown prerequisite is an error, and with a status date the engine reports what is overdue and anything marked done or in progress before it was due to start.

In the same space
Most users come to Roadmap from Productboard roadmaps, Aha! Roadmaps, Roadmunk, PowerPoint roadmap slides or Jira plans. flowss runs this engine in the browser — no install, shareable via URL, exportable to PNG / SVG / PDF / source.
Syntax at a glance
axis quarters 2027-Q1 .. 2027-Q4
today 2027-05-12
lane "Checkout"
item pay "Wallet payments" Q1 .. Q2 in progress 40%
item "Saved cards" Q3 planned after payPaste this in the Studio code pane to see Roadmap render live. The full grammar is at the upstream-docs link above.
Sample templates
All 12 →A fiscal-year product roadmap for a fictional workflow-analytics SaaS across five lanes, from core platform to mobile: 16 items (3 done, 5 in progress, 7 planned, 1 at risk) and 3 milestones on a quarter axis with a 14 May 2027 status date. All 11 dependencies finish before their dependents start, and the longest chain runs from the SOC 2 Type II report through EU data residency and bring-your-own-key encryption to Enterprise tier GA on 1 Dec 2027. Illustrative roadmap.
A customer-facing Now / Next / Later roadmap for a fictional running app, deliberately free of dates: 14 items (2 done, 4 in progress, 7 planned, 1 at risk) across five lanes and three captioned horizons. All 7 dependencies point forward to a later horizon, so nothing is promised before the work it waits for, and two chains run the whole width of the roadmap: adaptive plans to a coach marketplace, and watch sync through a recovery score to an injury-risk warning. Illustrative roadmap.
A four-year technology roadmap for a fictional building society replacing its mainframe core, drawn by half-year: 17 items (5 done, 5 in progress, 7 planned) and 2 milestones across five lanes with a 15 Mar 2027 status date. All 17 dependencies finish before their dependents start; the longest chain, six steps, runs from core vendor selection through the cloud core build and the savings, mortgage and current-account migrations to the mainframe switch-off at the end of 2029. Illustrative roadmap.
A five-year consortium grant on peatland restoration laid out by work package on a year axis, with deliverables and the funder's review points as milestones: 16 items (4 done, 4 in progress, 7 planned, 1 at risk) and 4 milestones in six lanes, status date 20 Sep 2027. All 20 dependencies finish before their dependents start; the longest chain, seven steps, runs from the kick-off through site instrumentation, the v1 carbon model, the mid-term review and the policy briefs to the final synthesis and the programme end. Illustrative roadmap.
A stage-gated hardware roadmap for a fictional 22 kW wall-box EV charger, from engineering validation to mass production, with gate reviews as milestones on the band above the lanes: 16 items (3 done, 5 in progress, 7 planned, 1 at risk) and 4 milestones over six quarters, status date 10 Jun 2027. All 22 dependencies finish before their dependents start, including CE (LVD, EMC, RED) and UL 2594 testing after design validation, and the longest chain runs from the G2 concept freeze through EVT, DVT and the CE campaign to the retail launch. Illustrative roadmap.
A month-by-month roadmap for taking a fictional retailer's customer-support LLM assistant from an internal pilot to general availability, with evaluation, retrieval, safety and cost work in their own lanes: 16 items (4 done, 4 in progress, 7 planned, 1 at risk) and 3 milestones, status date 19 Apr 2027. All 21 dependencies finish before their dependents start — the customer beta waits for red-teaming and the DPIA, and GA waits for online evaluation — and the longest chain, six steps, runs from the golden set through CI evals, model routing and the semantic cache to GA and the voice pilot. Illustrative roadmap.
roadmap · ← Browse all engines · Quick-start guide