Notion provides an affordable, flexible alternative to specialized roadmapping tools while maintaining the structured databases and filtering capabilities product managers need. You can build a fully functional roadmap without coding knowledge, and integrate it directly with your existing Notion workspace. Whether you're managing a small team or coordinating across departments, this guide walks you through building a production-ready roadmap in Notion.
Why Notion
Notion's relational databases make it ideal for managing the multiple dimensions of product roadmapping. You can create interconnected databases for initiatives, features, epics, and team members, then display them through multiple views optimized for different stakeholders. Unlike static spreadsheets or specialized tools with expensive per-seat pricing, Notion scales with your team while maintaining a single source of truth.
The platform's filtering, sorting, and formula capabilities allow you to segment your roadmap by quarter, team, priority, or status without maintaining duplicate data. You can embed your roadmap in documentation, share read-only views with executives, and update everything in real-time. If you're already using Notion for product specifications or meeting notes, keeping your roadmap here reduces tool fragmentation and keeps context adjacent to decision-making.
Step-by-Step Guide
Step 1: Create Your Master Features Database
Open Notion and create a new database called "Features" (or "Initiatives" if you prefer). Click the plus icon next to "Databases" in your sidebar and select "New database." Name it appropriately and select "Table" as your layout.
Your base columns should include: Name (default), Status, Priority, Team, Quarter, Description, Start Date, End Date, and Parent Epic. Add these by clicking the plus icon in the table header. For the Status column, select "Select" as the property type and create options like "Backlog," "In Planning," "In Progress," "Launched," and "On Hold." For Priority, use another Select property with options "P0 (Critical)," "P1 (High)," "P2 (Medium)," "P3 (Low)." For Quarter, create a Select property with values like "Q1 2024," "Q2 2024," etc.
The Team column should be a "People" property type so you can assign owners. Parent Epic should be a "Relation" property that links to a separate Epics database you'll create in Step 2. Add a checkbox property called "Blocked" for tracking dependencies. Finally, add a "Notes" property as a rich text field for additional context. Don't add too many columns initially; you can expand based on your specific needs.
Step 2: Build Your Epics and Strategic Initiatives Database
Create a second database called "Epics" using the same process. This database structures larger strategic initiatives that contain multiple features. Your columns should include: Epic Name, Strategic Goal, Owner, Target Quarter, Status, and Features Count.
The Features Count column is a "Rollup" property that counts how many features are linked to each epic. Click "Add a property," select "Rollup," choose the Features database as your relation, and count the linked records. This gives you quick visibility into epic scope. The Strategic Goal column should be a long text property where you explain how this epic aligns with company OKRs. You can reference your tool for connecting roadmap items to annual goals. The Status should match your Features status options so epics and features use consistent language.
Link this database to your Features database by going back to the Features table and setting the "Parent Epic" property to reference this Epics database. Now when you create a feature, you can select which epic it belongs to, and those relationships flow both directions.
Step 3: Set Up Your Quarterly Timeline View
Stay in your Features database and create a new view by clicking "Add a view" and selecting "Calendar." Name it "Timeline by Quarter." Configure the calendar to display by the End Date property so you can visualize when features launch.
This view helps stakeholders understand what's shipping when. However, for a traditional roadmap view, also create a "Gallery" view by adding another view and selecting Gallery. Set the gallery cards to group by Quarter (use the Quarter property as your grouping), then sort by Priority descending. This creates a physical roadmap layout where each quarter shows all planned work sorted by importance.
Configure the card display to show Name, Priority, Team, and Status. Click the three-dot menu in the view settings and select "Properties" to choose which fields appear on gallery cards. This gallery view is what you'd share with executives and other stakeholders who need a high-level picture.
Step 4: Create Status and Priority Filtered Views
Add a new table view called "By Status" and filter it to show only features that are "In Progress." Click the filter button at the top of the view, select "Add a filter," choose Status, select "is," and pick "In Progress." This gives your engineering team a dedicated view of current work.
Create additional filtered views for "Backlog," "Blocked Items," and "Upcoming Quarter." For the Blocked Items view, add a filter where "Blocked" equals checked. This ensures nothing gets forgotten. In your Upcoming Quarter view, filter where Quarter equals next quarter and Status is not "Launched," allowing you to prepare for handoff.
Add a sorted view called "By Priority" that shows all features regardless of quarter, sorted by Priority descending then by Quarter ascending. This helps when you need to make trade-off decisions and understand what would ship if you reordered items.
Step 5: Add Dependencies and Blockers Tracking
Return to your Features database and create two new properties. Add a "Dependencies" relation property that links to other features in the same database. This lets you mark when Feature A can't start until Feature B completes.
Add a second "Blocked By" property as a rollup that counts dependencies. Click "Add a property," select "Count," choose the Dependencies property, and select "count all." Then add a formula property called "Is Blocked Status." Click into the formula field and enter: if(prop("Blocked By") > 0, "Yes", "No"). This creates a status indicator so you can filter or sort blocked work.
Create a view called "Dependency Map" using your table view. Add a filter where "Is Blocked Status" equals "Yes." Sort by Quarter ascending so you see blocking issues chronologically. This view helps identify critical path items that need resolution.
Step 6: Create a Database for Strategic Themes
Add a third database called "Themes" to organize features by strategic business focus. Examples include "Performance," "User Retention," "Enterprise Features," or "Mobile Experience." Create columns: Theme Name, Description, Linked Features Count, and Owner.
In your Features database, add a "Theme" property as a relation that links to this new Themes database. Now you can tag each feature with one or more themes, allowing stakeholders to view roadmap by strategic initiative. Create a gallery view in Features grouped by Theme to show what features ladder up to each strategic focus area. This is invaluable for guide communication with executives who think in strategic terms rather than individual features.
Step 7: Build a Status Report Rollup Dashboard
Create a new database called "Roadmap Dashboard" with no properties initially. This becomes your executive summary database. Add a "Last Updated" property as a date/time field showing when you last refreshed the roadmap.
Add text properties for metrics like "Features In Progress," "Features Planned This Quarter," "Blocked Items Count," and "On Track Status." Manually update these or use Notion's API for automation. Most importantly, add a "Related Features" property and use a relation to link to your Features database. Create a single row in this dashboard and populate it with related features filtered to "In Progress" status. This gives you a quick dashboard view for status syncs.
Alternatively, embed your gallery view directly into this dashboard view for a visual overview. Click "Embed" in your dashboard database and paste the link to your quarterly gallery view.
Step 8: Set Up Sharing and Permissions
For stakeholder alignment, create a duplicate view of your gallery quarterly view and set its sharing permissions. Click the three-dot menu on the view, select "Share," and toggle "Share to web." This creates a read-only public link you can send to anyone. Stakeholders see a current snapshot without edit access.
For internal teams, set database permissions in Notion's sharing settings. Click the Share button at the top right of your database, add team members, and choose their permission level. Product managers and team leads typically get "Can edit" access, while executives and other stakeholders get "Can view" access. Create role-based access so engineers see only their team's features while product leadership sees the full roadmap.
Pro Tips
- Use templates for recurring work: Create a "Feature Template" at the top of your Features database with default values for commonly used statuses or teams. When creating new features, duplicate the template rather than building from scratch.
- Build a Features Backlog view filtered to "Backlog" status: Keep this separate from your active roadmap so stakeholders see a clear distinction between planned work and future consideration.
- Set up a "Refresh Schedule" database: Track when you last reviewed each epic and when the next review is due. Create relations to Epics and use a status property for "Due for Review." This keeps your roadmap data current.
- Create a "Risks" database: Link it to Features so you can capture known risks and track mitigation status. Include properties for Risk Type, Impact, Mitigation Plan, and Owner.
- Use database templates for recurring launches: If you follow a standard launch process, create a template with checklist items, stakeholders, and timeline that automatically populates when you create a feature marked as "Launching Soon."
When to Upgrade to a Dedicated Tool
As your organization scales, you may find Notion's limitations emerge. Specialized tools on the PM tools directory offer benefits Notion can't match: automated capacity planning based on team velocity, visual timeline dependencies, scenario modeling, and stakeholder collaboration features built for non-technical users. If you need to track hundreds of features across multiple teams, conduct sophisticated what-if analysis, or provide sophisticated Gantt charts, a dedicated roadmapping tool becomes worth the investment. However, for teams under 20 people or those already deeply invested in Notion, this database structure works well. Compare your options with our comparison of Notion's capabilities against other popular tools.