Video summary

5+ Years to Build the Perfect Obsidian Life Operating System

Main summary

Key takeaways

Educational

Main ideas / lessons

  • Most digital systems fail because information isn’t connected. People scatter meetings, tasks, journals, habits, and notes across many apps that don’t integrate—so PKM becomes storage instead of connecting ideas.

  • Don’t aim to make Obsidian an “everything app.” Use Obsidian as the single connected home for workflows that benefit from linkage (e.g., journal → habits → reflection → projects → writing → back to journal).

  • Reduce “seams” between tools. Every context switch between apps costs time and attention; over years those costs compound.

  • Use PKM multi-scale planning aligned to intentions. Daily actions roll up into quarterly retreat decisions, which then shape weekly/daily plans.

  • Behavior change comes from where you do the work. Habit tracking works better when embedded in the same place you already journal/capture daily notes—no notifications, no streak shame.

  • Dashboards make the system usable. DataView.js + structured note properties enable dashboards that visualize streaks, trends, quarter review metrics, and alignment with a “north star.”

  • Linking is the core power. Examples:

    • Bible verses as atomic notes enable sermon sketch notes to cross-reference verse-level links and topics.
    • Tasks beside project/person/context beat flat task lists.

Methodology / system structure (workflows and how they work)

1) Daily layer: Journaling with daily questions (effort-based)

Source of concept: Marshall Goldsmith’s book Triggers.

Daily prompt format:

  • Use questions beginning with: “Did I do my best to ___?”
  • Rate each prompt on a 1–10 scale:
    • 10 = great, 1 = terrible

What the scoring measures:

  • Emphasizes effort/intent, not outcomes/results.

Example daily questions rated 1–10:

  • grow spiritually
  • love your wife
  • love your kids
  • love being a good friend
  • learn something
  • create something
  • exercise

Why effort-based scoring helps:

  • It prevents self-judgment based on uncontrollable results (e.g., illness, missed run distance).

Implementation in Obsidian:

  • A custom end-of-day shortcut writes the rated values into properties of the daily note.
  • A Quick Add macro logs:
    • wins
    • gratitude
    • journal entries
  • No separate journaling app needed—everything lives in the daily note.

Power feature for reflection:

  • Use an “on this day” style query inside the daily note template to surface entries from years ago on the same calendar day.

Core takeaway wording:

  • “Journal to craft the future” by recording a useful marker for future-you.

2) Quarterly layer: Personal retreat (single day, high leverage)

Frequency: once per quarter (about every 90 days), taking a full day off regular work.

Storage approach:

  • Everything is stored in one Obsidian note (a repeatable template document).

Retreat workflow format (in order):

  1. Review life theme and personal core values (still resonant or not?)
  2. Review journal entries from the daily system:
    • use queries and a dashboard to spot trends
  3. Complete a Wheel of Life exercise:
    • rate happiness in life areas
    • choose which area(s) need attention for the next 90 days
  4. Do a two-part retrospective:
    • look back at the previous quarter
    • then look forward by listing what to start, stop, keep
  5. Set intentions for the next quarter
  6. Review the ideal week to ensure time is allocated for consistent action

Why Obsidian matters here:

  • Past retreat notes become linkable, letting you compare current retreat language/decisions to prior ones.
  • Creates a feedback loop that prevents rewriting goals “with slightly different wording.”

3) Multi-scale planning (daily/weekly/quarterly alignment; Cal Newport style)

Concept referenced: “multi-scale planning” by Cal Newport.

How planning starts:

  • Begin with what’s important:
    • life theme / personal mission statement
    • core values

Cadence:

  • Recommend quarterly, weekly, daily planning
  • Avoid annual planning (too long/impossible to get right)
  • Retreat sets the next 90-day intentions; reassess every 90 days

Obsidian implementation:

  • Each planning layer lives in its own note (daily, weekly, quarterly).
  • Notes connect using the Periodic Notes plugin so actions stay aligned with retreat intentions.

Big takeaway:

  • Linked notes ensure you consistently act on what you decided during retreat.

4) Habit tracking (embedded checkbox properties + dashboard)

Problem with past approaches:

  • Habit apps were tried (Streaks, Habitify, Strides, Way of Life), but habits didn’t stick because habit data lived separately from the reflection needed to understand missed days.

New implementation (simple data entry):

  • Habit tracking is included in the daily note template.
  • Use checkbox properties for each habit tracked “this season.”
  • Entry happens as part of the journaling workflow at end of day.
  • No separate app, no notifications, no streak shame.

