Notes as Thinking, Not Storage
LESSON
Notes as Thinking, Not Storage
By the end of this lesson, you will be able to...
Distinguish a capture from a note that records your own thinking.
Process a saved passage into a claim, context, possible use, and next question.
Decide when processing is worth its maintenance cost and when simple storage is enough.
Idea in one sentence: A note becomes part of your thinking when it records a decision about what an idea means, why it matters, or what you should do with it.
Core Insight
Mina is reading about attention because she wants to design better study sessions. A sentence seems important, so she highlights it. A month later, she opens a folder named Focus. It contains 63 highlights.
The sentence is still there. Mina can retrieve the author's words, but she cannot answer four simple questions:
- What did I think this meant?
- Why did it matter to my study problem?
- Where might I use it?
- What did I still doubt or want to test?
The highlight succeeded as storage. It failed as support for future thought.
That distinction starts this track. Capturing preserves something you encountered. Processing records a judgment you made about it. Both are useful, but they do different jobs.
The Storage Model Works—Until the Task Changes
The first model of note-taking is reasonable:
If I save useful information and organize it well, I can find it later.
This model works when the future task is retrieval. If Mina needs an exact quotation, page number, receipt, or meeting date, faithful storage may be the right design.
But knowledge work usually asks for more than retrieval. Mina may need to compare two claims, explain an idea, make a decision, design an experiment, or write a paragraph. Those tasks require an interpretation, not merely access to the source.
The failure becomes visible when she finds the highlight and still has to reconstruct the entire reason she saved it. The file has preserved the input but not the earlier thinking.
The missing operation is processing.
Plain meaning: Processing turns encountered material into a small decision about meaning, relevance, or action.
In Mina's situation: She states the idea in a form she understands, connects it to her study problem, and leaves a question that can guide a later test.
Working term: This lesson calls the result an authored note. “Authored” does not mean original in every detail. It means Mina has added a judgment that the source did not make on her behalf.
A Small Knowledge Loop
We can model the work with five stages:
encounter -> capture -> process -> reuse -> revise
| |
| +-- add your judgment
+------------- preserve the input
Each stage answers a different question:
| Stage | Question | Possible output |
|---|---|---|
| Encounter | What did I notice? | A passage, observation, conversation, or result |
| Capture | What must not be lost yet? | A highlight, quick sentence, photo, or source pointer |
| Process | What do I think this means or enables? | A claim, context, possible use, and open question |
| Reuse | Did the note help with real work? | A decision, explanation, comparison, experiment, or draft |
| Revise | What did use reveal? | A correction, stronger example, new link, or deletion |
This is a teaching model, not a law. Real work may skip a stage or move backward. Its purpose is to expose a common mistake: treating capture as if processing and reuse had already happened.
From Highlight to Authored Note
Assume the article in Mina's example makes this illustrative claim:
After a person switches tasks, some attention may remain on the previous task.
The sentence is enough for our exercise. We are not evaluating the scientific evidence behind it here; that belongs to a later epistemic audit. We are inspecting what Mina's note records.
Her first capture looks like this:
Task switching can leave attention on the previous task.
Source: article on interruptions, section 2.
This capture preserves a claim and its source. Now Mina closes the article and asks, “What does this change for my study problem?”
She produces this note:
Title: An unfinished task may increase the cost of switching
Claim:
When I stop a study task without recording where to resume, returning may
require me to reconstruct both the task state and my intention.
Context:
This is my interpretation of a source claim about attention after task
switches. The source pointer remains attached.
Possible use:
Before changing subjects, leave a one-sentence resume cue: current state,
next action, and unresolved question.
Open question:
Does a resume cue make the next session easier, or does it only feel tidy?
Compare two sessions before treating the practice as useful.
Notice the intermediate decisions:
- She selects a claim. The note is not “everything about focus.”
- She interprets it. She translates the source claim into a specific study problem.
- She preserves context. A future reader—Mina herself—can separate the source's claim from her interpretation.
- She names a possible use. The note can influence a future study session.
- She keeps uncertainty visible. The resume cue is a hypothesis to test, not an established conclusion.
The second note may later prove wrong or unhelpful. It is still more useful for thinking because its reasoning can be challenged and revised.
So far, we have not made the note true merely by rewriting it. We have made Mina's current model inspectable. That is the improvement.
What Counts as Thinking?
Writing in your own words can help, but paraphrase alone is not the goal. Changing “task switching leaves attention behind” into “attention remains after changing tasks” changes the wording without changing the intellectual work.
An authored note contains at least one meaningful choice:
- a claim you accept provisionally, reject, narrow, or want to test;
- a distinction that removes an ambiguity;
- a reason the idea matters in a named context;
- a consequence, example, or counterexample;
- a question that would change what you think or do.
You do not need all five in every note. The practical test is simpler:
If I rediscovered this note in six months, what earlier thinking would it save me from reconstructing?
If the answer is only “the source used these words,” the note is probably storage. That may be exactly what you need. Just do not confuse it with completed processing.
Check Your Understanding
Check: Which item records an authored judgment?
A. A verbatim quotation with a page number.
B. A bookmark tagged important.
C. “This claim applies to my study plan only if interruptions, rather than unclear tasks, cause the restart delay.”
D. A screenshot of a diagram.
Think first, then reveal.
Answer: C. It states a conditional interpretation that can be tested or revised. A, B, and D are captures. They may be valuable, but they do not yet record what the learner thinks the material means.
Check: Mina finds the processed note but cannot locate the original source. Which part of the loop is weak?
Think first, then reveal.
Answer: Context and provenance are weak. Authored thinking should not erase where an external claim came from. The source pointer and Mina's interpretation have different roles, and the note needs to preserve that difference.
Trade-offs and Boundaries
Processing improves future reuse, but it costs attention now. A system that demands a polished note for every article, conversation, or passing thought will create a processing backlog. The learner begins serving the archive instead of using it.
A situated preference for this track is:
Process selectively when you can name a plausible future question, decision, explanation, or project. Capture lightly when the value is uncertain.
This preference is useful under limited time. It is not a universal rule. Exact quotations, legal language, raw observations, and reference facts may need faithful storage before interpretation. Some fleeting ideas deserve a temporary inbox and nothing more.
Watch two signals:
- Reuse signal: processed notes appear in decisions, explanations, experiments, or drafts.
- Maintenance signal: unprocessed captures and required review grow faster than useful outputs.
If maintenance rises while reuse stays near zero, adding more templates or tags is unlikely to solve the core problem. Reduce what you capture, process fewer items, or delete material that has no plausible use.
This lesson also leaves important questions open. It does not decide how large one note should be, how notes should link, when review should be scheduled, or whether a claim deserves belief. The next lessons take those pressures one at a time.
Common Confusions
Confusion: Storage is bad.
Storage is necessary when fidelity and retrieval matter. The correction is not “never store.” It is “know whether the current artifact stores an input or records a judgment.”
Confusion: A good note must use a complex template.
Fields can remind you what to consider, but empty fields do not create thought. One clear claim plus a reason it matters may be enough.
Confusion: Authored means completely original.
Most knowledge work responds to other people, observations, or earlier notes. Authorship here means that your interpretation and the source's contribution remain distinguishable.
Confusion: Durable means final.
A durable note should survive long enough to be found and revised. It is not protected from correction. Reuse is often what reveals its weakness.
Practice: Process One Capture
Here is a new capture:
"Defaults influence behavior more reliably than instructions."
Source: notes from a talk about product design.
Turn it into an authored note for a real or imagined problem. Do not research the claim for this exercise. Work only on making your interpretation visible.
A good answer should include:
- a claim in your own conceptual frame, not only a synonym-based paraphrase;
- the context in which the claim might apply;
- one possible use, example, or consequence;
- one uncertainty, counterexample, or next question;
- the source pointer kept separate from your interpretation.
One possible answer:
Claim:
When people are unlikely to change a setting, the default is part of the
product's behavior, not a neutral starting point.
Possible use:
Review the default notification level before rewriting the help text.
Boundary:
This may not apply when users actively choose settings during setup.
Next question:
How many users keep the default, and what harm follows if they do?
Source:
Talk notes; speaker and date still need to be recovered.
The example does not prove that defaults always dominate instructions. It exposes a useful interpretation, a boundary, and evidence that would matter next.
Resources
- [ARTICLE] Andy Matuschak: Evergreen notes — Focus: Notice the shift from better note-taking toward developing insight over time.
- [ARTICLE] Introduction to the Zettelkasten Method — Focus: Compare copied material with notes written in your own words and kept with source context.
- [BOOK] How to Take Smart Notes — Focus: Follow the writing-centered view of notes as preparation for later thinking and output.
Key Takeaways
- Capture preserves an input; processing records a judgment about meaning, relevance, or action.
- A useful authored note makes earlier thinking inspectable through a claim, context, possible use, or open question.
- Writing in your own words is not enough if the result is only a shallow paraphrase.
- Storage remains valuable when fidelity or retrieval is the goal.
- Selective processing matters because a knowledge system must create more reuse than maintenance.
← Back to Knowledge Work, Notebooks, and Zettelkasten Systems