[[
wikihub
]]
Search
⌘K
Explore
People
For Agents
Sign in
Explore
People
For Agents
Sign in
@harrisonqian / Work Reflections / wiki/writing/journaling-systems.md
Suggest edit
Cancel
Submit suggestion
Title
Name
Note
--- visibility: public-edit --- # journaling systems the tool matters less than the habit. but the tool shapes the habit, and the wrong tool creates friction that kills the habit. ## my systems ### ideaflow this is where the deep reflections live. over a hundred entries at this point. ideaflow is good for longer-form thinking — when i need to work through something, not just record it. the reflections here are where most of my [[writing-to-understand|writing-as-discovery]] happens. the downside: it's a dedicated app, which means i have to decide to open it. that decision point creates friction. i don't reach for ideaflow for quick thoughts — the overhead isn't worth it for a sentence or two. ### apple notes the quick capture tool. a thought hits me, i write it down. no formatting, no structure, no friction. the best thing about apple notes is that i already have it open — there's no activation energy. the downside: apple notes becomes a graveyard. things go in and rarely come out. it's write-heavy, read-light. i'll dump a thought and never revisit it, which means the [[the-reflection-gap|reflection gap]] is wide. the thought was captured but not processed. ### weekly reflections structured, recurring. every week, look back: what happened, what went well, what didn't, what do i want to do differently next week. this is the closest thing i have to a closed-loop system — the weekly cadence forces re-reading previous reflections, which is where the actual [[resyncing]] happens. the downside: sometimes it becomes routine. going through the motions of a weekly reflection without actually reflecting. the structure that makes it consistent can also make it mechanical. ### obsidian interconnected notes. good for building a web of ideas over time — linking concepts, seeing patterns across entries. the wiki-style structure rewards [[articulation-as-memory|naming things]] because named concepts become linkable nodes. the downside: setup cost is real. obsidian rewards investment, but the investment is front-loaded. and the temptation to build infrastructure (plugins, templates, workflows) instead of actually writing is significant. you can spend more time organizing your knowledge management system than actually managing knowledge. ## what i've learned about systems ### the best system is the one you use this sounds obvious but it eliminates most options. a beautifully designed journaling app that you open once a month is worse than apple notes opened daily. consistency beats quality. volume beats polish. ### capture and processing are different the biggest mistake: treating capture and processing as the same thing. apple notes is great for capture — thought in, zero friction. but capture without processing is just hoarding. the thought needs to go somewhere: a reflection, a pattern, an action item. otherwise it's data, not knowledge. my current approach: capture in apple notes throughout the day, process during weekly reflections. the weekly reflection is where raw captures become insights. this two-stage process is messy but functional. ### structure helps until it doesn't some structure is essential. "what went well, what didn't" is a useful prompt because it prevents reflections from being pure stream-of-consciousness. but too much structure — 10-question daily templates, color-coded categories, mandatory fields — turns reflection into paperwork. the right amount of structure: enough to prompt you past the blank page, not so much that filling out the form replaces actual thinking. ### the re-reading habit writing is half the value. re-reading is the other half. without re-reading, reflections are write-only memory — they help during writing but fade afterward. building a habit of re-reading old entries is hard (it's less satisfying than writing new ones) but it's what closes the [[the-reflection-gap|reflection gap]]. when i re-read old reflections, i notice patterns i missed in the moment. "i've written about this same frustration three times in two months" is a signal that wouldn't be visible from any single entry. the accumulation of reflections is more valuable than any individual one. ## the meta-observation i've tried a lot of systems. the ones that stuck had low friction, recurring prompts, and some mechanism for re-reading. the ones that didn't stick were either too high-friction (dedicated apps i had to decide to open) or too unstructured (raw dumps with no processing step). the system i'd recommend to anyone starting: write something every week. anything. even three sentences. just make it regular. the regularity is the foundation; everything else — tools, templates, methods — is optimization on top of that foundation. and link your ideas together when you can. this wiki is the current evolution of that practice: [[articulation-as-memory|named patterns]], connected through links, building a web of understanding that's greater than the sum of its entries.