Product roadmap

Before you start defining or discussing your roadmap or timeline, it’s a good idea to spend two minutes organizing it.

Decide how you want to structure it: by quarters, months, or milestones. Choose the top row format that fits your work best — for example, a calendar view, four quarters, or key milestones.

Next, define what each row will represent. It could be:

Once you’ve structured it, you can start adding the activities and initiatives that need to get done one by one.

See How It Works

💬Tip: If you need it, you can keep the top section to mark key milestones or goals — or remove it if it’s not relevant. Delete everything you don’t need.

As time passes, things will naturally change, because the map is not the territory — and that’s fine. The goal is to keep track of the original plan and document the decisions, blockers, and challenges that affected it along the way, so you can learn from them.

To do this, turn the session into a recurring one. When a change happens, duplicate the current session (using the same template) and make updates in the new recurrence. Keep the original version untouched.

Then, add a note summarizing the changes and challenges inside conclusions. Stakeholders will be notified automatically, and they’ll be able to see both the original plan and the updated version — along with the reasons behind each change.

Over time, you’ll build a clear history of how your roadmap/timeline evolved, providing visibility, transparency, and shared learning across all stakeholders.