Frequently asked questions about thinking, epistemology, and cognitive tools. 9738 answers
Pick a workflow you executed this week — a meeting you ran, a document you produced, a deployment you shipped. Write down three sentences: what the workflow is, how long it took, and one specific friction point you noticed. Now write one change you will make next time to address that friction. Do.
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.
After each execution look for one thing to improve in the workflow.
The same type of task may need different workflows in different contexts.
The same type of task may need different workflows in different contexts.
The same type of task may need different workflows in different contexts.
The same type of task may need different workflows in different contexts.
The same type of task may need different workflows in different contexts.
The same type of task may need different workflows in different contexts.
Pick one recurring task type in your life — writing, exercise, cooking, problem-solving, or decision-making. List three to five different contexts in which you perform that task (varying by urgency, stakes, energy level, environment, or audience). For each context, write a one-paragraph.
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.
The same type of task may need different workflows in different contexts.
Build a collection of proven workflows you can deploy when needed.
Build a collection of proven workflows you can deploy when needed.
Build a collection of proven workflows you can deploy when needed.
Build a collection of proven workflows you can deploy when needed.
Open a new document or note and title it 'Workflow Library v1.' Create three sections: Daily (workflows you run every day or almost every day), Recurring (weekly, monthly, quarterly), and Situational (triggered by specific events or contexts). Under each section, list every workflow you can recall.
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.
Build a collection of proven workflows you can deploy when needed.
Complex workflows are built by combining simpler workflows. The output of one becomes the input of another. Composition is the mechanism that turns a library of small, proven workflows into an infrastructure that handles arbitrarily complex work.
Complex workflows are built by combining simpler workflows. The output of one becomes the input of another. Composition is the mechanism that turns a library of small, proven workflows into an infrastructure that handles arbitrarily complex work.
Complex workflows are built by combining simpler workflows. The output of one becomes the input of another. Composition is the mechanism that turns a library of small, proven workflows into an infrastructure that handles arbitrarily complex work.
Complex workflows are built by combining simpler workflows. The output of one becomes the input of another. Composition is the mechanism that turns a library of small, proven workflows into an infrastructure that handles arbitrarily complex work.
Complex workflows are built by combining simpler workflows. The output of one becomes the input of another. Composition is the mechanism that turns a library of small, proven workflows into an infrastructure that handles arbitrarily complex work.