Ask what users can infer after the technology has finished

Before changing how a system stores or displays a date, I ask the business owner what the value means. A calendar day used in contract administration may differ from an event timestamp that must be interpreted in a time zone. Treating the two as interchangeable can change the date shown to a user even when the conversion is technically consistent. Our 2019 migration exposed that mistake in a bounded review of eighty records. The CIO’s responsibility was to stop the affected use, organise correction and require acceptance against the business meaning. Contract owners retained interpretation of the underlying agreements. I do not treat one representation as suitable for every field; the useful discipline is to define the intended meaning and test that it survives the particular transformation and receiving context.

A converted document can retain every visible value while losing the structure that tells a reader what those values refer to. I ask whether row and column labels remain associated with the relevant cells, including when the content is read with assistive technology or displayed differently. The 2023 review found thirteen tables whose relationships did not survive adequately, despite the underlying figures being present. Acceptance therefore needed business and accessibility input alongside a visual comparison. We retained one unresolved table outside the release after the revised exercise rather than generalise from the others. The CIO should fund that work and make the limitation affect release scope. A successful test set is evidence about those reviewed documents and conditions, not certification that every future conversion or user experience will be equivalent.

An organisation may remove a source document while a separate search representation continues to offer its content. I ask who owns the document’s status across the retrieval route and how withdrawal is verified in the services people actually use. Our 2025 review concerned approved retirement of corporate administrative guidance, not erasure of every historical record or deletion of material subject to preservation instructions. Thirteen of seventy-two withdrawn items remained available through the reviewed search route. The correction had to address that route rather than declare success from the source folder alone. Document and legal owners retained decisions about retention, while technology owned faithful execution and evidence within the defined scope. I avoid claiming that a search check proves all backups, downloaded copies or other repositories have been erased.

A technology team needs a clear definition of completion, but it cannot invent the business meaning of every field or document it handles. I ask the relevant owners to identify what must remain true after a change and how that will be examined. The answer may involve calendar interpretation, table relationships or a document’s current status rather than another infrastructure metric. My function provides delivery capacity and technical evidence; contract, document, accounting and operational owners retain their decisions. The leadership responsibility is to make those boundaries workable, including a route for withholding acceptance when the technical job has completed. I would apply the same perspective in board oversight by questioning the evidence behind a transformation claim, without directing implementation or treating a non-executive role as an informal systems-approval position.