Sequential-by-default is a workflow smell — every numbered…

When This Fires

• When reviewing any existing numbered-list workflow for optimization opportunities
• When you notice a workflow taking longer than expected despite each step being efficient
• When creating a new workflow and writing it as a numbered list — pause and test for parallelism
• Complements Dependency test for adjacent steps — does step B require… (pairwise dependency test) with the meta-level awareness that serial is the default bias

Common Failure Mode

Accepting numbered order as dependency order without question. "The workflow says step 2 comes after step 1, so I'll wait for step 1 to finish before starting step 2." But the numbering may reflect the order the author thought of the steps, not their actual dependencies. The cost of questioning is a minute of analysis; the cost of not questioning is repeated unnecessary waiting.

The Protocol

(1) When you encounter or create a numbered-list workflow, treat the serial format as a smell, not a specification. (2) Apply Dependency test for adjacent steps — does step B require…'s dependency test to every adjacent pair: "Does step N+1 actually need step N's output?" (3) Regroup: put truly independent steps into parallel buckets. Notation: "Phase 1: [A, B, C in parallel]. Phase 2 (after A completes): [D]. Phase 3 (after B and D complete): [E, F in parallel]." (4) For workflows you execute regularly, the one-time cost of dependency analysis pays for itself within a few executions through time savings. (5) Make parallelism visible in the notation: side-by-side columns, "concurrent" labels, or dependency arrows rather than numbered lists.