Get AI summaries of any video or article — Sign up free
Notion Fundamentals | Supercharge your productivity with Khe Hy thumbnail

Notion Fundamentals | Supercharge your productivity with Khe Hy

Notion·
6 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

Use a two-by-two matrix of leverage (amplification) and skill (growth) to classify tasks into 10/100/1k/10k work rather than relying on generic urgency labels.

Briefing

The core message centers on a 10k productivity framework that pushes people to spend more time on “10k work”—high-leverage, high-skill tasks that compound over time—rather than getting stuck in low-leverage busywork like constant inbox management. The framework matters because it reframes productivity from “doing more” to “doing the right things,” tying day-to-day task choices to long-game outcomes, motivation, and even joy.

The system is built as a two-by-two matrix. One axis measures leverage—how much an effort can amplify results (for example, one-to-one work versus one-to-many work). The other axis measures skill—whether the work is low-skill or high-skill. Moving through the quadrants scales from 10 to 100 to 1,000 to 10k work. Leverage examples include teaching, writing, management, or building a learning culture—activities that multiply impact beyond a single moment. Skill examples show up in tasks that require growth and focus rather than routine execution.

A key distinction separates “efficient” execution from “effective” progress. The talk contrasts low-leverage, low-skill tasks that can be done while distracted or drained (even with a headache or hangover) with deeper, harder work that requires attention and commitment. “10 work” is framed as dopamine-inducing and immediately gratifying, while 10k work is “playing for the long game.” The emphasis isn’t money alone; it’s treated as a force-multiplier mindset. If checking email is “dollar work,” then writing a standard operating procedure or documenting processes can be “ten times” more impactful; learning a new skill can be “hundreds” more impactful; and activities like building relationships, finding mentors, or creating new capabilities can be “thousands” more impactful.

To make the framework usable, the session demonstrates building a task manager inside Notion using a database table. The database starts with columns that map directly to how tasks should be judged and scheduled: a task name, a done checkbox, a due date, a “task value” select field with options for 10/100/1k/10k, and multi-select tags for contexts like home/work and energy levels (high vs. low). After entering example tasks—such as getting to inbox zero (10), creating onboarding process documentation (100), enrolling in a writing course (1k), and finding a mentor (10k)—the system becomes actionable through Notion features.

Filtering and views turn the same underlying data into different daily lenses. Completed tasks can be hidden via filters without deleting them. The same task set can be displayed as a calendar view or a Kanban board grouped by task value. Templates let users create repeatable task types—like a pre-filled “10k task” with a rocket emoji—so capturing high-value work becomes faster.

A downloadable “advanced” template extends the model with projects and domains (ongoing areas of life that don’t truly end), plus formulas for overdue flags, recurring task templates, and multiple views such as overdue-by-date and grouped task-value dashboards. Quick capture buttons support adding tasks on the fly and automatically routing them into the right filters.

In Q&A, recurring tasks are handled through practical options: creating multiple dated instances, using recurring templates with manual due-date updates plus review routines, or automating via Zapier for those comfortable with APIs. Overwhelm is managed through metadata and multiple views—filtering tasks by energy level, time of day, or responsibility—paired with a weekly review to catch “leaky pipes.” For archiving, the guidance leans toward keeping tasks and relying on views/filters rather than deleting, since large databases remain workable. The session closes by urging a daily 25-minute commitment to 10k work and treating the search for 10k work as a question: what needs improvement or what’s blocking progress?

Cornell Notes

The 10k productivity framework uses a two-by-two matrix to classify tasks by leverage (how much they amplify outcomes) and skill (how much growth and expertise they require). Tasks are scaled into levels—10, 100, 1k, and 10k—where 10k work is hard, high-skill, and compounding, while lower levels often feel good in the moment but don’t move long-term goals. A Notion task manager implements this with database fields like done status, due dates, “task value” (10/100/1k/10k), and multi-select tags for context and energy. Filters and multiple views (table, calendar, Kanban) let users focus on the right subset of tasks without deleting anything. Templates and quick capture make it easier to repeatedly log high-value work and review it regularly.

How does the 10k framework define “leverage,” and why does it change how someone should prioritize tasks?

