Response/Coordination · AI systems
The case against coordination.
A standing objection to Thesis 003, published in full because the institute's rules require it.
Rachel Okafor28 Mar 20267 min read
Thesis 003 argues that as execution is automated, coordination quality compounds. I think the opposite is at least as likely, and the institute's standards require the strongest version of that objection to sit next to the thesis. This is it.
Coordination exists because work is divided. Handoffs, decision rights, information flow: all of it is the cost of splitting a process among people who cannot hold it whole. The premise of agentic software is that the process no longer needs to be split. If an agent can carry a workflow end to end, the handoffs that coordination manages do not become more valuable. They disappear.
The thesis answers that the coordination work moves to the interfaces among people, agents and exceptions. Perhaps. But that is a claim about a transition period, and the thesis is written as if it were a claim about a destination. Organizations investing heavily in coordination quality today may be polishing a layer that the next two years delete.
Organizations investing heavily in coordination quality today may be polishing a layer that the next two years delete.
What would settle it: a panel of organizations at high agent coverage, scored on coordination quality, watched for whether the advantage holds. The Decision Rights Index is meant to be that panel. Until it reports, I am keeping this objection open.
Moves the library. Raised the unresolved counterargument on Thesis 003 v1.1. Thesis 003, Management Is Becoming an Operating System.