Frequently asked questions about thinking, epistemology, and cognitive tools. 1214 answers
Identify the slowest step in each workflow — that step determines your throughput.
Select a workflow you perform at least monthly — a content pipeline, a client onboarding process, a project delivery cycle, a weekly review. Write out every step and estimate how long each step takes in practice (not how long it should take — how long it actually takes, including delays,.
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.
Identify the slowest step in each workflow — that step determines your throughput.
Look for steps that can be handled by tools or systems rather than manual effort.
Look for steps that can be handled by tools or systems rather than manual effort.
Look for steps that can be handled by tools or systems rather than manual effort.
Look for steps that can be handled by tools or systems rather than manual effort.
Look for steps that can be handled by tools or systems rather than manual effort.
Look for steps that can be handled by tools or systems rather than manual effort.
Select a workflow you documented earlier in this phase — ideally one you perform at least weekly. List every step. For each step, answer three questions: (1) Is this step well-defined enough that I could explain it to someone with no context and they could execute it correctly? (2) Does this step.
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.
Look for steps that can be handled by tools or systems rather than manual effort.
Define clearly what goes into each workflow and what comes out. Without precise input-output specification, you cannot chain workflows, automate steps, or diagnose failures.
Define clearly what goes into each workflow and what comes out. Without precise input-output specification, you cannot chain workflows, automate steps, or diagnose failures.
Define clearly what goes into each workflow and what comes out. Without precise input-output specification, you cannot chain workflows, automate steps, or diagnose failures.
Define clearly what goes into each workflow and what comes out. Without precise input-output specification, you cannot chain workflows, automate steps, or diagnose failures.
Define clearly what goes into each workflow and what comes out. Without precise input-output specification, you cannot chain workflows, automate steps, or diagnose failures.
Define clearly what goes into each workflow and what comes out. Without precise input-output specification, you cannot chain workflows, automate steps, or diagnose failures.
Choose one workflow you perform regularly. Write down, explicitly, the complete input specification: every piece of information, every material, every precondition that must be true before the first step can execute. Then write the complete output specification: the concrete deliverable, its.
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.
Define clearly what goes into each workflow and what comes out. Without precise input-output specification, you cannot chain workflows, automate steps, or diagnose failures.
Where one person or system passes work to another is where errors are most likely.
Where one person or system passes work to another is where errors are most likely.