If You Are the CTO

If you are the CTO, you have probably been describing this diagnosis for years, in memos that were read as complaints and in architecture reviews that produced acknowledgement without authority. What has changed is not the diagnosis itself but that making it no longer depends on you alone.

For most of the last decade, your reading of the system competed with everyone else's narrative, and narrative usually won, because there was no cheap way to demonstrate that the architecture did not support the strategy. A reconciliation that once required a consulting engagement of several weeks, and was softened before it reached the board, can now be produced in an afternoon and repeated every week. The reading you have been carrying privately can now be produced by the system itself, and that gives you a lever you did not have before. The instinct, when you finally have the board's attention, is to argue: for a programme, a reorganisation, a budget, a new operating model. That instinct should be resisted, because every one of those proposals can be absorbed into the coordination layer, and a board that has already funded three transformation programmes will recognise a fourth and fund it the same way. The move a board cannot absorb is evidence it did not commission and cannot attribute to your opinion.

Produce two things, for one critical process, before you ask for anything. The first is a reconciliation: the process described in machine-readable terms, compared against the code that implements it, with the divergences listed. The second is the deferred-investment trace for that process: the three costliest incident categories of the last eighteen months, set against the structural investment that would have prevented them. Neither requires a programme, a consultancy, or anyone's permission to begin, and both produce a figure the board can check for itself.

Bring the reconciliation and the trace to the board as a finding, not a request. The question the board has to answer is whether it would want to see the output of a reconciliation run against its own representations, and you are in a position to answer it for them, for one process, and to let the gap make the argument you have been making in prose for years. A board that reads the trace and asks what it would cost to close the gap has moved from narrative to evidence on its own, which is the only way the move holds. Some of you will do all of this and find that nothing moves. The board reads the reconciliation, agrees that it is accurate, and declines to act, because the correction would redistribute authority away from the people who would have to authorise it. That limit is real, and you should plan for it rather than be surprised by it. Honesty without sponsorship is career risk, and producing an unanswerable diagnosis inside an organisation that has decided not to answer it is a slow cost to you rather than a strategy.

When the board will not act, narrow the audience before you widen it. You do not need the whole board; you need one person with standing who would rather know than not: an audit committee chair, a single non-executive director, a chief executive who arrived from an organisation that operated differently. The trace is built to travel, because it persuades on its own terms and does not depend on your authority to carry it. If no such person exists, the conclusion is the same for you as for the organisation: the structure has chosen narrative over reconciliation, and the rational response is to take what you know to a structure that has not yet made that choice.

For years the cost of your knowing the system was carried by you alone, in memos no one acted on and in contradictions you held so that others did not have to. The cost of that knowledge has not fallen. What has changed is that the knowledge can be produced as evidence rather than asserted as judgement, which means the question is no longer whether you are right but whether the organisation wants to know, and that question is now the board's to answer rather than yours to keep raising.

...

See also: Full contents · Preview chapters · Illusions of Work