Free starter kit: 5 Notion templates with a setup guide · Get it free

How to Build a Visual Project Roadmap in Miro (Step by Step)

October 28, 2026·17 min read·Review Tools

Disclosure: this post contains affiliate links. If you sign up through them, Create Digital Tools may earn a commission at no extra cost to you. We only recommend tools we would point a small business to anyway.

A roadmap nobody looks at is just a pretty spreadsheet. The goal is a single picture your whole team can read in ten seconds and update in two minutes.

If you want a visual plan that the whole team can actually follow, building a project roadmap in Miro is one of the quickest ways to get there. Miro gives you an open canvas, a library of ready-made roadmap templates, and a native Timeline format that turns rows of work into time bars you can drag around. This guide walks through the full process step by step, using Miro’s own template pages and help center as the source for every instruction.

We also cover how to pair a Miro roadmap with Notion, so the big picture lives on a whiteboard while tasks, briefs and meeting notes live in a database. If you are still deciding whether Miro is right for you at all, our full Miro review is a good place to start.

Quick answer

To build a visual project roadmap in Miro, start from a roadmap template, set your time columns and team swimlanes, add a card for each piece of work, link dependent items, share the board with the right access level, and review it on a fixed rhythm.

  • Best starting point: Miro’s Project Roadmap Template or the native Timeline format (available on all Miro plans).
  • Timeline dependencies are a Business and Enterprise feature (in beta); connection lines work on any plan.
  • The Free plan includes 3 editable boards, enough to build and test one roadmap.
  • Notion can embed a live Miro board on a page, so the roadmap sits next to your tasks and docs.

Why a visual roadmap beats a task list

Task lists are great for the people doing the work. They are much less useful for the people who need to understand the work: clients, leadership, a new hire, or a freelancer joining halfway through. A visual roadmap answers the big questions at a glance: what are we doing, in what order, who owns it, and when does it land.

Miro’s own guide on how to create a roadmap for a project breaks the job into four basics: set objectives, assign tasks, establish timelines, and monitor progress. The board just makes those four things visible in one place.

A visual roadmap is especially useful when:

  • Several teams or freelancers work on the same project and need to see each other’s timing.
  • You present plans to clients or stakeholders who will never open your task manager.
  • The order of work matters, because one deliverable blocks another.
  • You run planning workshops and want to move ideas around live, with everyone on the same canvas.
Miro homepage
Miro homepage, captured live.

What you need before you start

You do not need a paid plan to follow this tutorial. Miro’s Free plan includes 3 editable boards, which is enough to build one roadmap and see whether the approach works for your team. A few things are worth preparing before you open the canvas:

  • The project goal and success metrics. One or two sentences on what “done” looks like.
  • The time horizon. Six weeks, one quarter, a full year. This decides whether your columns are weeks, months or quarters.
  • The teams or roles involved. These become your swimlanes (for example Design, Content, Development, Marketing).
  • A rough list of high-level work items. Keep it at the level of deliverables or epics, not individual to-dos.
  • Known fixed dates. Launches, client reviews, holidays, events.

With that in hand, the build itself goes quickly.

How to build a project roadmap in Miro: step by step

Here is the full process at a glance. Each step is explained in detail below.

  1. Pick a roadmap template from Miro’s template library (or start with a Timeline).
  2. Set your timeframe and swimlanes.
  3. Add cards and sticky notes for your work items.
  4. Add milestones.
  5. Map dependencies between items.
  6. Share the board and collaborate.
  7. Keep the roadmap updated.

Step 1: Pick a roadmap template from Miro’s library

Miro’s roadmap template gallery lists 71 roadmap templates at the time of writing, from simple product roadmaps to Now-Next-Later boards and workshop formats. For a classic project plan, these are the most relevant options on the gallery:

  • Project Roadmap Template: a timeline graph with time-frame columns and team swimlanes, task cards with project bars, and a retrospective section. This is the one we use in this guide.
  • Roadmap Planning Template: a lighter planning board for adjusting timelines, adding milestones and assigning tasks.
  • Product Roadmap Template: a high-level, shareable view of product direction and priorities over time.
  • Now-Next-Later Roadmap: useful when exact dates are uncertain and you only want to show priority order.
  • Roadmap Planning AI Template: a starting point that uses Miro AI to draft the first version.

To add one to your board, open the template’s page and click Use template. Miro’s Roadmap Planning Template page also says you can open Miro and find the template in the Template Picker from inside a board.

Miro roadmap templates gallery
Miro’s roadmap template gallery, captured live.

