DDIO isn't a process flowchart — it's a discipline: diagnosis before the proposal, decision before design, architecture before execution, measurement before optimization. When the order is skipped, you produce symptoms, not systems.
Four phases
Diagnose reads the current structure. Design determines the architecture and the hypothesis order. Implement turns the architecture into a working system. Optimize calibrates over time and compounds. Each phase builds on the output of the previous one.
Automation scales the error
Automating a broken process only repeats the error faster. So: diagnose first, then build. Not a campaign — a modular, documented and measurable system.