Project Management Made Simple in Notion (With Some Surprisingly Powerful Little Features 👀)

A simple two-database setup in Notion can turn project tracking into a structured workflow: create projects, attach tasks, generate project-specific views (including a timeline/Gantt-style layout), and archive completed work. The core idea is to keep everything anchored to a Projects database and a Tasks database, then use filtered “Project View” pages to show only what matters for a single client or business area.

The workflow starts with creating a new project from either the home dashboard or the Projects page. Projects are organized under business areas, with an “archive” area for completed items. When adding a project, the system uses a project template button to prefill helpful fields—optionally including a prioritization tool that scores projects using inputs like cost impact and urgency. The example walks through creating a short “Acme Inc” branding project with an end date, then moving to task creation.

Tasks are managed in a Tasks database that can be viewed by status (including highest-priority tasks) or by project. After removing sample tasks, the process shifts to adding real tasks to the newly created project. One approach is to link tasks directly to the project via database relationships. Another, highlighted as “quite neat,” is to create a dedicated project view and then drag tasks into a timeline. This drag-and-drop isn’t creating a duplicate; it updates the existing task records by setting start/end dates and assigning the task to the correct project.

To make project views truly specific, the system creates a “new project view” page and configures it with two key settings: a progress bar tied to the project’s name property, and filters that restrict both the project view and its tasks to the relevant project (e.g., “Acme branding” for Acme Inc). Once configured, the view provides an overview, a progress section, and a timeline that functions like a lightweight Gantt chart—showing task order and project progress over time. Marking tasks as done updates the project progress bar automatically.

Finally, the system handles cleanup through archiving. Completed tasks can be moved into an archive view, and projects can be archived from the timeline as well. The result is a clean separation between active work and historical records, without losing the underlying task and project data.

The setup ends with a clear takeaway: with just two databases (Projects and Tasks) plus a few configured project view pages, teams can quickly add tasks, track progress within each project, and generate focused views. From there, the structure can be expanded—adding contacts, objectives, or KPIs and linking them back to each project—while keeping the same core workflow intact.