Template or Timeline? There is a second route. Miro has a native Timeline format, available on all plans according to the Miro help center. To add one, you open the Creation bar on the left of the canvas, click Formats and Flows, then click Timeline. You can either prompt Miro AI (the Sidekick panel) to generate it, or click the canvas to place it manually.

Our suggestion: use the Project Roadmap Template when you want a presentation-style board with goals, team photos and a retro area. Use the Timeline format when you want structured records with dates, fields, filters and grouping. Many teams combine both: the template frames the project, and a Timeline sits inside it as the live schedule.

Miro Project Roadmap Template page
Miro’s Project Roadmap Template page, captured live.

Step 2: Set your timeframe and swimlanes

This step gives your roadmap its skeleton. The Project Roadmap Template page explains it plainly: add or remove columns to match your time frames (weeks or months, for example), and add or remove swimlanes to represent the teams involved.

A few practical rules for picking the scale:

  • Under 3 months: weekly columns.
  • 3 to 12 months: monthly columns.
  • Multi-year or portfolio view: quarterly columns.

Swimlanes usually follow teams or roles. For a small agency that might be Strategy, Design, Copy and Development. For a product launch it might be Product, Marketing, Sales and Support. Keep it to five or six lanes; past that, the board gets hard to read.

If you use the Timeline format instead, the Miro help center describes these controls:

  • Click the calendar icon in the upper left of the widget to choose start and end dates; the Timeline rescales automatically.
  • Use the scale dropdown to switch between Days, Weeks, Months, Quarters and Years.
  • Click Autofit above the records column to fit all time bars into view.
  • For swimlanes, click Group in the timeline menu, then pick a field from Select a field (for example a Team or Owner field). You can rename, reorder, hide or remove groups, and drag records between them.
Miro help center Timeline article
Miro help center article on the Timeline format, captured live.

Step 3: Add cards and sticky notes for your work items

Now fill the skeleton. In the Project Roadmap Template, each high-level task gets a card, and each card has a project bar that shows its duration. Miro’s instructions: duplicate the project bar on the card for the task you want to schedule, then adjust its length on the graph to set the task’s kick-off and deadline. Repeat for every task and place them in order.

Use sticky notes for the softer information around the plan: assumptions, open questions, risks and status updates. The template includes a toolbox of sticky notes for exactly this.

In a Timeline, the equivalent actions per the help center are:

  • Click the plus (+) above the records column to add a record.
  • Drag either end of a time bar to change its dates. Records with no dates show a plus (+) button to add a time bar.
  • Click the Fields icon at the top of the Timeline to add, edit, reorder, show, hide or delete fields such as owner, status or estimate.
  • Drag any Miro card or sticky note onto the Timeline to visualize its data there.
  • To create a synced card on the canvas, hover over a record, click and hold the dots icon, and drag it onto the board. Edits sync both ways.

Tip: keep card titles short and outcome-based (“Homepage copy approved”) rather than activity-based (“Work on homepage”). Outcome titles make progress obvious when someone scans the board.

If your team already tracks work in Jira, the help center notes you can drag a Jira card onto a Timeline row to create a Jira-synced record. Title, Description, Estimation, Start date, End date, Assignee and Status sync; other fields stay in Miro.

Step 4: Add milestones

Milestones are the fixed points everyone cares about: a client review, a beta release, a launch day. On a template board, a simple approach is a distinct shape or sticky note color placed on the relevant date column, with a vertical line through all swimlanes.

The Timeline format has milestones built in. According to the help center, you hover over the widget until a dotted line and flag icon appear, click the date, and name the milestone. You can double-click the name to edit it, change its color with the color circle, or move it with the calendar picker.

Step 5: Map dependencies

Dependencies are what turn a roadmap from a wish list into a plan. If the landing page cannot go live until copy is approved, that relationship should be visible.

Option A: connection lines (any plan). Miro’s help center explains that you can select Connection line on the toolbar or press L, or select an object and click one of the blue dots around it, then drag the line to the second object. Hold Shift for a straight line. This works on cards, sticky notes and shapes, so it fits template-based roadmaps well. Use an arrow from the blocking item to the blocked item.

Option B: Timeline dependencies (Business and Enterprise, beta). Inside a Timeline, you hover over a time bar to show its connection points, then drag from one bar to another. The dependency appears in both Timeline and Table views and creates Blocked by and Blocking fields in the table. The help center lists known beta limits: no support for Jira-synced or other third-party records, no indicators on synced cards, and no automatic date adjustments. That last point matters: if a blocking task slips, you still need to move the dependent bars yourself.

Step 6: Share the board and collaborate

