What does it mean that context-dependent workflows?

The same type of task may need different workflows in different contexts.

Example: You have a writing task. But 'writing' is not one thing. A quick Slack reply to a colleague needs no outline and no revision pass. A strategic memo to leadership needs structured thinking, multiple drafts, and a cooling-off period before sending. A creative essay needs freewriting, incubation, and ruthless editing. Same verb — write — but three completely different workflows. The person who uses the same process for all three either over-engineers the Slack message or under-engineers the memo.

Try this: 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 description of the ideal workflow variant. Notice where your current default workflow matches the context and where it does not. Identify the single highest-leverage context switch — the one where adopting a different workflow variant would produce the biggest improvement.