G’day.
Last week, I walked you through my current PKM workflow - the loops, the habits, the shortcuts I actually use.
This week, we zoom out. Because showing you my system is one thing. Designing yours is another.
Most systems don’t fail from missing features. They fade because using them costs more than they give back.
When opening your notes system feels like a chore, you stop, no matter how beautiful it is.
Why return value matters more than setup
The best system isn’t the most feature-rich.
It’s the one you keep coming back to even when you’re tired, busy, or distracted.
Last week, I introduced the “daily return” idea. Designing your system so you want to open it every day, not just when you have a big block of time. The magic of a notes system is in how often you return to it, not in how perfectly it’s structured.
That means designing for imperfect days, not ideal ones.
On a bad day, you might only have 5 minutes to check in. On a good one, maybe an hour. A dependable system works for both.
Principles of a returnable system
Here are four principles I use when building systems I know I’ll come back to:
Friction-aware design
Identify where you slow down, then remove steps.
Example: My own active projects are one click from my home screen. No digging through nested folders.Prompts over polish
A rough note that sparks action beats a perfectly formatted one you never touch.
Example: A messy checklist for “Next Steps” is more useful than a fully styled project page with no clear action.Small, consistent loops
Daily and weekly check-ins should take minutes, not hours.
Example: My daily review takes under 5 minutes. It’s enough to keep projects warm without turning it into admin work.Purpose-first organization
Organize by why you’d return to something, not just what it’s about.
Example: I tag ideas by “Write Soon” or “Use in Project X,” not just by topic.
Testing your system for return value
A quick test I use:
If you stopped adding anything new for a week, would you still want to open your notes system?
Other quick checks:
Can you find something to act on in under 30 seconds?
Does it surface notes you’d forgotten but still want?
If the answer’s no, your system might look good but isn’t working for you.
Common traps that kill return value
When you spend more time tagging than using.
Burying active work under archive layers - if it’s hard to find, you won’t.
Capture overload without processing - piles of half-baked notes that never turn into anything.
Each one adds friction. And friction kills return.
How to start redesigning for return
You don’t need a full rebuild.
Pick one area and make it easier to return to:
Remove one step from a high-friction process.
Add a small “Next Move” prompt to your most-used pages.
Shrink review scope - look at 5–7 items instead of your entire backlog.
A quick example:
Two months ago, my weekly review page was buried under three clicks. I moved it to my home screen, added a “What needs attention?” prompt at the top, and cut my review time from 30 minutes to 8. That change alone doubled how often I actually used it.
Before: Three clicks to reach the review page, no prompts, and I’d often skip the review completely.
After: One click from the home screen, a single action question at the top, and I now finish the review before my coffee gets cold.
Closing reflection
Last week, I did a friction audit of my own notes system.
The biggest surprise: A “Resources to Read” page I hadn’t touched in months because it wasn’t visible anywhere I actually worked from.
Think about the last time you opened your system outside of capture mode.
What pulled you back?
Could you design for that on purpose?
Then, make one tweak this week that makes it easier to return.
Creator Block
This week’s deep dive looks at someone most people in PKM circles overlook: Howard Rheingold.
He was part of the early internet, back when online communities were still experiments. But instead of chasing speed or novelty, Rheingold asked a timeless question:
👉 How do we use these tools to think more clearly, not less?
He called attention a civic act, and believed learning could (and should) be playful. In an age of AI-curated feeds, his voice is worth revisiting.
In Saturday’s deep dive, I’ll explore which of Rheingold’s lessons still stand, which haven’t aged well, and why his early wisdom matters for creators in 2025.
Don’t miss it. Follow me on Threads @gavin.create
What I’m Building
Layered Thinking Notes bakes in these return-value principles by default. It’s not about “perfect day” setups. It’s built for every day — even the messy ones.
You can explore the full Notion template here → Layered Thinking Notes
That’s all for this week,
Until next time,
Gav
