Frequently asked questions about thinking, epistemology, and cognitive tools. 604 answers
Treating the monthly review as a guilt session where you catalogue failures rather than a diagnostic session where you identify structural patterns and recalibrate commitments.
The most common failure is conducting a quarterly review that is just a bigger monthly review — checking metrics without questioning whether those metrics still measure the right things.
The most common failure is treating the annual review as a bigger quarterly review — evaluating projects and goals without stepping back to examine the life those projects and goals are embedded in. You emerge with a sharper strategy for the same trajectory, when the real question was whether the.
The most common failure is conducting AARs only for failures. When a project succeeds, most people move on without examining why it succeeded — which means they cannot reliably reproduce the conditions that led to success. A proper AAR covers both positive and negative outcomes, because.
The most common failure is asking questions that are too vague to generate specific answers. 'How am I doing?' produces 'Fine.' Every time. Vague questions invite vague answers because they do not constrain the search space — your brain has no idea what aspect of your experience to examine, so it.
The primary failure is editing while writing. You write a sentence, decide it sounds wrong, delete it, and try again. This converts reflective writing into performance writing — you are now optimizing for how the words sound rather than discovering what you think. The entire mechanism of.
The primary failure mode is narrative imposition — seeing patterns that are not actually there. Nassim Taleb calls this the narrative fallacy: the human compulsion to weave disconnected events into a coherent story. You review three weeks of reflections, find two instances of frustration after.
The most common failure mode is performing reflection rather than doing it. You sit down, open your review document, and write honest-sounding sentences that never actually touch the uncomfortable truth. The review is thorough, well-structured, and entirely safe. You identify lessons learned that.
The most common failure is conducting a success review that produces only feel-good platitudes rather than actionable insight. "We succeeded because we had a great team" is not a finding — it is a congratulation. The review must push past emotional satisfaction to structural understanding. What.
The most common failure is treating energy and emotion tracking as a mood diary rather than as operational data. You note that you felt tired on Tuesday and anxious on Thursday, but you never analyze why or change anything structural in response. The tracking becomes a ritual of self-reporting.
The most common failure is performing a systems review that is actually just action review in disguise. You write "my system for morning exercise is broken" when what you mean is "I did not exercise this morning." The distinction matters: a genuine systems review examines the structural elements —.
The primary failure mode is toxic positivity masquerading as gratitude — using the gratitude section to avoid or minimize genuine problems. If your project failed because you did not manage dependencies, writing "I am grateful for the learning opportunity" without also writing "I failed to track.
The most dangerous failure mode is sharing with the wrong person. You open a vulnerable reflection to someone who lacks psychological safety — someone who judges, competes, advises prematurely, or later uses what you shared against you. One bad sharing experience can shut down the practice.
The most common failure mode is treating reflection resistance as a personal deficiency rather than a data source. You notice that you skipped a topic, and instead of getting curious about why, you berate yourself for being undisciplined or cowardly. The self-criticism adds another layer of.
The most common failure is treating the reflection archive as a journal graveyard — a place where reflections go but never come back from. You diligently file every weekly review, every after-action report, every quarterly reflection. The archive grows to hundreds of entries. And you never search.
The most common failure is treating reflection as a fixed trait rather than a developable skill. You write a few mediocre journal entries, conclude that you are 'not a reflective person,' and stop. This is the fixed mindset applied to metacognition — the belief that reflection ability is innate,.
The capstone failure mode is building an elaborate review system on paper and then failing to actually use it — confusing the architecture with the practice. You design daily, weekly, monthly, quarterly, and annual reviews with beautiful templates and carefully chosen questions, and then life.
The primary failure mode is tool fetishism — spending more time evaluating, configuring, customizing, and switching tools than actually doing the work the tools are supposed to support. This is the person who has tried fourteen note-taking applications and has substantial notes in none of them..
The primary failure mode is feature-based selection — choosing tools by comparing feature lists rather than evaluating fit for your specific workflow. Feature comparison feels rigorous because it produces a neat matrix of checkmarks, but it systematically biases you toward the most complex option.
The most common failure is confusing tool collection with tool competence. You install a new application every week, watch the introductory tutorial, use it for one project at a surface level, and then move on to the next recommendation from a productivity blog. After a year, you have accounts on.
The most common failure is treating tool selection as a series of independent decisions rather than a system design problem. You choose the best note-taking app, the best task manager, the best calendar, the best reading app — each evaluated in isolation on its own merits. But a tool stack is not.
The most common failure is making the SSOT declaration without changing the behavior. You announce that your task manager is the single source of truth for tasks, but you keep jotting tasks in your notebook and never transferring them. The declaration becomes aspirational rather than operational —.
The most catastrophic failure is the big bang migration without a rollback plan. You export everything, import everything, delete the old system, and discover a week later that the import corrupted a critical subset of your data. The old system is gone. The corrupted data is unrecoverable. You.
The primary failure mode is confusing tool research with productive work. Reading comparison articles, watching demo videos, testing free trials, and configuring new applications all feel like progress — they activate the same reward circuits as actually doing meaningful work with your tools. But.