Illusions of Work

AI Has Made Reality Non-Negotiable

For engineers, architects, and CTOs

1. Author's Note Twenty years inside software-dependent corporates, from engineer to CTO. Why AI has made the structural patterns described in this book too expensive to ignore any longer.
2. Introduction If your organisation refers to “the business” as a group that excludes engineers, this book is about your company. It maps the structural dysfunction of software-dependent corporates and the changes AI now demands.
3. The Split
4. 1. When “the Business” Isn't the Business When engineers are excluded from “the business,” operational reality becomes advisory rather than binding. Strategy detaches from execution, ownership dissolves, and the organisation loses the ability to learn from its own outcomes.
5. 2. Why People Closest to Reality Suffer The people most punished by structural dysfunction are those whose effectiveness depends on contact with actual systems. The organisation selects for fluency in narrative over fluency in reality, then calls the result a talent shortage.
6. How People Cope
7. 3. Activity Without Reality When closing a ticket becomes the goal rather than changing the system, the representation has replaced the thing it was meant to represent. An eleven-week, €380,000 migration that produced no observable change in customer experience illustrates how activity substitutes for progress.
8. 4. Fake Products and the Buffer Class Some products exist in strategy decks but cannot be located in the codebase. The “buffer class” of product managers absorbs the incoherence these fake products produce, growing larger as the gap between narrative and system widens.
9. What the Machines See
10. 5. Architecture That Avoids Accountability Architecture in software-dependent corporates often functions as a source of avoidance rather than control. Organisations adopt the vocabulary of modern architectural styles without adopting the structural commitments that give those concepts force.
11. 6. Microservices Without Autonomy When the monolith was split, the coupling did not disappear; it migrated into shared schemas, shared databases, and undocumented inter-service dependencies. The core error was decomposing services by technical layer rather than by business process.
12. What Was Never Written Down
13. 7. Customer Journeys Are Business Processes Customer journeys and business processes describe the same mechanism observed from opposite sides, but most organisations treat them as separate concerns owned by different functions. The disconnection means no one owns the transitions where work actually fails.
14. 8. Writing Reality Down So It Bites Back Most organisations suffer not from a lack of documentation but from a lack of documents that are structurally permitted to be true. An artefact only matters if it removes options, collapses ambiguity, and forces consequences.
15. Now Go Faster
16. 9. AI as the Unforgiving Reader AI’s most important capability is not generating code faster but reconciling what the organisation says with what it actually does. Two contrasting vignettes show that the technology does not determine the outcome; the organisation’s willingness to read its own reflection does.
17. 10. When Clarity Becomes Cheaper Than Pretence AI is categorically different from previous technology waves because it collapses the cost of synthesis, making clarity cheap and pretence expensive for the first time. The gap between organisations that adapt and those that resist compounds each quarter.
18. Why Nothing Changes
19. 11. The Alignment-Industrial Complex Illusions of work have not persisted by accident; they have been institutionalised and monetised. A self-preserving system of roles, frameworks, and vendors whose survival depends on permanent deferral of reality converts structural incoherence into recurring revenue.
20. 12. The Machinery of Avoidance Three functions rule through lagging representations of reality: finance, HR, and budgeting. Each derives authority from controlling information about what has already happened, not from understanding what the system is currently capable of producing.
21. The Fix
22. 13. The Rate Has Changed The rational response to previous failed modernisations was to leave legacy alone. That calculation is no longer correct: AI has materially reduced the cost of understanding legacy systems, and bounded reconstruction through process-owning units provides a structurally different approach to replacement.
23. 14. Units of Truth The autonomous business unit, owning a real slice of value creation end to end, is the minimum viable structure for machine-readable reality. This chapter defines what authentic ownership means and distinguishes it from the simulated autonomy of squads and feature teams.
24. 15. Where This Fails Six adversarial cases stated as forcefully as possible and examined for what survives. The honest limits of the model, including the most dangerous failure mode: governance capture that produces clean dashboards while dysfunction continues.
25. 16. The First Unit The first autonomous unit is a permanent structural change, not a pilot. One unit operating with genuine autonomy creates selection pressure that shifts the question from “should we restructure?” to “why does everything else still work the old way?”
26. 17. The Authority to Decompose Scaling from one autonomous unit to many requires a transitional fund ring-fenced from the annual budget cycle and a CTO-CEO decision pair that collapses boundary decisions to two people. The chapter specifies how the CTO is measured and what remains central after the transition.
27. 18. Pull, Not Push Central functions that mandate adoption produce compliance without substance. When autonomous units own their process risk, they pull for capabilities they genuinely need rather than performing compliance with tools they did not choose.
28. 19. From Pretence to Autonomy The transition is primarily political rather than structural. This chapter describes what it does to the three populations it threatens most: middle management whose coordination roles disappear, finance teams who lose narrative authority, and product managers whose competence was shaped by the dysfunction the model resolves.
29. 20. Feeding AI, Healing the Organisation Autonomous units remove coordination as governance but do not remove the need for shared understanding. The medium changes: coherence is maintained by AI systems that read versioned artefacts continuously and produce synthesis on demand.
30. What It Looks Like
31. 21. What This Looks Like A year in the life of a fictional European insurer that has completed the transition, composed from real cases. What remains difficult, what has genuinely improved, and what the people who made it happen look like on the other side.
32. Conclusion AI does not change organisations by itself. What changes the structure is the decision to make process ownership real: to give the people who understand the system the authority to describe it, maintain the description, and be held to what it says.
33. If You Are the CEO The executive mandate without which the structural corrections described in this book are impossible. What the transition requires, what to protect, and four conditions under which you should not attempt it.

See also: Full contents · Illusions in the Boardroom