Get AI summaries of any video or article — Sign up free
Block by Block 2022: Essential productivity setups thumbnail

Block by Block 2022: Essential productivity setups

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

Productivity is framed as two connected systems: action management (values → goals → projects → tasks) and knowledge management (capture → organize → resurface in context).

Briefing

A systems-first productivity setup in Notion hinges on one idea: connect goals, projects, and daily actions through relational databases so work stays aligned with values instead of drifting into disconnected task lists. The framework splits productivity into two engines—action management and knowledge management—and then uses Notion’s database linking, views, and dashboards to keep both engines feeding each other. Action management centers on defining guiding principles, turning long-term value goals into measurable outcome goals, and driving progress through a limited set of active projects and their tasks. Knowledge management complements that by capturing notes, journaling, media, and reflections, then resurfacing them in the right context using linked views.

The core “life operating system” example is the PPV pillars-pipelines-involved setup, organized around an “alignment zone” and an “action zone.” The alignment zone is designed to prevent the classic failure mode: writing goals down and then forgetting them because they sit in a drawer. Instead, high-level aspirations connect down through layers of structure—pillars that categorize life domains (like personal growth, business/career, or home), value goals that reflect what feels emotionally meaningful, and outcome goals that are tangible and trackable. Projects sit in the middle as the mechanisms for reaching outcome goals, with tasks and action items underneath. A key operational rule is limiting active projects so progress doesn’t stall under too many parallel commitments.

Notion’s relational features make the system “emergent,” not just organized. Goals link to projects; projects link to tasks; and rollups can pull related information across those links so dashboards automatically update. From there, the action zone filters tasks to show only what matters today, using due dates so daily planning becomes a focused queue rather than a distraction-filled to-do list. A “command center” ties everything together—accessing the alignment zone, knowledge vault, and review cycles—while favorites and multiple views keep the most relevant work one click away.

The session also addresses how to build this from scratch without getting lost in Notion’s flexibility. The recommended starting point is a proven system (like PPV) and then customizing it, because the harder skill isn’t learning Notion’s interface—it’s adopting systems thinking, where the whole is more powerful than isolated components. A demo walks through creating three linked databases (goals, projects, tasks) using Notion’s relation property, then optionally adding rollups for automatic context.

In the second half, Francis Sadera Matthews shifts from productivity mechanics to a more personal “happiness bar” journaling dashboard built in Notion. The journal begins as a flexible database-based calendar, then adds interactive properties like workout check-ins and mood tags that update directly on the calendar. Linked database views create contextual slices such as “best day” entries, and filters generate different perspectives (for example, by mood or by tags). The design emphasis is deliberate: Notion is treated as a possibility tool, not a spreadsheet substitute—using callouts, white space, and even GIFs (sourced from Giphy.com) to make the system inviting enough to use consistently.

Cornell Notes

The productivity approach centers on building a connected Notion system where values guide goals, goals drive projects, and projects generate daily tasks. Action management is organized through an alignment zone (pillars, value goals, outcome goals, projects, tasks) and an action zone that filters tasks to what’s relevant today. Knowledge management complements this by capturing notes, journaling, media, and reflections, then resurfacing them in context using linked views and filtered databases. The PPV example relies on Notion relations and optional rollups so dashboards update automatically as links change. The practical takeaway: start from a proven system, then customize it—systems thinking matters more than mastering every Notion feature.

How does the PPV “alignment zone” prevent goals from becoming forgotten lists?

It links aspirations to daily execution. High-level value goals connect to measurable outcome goals, which connect to projects, which connect to tasks. Pillars categorize life domains (e.g., personal growth, business/career, home), so filtering and visibility stay consistent across the system. Instead of storing goals in isolation, the system creates connective layers that track progress and determine which tasks belong in the daily view.

What’s the operational difference between the alignment zone and the action zone?

The alignment zone focuses on choosing the right work by aligning daily/hourly tasks with values and aspirations. The action zone then filters tasks to show only what’s relevant for today, using due dates so the daily queue is clear and distraction-resistant. The command center ties both zones together with access to knowledge vault and review cycles.

Why does the system emphasize limiting active projects?

Too many active projects create a flood of tasks that none of them meaningfully advance. The setup aims for a small number of projects that are actively progressing, so daily action items actually move outcome goals forward rather than spreading effort thinly.

What does Notion’s relation and rollup functionality add to this workflow?

Relations connect entries across databases (goals → projects → tasks). Rollups can then pull related data across those links so higher-level views automatically reflect lower-level progress. In practice, tasks can be filtered “for today” while still inheriting context from the linked goal/project structure.

How does the journaling dashboard use database views to create “contextual resurfacing”?

The journal is built as a database-backed calendar with properties like workout check-ins and mood tags. Linked database views create slices such as “best day” entries by filtering on a property (e.g., best day checked). As new entries are added, those contextual views update automatically, surfacing relevant past reflections when needed.

What’s the recommended approach when Notion “isn’t working” for someone?

Start from a proven system and customize it rather than designing from scratch immediately. The hardest part is adopting systems thinking—treating the whole as more powerful than isolated components—then using Notion’s flexibility to tweak and re-engage when drift happens. Notion features like calendar views can help quickly reset due dates and get back into motion.

Review Questions

  1. If goals, projects, and tasks are not linked via relations, what breaks in the alignment-to-action pipeline?
  2. How would you decide which projects should be “active” in this system to avoid overwhelm?
  3. What kinds of journal properties (mood tags, workout checks, bookmarks) would you add to enable useful filtered views?

Key Points

  1. 1

    Productivity is framed as two connected systems: action management (values → goals → projects → tasks) and knowledge management (capture → organize → resurface in context).

  2. 2

    The PPV example uses an alignment zone to connect aspirations to daily work and an action zone to filter tasks to what matters today.

  3. 3

    Pillars categorize life domains so sorting and filtering stay consistent across goals, projects, and tasks.

  4. 4

    Relational links in Notion (goals↔projects↔tasks) create automatic context, and rollups can propagate related information across those links.

  5. 5

    Limiting active projects prevents progress from stalling under too many parallel task streams.

  6. 6

    When building in Notion, systems thinking matters more than feature mastery; start from a proven structure and customize it.

  7. 7

    A database-backed journal can become a life dashboard by adding interactive properties (mood, workout, bookmarks) and using linked filtered views for contextual resurfacing.

Highlights

The system’s daily clarity comes from filtering tasks “for today” while still inheriting context from linked goals and projects.
The classic problem of goals sitting in a drawer is addressed by relational connections that keep daily actions tied to long-term aspirations.
Francis’s “happiness bar” journal turns journaling into an actionable dashboard by using mood tags and linked views like “best day.”
Notion is treated as a possibility tool: design choices (callouts, white space, GIFs) are used to make the system usable, not spreadsheet-like.

Mentioned