There's a specific kind of productivity afternoon where you build a beautiful note template, with headings and callouts and a properties block, and then never write a single note in it. The template was the work. The notes were supposed to be.
Templates aren't the problem. Applying them to the wrong kind of note is.
The one rule
Use a template when the shape of the note is known before you write it. Don't when the shape is the thing you're figuring out.
A meeting has a knowable shape: it will produce decisions, actions, and open questions, every time, forever. Writing those three headings by hand every week is pure waste, and worse, under time pressure you'll skip a heading and lose the actions.
An idea has no knowable shape. You don't know if it's three lines or two pages, an argument or a question. Handing yourself a form to fill in doesn't help you think; it makes you write to fit the boxes, which is the opposite of what a thinking note is for.
| Template it | Leave it blank |
|---|---|
| Meeting notes | A thought you're chasing |
| Recurring 1:1s | Reading notes on a chapter |
| Weekly review | A draft argument |
| Decision records | Anything captured in a hurry |
| Recurring reports | Atomic notes |
Notice the pattern: templates fit notes with other people in them, or notes that repeat on a schedule. Solo thinking notes almost never want one.
The three templates most people actually need
You do not need a template library. You need about three.
1. The meeting note. Four headings, nothing else: Context · Decisions · Actions (owner + date) · Open questions. That's the whole thing. If you want the reasoning behind those four, see how to take meeting notes.
2. The weekly review. What moved · What didn't and why · What's next week. Its job is to force the same three questions when you're too tired to invent them.
3. The decision record. The decision · The options considered · Why this one · What would change our mind. This is the highest-value template almost nobody keeps, because six months later the only question anyone asks is "why did we do it this way," and nobody remembers.
Yours is too long
The reliable failure mode is the template that costs more than the note is worth. If your meeting template has nine sections and the meeting produces two facts, you will either spend five minutes deleting empty headings or leave them in, and a note full of empty headings is harder to read than no note at all.
A working test: the template should be shorter than the shortest note you'll actually put in it. Five fields is a lot. Three is usually right.
Two more things that keep templates honest:
- No field you won't fill in every time. An optional field is a decision you now have to make on every note.
- Prompts, not labels. "What did we decide?" pulls more out of you than "Decisions". The Cornell method works on exactly this principle: the cue column is a question, and questions get answered.
What a template can't fix
A template imposes structure on capture. It does nothing for retrieval, and retrieval is where note systems actually fail. Perfectly formatted meeting notes that nobody reopens are still a filing cabinet.
The structure that pays off later is the kind you add after writing — a clear title, a link to the related note, a short pass in your review routine. Or none of it, if your notes tool can simply answer questions across what you wrote, which is the bet behind asking your notes directly instead of pre-formatting them for a future search you'll never run.
Start with the meeting template. Add a second one only when you catch yourself typing the same headings for the third time.