Get AI summaries of any video or article — Sign up free
Notion Office Hours: Build With Me - Relational Databases 🗃 thumbnail

Notion Office Hours: Build With Me - Relational Databases 🗃

Notion·
5 min read

Based on Notion's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Treat creative work as a project with next steps and real visibility in the weekly agenda, not as an optional side intention.

Briefing

Relational databases in Notion aren’t the main productivity breakthrough here—turning creative work into visible, scheduled “projects” is. The session centers on a practical setup where creativity gets treated like client work: it lives inside the same task system, has next steps, and shows up in weekly planning so it doesn’t quietly fall off the radar.

A recurring theme is that time allocation beats tool obsession. Instead of hunting for a database trick to “balance life,” the workflow starts with deciding in advance when creative work will happen—whether that’s a dedicated weekly block or even 15 minutes a day. From there, the system uses dashboards and filtered views to surface the right context at the right time. The weekly agenda becomes the command center: tasks, personal projects, business work, and creative priorities are embedded together, with filters used to create a “creativity-first” dashboard when needed.

The relational engine behind the scenes uses connected databases, relations, rollups, and formulas to create progress and feedback loops. Goals connect to key results, which connect to next actions; progress can be calculated as a percentage between target and current values using formulas. Time is also structured through relations—years, quarters, months, and weeks are linked so that the same goals and projects remain visible whether the user is zoomed out or working day-to-day. Dashboards then pull in the relevant slices automatically.

Daily journaling and weekly review are built into this relational structure. Each week gets an agenda entry for every day, and those day pages relate to a master actions database. “Highlights,” gratitude, wins, and lows are captured in the daily journal format and roll up into the weekly view, making it easy to review patterns and stay motivated. Knowledge and learning also plug in through a “knowledge hub” database, which can be related to projects and goals so reading and course notes don’t become dead-end bookmarks.

The session also gets tactical about tracking effort and outcomes. Hours can be stored at the task level and rolled up to goals, or time can be replaced with impact/effort scoring (deep work, essential, small win, daily grind) to drive prioritization. For sales and revenue tracking, transactions imported from a sales database can be batch-assigned to a given week, then rolled up into weekly and monthly summaries.

Beyond the mechanics, the session offers guidance on managing complexity: duplicate databases for experimentation, archive completed projects rather than deleting them immediately, and design views that match how the user actually works. It also clarifies team constraints—sharing a filtered view with teammates isn’t possible without exposing the underlying database, so personal and team tasks often need separate databases.

By the end, the message is clear: relational databases are valuable because they make habits, goals, learning, and progress visible in the same place—especially in the weekly agenda—so creative work stays on the plan, not just in intention.

Cornell Notes

The core idea is to use Notion’s relational database features to make creative work and other priorities visible inside a weekly planning system. Creativity becomes a “project” with next steps and a scheduled time block, then gets surfaced through dashboards and filtered views. Connected databases (goals → key results → next actions) enable progress tracking via relations, rollups, and formulas, while daily journaling and knowledge capture roll up into weekly and monthly context. The payoff is faster feedback: it becomes easier to see what’s moving, what’s slipping, and what patterns emerge over time—without relying on memory or scattered notes.

How does the setup turn creativity into something that actually gets done?

Creativity is treated like client work: it’s placed into the same task/project system, given next steps, and shown in the weekly agenda. The workflow recommends scheduling a dedicated block (even 15 minutes a day) and then using dashboards/filters to surface creative items first when needed. A “creativity” dashboard can be created by duplicating the weekly agenda view and filtering to personal/creative items so the right context is always at the top.

What relational structure is used to compute progress bars?

Goals connect to key results, and key results connect to next actions. Target and current values are stored as numbers, and a formula calculates the percentage between them. Additional relations link time granularity (year/quarter/month/week), so the same goal progress can be viewed at different zoom levels (weekly agenda vs monthly vs yearly planning).

How do daily journals and weekly agendas work together in this system?

Each week has a daily agenda entry for every day. Day pages relate to master actions, so when the user marks highlights and completes journal fields (gratitude, wins, lows), those entries roll up into the weekly view. That means the weekly agenda can display a week’s worth of journal outcomes and encouragement without manual summarizing.

How can effort or time be tracked without making the system overly complicated?

Hours can be stored on tasks and rolled up to goals (e.g., a task has an hours value, and the goal page shows a rollup of those hours). Alternatively, the system uses impact/effort categories—deep work, essential, small win, daily grind—to prioritize without relying on precise time estimates. Formulas can even flag tasks that need delegation based on those categories.

What’s the practical approach to organizing PARA-style concepts (areas, resources, projects) with relational databases?

Areas function like ongoing responsibilities and “home pages” that contain embedded databases filtered by theme. Resources are more general reference material (guides, articles, videos) that support those areas, while projects are the actionable work that moves goals forward. The knowledge hub can be linked to projects and resources so notes and learning appear in the same context as execution.

Why are separate databases sometimes necessary for teams?

Filtered views can’t be shared with teammates without exposing the underlying database contents. To keep personal tasks private, the workflow recommends separating personal tasks from business/team tasks into different databases, then using each person’s dashboard to show only what’s relevant.

Review Questions

  1. If creativity is falling behind, what specific change would you make first: adding a creative project with next steps, or creating a filtered “creativity-first” dashboard? Why?
  2. Where in the relational chain would you store target/current values to compute progress—on goals, key results, or next actions?
  3. How would you design rollups so daily journal entries automatically summarize into weekly and quarterly reviews without manual work?

Key Points

  1. 1

    Treat creative work as a project with next steps and real visibility in the weekly agenda, not as an optional side intention.

  2. 2

    Schedule a recurring time block for creativity (even 15 minutes daily) and use filtered dashboards to keep creative context at the top.

  3. 3

    Build progress tracking by connecting goals → key results → next actions, then use formulas plus rollups to calculate target vs current completion.

  4. 4

    Use daily journal entries and highlights as relational data that roll up into weekly views to create motivation and feedback loops.

  5. 5

    Track effort either with task-level hours rolled up to goals or with impact/effort scoring categories to avoid over-measuring.

  6. 6

    Design views intentionally: duplicate and filter dashboards for different contexts (e.g., creativity vs business) rather than trying to make one view do everything.

  7. 7

    For team privacy, separate personal and team tasks into different databases because filtered views can’t be shared without exposing the underlying database contents.

Highlights

Creativity improves when it’s scheduled and treated like client work—next steps included—then surfaced through a creativity-first dashboard.
Progress bars come from relations plus formulas: target/current values at the goal level tied to key results and next actions.
Daily journal data can roll up into weekly context automatically, turning reflection into a built-in feedback mechanism.
Hours and outcomes can be rolled up from tasks to goals, or replaced with impact/effort scoring to drive prioritization.
Team sharing has a constraint: filtered views can’t be shared without revealing the underlying database, so privacy often requires separate databases.

Topics

Mentioned

  • Mike Vardy
  • PAR

Get summaries like this for any content

Videos, articles, research papers — all summarized by AI and searchable in one place.

Start building your library