How to build a personal project management system
Based on Reflect Notes's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Use pinned project pages as the source of truth for each project’s priorities, tasks, goals, notes, and ideas.
Briefing
A personal project management system built inside a notes app can keep multiple projects—work, side ventures, and even home maintenance—organized through a single set of linked pages for priorities, tasks, goals, and supporting notes. The core idea is to treat each project as a mini “workspace” while also maintaining cross-project rollups (like one place to see all top priorities). Backlinks tie everything together, so updating one project page automatically refreshes the aggregated views.
The setup starts with a sidebar of pinned notes that act as the system’s navigation. At the bottom sits a list of projects (for example, “Project one,” “Project two,” and “Project three”), each with its own pinned page. Alongside that, a “map” view visually connects the project pages to their components, showing how the structure is linked. Each project page is organized into category tabs that correspond to other pinned notes—so the categories aren’t just labels; they’re connected through backlinks.
For each project, the first category is “Top priorities.” These entries represent the few things that matter most, and they’re written as short, labeled bullets. A separate “Top priorities” page then acts as a rollup: because it receives incoming backlinks from every project’s priority list, it automatically displays a combined list of priorities across all projects. When a priority label changes inside a project page, the rollup updates automatically—meaning the system stays consistent as priorities evolve.
Next comes the “Task list,” which functions as an actionable inventory. Tasks can start as a mind-dump—everything that might need doing—then be sorted by priority so the work aligns with the project’s top priorities. The system also supports daily execution. A daily note can include a checklist (to-do items for that day), and those items can be backlink-linked to the project’s task list. Once linked, the task list becomes a living reference for what needs doing, while daily notes create a record of what was actually worked on.
Goals add a time-based planning layer. Instead of a single to-do list, goals are organized into cascading time increments: annual goals roll into quarterly goals, which roll into monthly goals, and then weekly goals. Daily tasks are handled separately in daily notes, while the goals pages use the same backlink logic to keep cross-project views updated. This structure is meant to reduce the mess that often appears when tasks and goals get out of sync: priorities inform goals, and goals inform tasks.
Two additional categories round out the system. “Project notes” stores contextual bullets—events, conversations, reminders—while “Project ideas” captures future possibilities that can be quickly found later. The system remains scalable: new projects can be added by pinning a new project page and reusing the same template structure, and retired projects can be removed from the active list without losing their historical backlinks. The result is a lightweight but expandable workflow where planning and execution stay connected through linked notes rather than separate spreadsheets or standalone task apps.
Cornell Notes
The system organizes personal project management inside a notes app by using linked pages for each project’s priorities, tasks, and time-based goals. Each project has its own “Top priorities,” “Task list,” and “Goals” sections, while separate rollup pages (like a single “Top priorities” view) automatically aggregate items across all projects via backlinks. Tasks can be mind-dumped, then prioritized, and daily checklists can be backlink-linked to the task list to track what gets done. Goals are structured as a cascade—annual to quarterly to monthly to weekly—so planning stays aligned with priorities. The approach is scalable: new projects can be added by copying the template structure, and old projects can be retired without losing linked history.
How does the system keep a cross-project “Top priorities” list accurate without manual copying?
What’s the practical role of the “Task list” compared with “Top priorities”?
How does the system connect daily work to project planning?
Why structure goals as annual → quarterly → monthly → weekly instead of a single list?
What purpose do “Project notes” and “Project ideas” serve in the workflow?
How does the system scale when adding or retiring projects?
Review Questions
- If a priority changes inside one project, which part of the system updates automatically, and why?
- How would you decide what belongs in “Task list” versus “Goals” in this setup?
- What backlink relationships would you create between a daily checklist and a project’s task list to track execution?
Key Points
- 1
Use pinned project pages as the source of truth for each project’s priorities, tasks, goals, notes, and ideas.
- 2
Create separate rollup notes (like “Top priorities”) that collect items via incoming backlinks from all project pages.
- 3
Start task lists with a mind-dump, then sort tasks by priority so daily work aligns with the project’s top priorities.
- 4
Plan goals in a cascading time structure—annual to quarterly to monthly to weekly—to keep tasks grounded in current objectives.
- 5
Backlink daily checklist items to the project task list so execution history stays connected to planning.
- 6
Add new projects by copying the template structure and pinning the new project page; retire projects by removing them from the active list while keeping backlinks for reference.