Define workflow inputs as precondition checklists — every…
Define workflow inputs as complete checklists of preconditions—every piece of information, material, and state that must be true before the first step can execute—rather than treating inputs as obvious or self-evident.
When This Fires
- When designing any workflow that will be executed more than once
- When a workflow repeatedly stalls at the beginning because something wasn't ready
- When handing off a workflow and wanting to ensure the recipient can start without interruption
- Complements Competent stranger test for workflow steps — could someone… (competent stranger test) by making the preconditions explicit rather than assumed
Common Failure Mode
"Obviously you need X before starting" — but what's obvious to the workflow author is not obvious to the executor, especially future-self after months of context loss. Every "obviously" is an undocumented precondition that will eventually cause a failed start.
The Protocol
(1) For each workflow, create a Start Checklist before the first step. (2) List every precondition in three categories: Information (data, documents, decisions that must be in hand), Materials (tools, templates, access credentials, software), and State (system status, environmental conditions, collaborator availability). (3) Make each item binary-checkable: "Client budget received: Y/N" not "Budget stuff is ready." (4) Before executing the workflow, run through the checklist. If any item is unchecked, resolve it before starting step 1. (5) After each workflow execution, ask: "Did I discover a missing precondition mid-workflow?" If yes, add it to the checklist immediately.