Get AI summaries of any video or article — Sign up free
My 2023 Obsidian Workflow for Note-Taking and Templated Thinking thumbnail

My 2023 Obsidian Workflow for Note-Taking and Templated Thinking

Systematic Mastery·
5 min read

Based on Systematic Mastery's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Treat the second brain as a daily decision tool: optimize for reduced friction in capture and follow-up, not for elaborate setups.

Briefing

Templated thinking in Obsidian is presented as a practical way to turn a “second brain” from a hobby into a daily decision-making system—by lowering the friction of capturing ideas and by using structured prompts to improve how people plan, reflect, and choose. The core message is blunt: productivity setups only matter if they change day-to-day behavior and help reach real goals, not if they consume time through endless tool optimization.

The workflow starts with consistency. Instead of relying on long note sessions at a computer, the system emphasizes quick capture and later refinement. For that, the creator uses an inbox approach: Todoist for quick capture tasks, and iA Writer for fast markdown-style writing that can be synced across devices. Notes live in cloud storage and are mirrored to an iPhone and macOS devices, keeping the same structure across Apple hardware. The key behavioral insight is that the “threshold” to use a second brain is often too high—people don’t have time to organize during the day—so the system intentionally creates small, low-effort actions that keep ideas “alive” until later. Quick capture, reflections, and knowledge mapping are highlighted as the main areas where this friction reduction pays off.

From there, the workflow adds feedback loops that make thinking measurable. Daily notes include a “productivity plan” built around Pomodoro estimates, plus end-of-day metrics like flow and engagement rates. A minor reflection prompt is used to increase self-awareness—tired, stressed, or otherwise—because that awareness supports better self-regulation. An energy log tracks variables such as fasting time, coffee intake, meditation, workouts, and a deep work score, with the creator stressing that strictness isn’t required; “good enough” tracking supports continual improvement. A to-do mechanism is also embedded so tasks can be created inside notes and revisited later.

The most concrete implementation is the daily note template, generated automatically via the templater plugin and tied into Obsidian’s Daily Note plugin settings. Macros like tp date, tp yesterday, and tp date f (week number) populate fields automatically. The daily note also links to a “workbench” note via the Workbench plugin, serving as a running scratchpad for work-in-progress items so unfinished tasks don’t vanish. In practice, the creator links daily notes into weekly reflections and uses local graph views to navigate from weeks to days to meetings.

Several additional templates extend the same idea of structured thinking: - A postmortem template for fast, blame-light reflection after mistakes, designed to preserve lessons and check whether they were applied later. - A decision journal template inspired by Atomic Habits, aimed at big decisions by forcing consideration of current state and consequences. - A mesocycle template (four to five weeks) for training goals like calisthenics progress, including measurement exercises and “focus exercises” when motivation or energy is low. - A meeting template that keeps notes lightweight: agenda, discussion topics, and action points, with notes linked to the day and optionally parked in the workbench for later follow-up.

Overall, templated thinking is framed as a way to build a personal system of prompts—questions tailored to weaknesses—so the second brain becomes an externalized product that improves decision quality through repeated feedback, not a static archive.

Cornell Notes

The workflow treats Obsidian as a decision-support system built on “templated thinking,” where templates reduce friction and turn reflection into actionable feedback. Consistency is achieved through quick capture (inbox-style notes) and daily notes that are auto-generated using the templater plugin with macros like tp date and tp yesterday. Daily notes also embed planning (Pomodoro-based estimates), self-awareness prompts, and an energy log to track engagement and deep work. A workbench note collects work-in-progress so unfinished items don’t disappear, and graph views connect daily notes to weekly reflections and meeting notes. Additional templates—postmortems, decision journals, mesocycles, and meetings—extend the same structure to learning, big choices, training cycles, and meeting follow-through.

Why does the workflow emphasize quick capture instead of perfect note-taking sessions?

