Improve one thing every time you touch a note — kaizen for knowledge bases
Each time you review or link a note, make one small improvement (sharpen title, add missing context, split tangled claim) rather than scheduling separate cleanup sessions.
Why This Is a Rule
Knowledge bases degrade through neglect, not through catastrophe. Titles drift out of sync with content. Context that was obvious at capture becomes opaque months later. Compound claims stay fused because nobody scheduled time to split them. The debt accumulates invisibly until retrieval quality drops and you declare "I need a cleanup week" — which never happens because there's always something more urgent.
The kaizen approach eliminates the need for cleanup weeks by distributing improvement across every interaction. Each time you touch a note — to read it, to link from it, to reference it — you make one small improvement. Sharpen the title. Add a sentence of context. Fix a vague pronoun. Split a compound claim. The individual improvement is trivial (30 seconds). The compound effect across hundreds of interactions transforms your knowledge base quality without dedicated maintenance time.
This works because you're already paying the context-loading cost of reading the note. The marginal cost of one improvement while the note is loaded in your mind is near zero. Deferring to a cleanup session means paying that context-loading cost again separately.
When This Fires
- Every time you open a note for any reason (reading, linking, referencing)
- When you re-read a note and find the title doesn't match the content
- When a note requires you to remember something that should be written in the note itself
- Any interaction with a note where you notice a small quality issue
Common Failure Mode
Trying to fully refactor every note you touch. The rule is one small improvement, not "fix everything wrong with this note." If you try to do a complete overhaul during a casual interaction, you break your workflow for the task you were actually doing. One improvement per touch. The note will be touched again, and improved again then.
The Protocol
Each time you touch a note: (1) Read it. (2) Notice one thing that could be better (vague title, missing context, tangled claim, broken link, stale information). (3) Fix that one thing — 30 seconds maximum. (4) Move on with your original task. Over time, frequently-accessed notes converge toward high quality, and rarely-accessed notes stay as-is (which is fine — if nobody touches them, nobody needs them polished).