A roadmap only works if the right people can see it. Miro’s help center describes two ways to share a board:

  1. Invite by email: click Share in the top-right corner of the board, enter email addresses on the Invite tab, set access rights, and click Send invitations.
  2. Share by link: click Share, find the Anyone with the link section on the Invite tab, choose view, comment or edit access, then click Copy board link.

Pick the access level by role. Core team members get edit rights. Stakeholders and clients usually get comment rights, so they can leave feedback directly on cards without moving anything. Note that the help center says commenter and editor access through a public link is not available on the Free plan, and guest links on the Business plan expire after 30 days.

You can also share just the Timeline widget: select it, click the more (…) menu, and choose Copy link. Anyone with view permission on the board can open it. For presentations, the diagonal arrow icon at the top of the widget opens it full screen.

Step 7: Keep the roadmap updated

Most roadmaps die in week three, not because the plan was bad but because nobody owned the updates. Build the maintenance habit into the project from day one:

  • Name a roadmap owner. One person is responsible for keeping dates and statuses honest.
  • Set a review rhythm. Weekly for short projects, every two weeks for longer ones. Walk the board left to right.
  • Use color for status. For example green for on track, amber for at risk, red for blocked. Keep a small legend on the board.
  • Use the retrospective area. The Project Roadmap Template includes a section to note what went well, lessons learned and improvement goals after each sprint.
  • Use filters in a Timeline. The filter and sort icons let you show only one team’s work or only overdue items during a review meeting.

Miro’s dedicated Roadmaps product page also describes features aimed at this problem, including status labels that show whether a roadmap is draft, approved, being finalized or outdated, an automated weekly updates Flow, and two-way integrations with Jira and Azure DevOps. Check your plan before relying on those, as the page positions them as part of its broader roadmapping offer.

Miro Roadmaps product page
Miro Roadmaps product page, captured live.

Template board vs Timeline format: which should you use?

Both routes get you a visual project roadmap. The right one depends on how structured your data needs to be.

NeedProject Roadmap TemplateTimeline format
Plan availabilityFree template, any planAll Miro plans
StructureFreeform cards, bars and sticky notesRecords with dates and custom fields
SwimlanesAdd or remove lanes manuallyGroup by any field
DependenciesConnection linesNative dependencies (Business and Enterprise, beta)
Filtering and sortingNoYes
Jira syncNoYes, by dragging Jira cards onto rows
Best forKickoffs, client presentations, workshopsOngoing scheduling and tracking

Tips for a roadmap people actually read

  • Put the goal at the top. A short frame above the timeline with the project goal and two or three success metrics keeps every discussion anchored.
  • Stay high level. If a card would take less than a few days, it probably belongs in your task manager, not on the roadmap.
  • Show owners. The Project Roadmap Template includes space for team member images on the timeline graph; use it. Faces make ownership obvious.
  • Separate committed from tentative. Use a lighter color or dashed outline for work that is planned but not confirmed.
  • Add a “Today” marker. A vertical line on the current week shows instantly what is late and what is next.
  • Archive, do not delete. When a phase ends, move finished cards to a “Done” area. The history is useful in retrospectives.

Pairing Miro with Notion: the roadmap plus the details

Miro is excellent at the visual layer: timing, sequence and the big picture. It is less suited to the detailed layer: individual tasks with checklists, project briefs, meeting notes and client documents. That is where Notion fits. A setup that works well for small teams:

  • Miro: the visual project roadmap, planning workshops, and stakeholder presentations.
  • Notion: the task database, project brief, meeting notes, SOPs and the client-facing docs.

Can you embed a Miro board in Notion?

Yes. Notion’s own Miro integration page confirms it and describes Miro as embedded “as a live artifact, with a real-time sync.” Per Notion, there are two ways to do it:

  1. Copy a Miro board link, paste it into a Notion page, and select Embed Miro board.
  2. Or type /miro in a Notion page and paste the Miro link into the field that appears.

Two caveats from the official docs. First, Notion notes that only signed-in users with permissions can access the board, so if you want anyone with the link to view it, change that in Miro’s Share menu. Second, Miro’s marketplace listing for the Notion embed says boards cannot be edited from Notion; you open the board in a new tab to edit. Viewers can still move around the board and zoom in and out inside Notion.

A simple Miro plus Notion workflow

  1. Build the roadmap in Miro with the steps above.
  2. Create a project page in Notion with the brief, goals and key links.
  3. Embed the Miro roadmap at the top of that project page.
  4. Break each roadmap card into tasks in a Notion database, with owners, due dates and status.
  5. Add the Notion page link to each Miro card (the Timeline lets you add links when editing a record’s text), so people can jump from the big picture to the detail.
  6. In your weekly review, update task status in Notion first, then adjust bars and colors on the Miro roadmap.

