Build with me: Notion's project management starter kit

A Notion project-management starter kit centers on one idea: build project tracking from connected databases—then use views, filters, and rollups to keep teams aligned without duplicating work. The system starts with a workspace organized by top-level pages (by team or function), then moves into a project roadmap database where each project is a database entry with structured properties like status, launch date, priority, team, and owner. Because each row becomes its own full Notion page, teams can attach specs, links, images, and ongoing discussion directly to the project record—turning “tracking” into a living workspace rather than a static spreadsheet.

The core mechanics come from Notion databases and their building blocks: properties and views. Properties define the data model—text, dates, URLs, and especially select tags for initiatives—while views reshape the same underlying data for different workflows. The kit demonstrates five view types (table, board/kanban, calendar, list, and gallery) and shows how a board view can group projects by initiative or status, with card counts that make it easy to see what’s next. Views can also be filtered down to a specific person’s workload (e.g., “me”) and saved for quick reuse. Even the card content is customizable, letting teams decide which properties matter at a glance.

Where the system becomes truly project-management-grade is the relationship between projects and tasks. Instead of listing tasks as plain text inside a project page, the kit recommends a master tasks database with task-specific properties (type, assignee, priority, status, due date). Tasks then connect to projects through a relation property, creating a two-way link: selecting a project on a task automatically surfaces the task under that project, and vice versa. This keeps data sane—project tracking stays in the project database, task tracking stays in the task database—while still making them codependent through the relation.

Once relations exist, rollups provide the next layer of automation-like visibility. The kit shows rolling up task statuses onto the project roadmap so a project can display how many related tasks are “next up,” “in progress,” or “completed,” without manually updating anything. It also demonstrates rolling up other fields such as project launch dates and estimated time in hours derived from task properties. The same pattern extends beyond projects and tasks into OKRs: objectives relate to key results, key result statuses and numeric progress roll up into objective dashboards, and formulas (based on JavaScript) can calculate progress toward targets.

Finally, the starter kit emphasizes collaboration features that make the system operational: Notion’s updates feed logs changes and who made them, and pages can be followed so notifications appear in the updates area. Setup is framed as incremental—build the property “skeleton” first, then add relations and rollups as teams discover what needs to connect. The result is a flexible project-management system that supports multiple perspectives (by team, owner, initiative, or status) while keeping the underlying data connected rather than duplicated.