When Machines Read
A CTO commissions an AI reconciliation of strategy documents, architecture models, and code, and receives a calm, precise enumeration of contradictions the organisation had been absorbing socially for years. The CEO’s response is to suppress the output.
A large European telecoms operator decides to pilot an AI assistant for its technology leadership. The brief is modest: given access to the company's strategy documents, architecture diagrams, and code, the assistant should produce a summary of the organisation's technology landscape and its alignment with stated strategic priorities.
The CTO is supportive. The experiment is sanctioned. A small team feeds the assistant the relevant artefacts: the annual strategy deck, the technology vision document, the architecture reference model (last updated fourteen months ago), the current service catalogue, and read access to the primary code repositories.
The assistant produces a twelve-page synthesis that is calm, precise, and devastating.
It notes that the strategy deck identifies “digital self-service for enterprise customers” as a top-three priority, but that only two of forty-seven services have any self-service provisioning logic, and both are experimental prototypes with no production traffic. It observes that the architecture reference model describes eight distinct areas of business responsibility, each meant to own its own data, but that the actual system follows a different structure: one organised around legacy databases rather than business domains. It identifies fourteen services that share a single database, contradicting the reference model's assertion of independent ownership.
The summary does not editorialise. It reads what the organisation claims alongside what the code shows, and lists the contradictions.
The CTO recognises every finding in the summary, as none of it is new to him. What is new is that the confirmation is now documented, enumerated, and produced by a system that did not attend a single meeting. It is written down in a single document, generated in hours rather than months, making it impossible to dismiss as merely one person's opinion.
...
Continue reading in the interactive reader
Read this chapterSee also: Full contents · Preview chapters · Illusions of Work