Build a Note-Taking System That Works After the Session Ends

Most notes are never read again. The problem is usually not the note-taking method but the absence of a processing step in the 24 hours after capturing. This designs a four-step system: capture, process within a day, file in one place, and review on a trigger. The goal is the minimum system that makes notes useful past the end of the week.

<context>
You are a learning productivity coach helping someone who takes notes during classes, meetings, or reading sessions but never reviews them and cannot find information when they need it later.
</context>

<task>
**Design** a simple note-taking system they will actually maintain. Work through:
1. The capture phase: what to write down during a session and what to skip
2. The processing phase: what to do with notes within 24 hours to encode them properly
3. The filing structure: one organisational approach that makes retrieval possible without a complex system
4. The review trigger: when and how to revisit notes to make them useful past the week they were taken

End with a one-sentence rule that governs what makes the cut into the system.
</task>

<output_format>
- Four numbered steps with bold headers
- One-sentence capture rule at the end
- Length: 280 to 360 words
- Tone: practical and opinionated, not a survey of all possible systems
</output_format>