Elena reads a reconciliation report and discovers that a feature described in nine months of board packs as “deployed and in optimisation” does not exist. The choice between narrative governance and structural honesty cannot wait: each quarter builds institutional sediment around whichever path the organisation is on.
Elena, the audit committee chair, opens a reconciliation report at 7:40 on a Tuesday morning, twenty minutes before the quarterly review. The report is six pages. It compares the renewals process definition against the code that implements it. She reads that the automated risk reassessment described in the strategy update has not been implemented. The renewals process still routes every modified policy to a manual review queue. The queue is staffed by four people. Average time in queue: eleven days. The strategy update she approved last quarter described the reassessment as “deployed and in optimisation.”
She checks the previous two quarterly updates. The same phrase appears in both. “Deployed and in optimisation” has been the status for nine months. The feature does not exist and never has. Someone wrote the sentence once and it has been carried forward since, probably by an AI assistant drafting from the previous quarter's pack, certainly without verification.
She turns to the management narrative prepared for this morning's meeting. Page three describes renewals performance as “on track, with automated reassessment reducing processing time by 40%.” Forty per cent of nothing is nothing. She thinks of the four people staffing the manual review queue who have known this for nine months and were never asked.
She checks the three previous board packs. The phrase appears in each of them under “Technology Delivery.” Each pack was reviewed in committee and approved. The board has been measuring programme performance against a feature that no engineer ever built. It has been approving a narrative. Three consecutive cycles, and no one checked or asked. The four people in the queue knew.
Elena sets the management narrative down. She considers the possibility that the reconciliation report is wrong, that the feature exists in a form the system definition has not captured. She checks the deployment manifests herself, tracing the service name through three environments. The feature does not exist.
At the quarterly review, she reads the reconciliation finding aloud. She asks the CTO when the automated reassessment was last verified against the production system. He does not answer immediately. The head of product says the feature was signed off by the vendor in January. Elena asks whether anyone confirmed that the sign-off corresponded to something running in production. The silence is brief and complete. She asks the CFO for the capital allocated to the renewals improvement programme over the past three quarters. The figure is € 2.8 million.
...
Continue reading in the interactive reader
Read this chapterSee also: Full contents · Preview chapters · Illusions of Work