Frequently asked questions about thinking, epistemology, and cognitive tools. 1668 answers
Treating every notification as a trigger and every trigger as equally important. You install a habit app, set twelve daily reminders, enable notifications for every productivity tool, and create calendar events for every intention. Within a week, your phone buzzes so frequently that you stop.
Confusing social triggers with social pressure. You recruit five accountability partners, join three mastermind groups, and post your goals publicly on LinkedIn. Now you have performance anxiety instead of activation energy. The trigger fires constantly but produces avoidance rather than action..
Adding one more trigger because this one feels important — while ignoring that the last five also felt important when you added them. The failure is never a single trigger; it's the cumulative weight of triggers that each seemed reasonable in isolation. You'll know you've hit fatigue when you feel.
Building an elaborate trigger system and then never reviewing it. Your triggers quietly degrade as your environment, schedule, and priorities shift. You blame yourself for 'losing discipline' when the real problem is unmaintained infrastructure. The system didn't fail — you stopped maintaining it.
Designing triggers that are legible only to your aspirational self — the version of you that is alert, motivated, and paying attention — rather than your actual self, the one who is tired, distracted, and operating on autopilot. This is the equivalent of designing a beautiful interface that only.
Spending weeks designing the 'perfect' trigger before ever testing it. You research the ideal conditions, the optimal phrasing, the best environmental setup — and you never actually deploy anything. Or the opposite: you set a broad trigger on day one and never revisit it, accepting a 30%.
Believing that mastery means having triggers for everything — including things that do not matter. Comprehensive does not mean exhaustive. A system with triggers for every possible condition is not masterful; it is overloaded. Trigger fatigue (L-0436) will destroy it. Mastery is coverage of what.
Treating every decision as unique. When you fail to recognize recurring types, you approach each decision from scratch — re-gathering information, re-weighing criteria, re-deliberating tradeoffs that you have already resolved in structurally identical situations. This is not thoroughness. It is.
Building one master decision framework and applying it to everything. This is the 'man with a hammer' error Munger warned about. You'll either slow to a crawl on low-stakes decisions or dangerously simplify high-stakes ones. The failure feels like productivity — you have 'a system' — but the.
Treating the matrix output as the answer rather than as a structured input to your judgment. When people build their first decision matrix, they tend to either game the weights to confirm what they already wanted or mechanically follow the highest score without asking whether the model captured.
Intellectually agreeing that most decisions are reversible while continuing to deliberate on every one of them. The framework becomes another thing you know about instead of something that changes your behavior. You'll catch yourself when you notice the third meeting about a decision that could be.
Nodding along with this lesson and then maximizing anyway because 'this decision is different — it really matters.' That rationalization is the maximizer's signature move. The more a decision feels important, the more likely you are to over-search. But consequence magnitude is not the same as.
Writing pre-commitment rules that are too vague to enforce. 'I'll eat healthier' is a goal, not a pre-commitment. 'If I reach for a snack after 8pm, then I drink a glass of water and wait ten minutes' is a pre-commitment. The other failure mode is creating so many rules that you can't track them..
Applying artificial urgency to genuinely irreversible decisions that deserve deliberation. Time pressure is a tool for the 90% of decisions that are reversible and low-stakes. Using it on one-way doors — selling a house, accepting a job in another country, shutting down a product line — produces.
Designing defaults that serve your current preferences but never revisiting them. Defaults calcify. A default you set six months ago may no longer match your priorities, and because the entire point of defaults is that they operate without conscious attention, outdated defaults silently steer you.
Treating opportunity cost as a reason to never commit to anything. Analysis paralysis is not opportunity cost thinking — it's the failure mode of opportunity cost thinking. The goal is not to agonize over every alternative. It's to build the reflex of asking 'what am I giving up?' before the.
The most common failure is delegating the decision but not the authority. You tell someone they own the vendor selection, then override their choice because you would have picked differently. This is worse than never delegating at all — it teaches your team that delegation is theater and that the.
Applying a solo decision framework to a group context and wondering why it fails. You build a careful decision matrix, present it to the team, and expect alignment — but the group resists, not because your analysis is wrong, but because they had no role in constructing it. Group decisions require.
Using regret minimization to rationalize impulsive decisions. The framework asks you to consult your future self, not your excited present self wearing a future-self costume. If your 'age 80 projection' conveniently agrees with whatever you already want to do right now, you haven't done the.
Setting kill criteria so vague they never trigger ('if things aren't going well') or so extreme they're functionally irrelevant ('if we lose all our customers'). Useful kill criteria live in the uncomfortable middle — specific enough to fire, realistic enough to actually happen. The other failure.
Conflating outcome quality with decision quality. When things go well, you credit your brilliance. When things go badly, you blame your judgment. This makes your review useless — you learn nothing about your actual decision process because you are only responding to results. The deeper failure is.
The most common failure mode is framework lock-in — defaulting to the same decision framework for every decision regardless of fit. You learn the weighted decision matrix, it works well once, and now every decision gets a matrix. This is the meta-decision equivalent of the law of the instrument:.
Systematizing everything, including the decisions that should stay open. You build frameworks for your creative process itself — which ideas to pursue, which aesthetic directions to explore, which risks to take. Your work becomes efficient and utterly predictable. The point of decision frameworks.
Treating the loop as a one-time event instead of a continuous cycle. You evaluate once, adjust once, and then coast on the assumption that the adjustment worked. The loop only generates learning when it keeps running — when the adjustment itself becomes the next action that gets observed and.