Workflows you can repeat without numbness
A workflow is the story of how work moves — who touches it, what “done” means at each stage, and where quality is actually checked.
From one-off to pattern
People create repeatable processes by noticing a sequence that already worked twice — then writing it down before pride renames luck as instinct. The first draft should be embarrassingly concrete: attach the template file, name the approval person, specify the folder path. Abstraction comes later; legibility comes first.
Checkpoints beat hope
Workflows fail when quality is assumed at the end. Intermediate checkpoints — a draft reviewed for structure before line-editing, a prototype before visual polish — catch expensive mistakes early. Each checkpoint should have a single question: “Does this stage’s job match reality?” If the question spawns a meeting, the workflow is still too vague.
Handoffs are where work disappears. A good handoff includes three things: the artifact, the decision already made, and the next decision required. “Please review” is not a handoff; it is a shrug. Replace it with “choose A or B by Thursday; default is A if silent.” Defaults respect other people’s time.
Automation helps when the task is stable; it hurts when the task is still learning. We automate late — after the human loop has settled — so you do not encode the wrong problem efficiently.
- Trigger: What event starts the workflow — a client message, a calendar date, a threshold in a sheet.
- Inputs: What must be present before step one earns the name “step one.”
- Outputs: Artifacts named like files, not vibes — “invoice PDF v1,” not “finished.”
- Owner per stage: One throat to choke; shared ownership is unowned work.
