TL;DR:
Make one note per source, named in a consistent pattern, so every claim has a home.
Use a small fixed set of tags for themes and status, not a new tag for every idea.
Write a summary note per topic or week that links to the source notes. That is what you will actually reread.
After a month of reading for a project, you remember that someone made a good point about onboarding costs, but you cannot remember where. It might be in a long note called "Research", a highlight in a browser, or a screenshot. Finding it takes an hour. A small, steady system turns that hour into a minute.
What good notes have to do
Notes serve two later moments: when you need to find one fact, and when you need to see the whole picture. Searching serves the first, so write notes with words you will search for. Summaries serve the second. Everything else, such as colors, icons and folders three levels deep, is optional.
The method below works in any notes app, a folder of documents or a spreadsheet, because it relies on habits and not on features. Check your own app for how it handles search, tags and links before you rely on one.
Setting up the system
One note per source: Each article, paper, meeting or interview gets its own note. Never pile several sources into one long note, because you will not be able to tell where a claim came from.
Name notes the same way: Use a pattern such as
2026-11-03 Author or site, short topic. Putting the date first sorts them in order, and the same pattern makes searching easier.Use the same top lines: Start every note with the link or reference, the date you read it, and a one-line summary. Then your own notes, then any quotes marked as quotes.
Tag lightly: Pick a few theme tags (for example
onboarding,costs,tools) and a status tag (to-read,read,used). Add a new tag only when you have used the idea in at least three notes.Write summary notes: Once a week, or once per theme, write a note that states what you have learned so far and links to the source notes behind each point.
Keep an index: One note listing your summary notes. This is where you start whenever you return to the project.
Worked example: notes from a month of research
Say you spent four weeks on a project about onboarding costs and read 24 sources. Here is how the system looks at the end.
Kind of note | How many | Purpose |
|---|---|---|
Source notes | 24 | One per article, paper or conversation, each with link, date and one-line summary |
Weekly summary notes | 4 | What you learned each week, linking to the source notes |
Theme summary notes | 3 | Onboarding, costs, tools: the picture across weeks |
Index | 1 | Start here; links to the 7 summary notes |
Check the totals: 24 + 4 + 3 + 1 = 32 notes in all, and the index lists 4 + 3 = 7 summary notes. Thirty-two notes sounds like a lot, but you will only ever open the index and a few summaries; the source notes sit behind them for checking.
Now try the search test. You remember a point about onboarding costs. Open the index, then the costs theme note. It states the point and links to the two source notes that support it. If you instead search for a word you remember, the consistent first lines and summaries make the right note show up near the top.
Capturing as you read
When you read, resist copying everything. Write the claim in your own words, add a short quote only when the wording matters, and put the page or time in the note so you can return to it. Mark your own thoughts clearly, for example with the word "Me:", so a month later you can tell what the source said from what you concluded.
A weekly ten-minute tidy
Move anything in an inbox or unsorted note into its own source note.
Fix names that break the pattern.
Remove tags you only used once.
Write or update this week's summary note.
Add anything unfinished to a short list of open questions.
Mistakes to avoid
Collecting without reading. Saved articles are not notes.
Making tags for every idea, so none of them mean anything.
Skipping the source link, which makes it impossible to cite or recheck.
Reorganizing the whole system every week instead of using it.
Mixing your opinions with what the source said.
Doing it faster
Keep the system boring and the habits small. The notes also make later checking easy, as described in checking facts before you share them, and they feed straight into a brief or review. For sizing a market from your numbers, see back-of-the-envelope market sizing. If you want help finding a note while you work, DuckyHelper remembers you across sessions and answers out loud when you press fn on a Mac, so you can ask without leaving your app.
Frequently asked questions
Folders or tags?
Either works if you use it consistently. Folders suit one home per note; tags suit notes that belong to several themes. Many people use a few folders and a few tags.
How detailed should a source note be?
Enough that you could cite the source and explain its main point without reopening it. Long notes are less useful than clear short ones.
Get started
