The questions a technology proposal owes its board

I want a board discussion of insurance technology to begin with the responsibility being exercised. A claim communication, a renewal instruction and access to a member's file have different consequences. Describing all three as digital transactions can conceal the judgement needed in each. Management should be able to explain who has authority, what evidence that person receives and what remains outside the system's approved scope. The technology report becomes more useful when those questions are answered alongside delivery dates and expenditure.

My executive role at Caldermere includes regular presentations to the board risk committee. I prepare the technology account and respond to challenge, but I am not a director or a committee member. I make that distinction because the experience of defending a management proposal is valuable preparation without being equivalent to collective board service. The board must consider the enterprise more broadly than the remit I manage. My responsibility is to provide information that helps it do so, including costs and limitations that make my own programme less convenient to present.

The correspondence assistant illustrates why the scope of authority belongs in the approval paper. Our early closed-file test found drafts with unsuitable supporting references. We retained supervised preparation and removed autonomous dispatch from the approved release. The committee needed to understand both the remaining value and the review effort that stayed in the operating process. It did not need to adjudicate individual claims. I would want any later proposal to expand that scope to identify the new evidence and the executive owner accepting the changed responsibility.

Measures should describe the population they cover. A report on online renewal can be accurate while giving an incomplete picture of member service. In our pilot, 1,500 of 7,600 invited members used telephone or post. Funding that route was an operating commitment with a visible cost, not an inconvenient footnote to the digital result. I would ask a board paper to show what happened to the whole population and where management still lacked an explanation. The channel someone ultimately used did not, by itself, reveal every reason for their choice.

Investment benefits also need a chain of decisions. The work study with sixty adjusters found a net twenty-four minutes a day after additional checking was considered. Claims management assigned fifteen minutes to customer follow-up and left nine unallocated while examining variation. No staffing reduction was claimed. A board can judge the value of improved service or capacity available for demand if management describes it clearly. It should not have to infer whether a reported benefit is a cash saving, a different use of existing time or an assumption awaiting an operating decision.

Assurance should be proportionate to the consequence and sufficiently separate from delivery enthusiasm. The people building a tool know its design in detail, but they may also be committed to the programme's original ambition. I support review by colleagues able to test the evidence and challenge the proposed scope. That review needs usable material, realistic examples and a route for unresolved findings. A formal approval field in the workflow cannot replace the professional discussion about what has actually been demonstrated.

The ongoing account matters after launch. Supplier access, for example, should reflect assignments that are still current. Our review closed eighty accounts, restricted sixty and retained 340 within reviewed scope. Those decisions described one point in time. The continuing responsibility belonged in the relationship process, with people able to confirm who was doing the work. I would not present the review as permanent assurance that every future change would be handled correctly. Directors should understand both the improvement made and the management routine needed to sustain it.

In a future external appointment, I would use these experiences to ask clearer questions rather than to recreate my executive role. I would learn the organisation's operating model, financial position and obligations, then contribute within the chair's agreed approach. A board seat should not become a concealed assignment to run technology. I would disclose commercial connections early, seek advice on independence and decline a role whose central decisions I could not properly join. The contribution I offer is a disciplined examination of the responsibilities beneath a technology proposition, with respect for the specialists and managers who must carry them.