Systematize only recurring activities with consistency…

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… (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.