If you do not have a Notion workspace yet, you can start with Notion for free and add the Miro embed to your first project page.

Ready-made Notion systems that pair well with a Miro roadmap

Rather than build the Notion side from scratch, you can start from a template designed for project work. Two from the Create Digital Tools shop that fit this workflow:

  • Product Launch OS: a Notion system for planning and running a launch. Use the Miro roadmap for the launch timeline across teams, and Product Launch OS for the tasks, assets and checklists behind each phase.
  • Creative Agency Project OS: a Notion workspace for agencies managing client projects. Embed a client-facing Miro roadmap on each project page and track deliverables and feedback in Notion.

How much does Miro cost for roadmapping?

Pricing as of October 2026, taken from Miro’s pricing page (USD, per member, billed yearly). We keep this short; our Miro pricing breakdown covers the details and the hidden costs.

PlanPrice (billed yearly)Roadmap-relevant notes
Free$03 editable boards; Timeline available; public links are view-only for collaborators
Starter$8 per member/monthUnlimited editable boards
Business$20 per member/monthUnlimited guests; Timeline dependencies (beta); 14-day free trial
EnterpriseCustom, from 30 membersContact sales; Timeline nesting (beta) with the Accelerate license

Monthly billing costs more: Miro’s FAQ says annual billing saves 20% over monthly. The monthly-billed rates were not shown in the page content we reviewed, so check the toggle on the pricing page before you buy.

Miro pricing page
Miro pricing page, captured live.

For most small teams, the Free plan is enough to build and test one roadmap. Move to Starter once you need more boards, or to Business if native Timeline dependencies and guest access for clients matter to you.

Common mistakes to avoid

  • Too much detail. A roadmap with 200 cards is a backlog. Keep the roadmap at deliverable level and push tasks into your task tool.
  • No owner per item. Every card should show who is accountable.
  • Dates without dependencies. If you show dates but not what blocks what, slips will surprise everyone.
  • Edit access for everyone. Give stakeholders comment access so the plan does not change by accident.
  • Two sources of truth. If you pair Miro and Notion, decide which one owns dates (usually Miro for the roadmap view, Notion for task due dates) and stick to it.

FAQ

Is there a free project roadmap template in Miro?

Yes. Miro’s template gallery includes a Project Roadmap Template, a Roadmap Planning Template and dozens of other roadmap formats. You can add them to a board with the Use template button, including on the Free plan.

Is Miro’s Timeline available on the Free plan?

According to the Miro help center, the Timeline format is available on all Miro plans. Some Timeline features are restricted: dependencies require Business or Enterprise, and nesting requires Enterprise with the Accelerate license. Both are labeled beta.

How do I show dependencies on a Miro roadmap?

On any plan, draw connection lines between cards (select Connection line on the toolbar or press L). On Business and Enterprise, you can also drag between time bars inside a Timeline to create native dependencies, which add Blocked by and Blocking fields.

Can I embed my Miro roadmap in Notion?

Yes. Paste the board link into a Notion page and choose Embed Miro board, or type /miro and paste the link. The embed is view-only; you open the board in Miro to edit it. Board permissions in Miro decide who can see it.

Can clients comment on my Miro roadmap?

Yes, if you invite them with comment rights through the Share button. Note that commenter and editor access through a public link is not available on the Free plan, so on Free you would invite clients by email instead.

Does Miro sync roadmaps with Jira?

The help center explains that dragging a Jira card onto a Timeline row creates a Jira-synced record, with title, description, estimation, dates, assignee and status kept in sync. Miro’s Roadmaps page also lists two-way integrations with Jira and Azure DevOps.

Miro or Notion for a project roadmap?

Use Miro when the visual layout and collaborative planning matter most. Use Notion for tasks, documents and databases. For most small teams the best answer is both, with the Miro board embedded on the Notion project page.

Bottom line

Building a project roadmap in Miro comes down to a repeatable routine: start from the Project Roadmap Template or a Timeline, set columns and swimlanes, add cards and milestones, connect dependencies, share with the right access, and review on a fixed rhythm. The Free plan is enough to try it on a real project. Pair it with Notion for tasks and docs, and you get a plan that is both easy to see and easy to execute.

Ready-made templates for this

Notion systems, spreadsheets and planners with a setup guide. Instant download.

Browse templates
Keep reading

More guides

All guides →
Free starter kit

Get 5 free Notion templates

The free starter kit with a setup guide, plus a useful template tip each week. Unsubscribe anytime.

Get the free kit