Atomic Notes and One-Idea Pressure

By the end of this lesson, you will be able to...

• Choose a note boundary based on one reusable point rather than a broad topic or a single sentence.

• Split an overgrown note while keeping the context and qualifiers that make each new note honest.

• Recognize when several parts should stay together because separating them would damage the meaning.

Idea in one sentence: An atomic note holds one point that can be understood, questioned, revised, or reused on its own; it is not simply the shortest possible note.

Core Insight

In the previous lesson, Mina turned a saved highlight into an authored note about resume cues. A few days later, she keeps reading and adds everything related to focus into one file named Study interruptions.

At first, this feels tidy. Every relevant thought has one home. Then Mina wants to design a small end-of-session routine. She remembers that one item in the file mattered, but the file now contains source fragments, three claims, a possible habit, and a warning about notifications.

She can read the whole file again. What she cannot do easily is take one useful point into a new context without carrying unrelated material with it.

The pressure is not that the file is long. The pressure is that it has more than one job.

One Topic Per File Works—Until the Topic Contains Several Decisions

The first design is reasonable:

Keep everything about one topic in one note.

This works while Mina is reading one source in one sitting, or while the future task is simply to revisit that source. A source note can be broad on purpose. Its job is to preserve provenance and local context.

It breaks when the file contains points that can change, be tested, or be used separately. Mina may want to use the resume-cue idea in a study plan, question the notification claim, and keep the article quotation for later reference. Those are different future jobs.

The opposite response is also tempting:

Make every sentence its own note.

That produces lots of small files, but smallness alone does not create reuse. A note reading “helps you restart” is short, yet it does not say who is helped, restart what, under which condition, or why the phrase matters. It is a fragment, not a usable point.

The missing design choice is a note boundary: the decision about what belongs inside one note and what deserves its own note.

Plain meaning: A note boundary groups the material that must travel together for one point to remain understandable.

In Mina's situation: The claim about resume cues stays with the condition that makes it useful and the source context that distinguishes it from a universal rule. The notification claim becomes separate because it can be questioned and used independently.

Working term: An atomic note holds one reusable point. That point may be a claim, question, decision, comparison, or small procedure. It may need several sentences. Atomic does not mean tiny.

Compare Three Possible Boundaries

Mina's overgrown note currently looks like this:

Study interruptions

- A source says that attention can remain on a previous task after a switch.
- At the end of a study session, write the current state, next action,
  and unresolved question.
- Interruptions may be less costly when the return state is explicit.
- Default notifications can create unplanned task switches.
- Turning every notification off may hide something genuinely urgent.
- Try a two-week experiment with a quieter notification setting.

All six lines concern interruptions. They do not all make the same point.

For this track, the third design is the useful default. It is not a command to split everything. It is a preference for material that will be revisited across questions or projects.

A Worked Split

First, Mina keeps the article's quotations and page pointers together in a source note. That note can remain broad because its job is faithful reference. It is not trying to be a reusable claim.

Then she separates the overgrown file into three authored notes.

Title: A resume cue preserves the state needed to restart a task

Claim:
After pausing a study task, recording the current state, next action, and
unresolved question can reduce the work of reconstructing what to do next.

Scope:
Useful when the task has enough unfinished state to be forgotten; less useful
for a two-minute task with an obvious next action.

Use:
End a study session with one resume cue.

Source and status:
Working interpretation of the interruption reading; compare two sessions.

This note has one point: preserving return state. Its scope is not a second note because the scope changes what the claim means. Without it, the note would silently promise help for every kind of task.

Title: Notification defaults can create unplanned task switches

Claim:
A setting that exposes every incoming notification can interrupt work even
when the person did not choose to switch tasks.

Boundary:
Changing the default may delay messages that are genuinely time-sensitive.

Question:
Which notifications need immediate attention during a study session?

This is separate because Mina can investigate or use it without discussing resume cues. It has a different condition, a different risk, and a different next question.

Title: A notification experiment needs a success signal

Decision:
For two weeks, use a quieter notification setting during study sessions.

Success signal:
Count unplanned switches and note whether urgent messages were missed.

Revisit condition:
Change the setting if an urgent message is missed or if switches do not fall.

This is a small decision record. It belongs together because the choice, its signal, and its revisit condition are one decision. Splitting them into three notes would make the decision hard to evaluate later.

The same source material has now produced different note jobs:

So far, the split did not make Mina's archive more clever. It made the points easier to inspect. Each note now answers a different future question without pretending that all notes must have the same shape.

The Split Test

Before creating a new note, Mina can ask four questions.

