When the org chart becomes an architecture decision
Jack Dorsey and Roelof Botha recently argued that corporate hierarchy was never a management philosophy but a workaround. A single leader can coordinate only three to eight people, so organizations added layers to move information up and down a chain of command. On this reading, every structure from the Roman legion to the McKinsey matrix has solved the same problem - coordination under a fixed human bottleneck - with the same instrument. The claim is that a system can now maintain a continuously updated model of an entire business and coordinate work across it, making the routing layer obsolete. Block is reorganizing around exactly this logic, replacing the pyramid with three roles: people who build, people who own specific outcomes, and player-coaches who develop others while staying close to the work.
The argument is clean, and the historical framing is largely correct. The interesting question is whether the proposed replacement holds under the conditions of an ordinary enterprise?
The assumption that carries the whole thesis
Everything rests on one claim:
The coordinating context, managers used to carry, can be relocated into a system.
Block calls this a company world model, built continuously from machine-readable artifacts - decisions, code, plans, progress - because the company is remote-first and records almost everything by default. Where work already exists as structured signal, an AI can plausibly maintain a live picture of what is being built, what is blocked, and where resources sit. Block pairs this with a customer world model fed by transaction data, on the reasonable premise that money is a more honest signal than surveys or clicks.
These are specific preconditions, not general ones. They are also where most enterprises diverge from the example.
