No method is best in general, because these systems solve different problems. They also differ in where they charge you: at capture, at retrieval, or monthly in migration and review. Below are six well-known approaches, what each optimizes for, and the specific point where each tends to break down once you are writing something long.
- Methods differ in where they charge you: at capture, at retrieval, or monthly.
- Zettelkasten develops ideas; it will not produce an outline before a deadline.
- PARA files by actionability but never explains how two notes relate.
- Bullet journaling and dated logs are capture layers, not research stores.
- Most durable setups combine two or three layers with one clear promotion rule.
Zettelkasten: built for connection
The slip-box approach, associated with the sociologist Niklas Luhmann, asks for small notes holding one idea each, written in your own sentences and linked densely to their neighbours. Nothing sits in a hierarchy. Structure emerges from links, and entry points arrive later as index notes or maps of content.
It is unmatched for developing thought across years, since rereading a chain of linked notes often yields an argument you never consciously formed. The cost lands hardest on deadlines: a dense web offers no obvious place to start a piece due Friday, and a link is not an outline.
PARA: built for action
PARA, from Tiago Forte, sorts material by how actionable it is rather than by subject: Projects with end dates, Areas of ongoing responsibility, Resources for topics of interest, and Archives for anything closed. Notes migrate as status changes, and filing is quick because there are only four options.
It suits writers juggling commissions, since one folder holds the brief, the sources, and the draft. It struggles with books, where a project runs for years and Resources becomes an undifferentiated dump. PARA says nothing about how two ideas relate, so alone it stores material without developing it.
Every method is a bet about which problem will hurt most, and long-form writers usually bet wrong on their first try.
Bullet journaling: built for the day
Ryder Carroll's method runs on rapid logging in a paper notebook: short entries marked as tasks, events, or notes, written under the date and carried forward by hand when a month ends. Manual migration is the mechanism, because anything not worth rewriting is allowed to die.
The honesty is the strength, and many writers find the daily page settles the mind before a session. The limits are practical. Paper cannot be searched, entries are chronological rather than thematic, and gathering everything you have thought about one theme means flicking back through months.
Commonplace book: built for language
The oldest method here, kept by readers for centuries, is a book of copied passages, quotations, and observations, often gathered under headings such as memory or ambition. You transcribe whatever strikes you, then reread the collection for pleasure and for phrasing.
It is genuinely useful for voice, because a store of well-made sentences trains the ear. The weakness is that it holds other people's language. Synthesis is optional, so the book fills with admired lines and few claims of your own, and heavy borrowing raises attribution problems in published work.
Progressive summarization: built for rereading
Also from Tiago Forte, this method layers on top of sources you have already saved. You bold the passages that matter, highlight the strongest of those bolded lines, and later add a short summary at the top, so a long document can be skimmed at whichever depth you need.
It makes a saved library usable, and the effort follows real use, since each layer is added only when you open the file again. The trap is that it rewards decorating other people's text. Highlighting can feel like thinking while producing no sentence of your own.
The plain dated log: built for zero friction
One file per day, or a single append-only file, with everything typed in as it occurs and found later by searching. There is no filing and nothing to maintain. Its advantage is that it never fails at the moment of capture, which is where most systems actually die.
It also preserves chronology, which helps when you need to reconstruct how an opinion developed. Retrieval, though, depends entirely on recalling your own phrasing, and nothing is ever promoted, so ideas stay buried in the day they arrived. Use it as a capture layer feeding something else.
Combining them without building a hybrid mess
Most working setups end up as two or three layers rather than one method. A common shape: capture in a dated log, promote the few ideas worth keeping into permanent notes, and organize live commitments by project. Each layer does one job and hands off.
Keep the seams simple. Decide the single rule for promotion and the one place a live project lives. Trouble starts when two methods both claim to own active work. Add a further layer only once you can name the failure it prevents, or it will be abandoned within a month.
One Tuesday's captures, routed through a combined setup
Dated log, 14 May, typed as things happened: 09:20 call with the print supplier, lead times now four weeks, they blamed the paper mill again. 11:05 idea while walking: committee decisions feel slow because everyone is optimising for not being blamed rather than for the outcome. 14:30 book, chapter on shipbuilding, apprenticeship lasted seven years and nobody thought that long. 16:00 send the revised contract. 21:15 the essay is still two arguments pretending to be one.
Promoted the same evening. The blame line became a permanent note titled 'Committees optimise for defensibility, not outcomes', written in full sentences and linked to two earlier notes on decision speed. The shipbuilding detail was appended to an existing note on how long mastery takes, since it is evidence rather than a claim. Supplier lead times went to the print project. The contract reminder went to the task list, and the last line into the essay's own file.
Five captures, four destinations, one rule: claims become permanent notes, job-specific facts go to the project, and the rest is discarded.
Common mistakes
| The mistake | Why it costs you, and what to do instead |
|---|---|
| Adopting the whole system at once | A complete method looks coherent in an article and collapses in week three, because every habit arrived together. Adopt one behaviour, such as writing notes in full sentences, and live with it for a month. |
| Copying a method built for a different job | Systems designed for consultants and students are optimised for recall and throughput, not for building an argument. Read what a method assumes. If it never mentions producing text, expect to supply that layer yourself. |
| Running two homes for active work | When both a project folder and a linked note tree claim the current piece, material splits and neither half is complete. Name one location as the home of live work; the other becomes a source. |
| Switching methods to avoid writing | Reorganising feels productive and risks nothing, which makes it tempting when a draft is stuck. Watch the timing. If the urge to migrate arrives mid-project, finish the piece before deciding anything. |
Your checklist
- Name the job you need most: connection, action, capture, phrasing, or recall.
- Pick one method for that job and a capture layer beneath it.
- Write down your single rule for promoting a capture into a permanent note.
- Declare one home for live projects and treat the rest as sources.
- Run the setup for four weeks before judging it.
- Add a further layer only when you can name the failure it prevents.
Key terms
- Atomic note
- A note holding one idea, written in complete sentences so it can be understood alone and reused in any piece without reopening the source it came from.
- Map of content
- A curated index note listing links to related notes on a theme, added later to give a growing web of notes deliberate entry points.
- Rapid logging
- Bullet journaling's capture technique: very short entries marked by symbol as tasks, events, or notes, written under the current date as they occur.
Turning a pile of notes into something?
Frequently asked questions
Which method is best for writing a book?
+
A layered setup usually wins: a low-friction capture log, permanent notes for the ideas and evidence you will argue from, and a project structure holding chapters, sources, and drafts. No single named method covers all three well over the length of a book.
Is Zettelkasten worth the effort for a working writer?
+
Zettelkasten is worth the effort if you write repeatedly about overlapping subjects, because the same notes keep paying out across pieces. It is poor value if your commissions are unrelated one-offs, where a project folder and good search will serve you better for far less work.
Can I use PARA and Zettelkasten together?
+
Yes, and it is a common pairing. PARA organises commitments and their supporting files, while the note tree holds durable ideas independent of any deadline. Keep the boundary explicit so a note has an obvious home rather than two plausible ones.
Does paper still make sense?
+
For planning and thinking, often yes: handwriting is slower, which improves what you choose to record. For research you intend to search, quote, and draft from, digital wins clearly. Many writers run both, with the notebook feeding the searchable store.
How do I know a method has failed?
+
Two signals. You stop capturing during busy weeks, meaning the friction is too high. Or you start a piece and cannot find material you know exists, meaning retrieval has failed. Fix whichever end is broken instead of replacing the entire system.
Should I migrate years of old notes when I change method?
+
No. Migrate only what a current project needs, and leave everything else searchable where it sits. Bulk migration takes weeks, produces no writing at all, and usually ends by revealing that most of the old archive was never going to be used.