Block by Block 2022: Taking Notion to the max

TL;DR

Centralize tasks, documents, and internal communication in Notion to reduce tool-hopping and context switching.

Briefing Cornell Notes

Briefing

A tightly integrated Notion setup is being used to eliminate notification noise and “work grazing” by centralizing tasks, documents, wikis, calendars, and internal communication in one place. The practical payoff: fewer context switches, clearer expectations, and a workflow where overdue items and required reviews surface automatically in personalized dashboards—so people don’t have to hunt through email, Slack, or scattered Google Docs.

Rad Reads’ internal system is built around two goals: avoid the fire hose of pings that leads to shallow attention, and avoid bottomless email threads that mix assignments, comments, and to-dos into a single hard-to-audit mess. Instead, the company routes work through Notion dashboards and inboxes. Tasks and documents share the same “foundation” project layer, letting teams roll up related work without leaving the workspace. Communication is also streamlined: internal email is not used, Slack is barely checked, and review requests land in a “document inbox” where people can see what needs attention, who it’s assigned to, and when it’s due.

At the center of the task workflow is a customized prioritization framework called the “10k work framework,” which sorts tasks into quadrants based on skill and leverage (10k, 100, 1k, and 10,000 work are used as shorthand). The system then turns that framework into views that match how work actually gets done across a day: a “10k group view” lists the highest-priority tasks for the current morning, while “do soon” and “overdue” views filter incomplete tasks by due date using nested rules (for example, showing only items due within the next week). Visual metadata—energy levels, contexts, due dates, and assignment—acts as cues for what to tackle next.

Documents follow the same logic. Each document type (brainstorm, documentation, ongoing research) carries an explicit review expectation and a “reviewed by” field. Rules and filters ensure only relevant review items appear—such as documents needing review within the next week—so people can clear their inboxes by completing the required action. The result is a workflow where tasks and documentation are both managed through the same dashboard-driven structure.

Marie Poulin’s personal system extends the same customization philosophy, but through an ADHD-first lens. Her workspace is organized around “horizon” time scales (daily, weekly, monthly/quarterly-style thinking) and “theming” by energy and day-of-week. Instead of relying on a single productivity style, she uses color, icons, and Pomodoro-style visuals to prime focus, then anchors her day with a daily journal that functions like a structured log. The journal tracks intentions, feelings, a single “win,” activities, gratitude, challenges, and a practices database that scores the day—nudging her toward the behaviors that matter most.

Across both setups, the core message is consistent: Notion’s flexibility is most valuable when the architecture matches the person’s brain and the team’s workflow. Clear hierarchy, linked databases, and dashboard-first navigation replace scattered tools—turning remote and asynchronous work into something calmer, more predictable, and easier to sustain.

Cornell Notes

Rad Reads and Okey Dokey use Notion as a single operating system for tasks, documents, calendars, and internal communication, aiming to cut notification noise and prevent “work grazing.” Rad Reads builds dashboard-driven workflows with a custom “10k work framework,” then turns it into filtered views like “10k group,” “do soon,” and “overdue” using nested rules on due dates and completion status. Document reviews also land in a “document inbox,” where “reviewed by” fields and rules surface only what needs attention soon. Marie Poulin complements this with an ADHD-centered system: horizon-based planning, day-of-week “theming,” energy cues, and a structured daily journal that rolls up into practice scoring. The shared takeaway is that Notion works best when its architecture mirrors how people think and how teams coordinate.

How does Rad Reads prevent notification overload and context switching while using Notion for both tasks and communication?

Rad Reads explicitly avoids internal email and barely checks Slack, routing assignments and review requests through Notion dashboards and inboxes. Two pain points drive the design: (1) the “fire hose” of pings that causes content grazing and makes deep work harder, and (2) bottomless email threads that blend comments, assignments, and to-dos. Instead, tasks and documents share a common project “foundation,” and people check personalized task/document inboxes where due items and required reviews surface automatically. This reduces hunting across tools and keeps attention on the next actionable item.

