In February, Block cut more than 4,000 roles — nearly half its workforce — and Jack Dorsey told shareholders the reason was “intelligence tools.” He said most companies were late, and would reach the same conclusion within a year. In late March, he and Roelof Botha published the blueprint behind that decision: an essay called “From Hierarchy to Intelligence,” arguing that the management layer itself is what AI is about to replace. Agency founders are posting their implementations. Enterprise vendors are rebranding. The idea is sound — a large share of what fills managers’ calendars is work software can now do faster and cheaper, and the companies that automate it will be structurally faster than the ones that don’t.
Every management revolution since the first org chart has produced a specific failure mode. This one’s failure is that it looks like success for a year. Badly implemented, a world model produces a simulation of organizational intelligence: dashboards stay clean, reports keep flowing, status gets synthesized. Underneath, the quality of decisions degrades — structurally, one small editorial choice at a time — because the system is making judgment calls it isn’t equipped to make, and the humans who used to catch those calls are no longer in the room. By the time it’s visible in results, several quarters are gone, and the damage reads as “execution was off” or “the market shifted” rather than what it actually was: a system drew the line between information and judgment in the wrong place. Or didn’t draw it at all.
Three different architectures are being sold as “world models” right now — vector databases, structured ontologies, signal-driven systems — and each one gets the information-versus-judgment boundary wrong in its own specific way. Which one you pick matters less than whether you build an explicit boundary layer before anything else. Most implementations I’m seeing skip that step entirely.
This briefing covers:
The editorial function nobody accounts for. Managers didn’t just move information around. They edited it. They decided what mattered. A world model replaces that editorial function with something that feels like judgment but isn’t. The mechanism is specific, and the failure is invisible until it’s structural.
Three architectures, three failure modes. Vector databases, structured ontologies, and signal-driven models are completely different bets on what “understanding” means. Each one gets the line between information and judgment wrong in a different way.
Five principles that determine whether it compounds or rots. Signal fidelity, earned structure, outcome encoding, organizational resistance, and accumulated reality. These hold regardless of which architecture you choose.
Which approach fits your company. A mapping from company type to paradigm, including the hardest and most common case: knowledge-work companies where the data is mostly conversations and documents.
A diagnostic plugin at the end. Once you have the framework, a twenty-minute readiness assessment to map your company to a paradigm and a starting sequence.
The companies that get this right will compound. The ones that get it wrong won't know for a year.
