Getting Things Done: Microsoft OneNote Second Brain

TL;DR

Use Microsoft OneNote as a low-friction capture hub with a default destination in “Quick Notes,” so ideas are recorded immediately and synced across devices.

Briefing Cornell Notes

Briefing

A practical “second brain” setup using Microsoft OneNote turns David Allen’s Getting Things Done (GTD) idea—capturing thoughts outside the mind—into a working workflow that also supports Thiago Forte’s “CODE” method (Collect, Organize, Distill, Express). The core finding is that the app choice matters less than having a low-friction capture system that syncs instantly, then routing notes into the right buckets so they become actionable later rather than dead-ended scraps.

The workflow starts with capture. Using Microsoft OneNote, the creator sets OneNote’s default destination to a “Quick Notes” area inside a GTD structure. On a Surface Pro, handwritten notes and pen input are captured directly, while a phone-based OneNote badge enables quick additions: thoughts can be typed, and images can be snapped and automatically scanned. Notes are confirmed as they appear on the desktop and sync across platforms. The key behavior is intentionally low effort: whenever something might be useful later, it gets written down immediately; if it turns out not to matter, it can be deleted or archived. Over time, the system builds intuition about what deserves detail, because the capture step stays fast and forgiving.

Next comes organization, where the collected material is sorted into categories aligned with Forte’s framework: projects, project areas, resources, and archives. “Projects” hold active work—such as drafting an article from podcast notes—while “resources” store supporting material and “archives” preserve completed or inactive items. The creator also uses Microsoft To Do as the task execution layer, treating OneNote more like a capture and reference hub than a daily task manager. Examples include planning weekly reviews on Sundays, storing podcast highlights, brainstorming content ideas for a newsletter over time, and tracking research tasks related to Bayesian statistics and experimental design concerns.

Distillation reduces friction after capture. Raw notes can be messy, but the system’s purpose is to extract takeaways that can become publishable outputs. The creator describes distilling notes into usable conclusions—turning rough material into the “what matters” needed for an article or other deliverables.

Finally, “Express” closes the loop by turning distilled information into action and sharing. Blog posts, shared Notion pages, and Readwise quote sharing are treated as the end goal: notes aren’t just stored, they’re used to create. The creator also offers a pragmatic warning: starting with an overly complex GTD template can lead to unused features. A minimalist setup—like a single gift list or grocery list that grows over time—can build the same system gradually, using whatever tools fit the user’s habits. The takeaway is a workflow that offloads memory, organizes work, and reliably converts captured ideas into real outputs.

Cornell Notes

The workflow combines GTD’s central principle—offloading ideas from the brain—with Thiago Forte’s CODE method to make notes actionable. Microsoft OneNote serves as a fast capture layer using synced “Quick Notes,” including pen input and phone-based scanning so ideas can be captured in seconds. Notes then get organized into Projects, Project Areas, Resources, and Archives, with Microsoft To Do used for task execution rather than daily note-taking. Distillation turns messy raw notes into takeaways suitable for writing, and “Express” converts those takeaways into outputs like blog articles, shared pages, and quote sharing. The system matters because it reduces friction at capture while ensuring information eventually becomes work or publishing.

Why does the system emphasize capturing everything quickly instead of deciding usefulness immediately?

Capture stays low-friction: whenever something might be useful later, it gets written down in OneNote’s “Quick Notes.” The creator explicitly avoids overthinking at the moment of capture, then relies on later sorting and search. If a note turns out irrelevant, it can be deleted or archived. Over time, this builds intuition about what to keep and how much detail to add, without slowing down the flow of ideas.

How does organization turn scattered notes into a structure that supports action?

Collected notes are routed into categories aligned with Forte’s framework: Projects (active work like drafting an article from podcast notes), Project Areas (broader domains such as “Planning your week”), Resources (supporting material), and Archives (inactive/completed items). The creator also uses Microsoft To Do as the execution layer for tasks, keeping OneNote more focused on capture and reference.

What does “distill” mean in this workflow, and why is it separated from capture?

Distillation is the step where rough notes become usable takeaways. The creator notes that raw material can contain typos and clutter, so the goal isn’t to perfect it during capture. Instead, after organizing, the system reduces friction by extracting what matters—turning notes into the conclusions needed for an article or other output.

What does “express” look like when notes are meant to produce real outcomes?

“Express” is the conversion of distilled information into action and sharing. Examples include writing and publishing blog articles, sharing Notion pages, and using Readwise to share quotes. The system is designed so notes don’t remain static storage; they feed creation and communication.

What’s the practical advice for someone overwhelmed by GTD templates and tool sprawl?

Start minimalist and expand only as needed. The creator warns against importing a full GTD OneNote template and ending up with unused features. A simpler starting point—like maintaining a birthday and Christmas gift list or a centralized grocery list—can grow into a complete system over time. The “best tools” are the ones that match the user’s habits, even if that means adding Microsoft To Do, Readwise, Notion, or other apps later.

Review Questions

How does the workflow handle the tradeoff between fast capture and deciding what’s useful?
Describe the roles of OneNote versus Microsoft To Do in this system.
What steps connect raw notes to a publishable blog article in the CODE framework?

Key Points

1
Use Microsoft OneNote as a low-friction capture hub with a default destination in “Quick Notes,” so ideas are recorded immediately and synced across devices.
2
Rely on quick capture features—pen input on Surface Pro and phone-based scanning—so collecting information takes seconds, not minutes.
3
Organize notes into Projects, Project Areas, Resources, and Archives to separate active work from reference material and completed items.
4
Use Microsoft To Do for task execution rather than trying to manage daily action inside OneNote.
5
Distill messy raw notes into takeaways after organizing, focusing on what will actually be used for writing or other outputs.
6
Close the loop with “Express” by turning distilled information into actions like blog posts, shared pages, or quote sharing.
7
Start with a minimalist setup and add complexity gradually; importing a full template can create unused clutter.

Highlights

The system’s capture rule is simple: write down anything potentially useful immediately, then delete or archive later if it doesn’t matter.

OneNote functions as the “brain offload” layer, while Microsoft To Do becomes the execution layer for tasks.

Distillation happens after organization—raw notes can be imperfect, but takeaways must be extracted for real work.

“Express” is treated as the final step that turns notes into outputs like blog articles and shared content.

A minimalist starting point (like gift and grocery lists) can grow into a full GTD environment without template overload.

Topics

GTD
Second Brain
Microsoft OneNote
Microsoft To Do
Thiago Forte CODE