The COO Decides Which Stages Stay Human
The COO guide
Companion to The Code Takes Care of Itself · Updated 2026-09-29
Core point. Evolve operational process one stage at a time; never automate a whole process at once. AI assistance compounds fastest, and risks least, at Generate and early Evaluate. Pull the human decision-maker out of Governance or final Validation and a completion problem becomes an operational incident.
Discussion questions.
-
Which processes did we make AI-assisted without deciding which stage still needs a named human decision-maker?
-
Where does governance live now for decisions that were once too slow to need a name, and does it hold when they arrive ten times as often?
-
Which work stays human because the cost of being wrong is asymmetric: regulatory, safety, customer trust?
-
Signal of success. Every automated process documents the line where human judgment re-enters.
-
Signal of failure. An incident review finds nobody could say who owned a decision the AI made by default.
-
Common misconception. Operational efficiency is the goal. It isn’t; operational readiness, the Deploy stage in “AI Makes Drafts Cheap, So Finishing Is the Constraint,” is. Efficiency without readiness moves the incident downstream.
-
Recommended intervention. Run the Completion Loop audit as a standing operational review, not once. The audit is the playbook at the end of that chapter.
-
Warning sign. Process documentation that describes what the AI tool does and never names who is accountable when it’s wrong.