Leverage is anything that amplifies the impact of work. The talk contrasts one-to-one efforts (lower leverage) with one-to-many efforts (higher leverage). Examples include communicating ideas at scale (like teaching or writing), managing others, or building a culture of education and learning. This matters because the same time spent on a low-leverage task (e.g., routine execution) can produce far less long-term value than a high-leverage activity that multiplies results beyond a single person or moment.

What does “task value” mean in the Notion setup, and how is it different from simple priority labels like high/medium/low?

Instead of using high/medium/low, the system uses a “task value” select field aligned to the matrix levels: 10, 100, 1k, and 10k. That forces a different prioritization lens: a task isn’t just urgent or important—it’s evaluated by where it sits on the leverage/skill scale. In the demo, inbox zero is treated as a 10 task, process documentation as 100, learning a writing course as 1k, and finding a mentor as 10k.

How do filters and views help prevent a task manager from becoming overwhelming?

Filters hide completed work and let users display only the tasks that match a condition (like done being unchecked). Views then present the same database in different formats without losing data—calendar view maps tasks to dates, and Kanban groups tasks by task value. This means the system can keep many tasks stored while still showing only what’s relevant for a given day or planning session.

What role do templates play in making 10k work easier to capture consistently?

Templates pre-fill fields so recurring or repeatable task types can be logged quickly. The demo shows creating a “10k task” template with a rocket emoji and a preset task value of 10k. When a new task is captured using that template (e.g., “study for gmat”), the task value and identifying emoji are already set, reducing friction and making high-value work more likely to get logged.

How should recurring tasks be handled inside the framework?

Three approaches are offered in Q&A. The simplest is creating multiple dated tasks (e.g., 12 rent-payment tasks for each month) and using filters to show only upcoming ones. A second approach uses a recurring template and requires manual due-date updates when it becomes due, supported by a review routine to ensure the due dates are refreshed. A third, more advanced option connects automation via Zapier on a schedule, which requires familiarity with APIs and typically a paid Zapier account.

Why does the guidance recommend keeping completed tasks rather than deleting or archiving them?

The guidance favors leaving tasks in the database and using views/filters to hide them. Large databases are described as workable even at scale, and search is expected to become less noisy over time. Archiving is treated as possible but cognitively risky because it requires matching fields exactly in an archive table; deleting is generally unnecessary for personal task managers.

Review Questions

  1. In your own workflow, what would count as high-leverage, high-skill work (10k) versus low-leverage busywork (10)?
  2. How would you design Notion fields and tags so that different parts of your day automatically surface the right tasks?
  3. What recurring-task strategy would you choose (multiple instances, recurring template with manual updates, or Zapier automation), and what trade-offs come with it?

Key Points

  1. 1

    Use a two-by-two matrix of leverage (amplification) and skill (growth) to classify tasks into 10/100/1k/10k work rather than relying on generic urgency labels.

  2. 2

    Treat 10k work as compounding, harder effort that may not feel immediately rewarding, and contrast it with low-leverage tasks that provide short-term dopamine.

  3. 3

    Build a Notion task database with fields that enforce the framework: done checkbox, due date, “task value” (10/100/1k/10k), and multi-select tags for context and energy.

  4. 4

    Use filters and multiple views (table, calendar, Kanban) to focus on the right subset of tasks without deleting older entries.

  5. 5

    Speed up capture with templates that pre-fill task value and identifiers (e.g., a rocket emoji for 10k tasks).

  6. 6

    Extend the system with projects and domains so tasks can be assigned to ongoing responsibilities and never-ending life areas.

  7. 7

    Manage overwhelm through metadata-driven views and a weekly review that checks tasks across different life lenses (work, family, habits).

Highlights

The 10k framework reframes productivity as a leverage-and-skill problem: the goal is not more activity, but higher-impact, compounding work.
Notion’s database views let the same task data power a calendar, a Kanban board grouped by task value, and filtered “today” lists without losing information.
Templates turn high-value work into a fast capture process by pre-setting task value (10/100/1k/10k) and other identifiers.
Recurring tasks can be handled with multiple dated instances, recurring templates plus manual due-date updates, or Zapier automation for scheduled creation.
Overwhelm is addressed by using tags (context/energy) and multiple views, then validating everything through a weekly review.

Topics