Frequently asked questions about thinking, epistemology, and cognitive tools. 3617 answers
Defining your workflows turns inconsistent effort into reliable output.
Defining your workflows turns inconsistent effort into reliable output.
Defining your workflows turns inconsistent effort into reliable output.
Defining your workflows turns inconsistent effort into reliable output.
Defining your workflows turns inconsistent effort into reliable output.
Identify one recurring task you perform at least weekly — something you do repeatedly but have never formally described. It could be your morning routine, your process for responding to emails, how you prepare for meetings, how you write, how you cook dinner on weeknights, how you review your.
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 —.
Defining your workflows turns inconsistent effort into reliable output.
An undocumented workflow lives only in your head and degrades over time.
An undocumented workflow lives only in your head and degrades over time.
An undocumented workflow lives only in your head and degrades over time.
Pick one workflow you do at least weekly — your morning routine, your expense process, your content creation sequence, your weekly review. Set a timer. Write every step as a numbered list, including steps that feel too obvious to mention. Include decision points: 'If X, then step Y; otherwise step.
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.
An undocumented workflow lives only in your head and degrades over time.
Every workflow needs a clear trigger that initiates the sequence.
Every workflow needs a clear trigger that initiates the sequence.
Every workflow needs a clear trigger that initiates the sequence.
Every workflow needs a clear trigger that initiates the sequence.
Every workflow needs a clear trigger that initiates the sequence.
Every workflow needs a clear trigger that initiates the sequence.
Choose one workflow you already have documented — or one you perform regularly but have not yet written down. Identify whether it currently has an explicit trigger or whether it relies on you 'remembering' or 'feeling like it.' If there is no trigger, design one using the if-then format: 'When.
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.
Every workflow needs a clear trigger that initiates the sequence.
Each step in a workflow should be small enough to complete without ambiguity.