Now Go Faster

Chapter 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.

What changes when a machine can read the organisation literally, without fatigue and without deference, is the cost of ignoring the diagnosis.

AI does not introduce truth; it removes the insulation that allowed illusions to persist.

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 codebase, 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 spends two weeks feeding the assistant the relevant artefacts: the annual strategy deck (94 slides), the technology vision document (38 pages), 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 completely devastating.

It notes that the strategy deck identifies “digital self-service for enterprise customers” as a top-three priority, but that only two of its 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 a domain-driven decomposition into eight bounded contexts, but that the actual service topology follows a different structure entirely: one organised around legacy database schemas rather than business domains. It identifies fourteen services that share a single relational database, contradicting the reference model's assertion of data ownership.

It flags that the technology vision document commits to “API-first design,” but that 62% of inter-service communication uses direct database reads. It notes that the stated strategic priority of “operational excellence” has no corresponding process definitions, SLAs, or monitoring in any of the codebases it can access.

The summary does not editorialise. It simply reconciles what the organisation says with what the organisation does, and lists the contradictions.

...

See also: Full contents · Preview chapters · Illusions in the Boardroom