Tools alone don't transform organisations. The work that moves the needle is the work most programmes never do.
Most "AI transformation" programmes are procurement cycles dressed up. A vendor selection. A handful of pilot teams. A new role with "AI" in the title. A steering committee with quarterly status reports. None of it touches the operating model. None of it explains why throughput hasn't shifted a year in.
This isn't because the people running them are wrong. It's because the playbook they inherited was built for a different kind of change: deploying systems, not redesigning how work flows around them.
Tools don't transform organisations. Operating models do.
The destination is what the book calls a Kinetic Organisation. Roles defined as judgment systems rather than task lists. Persistent apprentices that carry the work between humans. Dynamic workflows that route through the mesh based on what the work needs, not what the org chart says. A Work Graph that makes the flow visible at the enterprise level.
This isn't a future state vision. It's a concrete architecture, and the tools you've already deployed are pieces of it. The transformation work is connecting those pieces into a system that produces collective lift, not isolated wins.
The sequence the book lays out doesn't ask the organisation to redesign itself in one motion. It starts where the friction is most visible, picks the role most ready for an apprentice, and lets the rest of the system absorb the change as it learns from the pilot. The mesh forms because the work demanded it, not because a programme decreed it.
For sponsors of AI programmes, the architectural reading list is now: this is the conversation behind every roadmap, every prioritisation, every decision about where the next pilot goes.
The operating-model destination and the sequence to reach it. By Christopher Jackson, May 2026.
Read about the book arrow_forwardNo spam. One email when Proxy.Me is available.