A roadmap gets seen outside the room it was written in, by people who were not there for the argument about what got cut.
Product roadmap — second half
Three themes carry the half: reliability, self-serve onboarding, and reporting. Dates are estimates, not promises.
A native mobile app, the public API and single sign-on for the free tier — deferred, with the reasons noted in the appendix.
A roadmap has to say what is coming without promising it, so what is confirmed and what might still move have to look different at a glance, not blend into the same sentence. It gets handed to people outside the team — a customer, a candidate, a board — who will treat every date on it as a commitment unless the document says otherwise. This is written for what is next across the whole product, not the plan for shipping one thing.
Every initiative on one axis of time
Each quarter groups whichever initiatives land in it on the same timeline, so the page works as a plan for the whole product rather than the streams inside a single launch.
Detail that waits until someone asks for it
What a quarter’s entry will actually involve sits behind a closed line, unopened, so the page states the plan at a glance without forcing every dependency into view at once.
What is confirmed, set apart from what might still move
A marked note above the quarters says plainly which dates are committed and which are a best guess, so a roadmap handed to someone outside the team is not mistaken for a promise it never made.
Which section of the roadmap held them longest
What decides a section here is the same thing that decides one anywhere else: a heading — so the timeline counts as one, and the note above it as another. You see which of those held attention longest, and whether it earned a second look; you cannot see which quarter on the timeline itself did, because a quarter is not a heading.
An example — not your document. Sections are the document’s own headings.
Most of their attention went to “Timeline” — 2m 09s of 4m 00s. They came back to “Timeline”.
Time each section spent on screen, counted only while the tab was in front and the reader was active. It shows what was in front of them, not what they read.
This page is about what a roadmap has to do. For the blocks the editor is built from — see the editor.
Yes — a project overview is one project across every team working on it. A roadmap is every initiative across the product, laid out by the quarter it lands in, and it is the one built to be handed to someone outside the team.
No — Quixli has no scheduling engine behind the page. Moving a date is an edit you make, the same as changing any other fact in the document.