Somewhere between the third note-taking app and the fourth abandoned filing system sits this eighty-five-minute audiobook, which is aimed squarely at the person who has already tried and failed twice. The pitch is unusually narrow for the genre. Rather than argue for the Zettelkasten method, David Kadavy assumes you are sold and moves directly to the question of how to run one in software you already own, borrowing an element of the Getting Things Done framework to keep an unread pile from silently growing. It is a configuration guide wearing a book's cover, and whether that is a compliment depends entirely on what you came for.
Scope is what makes this work and also what makes it thin. The recording covers how to structure a Zettelkasten, whether the classic Folgezettel naming convention still earns its keep once digital search exists, the exact steps for turning reading into notes you can recombine, and how to keep the habit alive away from a desk. Every one of those is treated as a decision with tradeoffs rather than a doctrine, which is rarer in this corner of productivity writing than it should be. The description promises examples repeatedly, and the recording does deliver them, though how you receive them is a format question worth a paragraph of its own.
History gets almost no airtime, which is a deliberate omission worth knowing about. The description dates the method to the sixteenth century and credits its fullest practice to a German sociologist who produced seventy books and hundreds of articles, then reaches for the familiar metaphors, an external brain and a bicycle for the mind. That is roughly the last you hear of the lineage. Whether a method invented for index cards survives the move to software, and what is lost in the translation, are the interesting questions in this area, and this recording steps around both of them in order to get you configured faster. The tradeoff is defensible. It is still a tradeoff.
Padding is the charge the harshest notice makes, and it deserves an honest hearing. A three-star reviewer concludes this is "not a book, but more an extended article or collection of short blog posts" and adds that it is "very short which would be good if it delivered". Eighty-five minutes is genuinely short, and a listener who expects the intellectual history of the method, or an argument for why external note systems produce better thinking, will find neither. The book knows this about itself, promising to be short and to the point with no fluff, and the disagreement is really about whether brevity here is discipline or absence.
Kadavy's PDF Carries What Audio Can't Show
Tool independence is the promise, and the most detailed five-star notice confirms it was kept. That reviewer already owned another well-known book on the method and reports that reading it "didn't organically get me into using Obsidian the way I wanted", where this one did, crediting an author who "restricts the scope of study to the bare essentials" while keeping "the promise of a software-agnostic implementation guide". The same notice says the book answered the questions left over from How to Take Smart Notes. That is the useful positioning: this is not a rival theory, it is the implementation layer somebody else's theory never supplied.
Another five-star listener describes being stuck rather than uninformed, having read about the method and watched many videos without getting anywhere, and reports that this one "opened my understanding and also gave practical solutions for its application". Stuck is the right word for the audience. The recording is not competing for the attention of somebody encountering the idea for the first time, it is aimed at the person who understands the concept perfectly and still has an inbox of orphaned notes. On that specific problem it is unusually direct.
Kadavy reads his own work, which for a book of personal workflow decisions is the right call, since every recommendation here is a report on what one working nonfiction author actually does. The production makes one further decision that matters more than the reading: a companion PDF ships with the file, carrying the examples the audio can only gesture at. One reviewer praises "helpful infographics strategically placed throughout", and those infographics are precisely what a linear recording cannot hold. Download the PDF before you start rather than after, or the chapter built entirely around worked examples will pass by as abstraction, which is the one part of this recording that genuinely cannot be salvaged by attention.
Five Reviews Behind a Single Rating
Tool advocacy is the recurring irritation. A four-star notice objects that it does not like "when an author picks a program or suite of tools and basically advertises for them", concedes that alternatives do get mentioned, and notes that the mention was "about it". Both things are true at once. The method is genuinely portable, but the worked examples come from one setup, and a listener committed to a different application will spend some of the eighty-five minutes translating. That translation is not hard, though it does undercut the software-agnostic claim slightly.
This listing's counter does not match its own comment section. A 4.0 average sits behind exactly one rating while five people have written reviews underneath, so the score reflects a single vote and tells you nothing about consensus. One of those five comments predates the recording's release by roughly four months, which places it with the printed edition rather than this file. Read the written notices, ignore the number, and treat the star average on this page as an artifact rather than information.
Researchers Who Already Chose Their System
Writers, researchers and academics who have already decided to build a note system and want somebody to hand them a working default are the audience, and eighty-five minutes is a fair price for that. It also suits anyone rebuilding a collapsed system, since the reading workflow is described step by step rather than in principle. Listeners who prefer paper notebooks will still find something here, as the reviewer who prefers handwritten files did, though most of the value assumes software.
Anyone wanting the case for the method rather than the mechanics should look elsewhere, and so should anyone allergic to productivity writing that recommends specific applications. The other group to steer away is anyone who cannot use the companion PDF, because roughly a fifth of the value is sitting in it. Treated as a manual to be replayed while you set things up, this earns its runtime. Treated as a book to sit and listen through, it will feel like a long article with a cover charge.
