Get AI summaries of any video or article — Sign up free
Building a better thinking environment thumbnail

Building a better thinking environment

5 min read

Based on Linking Your Thinking with Nick Milo's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Separate capture from ideation: keep note taking in productivity spaces and reserve a cleaner area for note making and concept play.

Briefing

A cluttered notes system can quietly sabotage deeper thinking, and Justin Horton’s Obsidian setup is built to prevent that by separating “note taking” from “note making.” The core move is structural: he treats time-stamped capture and external reference as a productivity runway, while reserving a cleaner, less burdened space for idea play, synthesis, and concept development. The result is an “integrated thinking environment” designed to reduce day-to-day noise so higher-level work has room to happen.

Horton frames the problem in personal terms—years of taking notes that eventually became “absolutely cluttered” and harder to process than to use. He connects that experience to a broader productivity principle popularized by David Allen’s Getting Things Done: clearing the runway at lower levels so attention can rise to higher levels. In Horton’s case, the clutter isn’t just volume; it’s mixing functions. When capture, organization, and ideation live in the same place, the system pulls him into busy work and keeps him from thinking.

To address that, he borrows the “exocortex” idea—an externalized extension of the mind—then translates it into an Obsidian vault he calls “exocortex.” The sci-fi inspiration (Tony Stark’s workshop) is more flavor than function; the practical influence comes from Charles Strauss’s Accelerando and the broader “extended mind” conversation. The key takeaway is operational: build a dedicated note-taking system that reliably stores inputs, and a separate note-making space where ideas can be explored without the pressure of getting things “right.”

His vault is organized around eight main components, anchored by an “Idea Lab” at the center. That area stays intentionally tidy and concept-focused, supported by a “MOC” (map of content) layer used to collect and connect materials for processing. For note taking, he uses a “Log Book” for time-stamped entries, organized by year to avoid an unmanageable sprawl. He also splits incoming reference into “External Sources” (notes on books, videos, and similar materials) and a “Resource Library” for support files such as images and Obsidian-related assets.

Utility functions sit alongside but do not dominate the thinking spaces. “Workspaces” acts as a hybrid holding area for day-job projects where rough material can be dumped and cleaned later. A “Toolbox + Inbox” combination supports quick capture (the inbox) and navigation as the library grows, including dashboards and early experiments with Dataview to surface recently changed or created notes. Finally, a “Home note” serves as the common access point tying everything together.

Horton’s daily workflow reinforces the separation. He uses a home/daily hybrid note that links out to task and planning tools (OmniFocus, Fantastical, and time tracking) so he can check commitments quickly, then take notes during the day. Meeting notes and other working documents become part of a PKM-style productivity loop—useful for connecting ideas—while the system’s design goal remains consistent: keep the environment out of the way so deeper thinking can actually happen. The setup is presented as a starting point, not a finished product, meant to evolve as his needs change.

Cornell Notes

Justin Horton’s Obsidian “exocortex” setup is designed to make deeper thinking easier by separating note taking from note making. He treats capture and reference as a productivity runway—time-stamped “Log Book” entries, “External Sources” for books/videos, and a “Resource Library” for support files—so they don’t crowd out ideation. At the center sits an “Idea Lab” kept tidy for concept play, supported by MOCs to map and process information. Utility areas like “Workspaces” and a “Toolbox + Inbox” handle rough dumping and later cleanup, while dashboards and Dataview help navigation as the library grows. The payoff is a system that reduces clutter-driven busywork and gives higher-level thinking more room.

Why does separating note taking from note making matter more than simply “using Obsidian for everything”?

Horton says mixing functions makes him get in his own way. When capture, organization, and ideation share the same space, the system pulls attention toward busy notes instead of concept development. His approach keeps note taking as a productivity pipeline (time-stamped logging and reference storage) while note making happens in a dedicated, cleaner “Idea Lab” where ideas can be explored without the pressure to be correct immediately.

How does Horton use the “runway” concept to protect higher-level thinking?

He connects his experience to David Allen’s Getting Things Done emphasis on clearing the runway at lower levels so attention can rise to higher levels. In practice, Horton builds a structured capture and storage layer—Log Book, External Sources, Resource Library—so the rest of the system doesn’t become a cluttered dumping ground that blocks synthesis and deeper work.

What roles do the “Idea Lab” and MOC play in his vault?

The “Idea Lab” is the heart of the system: a tidy zone focused on playing with concepts and ideas, with no time stamps or heavy structure. Surrounding it is the MOC side, where materials are collected and mapped so they can be processed and connected. This division keeps ideation clean while still enabling later synthesis through structured navigation.

How is Horton’s note-taking storage segmented to avoid clutter?

He uses multiple dedicated areas: the “Log Book” for time-stamped entries organized by year; “External Sources” for notes derived from books, videos, and similar inputs; and a “Resource Library” for support files like images and Obsidian-related assets. Segmentation prevents everything from landing in one place and becoming hard to process.

What utility spaces support the system without dominating it?

“Workspaces” is a hybrid holding area for day-job projects where rough material can be shoveled in without getting it right immediately, then cleaned later. A “Toolbox + Inbox” supports frictionless capture (inbox) and navigation (dashboards and early Dataview experiments), such as finding notes created or changed in the last week as the library expands.

How does Horton connect the vault to daily execution?

His daily workflow uses a home note/daily note hybrid that links out to task and scheduling tools—OmniFocus for task lists, Fantastical for calendar checks, and a toggle for time tracking. During the day, he takes notes tied to what he’s doing (including meeting notes), using the PKM-style connections for productivity while relying on the vault’s structure to keep ideation accessible.

Review Questions

  1. What specific problem Horton describes happens when note taking and note making are kept together, and how does his vault structure prevent it?
  2. Describe the difference between the “Idea Lab” and the “Log Book” in Horton’s system, including what each is optimized for.
  3. How do MOCs, Dataview, and dashboards work together to help navigation as the Obsidian library grows?

Key Points

  1. 1

    Separate capture from ideation: keep note taking in productivity spaces and reserve a cleaner area for note making and concept play.

  2. 2

    Use a “runway” mindset so lower-level clutter doesn’t block higher-level thinking, aligning capture structure with deeper work.

  3. 3

    Center the system around a dedicated ideation zone (“Idea Lab”) and support synthesis with MOCs rather than mixing everything into one stream.

  4. 4

    Segment inputs by purpose: time-stamped logging (Log Book), external references (External Sources), and support assets (Resource Library).

  5. 5

    Add utility areas for rough dumping and later cleanup (Workspaces) so unfinished material doesn’t pollute thinking spaces.

  6. 6

    Use an inbox for frictionless capture, then rely on dashboards/Dataview to navigate and surface recently changed or created notes.

  7. 7

    Create a single common access point (Home note) and link daily execution tools so the vault supports work instead of becoming another chore.

Highlights

Horton’s central fix is structural: separating note taking from note making so busy capture doesn’t crowd out deeper thinking.
The “Idea Lab” is intentionally kept tidy and concept-focused, while time-stamped logging lives elsewhere in the “Log Book.”
His vault uses segmentation—External Sources and a Resource Library—to prevent reference material from turning into clutter.
Dataview and dashboards are used as navigation aids for a growing library, not as replacements for a thinking workflow.
A home/daily hybrid note links out to OmniFocus, Fantastical, and time tracking to speed up day-to-day execution.

Mentioned