1. Can this part be stated as one point? A reusable point can be a claim, question, decision, comparison, or procedure. “Everything about focus” is a topic, not one point.
2. Could I use or challenge this part without reopening the rest? If yes, it may deserve its own note. If no, the missing context may need to stay with it.
3. Would this part change for a different reason? A hypothesis, a source quotation, and a personal experiment often evolve independently. That is a reason to separate them.
4. Would splitting remove a necessary qualifier or step? Keep material together when the pieces only make sense as one procedure, one decision, or one carefully bounded claim.

These questions are a teaching model, not a filing algorithm. They make the design decision visible before a growing archive turns it into a search problem.

What This Changes

Before this idea, Mina might ask, “Which folder should contain this thought?”

After this idea, she can ask, “What is the smallest point I expect to revisit, and what context must stay with it?”

That change matters because an atomic note has a clearer handle. Mina can later connect it to another note, test it against an example, put it in a project outline, or revise it without rewriting every thought about focus. The next lesson will focus on those connections; this lesson only prepares notes that are worth connecting.

Trade-offs and Limits

Atomicity improves reuse, but it costs time and can destroy flow if applied mechanically.

This helps when a broad note repeatedly forces Mina to hunt for one point, or when its parts have different uses, evidence, or revision conditions. It costs a short pause to name the point and carry along its necessary context.

It can still fail in two directions:

• Too broad: a note contains several independent claims or decisions. The signal is that Mina keeps copying one paragraph out of it or cannot title it without using “and.”
• Too fragmented: a note cannot explain itself, or every reading task produces dozens of tiny pieces. The signal is that Mina must open many files to recover one argument.

Do not split an argument merely because it has several sentences. A claim and its decisive qualification may need to remain together. Do not split a short procedure merely because it has several steps. The purpose is future use, not a graph with many nodes.

Check Your Understanding

Check: Which revision creates the strongest atomic note?

A. Rename Mina's file Very important interruption ideas.

B. Make a separate note for each word in “current state, next action, unresolved question.”

C. Create one note about resume cues that keeps its useful condition, and a separate note for the notification question because it can be investigated independently.

D. Keep all material together because every line came from the same week of reading.

Think first, then reveal.

Answer: C. It separates two reusable points while preserving the context that makes the resume-cue claim honest. A only renames the bundle, B fragments one procedure, and D uses source timing as a boundary even though the later jobs differ.

Check: Should Mina split the success signal from the notification experiment into its own note?

Think first, then reveal.

Answer: Usually no. The signal tells Mina whether to keep or change that particular decision. Separating it would hide the test that gives the decision meaning. It could become a separate claim only if the signal itself is reused across several unrelated experiments.

Practice: Refactor a Reading Note

Here is a fictional note from a cooking course:

Better soup notes

- Salt changes flavor more than people expect.
- Taste the soup before adding salt.
- Acid can make a finished soup taste brighter.
- Lemon does not suit every soup.
- Next time, compare a spoonful before and after a small amount of acid.

Refactor it into two or three notes. Preserve the context that makes each note usable. You do not need to decide whether the cooking claims are universally true; treat them as working material from the course.

A good answer should include:

• a note whose title states one reusable point rather than the broad topic “better soup”;
• a qualifier kept with a claim when it changes the claim's scope;
• a separate experiment or question only when it can be reused independently;
• no sentence fragments that require the original note to make sense.

One possible answer:

Title: Taste before adding more salt
Point: A small taste test can prevent seasoning a dish by habit rather than by
its current flavor.
Boundary: This does not say that salt is the only adjustment a soup may need.

Title: Acid is a separate finishing adjustment from salt
Point: A small amount of acid may change a finished soup in a different way
from salt.
Question: Which soups from this course became less balanced after acid?

Title: Compare a spoonful before and after one small adjustment
Procedure: Keep the before-and-after tasting steps together so that the
comparison remains reproducible.

The final procedure note stays intact because its steps form one small experiment. Atomicity has preserved a usable unit, not created three isolated slogans.

Resources

• [ARTICLE] Andy Matuschak: Evergreen notes — Focus: Compare an atomic, concept-oriented note with a broad topic bundle.
• [ARTICLE] Introduction to the Zettelkasten Method — Focus: Notice how one topic and an author's own words support later use without prescribing a fixed note length.
• [ARTICLE] 4 Use Cases to Determine What a Zettel Should Be — Focus: Use future browsing and writing tasks to judge whether a note can stand on its own.

Key Takeaways

• An atomic note holds one reusable point, not necessarily one sentence or one fact.
• A good boundary keeps the context, qualifier, and provenance that make a point understandable.
• Split material when its parts have different future uses, evidence, or revision conditions.
• Keep material together when it forms one decision, one procedure, or one bounded claim.
• The goal is easier reuse; a large pile of fragments is not evidence of a better system.