Mental Inventory in Obsidian

TL;DR

Start with a full brain dump to externalize every task and idea that’s causing mental load.

Briefing Cornell Notes

Briefing

When stress builds because too many tasks live in someone’s head, a “mental inventory” workflow can turn that overload into a prioritized, actionable plan. The core move is a structured brain dump followed by splitting every item into three buckets—what’s currently being worked on, what should be done, and what someone wants to do—so competing priorities become visible and easier to sort. The method matters because it restores momentum when planners stop working, replacing vague guilt and scattered intentions with concrete next steps.

The process starts with a fresh page (or a dedicated workspace in Obsidian) and a full brain dump: every task, obligation, desire, and lingering idea that feels overwhelming. In the example, the list is long and mixed—work prep for onboarding a new team member, learning the Go programming language, converting meeting diagrams into wireframes, finishing a presentation-related “film the fallout,” paying a medical bill, uploading a podcast recorded weeks earlier, and turning a time-blocking article into a short ebook. The point isn’t to finish everything; it’s to capture the full inventory so the mind stops “holding” it.

Next comes the three-column split. “Working on” holds the most immediate commitments. “Should” captures the less exciting but important items—things that trigger guilt when ignored, such as prerequisite work for a speaking opportunity, converting research into permanent notes, or handling practical chores like insulating a garage (crossed off when it’s not critical yet). “Want” lists the appealing ideas that still compete for attention, like watching or reading additional content, exploring tutorials, or starting community projects. Items get crossed off as they’re judged against the context of everything else in the same bucket, which makes decisions less arbitrary.

A key refinement is what happens after the cut: tasks that survive the inventory get moved into a planner for the near future, while the rest roll forward. Instead of dumping everything into a distant “future log,” the workflow breaks tasks into something actionable and schedules them into the current week or next week. In the example, onboarding work is converted into concrete steps (setting up a teams meeting, preparing onboarding instructions, and filling out a form). Other items are assigned to specific days—reading and progress on Go, printing an article for weekend reading, cleaning up the Obsidian vault, and converting a roadmap into a wireframe task.

The result is a day that’s no longer dominated by mental noise. The planner becomes the “rails” that keep work from derailing, with time blocks for deep work, a shallow batch for miscellaneous tasks, and checkable items that reduce stress. The workflow is presented as a digital adaptation of a mental-inventory exercise from the Bullet Journal system by Carol, with tweaks that make it practical inside Obsidian.

Cornell Notes

A mental inventory workflow turns an overwhelming brain dump into a prioritized plan. First, all tasks and ideas are captured in one place, then split into three buckets: what’s being worked on, what should be done, and what someone wants to do. Crossing items off becomes easier because each task is judged in context against competing priorities. After deciding, the remaining tasks are converted into actionable steps and moved into a near-term planner (days and next week), rather than being buried in a distant future log. The payoff is less stress and clearer momentum because the planner regains control when the mind stops being able to hold everything.

Why does the workflow start with a “brain dump,” and what problem does it solve?

It prevents tasks from living only in working memory. When the list grows too large, the person stops using a planner because there’s “too much in my head,” which creates stress and derails motivation. Writing everything down—tasks, desires, obligations—produces a complete inventory so decisions can be made from a visible list instead of vague guilt.

How do the three buckets (“working on,” “should,” “want”) change decision-making?

They separate tasks by urgency and emotional weight. “Working on” holds immediate commitments. “Should” contains less desirable but important items that trigger guilt when ignored (e.g., converting a diagram into wireframes, prerequisite work for a speaking opportunity, or back-porting research into permanent notes). “Want” lists appealing ideas that still compete for time (e.g., tutorials, community projects, extra content). Seeing them side-by-side makes it easier to cross off what loses to higher-priority items.

What does crossing off an item accomplish beyond “not doing it”?

Crossing off is a decision mechanism. Items that aren’t worth doing now are removed from the current cycle and either resurface later or get moved into the next planning window. In the example, “AirPods” gets crossed off during a walking meeting because it’s not urgent, while other items are moved to a later migration stage and scheduled for subsequent weeks.

How does the workflow prevent future overload when moving tasks into a planner?

It avoids dumping everything into a distant future log. Instead, tasks that survive the inventory are broken into actionable steps and scheduled into the current day or next week. The logic is that worrying about months of backlog increases overload and leads to not working on the right tasks.

What kinds of tasks get turned into concrete planner items?

Both work and personal maintenance tasks. Examples include onboarding a new team member (setting up a Teams meeting, preparing onboarding instructions, and filling out a form), learning Go (reading in a dedicated time block), converting a roadmap into a wireframe task, printing an article for weekend reading, cleaning up the Obsidian vault, and importing permanent notes.

Review Questions

What are the three categories used in the mental inventory, and how does each category influence which tasks get scheduled first?
Describe the difference between moving tasks into a near-term planner versus a distant future log in this workflow.
Give two examples of tasks that would likely fall into “should” versus “want,” and explain why.

Key Points

1
Start with a full brain dump to externalize every task and idea that’s causing mental load.
2
Split items into three buckets: currently being worked on, should-do (important/guilt-inducing), and want-to-do (appealing but competing).
3
Crossing off items becomes easier when tasks are judged in context against other tasks in the same bucket.
4
Move only the surviving tasks into a near-term planner by converting them into actionable steps.
5
Avoid burying tasks in a distant future log; schedule for days and the next week to reduce overload.
6
Use time blocks for deep work and a separate “miscellaneous” batch so small tasks don’t derail scheduled progress.
7
Treat the inventory as a stress trigger: when planners stop working and stress rises, rerun the mental inventory to regain control.

Highlights

The method’s core is a structured brain dump followed by a three-column split that makes competing priorities visible.

Crossing off isn’t just deletion—it’s a decision that determines what gets scheduled now versus rolled forward.

A near-term planner beats a distant future log because it reduces the anxiety of months of unresolved backlog.

Obsidian can host a digital version of the mental inventory, turning vague overload into checkable daily and weekly actions.

Time blocking plus a “shallow batch” for miscellaneous tasks helps keep momentum without letting small chores take over.