Frequently asked questions about thinking, epistemology, and cognitive tools. 200 answers
Blocking time but treating the blocks as soft suggestions rather than commitments. The most common pattern: you block 9 to 11 for deep work, an 'urgent' Slack message arrives at 9:15, and you tell yourself you'll return to the block after this one thing. You won't. The block is gone. Time blocking.
Confusing a workflow with rigidity or bureaucracy. When people hear 'repeatable sequence of steps,' they sometimes imagine a factory assembly line — soulless, mechanical, creativity-destroying. This is the wrong image. A workflow is a baseline, not a cage. Jazz musicians practice scales —.
Treating documentation as a one-time project rather than a living artifact. You write down your morning routine, feel organized, then never update it. Six months later the document describes a workflow you abandoned in March. The failure isn't in the initial capture — it's in assuming.
The most common failure is designing triggers that are actually goals in disguise. 'When I feel motivated to exercise' is not a trigger — it is a hope. 'When I notice the kitchen is messy' is not a trigger — it is a judgment call that requires the very executive function the trigger is supposed to.
Going too fine. Atomicity is not an instruction to decompose every action into its smallest conceivable components. If your morning workflow includes a step that says "pick up the toothbrush with your dominant hand," you have passed the useful threshold and entered bureaucratic overhead territory..
Two opposite errors are common. The first is treating everything as sequential when most steps have no real dependency — you wait for the oven to preheat before you start chopping, even though chopping requires nothing from the oven. The workflow takes twice as long as it needs to. The second.
Two opposite failures. The first is checkpoint absence — no verification points at all, so errors propagate from the step where they originate to the final output with nothing in between to catch them. You draft, edit, and send an email in one unbroken flow, and the factual error in paragraph two.
Treating a template as scripture rather than scaffolding. You created a project kickoff template six months ago. The world has changed, your tools have changed, your role has changed — but the template hasn't. You follow it mechanically because it exists, skipping the judgment call about whether.
The most dangerous failure mode is not building too little — it is building too much. The person who designs a fourteen-step morning routine before executing it once, who creates elaborate templates before knowing which fields they actually use, who automates a process they have never run.
The most common failure is optimizing a non-bottleneck step. You make your fastest step even faster while the slowest step remains untouched. Total throughput does not change. The second failure is identifying the wrong bottleneck — confusing the step that feels most painful with the step that.
Automating everything indiscriminately. The failure is not too little automation but automation applied without the sovereignty check — automating judgment steps, automating steps you do not fully understand, or automating so aggressively that you lose the situational awareness required to catch.
Treating input-output specification as obvious and therefore not worth writing down. The failure is not imprecise specification — it is absent specification. You know what the input 'should be' and you know what 'done' looks like, but you have never made either explicit. The result is that every.
The most common failure is assuming that the handoff is the other party's problem — that if the recipient does not understand, they should have asked better questions. This reverses accountability. The sender is responsible for ensuring that the handoff contains sufficient context for the receiver.
Measuring so many things that the measurement itself becomes a workflow burden. You install time trackers, build dashboards, tag every task — and then spend more time maintaining the measurement system than improving the workflows it was supposed to illuminate. The opposite failure is equally.
Changing three things at once after every execution, making it impossible to know which change helped and which hurt. Or worse — redesigning the entire workflow every time it feels slow, oscillating between approaches without ever letting one stabilize long enough to measure. Iteration requires.
Treating all instances of a task type as identical and applying the same workflow regardless of context. This produces two failure patterns: over-engineering low-stakes situations (spending forty-five minutes drafting a two-sentence reply) and under-engineering high-stakes situations (dashing off.
Building a massive library that you never maintain. Workflows go stale as your tools change, your context shifts, or you discover better approaches. Six months later, half the library describes processes you no longer follow, and the other half is missing workflows you developed since the last.
Building monolithic workflows that try to do everything in one unbroken sequence. The monolith feels simpler because it is one thing rather than five, but it is fragile in ways that composed workflows are not. When a monolithic workflow fails at step seven, you must restart from step one — because.
Never reviewing at all, letting your workflow portfolio accumulate dead weight — workflows for projects that ended, tools you no longer use, processes that were patched so many times they no longer resemble their original design. Or reviewing too frequently at too granular a level, spending more.
Two symmetric failures. The first is never sharing — hoarding your workflows as personal competitive advantage, or simply never bothering to document them well enough for anyone else to use. This leaves your team fragile, your knowledge trapped, and your workflows unimproved by outside.
Two capstone-level failures bracket this phase. The first is workflow nihilism — completing twenty lessons on workflow design and concluding that it is all too mechanical, too structured, too industrial for a creative and autonomous life. This person learned the tools but rejected the premise..
Two equal and opposite failures bracket this lesson. The first is time blindness — the belief that time is abundant, elastic, or somehow renewable. This person treats time like money: spend it now, earn it back later. They schedule more tasks than hours, agree to more commitments than their.
Two failures bracket the ideal week. The first is the fantasy template — a schedule so optimistic, so perfectly balanced, so ruthlessly efficient that no actual human could sustain it. Every hour is allocated. Every day is themed. There is no slack, no buffer, no margin for the unexpected. This.
Two complementary failures bracket this lesson. The first is undefended maker time — blocking time on a calendar but treating the block as a suggestion rather than a commitment. This person has "focus time" on their schedule, but they answer messages during it, accept meeting invitations that.