Systematize only recurring activities with consistency requirements — protect spontaneous, creative, and variable activities from workflow engineering
Apply workflow design methodology only to recurring activities with consistency requirements—protect spontaneous, creative, and variable activities from systematization.
Why This Is a Rule
Workflow design methodology is powerful for recurring, consistency-dependent activities: weekly reports, data processing, client onboarding, code deployment. But the same methodology applied to creative exploration, relationship building, brainstorming, or novel problem-solving destroys the very qualities that make those activities valuable. Creativity requires variability; workflows eliminate variability. Exploration requires following unexpected paths; workflows define predetermined paths.
The distinction maps to Kahneman's System 1/System 2 framework at the activity level: some activities benefit from deliberate, structured execution (System 2 territory — workflow them). Others benefit from intuitive, fluid, responsive engagement (System 1 territory — protect them from systematization). Trying to workflow a brainstorming session is like trying to flowchart a conversation — the structure constrains the emergent discovery that is the whole point.
Two criteria determine whether an activity should be systematized: Recurrence (does this happen regularly?) and Consistency requirement (does the output need to be reliably similar each time?). Activities that are both recurring and consistency-dependent (payroll processing, safety checklists, deployment procedures) benefit enormously from workflow design. Activities that are neither recurring nor consistency-dependent (one-time creative projects, exploratory research, relationship conversations) are actively harmed by it.
When This Fires
- When tempted to systematize everything in your life for "optimization"
- When a creative or exploratory activity feels constrained by the process you put around it
- When deciding which activities to workflow-design and which to leave fluid
- Complements Reduce choices for routine/low-stakes/high-frequency decisions — maintain full optionality only for novel/high-stakes/infrequent ones (choice reduction scope) with the parallel scope boundary for workflow engineering
Common Failure Mode
Productivity-system creep: the satisfaction of systematizing one domain leads to systematizing everything. "My deployment workflow is great — let me workflow my creative writing too!" The deployment workflow made deployment faster and more reliable. The writing workflow made writing feel like filling out a form. The tool was right for one domain and wrong for the other.
The Protocol
(1) Before designing a workflow for any activity, apply the two-criteria test: Is it recurring (happens at least monthly)? Does it require consistency (output quality or format needs to be reliably similar)? (2) Both criteria met → workflow it. (3) Only recurrence met (but consistency isn't needed) → use light structure at most (a checklist, not a full workflow). (4) Neither met → protect from systematization. Leave it fluid, intuitive, responsive. (5) Regularly audit your workflow portfolio for over-systematization: are any creative, spontaneous, or variable activities feeling constrained by workflows? If yes, remove the workflow and return to fluid execution.