It targets the real bottleneck: the “threshold” to use a second brain is often too high. People may not have time to sit at a computer for organizing or thinking. By capturing ideas immediately (via an inbox approach using Todoist and fast markdown capture in iA Writer), the system keeps thoughts available for later refinement. The creator argues that capturing items you still want to work on—plus reflections and knowledge mapping—helps integrate the second brain into daily life rather than leaving it as an occasional project.

How does the daily note template automate structure, and what role do plugins play?

The daily note template is generated automatically using the templater plugin, configured in the Obsidian Daily Note plugin settings. Macros such as tp date (current date), tp yesterday (previous day), and tp date f (current week number) populate fields without manual setup. This automation lowers friction so daily notes are created quickly and consistently, and it supports linking daily notes into a larger weekly reflection workflow.

What is the “workbench” for, and how does it prevent work from getting lost?

The Workbench plugin provides a single running note where items can be added from anywhere. The creator links the workbench into the daily note so it becomes a prompt to revisit work-in-progress. This addresses a common failure mode: forgetting what’s unfinished (work in progress) and losing overview. By parking meeting follow-ups or tasks in the workbench, the system makes later completion easier without forcing immediate deep work.

What metrics and prompts are used to turn daily reflection into feedback?

Daily notes include a productivity plan with Pomodoro estimates (the creator estimates time in pomodoros and maps that to hours). End-of-day fields track flow and engagement rates, and a minor reflection prompt captures short self-awareness notes like being tired or stressed. An energy log tracks variables such as fasting time, coffee intake, meditation, workouts, and a deep work score. The creator stresses that tracking doesn’t need to be strict; “good enough” data supports continual improvement.

How do the postmortem and decision journal templates differ in purpose?

A postmortem is a fast reflection after a bad event or mistake, focused on what happened, how it was resolved, what was learned, and whether the lesson can be applied or shared later. A decision journal is used before big decisions to force rational thinking about current state and consequences; it’s recommended for impactful decisions rather than small ones. Both rely on structured prompts, but one targets learning from outcomes while the other targets improving choice quality upfront.

How does the meeting template balance note-taking with actually attending the meeting?

The meeting template stays intentionally simple to avoid context switching. It uses an agenda (when available), a topics section filled with keywords during the meeting, and action points captured at the end. The creator notes that agendas rarely cover everything discussed, so topics are treated as the flexible core. If follow-up work can’t be done immediately, the meeting note can be linked to the workbench for later expansion.

Review Questions

  1. Which parts of the workflow are designed specifically to reduce friction, and how do they change daily behavior?
  2. How do templater macros (like tp date and tp yesterday) support linking daily notes into weekly reflections and graph navigation?
  3. What distinguishes a postmortem template from a decision journal template in timing and intended outcome?

Key Points

  1. 1

    Treat the second brain as a daily decision tool: optimize for reduced friction in capture and follow-up, not for elaborate setups.

  2. 2

    Use an inbox-style capture system so ideas enter the system immediately, then get structured later when time allows.

  3. 3

    Generate daily notes automatically with templater macros configured through the Daily Note plugin to keep structure consistent without manual effort.

  4. 4

    Embed planning and feedback loops in daily notes using Pomodoro estimates, flow/engagement ratings, and short self-awareness prompts.

  5. 5

    Use the Workbench plugin as a single place for work-in-progress so unfinished items don’t vanish and can be revisited efficiently.

  6. 6

    Apply specialized templates—postmortems, decision journals, mesocycles, and meetings—to make reflection, choices, training cycles, and meeting follow-through repeatable.

Highlights

The workflow’s central constraint is friction: the system is built to make capture and later review easy enough to happen even on busy days.
Daily notes are auto-filled via templater macros (tp date, tp yesterday, tp date f), turning routine structure into a near-zero-effort habit.
A workbench note acts like a “home” for work-in-progress, linking meetings and tasks back into daily and weekly review.
Templates are treated as feedback instruments—postmortems preserve lessons, decision journals improve big choices, and mesocycles keep training goals top-of-mind.

Topics

Mentioned