What is the “10k work framework,” and how does it translate into daily execution views?

The “10k work framework” sorts tasks using a skill/leverage matrix (described as quadrants such as 10k, 100, 1k, and 10,000 work). The system then creates views that match how work is tackled across the day. In the “10k group view,” the highest-priority tasks for the current focus window appear (e.g., morning tasks tied to specific days). Tasks are linked to projects (“foundations”) and annotated with metadata like energy levels and contexts, so the dashboard becomes a cue-driven execution list rather than a generic task board.

How do “do soon” and “overdue” views work without showing irrelevant items?

The dashboards rely on filters and nested rules. For “do soon,” the rules show only incomplete tasks due within the next week, excluding items due later (e.g., due in two months won’t appear). For “overdue,” tasks with due dates earlier than the current date are flagged and displayed in a dedicated view. The overdue logic is implemented as a nested conditional that triggers a red-flag indicator when a task is past due.

How does the document dashboard replace the “frankenmonster” email + Google Doc workflow?

Documents in Notion carry explicit expectations (e.g., “review this document by March 3rd”) and a “reviewed by” field. Stakeholders are listed via properties, and rules filter documents so only those needing review within a defined window appear in a person’s document inbox. When someone completes the review, they update the “reviewed by” field, which clears the item from their inbox—so review status is tracked in one system rather than through scattered comments and threads.

What makes Marie Poulin’s system feel ADHD-friendly, beyond just using dashboards?

Her approach combines time-horizon planning with energy-based theming. She uses “horizon” pages so she doesn’t need to see everything at the daily level, which helps with time blindness. She also pre-decides which activities belong to which days of the week, then uses color and icons to prime focus (e.g., speech icons for events, green checkboxes for deep work, orange for administrative work). Her daily journal is structured and always visible, acting as an emotional regulation tool and a momentum builder rather than an open-ended notebook.

How does the daily journal connect to behavior change in her system?

Her journal entry includes an intention, feelings, and a single “win the day” task. It also links to a practices database where each practice has a value/score. As she marks which practices she completed, a daily score fills in; the system targets a high score (aiming for 100) and provides supportive messaging when the score is low (e.g., “are you okay” style encouragement). This turns reflection into a feedback loop that nudges her toward deep work and other chosen priorities.

Review Questions

What specific design choices help Rad Reads avoid both notification overload and bottomless email threads, and how do those choices show up in dashboards?
How does the “10k work framework” influence what appears in Rad Reads’ task views, and what metadata makes those views actionable?
In Marie Poulin’s system, how do horizon planning and day-of-week theming work together to reduce time blindness and improve follow-through?

Key Points

1
Centralize tasks, documents, and internal communication in Notion to reduce tool-hopping and context switching.
2
Use dashboard-first workflows with personalized task and document inboxes so due items and review requests surface automatically.
3
Build a prioritization framework (like the 10k work framework) and convert it into filtered views that match how work is executed across the day.
4
Link tasks and documents to a shared project layer (“foundation”) so expectations and progress live in one place without duplicating work across tools.
5
Replace scattered review workflows with document properties like explicit due expectations and “reviewed by” fields, supported by rules and nested filters.
6
Design personal systems around how attention and energy actually work—using horizon planning, theming by day-of-week, and cueing via color/icons.
7
Start with fewer database properties and add only what your team or brain consistently needs; then audit and refine over time.

Highlights

Rad Reads runs internal work with Notion as the single system—internal email is avoided and Slack is barely checked—so assignments and reviews land in dashboards instead of inboxes.

The “10k work framework” is turned into practical views like “10k group,” “do soon,” and “overdue,” using nested filters on due dates and completion status.

Document reviews are managed through properties and rules: “reviewed by” updates clear items from a person’s document inbox.

Marie Poulin’s ADHD-first design uses horizon-based planning and day-of-week theming, reinforced by color/icons and a structured daily journal that scores practices.

Both systems emphasize architecture: clear hierarchy, linked databases, and navigation that brings information to the user rather than making them search. 