Most note-taking systems fail in the same place: at the moment of writing something down.
Not at organising, not at reviewing. At capture. Someone tells you a name on a phone call and there is a decision to be made — which note, which folder, which tag — and the decision takes longer than the writing. So the name goes on the back of an envelope, or into your head, where it does not stay.
The fix is one note with no rules, which you never organise. Everything lands there first.
Why the friction matters more than the filing
The good news is that this is a solved problem, and the solution is not discipline.
Every well-designed capture system in the world has the same first step: an inbox with no requirements. The reason is that filing something correctly requires you to know what it is, and at the moment you write it down you often do not. "Ask Ruth about the invoice date" might turn out to be a task, a project, a five-minute thing or nothing at all. Deciding which, right then, is real cognitive work interrupting whatever you were actually doing.
An inbox lets you defer that decision to a moment when deciding is the job. And critically, it makes capture cost roughly nothing, which is the only thing that determines whether you will do it while distracted, which is when it matters.
What goes in it
Everything with nowhere else to be, yet:
- Names, numbers and addresses from a phone call.
- A sentence you thought of in the shower and will otherwise lose.
- The command you just worked out, before you forget which flag it was.
- A link somebody sent that you might want.
- Three words about a thing that annoyed you, which may become a real task.
- The thought that arrives while you are doing something else and would otherwise derail it.
That last one is the underrated case. A scratch note is not only a memory aid; it is a way of putting an intrusive thought somewhere so you can stop holding it. Writing "check the renewal date" takes four seconds and buys back the attention you were spending on remembering to check the renewal date.
Why one note, not many
The temptation is to have a scratch note per project, or per day, and both are worse.
Per project reintroduces the decision you were trying to avoid. Which project is this? You do not know — that is why it is in the scratch note.
Per day is more defensible, and it is how daily-note systems work, but it scatters. Something written on Tuesday and needed on Friday is now in a note you have to remember the date of. If you like daily notes, keep them for what happened that day and still have one permanent scratch note on top.
One note also means one place to look, which turns out to be the property that keeps people using it. The whole system is "when in doubt, put it there; when looking, look there".
The ten minutes that stop it rotting
An unmanaged scratch note becomes a landfill, and a landfill gets abandoned. So there is exactly one rule, and it is a sweep rather than a discipline:
Once a week, read it top to bottom and empty it. Each line gets one of four fates:
- It is a task → move it to your list, with a date if it has one.
- It belongs somewhere → move it into the real note it belongs to.
- It is done, or it does not matter any more → delete it, without ceremony.
- It is still genuinely undecided → leave it, and notice if it is still there next week.
Ten minutes, and the value is not the tidying. It is that reading a week of your own fragments in one sitting shows you what you have actually been thinking about, which is information you cannot get any other way. It fits neatly into a weekly review that takes twenty minutes — the scratch note is the natural first item.
The fourth line matters more than it looks. Something that survives three sweeps untouched is telling you something: either it is a real project pretending to be a fragment, or it is a thing you keep not doing and should let go of. Both are worth knowing, and neither is visible while it sits in a list you never re-read.
Make it cost nothing to open
Two practical requirements, and they are the difference between a scratch note that works and one that is a nice idea.
It has to be one keystroke away. Pinned to the top of the sidebar, or on a global shortcut, or whatever your app offers. If getting to it involves navigating, you will not use it at the exact moments it exists for.
Writing in it must require no decisions. No template, no headings, no date stamps you have to type. New line, type, done. If you like knowing when something was written, let the app do it or just start lines with the date when you feel like it — but never make it a rule, because rules are what you are avoiding.
Cyanote users usually pin one note called something like Inbox or Scratch and reach it with the command palette. What the app is matters less than the fact that opening it takes no thought.
Against tidiness
There is a version of note-taking that is really about arrangement — nested folders, a tag taxonomy, links between everything — and it is genuinely satisfying. It also has a failure mode, which is that a system beautiful enough to admire is a system you become reluctant to make a mess in.
A scratch note is where the mess goes, so the rest can stay clean. It is not an admission that the system does not work; it is the part of the system that makes the rest of it usable by a distracted person with a phone in their hand.
Every organised person I know has one. Some of them call it an inbox, some call it a daybook, one calls it "dump". None of them tidies it, and all of them empty it.
If you want the opposite end of the same pipeline — what happens to the things you move out of it — there is a post on what to delete, and one on a someday list that is not a graveyard.