What directors need to see behind my technology recommendation

A technology paper reaches a board after many practical decisions have already shaped its account. Someone has chosen the service boundary, the measure of completion and the point at which an exception becomes material enough to mention. I want directors to be able to examine those choices without having to reconstruct the entire technical programme. My responsibility as CIO is to provide an intelligible recommendation with the evidence and limitations needed for collective judgement.

I begin with the banking service and the decision requested. A proposal to improve recovery should explain which unfinished obligations the current arrangement can leave behind. A migration recommendation should identify the instructions as well as the balances it must preserve. A supplier renewal should distinguish contractual access from demonstrated operating capability. These descriptions make the paper relevant to the enterprise rather than ask directors to approve a collection of technology activities whose business consequences remain implicit.

The account should preserve who owns each judgement. I can explain the technical evidence and organise the engineering response. Operations decides its authorised procedures, risk colleagues provide challenge, finance examines affordability and legal specialists advise on the agreement or obligation in question. Their contributions should be visible when they materially affect the recommendation. A CIO who presents every conclusion as a technology decision can make the paper simpler while removing an essential part of its authority.

I also want disagreement to survive the drafting process. A commercial sponsor may have a valid reason to resist delaying a feature. Procurement may reasonably seek a lower support fee while the service owner needs more transfer work. Those positions help directors understand the choice. The management recommendation should state what was given up and why the preferred option remains justified. Removing the alternative can make approval easier, but it weakens the record available when the result is reviewed later.

The same discipline applies after approval. If management funds recovery improvements, the next report should explain what the subsequent exercise established and what remained outside its scenario. If it approves a capability-transfer programme, completed sessions are not sufficient evidence that the bank can reproduce the service. Reporting should follow the decision's intended purpose rather than switch to whichever activity is easiest to count. Where the result is incomplete, the board needs a dated account of the remaining condition and the proposed response.

Our technology portfolio provides another example. The authorised change envelope required choices among requests that were individually attractive. Deferring seven proposals made the programme affordable and reduced competing demands, but three first-half milestones still remained late. I would not use the original prioritisation decision to excuse that unfinished work. Management must explain the current position, including changes in assumptions and responsibilities, while the board considers whether the larger allocation remains sound. Approval is the start of accountability, not a substitute for later evidence.

I have presented these matters to directors as an executive. I do not hold a board seat, and my interest in an external appointment does not erase that distinction. In a non-executive role, I would need to contribute through the chair and the agreed committee responsibilities. I would ask questions that clarify management's evidence and choices, without becoming an informal technology manager or inviting employees to bypass their own leaders. Specialist knowledge is useful only if it strengthens the board's collective oversight rather than fragments it.

The best technology discussion leaves directors with a clear understanding of the responsibility accepted by the enterprise. They should know what the recommendation is expected to improve, what it costs, which alternative was rejected and which uncertainty remains. Not every condition can be resolved before a decision. It can still be described honestly enough for the board to judge whether the proposed course is proportionate and whether management has the authority and resources to carry it through. That is the standard I seek in my own executive papers and the contribution I would hope to make in a carefully chosen external seat.