Frequently asked questions about thinking, epistemology, and cognitive tools. 200 answers
Transcribing instead of transforming. If your notes are a slightly shorter version of the source text using the author's language, you have not processed the information — you have copied it. The test is simple: could you have written your note without understanding the material? If yes, the note.
The most common failure is collecting without connecting. You create hundreds of notes but never link them, producing a digital filing cabinet rather than a knowledge network. The notes sit in isolation, and since a note without connections is invisible to the network traversal that makes the.
The most common failure is creating cards that are too complex. A card that asks 'Explain the forgetting curve and its implications for learning' is not a spaced repetition card — it is an essay prompt. The system works because it tests small, specific facts that you can retrieve in seconds..
The most common failure is setting expiration dates that are too generous. You tag a project status update as "expires in one year" when its real useful life is two weeks, because you are uncomfortable committing to deletion. The result is that your expiration system barely removes anything, and.
The most common failure is interpreting 'search over sort' as 'never organize anything.' You abandon all structure, dump everything into a single undifferentiated pile, and trust search to do all the work. This fails when your notes have vague titles, when you use inconsistent terminology, or when.
The most common failure is summarizing too early and too eagerly — treating progressive summarization as a batch processing job rather than an incremental, just-in-time practice. You sit down on a Saturday, open fifty notes, and try to bold, highlight, and summarize all of them in one session..
The most common failure is confusing aggregation with synthesis. Aggregation collects: here are five sources that discuss leadership. Synthesis creates: these five sources, taken together, reveal a contradiction in how leadership is taught versus how it is practiced, and that contradiction.
The most common failure is sharing at the wrong level of abstraction for the audience. You spent hours processing and synthesizing, so you want to share all of it — the full journey, every nuance, every caveat. But the person receiving your information does not need your journey. They need the.
The most common failure is treating bankruptcy as a last resort rather than a maintenance operation. You wait until the backlog is so enormous that it has become a source of daily anxiety, and by then the emotional weight of declaring bankruptcy is high — it feels like admitting defeat. The fix is.
Designing the perfect processing schedule instead of starting an imperfect one. You spend an hour deciding whether 8:00am or 8:30am is optimal, whether to process email first or notes first, whether a 20-minute or 30-minute window is ideal. Meanwhile, your inboxes accumulate another day of.
The most common failure is using this lesson as justification for never improving your tools at all. The lesson does not say tools do not matter — it says habits matter more. A tool that genuinely cannot support your workflow should be replaced. The criterion is whether the limitation is in the.
The capstone failure is treating information processing as a project to complete rather than an infrastructure to maintain. You finish this phase, feel the satisfaction of having a system, and then gradually stop using it. The daily sweep lapses. The processing cadence breaks. The notes accumulate.
Treating this lesson as permission to stop learning and start mindlessly producing. The point is not output at the expense of quality — it is that learning without output is incomplete. The failure is swinging from pure consumption to pure production without the processing that makes output.
The most common failure is never distinguishing between output types at all — treating everything you produce as undifferentiated "work." When all output is just work, you cannot allocate effort intelligently, you cannot set different quality thresholds for different types, and you cannot identify.
The most common failure is applying a single quality standard to all output types — treating every deliverable as if it requires the same level of polish, rigor, and review. This produces two simultaneous problems: critical outputs are under-polished because you ran out of energy over-polishing.
The most common failure is building a checklist so long it becomes its own project. A forty-item checklist is not a quality gate — it is a bureaucratic obstacle that you will skip the moment you are under time pressure. Effective checklists are short enough to use every single time, which means.
The most common failure is a stealth merger — you tell yourself you are doing a creation pass, but you cannot resist rereading the last paragraph and tweaking a sentence before moving forward. Each tweak pulls you out of generative mode and into evaluative mode, and the switching cost accumulates.
The most common failure is over-engineering templates — building elaborate multi-page structures with detailed instructions for every section, creating a template so rigid that filling it out feels like compliance paperwork rather than accelerated creation. The second failure is hoarding templates.
Treating MVO as permission to ship sloppy, thoughtless work. The minimum viable output is not the minimum possible effort — it is the minimum complete version that delivers real value. Stripping an output below the viability threshold produces something that wastes the recipient's time and damages.
Interpreting this lesson as permission to ship garbage at high velocity. Frequency without a minimum quality threshold produces noise, erodes trust, and trains your audience to ignore you. The point is not maximum frequency — it is consistent frequency above the MVO threshold established in L-0867.
The most common failure is treating "ship early" as permission to ship garbage. Early shipping without a minimum viable quality bar produces noise that trains your audience to ignore you. The second failure is shipping early once, receiving critical feedback, and retreating into perfectionism.
The most common batching failure is batching without preparation, which turns a focused production session into a scattered research session. If you sit down to batch four blog posts but have not outlined any of them, you are not batching production — you are doing serial creative work with no.
Designing an elaborate pipeline with six or seven stages, detailed checklists at each gate, and formal sign-off procedures — then abandoning it within a week because the overhead exceeds the value for your actual output volume. The pipeline must match the scale of your production. A solo creator.
Versioning everything with equal rigor, turning every casual email and Slack message into a tracked artifact. The cost of versioning must be proportional to the value of the output. Over-versioning creates administrative overhead that slows production rather than supporting it.