How to Take Smart Notes: think in writing

Suppose a passage makes you wonder whether meeting records preserve decisions while losing the reasons behind them. You are still reading, so you jot down a reminder: what gets lost when we record only the decision? That is enough to keep going without trying to solve the whole question immediately.

Ahrens calls this a fleeting note. It is a cue for a thought you have not yet developed. A few words, a margin comment or a voice recording may do the job. In Aspen, a Daily notes entry is a straightforward place to begin. You can keep the encounter in its date context and return when there is room to think.

The return matters because the cue relies on what is still in your head. Read it again while you can recover why it seemed interesting. You may decide to explain it, connect it with a source, treat it as a project task or leave it alone. You do not have to develop every passing thought. When an idea is already clear, you can write it properly straight away.

Before developing the idea, keep a route back to what prompted it. Ahrens's literature notes record the relevant content of a source with the details needed to find it again. They are selective: what matters here, and where can you find it again? A difficult argument may need a fuller account than a familiar one.

You could begin by recording Ahrens's distinction between a reminder and a note that contains an understandable thought. Keep the book, author and passage location with that explanation. Later, you can check whether you represented the distinction accurately instead of relying on your memory of what the book seemed to say.

These reading notes stay in the reference collection. They are not scraps that must disappear once you write another note. Their purpose differs from the main slip box, where you develop the idea's relevance to your own questions. Ahrens's broad category of permanent notes includes both retained source records and developed main-box ideas. The source record preserves the reading; the next note explains what you want to do with it.

That separation is especially helpful when an application starts to sound convincing. Ahrens describes how notes can preserve thought beyond its original moment. Applying that to a team's meeting records is our proposed use of the idea. Keeping the two accounts distinct lets us investigate the application without making the book responsible for a claim it did not establish.

Now return to the reminder about decisions. A developed note might propose that a decision record should preserve the reasoning behind a choice, because a later reader needs more than the outcome to evaluate it. You would explain what kind of record you mean, why the distinction matters and where the idea came from.

Trying to write that explanation may expose a problem. Does the later reader need the reasoning to understand the decision, to challenge it or to decide whether it still applies? Those are different uses. The note gives you somewhere to make the difference clear. You are already thinking through the question while writing, rather than waiting to write until the thought is complete.

Ahrens recommends one idea per main slip box note so it can be used in different discussions. One idea can need several paragraphs. A reason, an example and a condition may all explain the same claim. The point at which to split is where two parts would be useful independently, not where you exceed a sentence count.

The note should make sense to a future version of you who has forgotten this reading session. Explain it in your own words, then compare it with the source. If you cannot explain a step, you have found something to investigate. Changing the original wording is useful only when it makes the meaning clearer without distorting it.

The decision note becomes more interesting when it meets another thought. Imagine you also have a note proposing that a choice can make sense under conditions that later change. Put the two beside each other. Recording a reason may help a later reader, but that reader may also need to know the circumstances under which the reason held.

That is a connection worth explaining. You could link the notes and write that the second one qualifies the first: a useful record may need both the reason and the conditions. The relationship has changed what the first note asks you to investigate.

This is what gives a reference a job. A note can supply support, a counterexample, a distinction or a question for another note. Shared subject matter can suggest a connection, but the explanation tells you whether it helps. A backlink lets you find the mention from the other direction; the words around the link tell you what to make of it.

Luhmann's addresses let a note keep its identity while different lines of thought referred to it. Ahrens also describes selective index entries and overview notes as ways into those discussions. An overview could begin with the question, then point to the notes about reasons, changing conditions and unresolved objections. It need not catalogue every note about meetings.

We began with a broad concern about teams reopening decisions. The notes have suggested a more specific question: what must a decision record preserve for someone outside the original conversation to judge whether the choice still makes sense? That question now has a few distinctions behind it, along with things we still need to learn.

Ahrens encourages this development. Read with existing questions in mind, but allow a source to change them. Look for contradictions and missing cases as well as further support. A decision record might contain a detailed explanation and still fail to settle a disagreement. We would need to investigate that possibility before claiming that more documentation solves the problem.

A connected collection gives these observations somewhere to stay even when they do not fit the current project. You can preserve an objection, narrow an earlier claim or follow a different question. The collection still reflects what you chose to read and keep, so it helps to ask whose experience or which kind of failure is absent. More notes alone cannot answer that.

Research can feel like one large task called writing, even though reading a difficult passage, comparing two notes and correcting a draft require different attention. Ahrens asks you to give each job its own attention. Looking for an idea and judging its final wording at the same moment can make both harder.

A useful session might be checking whether a source supports one claim. Another might explain why two notes disagree. When you stop, record what you found and what remains open. A clear continuation makes it easier to return after a break without keeping the whole argument active in memory.

Consistent places for capture, references and developed notes help with this continuity. You spend less time deciding where each result belongs. The routine can be dependable while the inquiry changes direction. There is room for a short reading session or one carefully revised note; you do not need to reorganize an entire library before seeing whether the practice helps.

Eventually you may have enough material to write an article. The task changes. The collection can hold several questions and competing claims; the article needs a particular argument that someone else can follow. Gather the relevant notes and try a provisional order. Give each part a reason to be there.

The research might become a piece about what a later reader needs from a decision record. The notes about reasons and conditions supply a starting point. The objection about unresolved disagreements limits what the piece can promise. Arranging them may reveal a missing example or a claim whose evidence is weaker than you thought. That sends you back to the work with a more precise question.

Ahrens treats this as project work. An outline, a draft paragraph and a reminder about this article can stay together without making the whole slip box conform to the article's order. A useful idea excluded from the draft remains available for another discussion.

Write the prose for someone who has not followed your research. Supply the definitions, evidence and transitions that the private notes could leave implicit. Then revise the result. The outline can change when a better sequence appears, and an attractive passage can be removed when it does not serve the argument. Connected notes provide material you have thought about; they still need this editorial work.

In [[Write Useful Books]], the emphasis shifts to the person who will use a practical book. Rob Fitzpatrick asks the writer to choose a wanted result and test whether the material helps someone reach it. That adds a question the research project has not yet answered: who needs the explanation, and what would it help them do?

Ahrens makes room for a question to emerge through research. Fitzpatrick asks for a reader promise early in the design of a practical book. Keeping those priorities distinct is useful. An open inquiry needs freedom to discover what it can support. A guide offered to someone else also needs a clear purpose and evidence that its explanation works for that reader.

Research about decision records could eventually inform a guide for a particular team. The guide would need testing in that setting. A coherent collection of notes would help prepare it, while the team's experience would tell us something the collection alone cannot: whether the proposed help is useful.