Visualization and insight layer:

  • Build a custom dashboard using DataView.js snippets.
  • Dashboard pulls from checkbox properties across daily notes and displays:
    • streaks
    • gaps
    • trends

Behavior-change logic:

  • The benefit is context next to the journal entry:
    • it’s more useful to understand why you missed days (e.g., dad in hospital) than to simply count streak failures.

Support material mentioned:

  • A “Habit Canvas” dashboard setup video
  • A free downloadable starter vault

5) Daily Bible reading (chapter + verse “atomic note” linking)

Two Bible-text formats in the vault:

  • Note as chapter: used for the daily reading plan in the daily note
  • Note as verse: each verse is its own atomic note

Daily reading plan:

  • A chronological plan file assigns chapters to specific days.
  • Appears in the daily note via a custom callout.

Why verses are atomic notes:

  • The creator makes sketch notes of sermons.
  • Sermon notes link to specific verses referenced.
  • Over time, this creates:
    • a personal cross-reference library using the local graph
    • links out to other notes (topical Bibles, Bible college notes, paper highlight tags)

Core argument:

  • Dedicated Bible apps can’t connect sermon notes, book notes, and journal context in one vault—the value is in linking across domains.

6) Task management (context-aware tasks inside Obsidian)

Past tools referenced:

  • OmniFocus, Todoist, Things, TickTick, Asana

Why Obsidian replaces them (for this creator):

  • Tasks are captured via Obsidian’s task plugin as inline tasks.
  • Tasks are surfaced through queries at the right time.

Core workflow components:

  • Capture tasks with tags (e.g., “discuss” + person name)
  • Use:
    • People notes: each person has custom queries to surface relevant tasks
    • Project organization: tasks rolled up into project views/dashboards
    • A task dashboard note that queries all tasks and recommends what to look at today

Key philosophy:

  • Tasks without context become “a list of guilt.”
  • Tasks beside project/person/context change how you relate to to-dos.

Important limitation stated:

  • If your work needs location-based reminders or complex 50-client SLA-style management, this system may be a poor fit.

Execution detail:

  • Tasks live in Obsidian, but actual execution uses time blocking based on dashboard recommendations.

7) Writing workflow (drafting in Obsidian; export to publishing tools)

Writing types supported:

  • newsletters, YouTube scripts, course content, book notes, articles

Why Obsidian helps:

  • Source material and drafts are in the same vault.
  • Reduced friction: link/embed quotes from book notes while drafting.

Project management:

  • Use Kanban boards inside Obsidian.
  • Separate folders and boards per writing project type.
  • Use Quick Add macros to capture backlog items.
  • Drag items left-to-right until publishing.
  • Each writing type uses template files with metadata.

Publishing/export steps:

  • Export markdown to required tools/platforms:
    • YouTube scripts → video editor in Notion
    • newsletter → Kit
    • articles → Practical PKM (Ghost platform)

8) “Life OS” dashboards (DataView.js visual integration)

Purpose: keep alignment with vision and values; connect all layers.

Example dashboard widgets:

  • Wheel of Life graph
    • dynamically generated from the current quarter personal retreat note
  • Daily questions widget
    • shows lines/averages from daily question properties
  • Habits widget
    • generated from daily note checkbox properties
    • includes streak/best streak/longest break/completion %
    • shows which habits were completed/missed over recent days
  • Includes:
    • life theme
    • “Memento Mori” widget (from daily template)
    • quick links to capture journal entries / jump to planning notes

Key implementation claim:

  • Dynamic generation means no code changes needed after configuration; it stays up to date.

Overall system philosophy (as stated)

  • Pick workflows that should be connected, not an “everything app” mindset.
  • Start with the foundation workflow:
    • the creator recommends daily journaling first.
  • Implement gradually:
    • Work sequentially (“layer one at a time”) so it sticks.

Speakers / sources featured

  • Speaker: The YouTube video narrator/creator (referred to as “Mike” in comments)
  • Book/Author referenced: Marshall Goldsmith — Triggers
  • Planning concept referenced: Cal Newport — multi-scale planning
  • Tool/platform referenced for AI assistance: Claude (used to help create journaling dashboards)
  • Software/tools referenced (prior or alternate options):
    • Streaks, Habitify, Strides, Way of Life
    • OmniFocus, Todoist, Things, TickTick, Asana
    • Notion, Kit, Ghost

Original video