Good day.
Personal Knowledge Management systems rarely survive first contact with real work.
In the setup phase, everything looks clean.
The dashboards are polished. The rules make sense.
But once you start using it, gaps appear, and the “perfect” design starts bending to reality.
This issue isn’t about the ideal version of my workflow.
It’s the one I’m actually running today, how it holds together in an average week, the loops that keep it alive, and the parts I’ve learned to skip.
The gap between design and reality
I’ve spent years caught between two pulls:
The urge to keep “tuning” my setup.
The need to just get on with using it.
The truth is, real-world use is always messier than the setup.
I’ve stopped measuring success by how complete or clean the system looks.
The only metric that matters now: How often do I return to what’s in there?
(Because a system you don’t return to isn’t a system—it’s storage.)
If I’m back in my notes every day, following threads, revisiting ideas, it’s working.
If I’m avoiding it, no amount of organization will save it.
My daily loop
Morning
I start with a quick scan of yesterday’s Builder Notes.
If something still feels alive, I tag it for “Next Move” or “Prompt.”
That way, I’ve already planted seeds for today’s work.
(This turns yesterday’s momentum into today’s starting point.)
During work
I run an interstitial journal all day. It’s a simple log of thoughts in the gaps between tasks.
It catches those passing ideas that disappear if I “save them for later.”
(The short gaps between tasks are when I notice patterns or make connections I’d otherwise forget.)
When something feels worth keeping, I move it into my Commonplace journal.
Here it starts linking to what’s already there - quotes, notes, fragments.
Over time, it becomes a dense web of connected sparks.
(Connection gives ideas more staying power than capture alone.)
This is my Layered Thinking Notes system in motion:
Live capture in the interstitial journal.
Growth and connection in the Commonplace journal.
End of day
A light pass over new entries - title, quick context, and a job for future return.
Nothing more. Enough to make tomorrow’s self grateful.
(Minimal friction here keeps me consistent. If it’s heavy, I’ll skip it.)
My weekly loop
Once a week, usually Sunday evening, I run a short review, 20–30 minutes.
Pull 5–7 notes from the “Active” view. Decide to develop, archive, or delete. (The small batch keeps the review sharp and focused.)
Review my Commonplace journal. The best ideas graduate into Thinking Notes. It is one of the LTN layer for developed concepts. (Promotion feels like progress. It’s a built-in reward loop.)
Tag new Builder Notes by usage mode: “teaching,” “testing,” or “story seed.” (These tags point me back to notes when I’m ready to use them, not just admire them.)
This keeps the whole system moving without letting unused notes pile up.
What I’ve stopped doing
Chasing the perfect tagging hierarchy. (The more rules I made, the less I used them.)
Forcing every note into a polished permanent format. (Polish can come later, use comes first.)
Hoarding highlights or quotes “just in case.” (If I don’t see a use for it now, I rarely do later.)
Long processing sessions that push publishing further away. (Over-processing kills momentum.)
Every one of these slowed me down. Dropping them made the rest easier.
Why it works for me now
This workflow isn’t fixed but bends to the pace of my projects.
It’s built for prompts and reuse, not archive density.
Small, consistent loops - daily interstitial logs, weekly commonplace reviews, keep the vault alive without turning it into a second job.
I no longer expect the system to be perfect.
I expect it to be ready when I need it.
(That shift alone removed most of the guilt that used to build up.)
This week’s prompt
Sketch your real workflow, mess and all.
What’s in your daily loop? Weekly loop? What have you stopped doing?
Then ask yourself:
If you opened your vault right now, what’s the first note you’d act on?
Creator Block
This week, I’m unpacking Sönke Ahrens — the author who popularised How to Take Smart Notes.
Not as a shrine to the slip-box.
But as a case study in why the “one idea per card” method is cracking in the AI era.
We’ll break down:
- What the original Zettelkasten got right.
- Why infinite capture and auto-linking have made it fragile.
- What still works — and how I adapt it in my Layered Thinking Notes system.
The deep dive thread drops Saturday night.
→ Follow the series on Threads (@gavin.create)
or wait for the full version — goes live this Saturday.
What I’m Building
Lately, I’ve been refining the backbone of the workflow you just read: Layered Thinking Notes.
It’s not built for perfect capture days—it’s built for everyday return.
A way to move from live capture, to connected ideas, to developed thinking—without breaking the flow of real work.
The first version is now live—built for Notion, with an Obsidian vault available too.
→ Explore LTN on the Notion Marketplace
That’s al for this week.
Until next time,
– Gav
