How to build your ideal project roadmap (Block × Block)

Project roadmaps in Notion work best when every project lives in a single database that acts as a “source of truth,” then gets reshaped into whatever view each team needs—table, Kanban board, timeline, or calendar—without duplicating information. In the example workspace for the fictional company fig.io, a “Project Roadmap” database gives a company-wide bird’s-eye view of project status, ownership, priority, OKR alignment, and launch timing, while still letting teams drill into full project context on one page.

The core setup starts with a database table where each row represents a project and each column (called properties) captures structured fields like status (e.g., approved or in progress), related OKRs, launch schedule dates, teams involved, owners, and priority. Clicking a project opens a full page containing the entire lifecycle: specifications, notes, links to supporting documents, checklists, milestones, and key decisions. That design eliminates the need to juggle multiple tools or tabs (spreadsheet + documentation + board/Jira ticket) because the roadmap card itself becomes the repository for both summary and detail.

Flexibility is a major theme. Teams can customize properties on the fly—for instance, adding an “initiative” property using select or multi-select tags such as Growth, Retention, and Advocacy. Once properties exist, they become the building blocks for slicing and dicing the roadmap. Notion’s filtered views let teams create reusable, named subsets like “All Growth Projects,” “High Priority Projects,” or “All Approved Projects,” using one or multiple filters (e.g., initiative contains Growth AND status is approved). Instead of maintaining separate spreadsheets for each audience, everyone can toggle between views that all pull from the same underlying database.

The same database powers multiple visual formats. A Kanban-style board groups projects by status, but can just as easily group by initiative, owner, or any other property—making it easy to see workload and dependencies. Drag-and-drop updates status instantly, and adding a new card can auto-assign ownership based on the column it’s created in. For planning and scheduling, timeline (Gantt-like) and calendar views overlay projects onto dates, helping teams spot overlaps, delays, and upcoming releases; moving cards updates launch dates dynamically. Calendar views also support month-level use cases like marketing content calendars or leave schedules.

At scale, the workflow depends on consistency. Notion emphasizes templates for database entries so teams don’t freehand new projects with inconsistent fields. Templates pre-fill default values such as priority, assigned teams, OKR linkage, and owners, and also standardize the structure of the project page body (specs, milestones, tasks). Finally, the roadmap can be embedded elsewhere using linked databases, so hubs for product, marketing, or other teams can show only the filtered slice they care about—while edits still update the master roadmap automatically. The result is less back-and-forth about “what’s going on,” more accountability, and faster access to context across teams.