The depot taught me to ask which event the timestamp belonged to

A depot colleague once showed me a shipment history that appeared to run backwards. The vehicle had not reversed its journey. The record had received several scans after a handheld regained its connection, and our display treated arrival at the server as if it were the order of events on the ground. I was early in my career, impressed by the speed with which the new interface could assemble a screen. The colleague wanted something more useful: a sequence they could explain to the person waiting for the freight.

I completed a computing degree at Aldervane College in May 1993 and joined Belvarin Freight the following month. I was part of an eight-person applications team, with no direct reports or spending authority. Depot and customer-service colleagues helped me learn the difference between a transaction that passed through a system and a piece of work that had reached its intended state. A received message could leave a tender undecided. A scan could describe one item without describing the whole consignment. I learnt to ask those questions before treating a common code as a common meaning.

In January 2002 I joined Merovant Freight Systems as transport applications manager. I reported to the head of technology and took responsibility for a team that reached twenty-eight employees through three direct reports by the end of the appointment. My annual authority was USD5.2 million in 2008, when the enterprise operated twenty-eight depots and employed 3,000 people. Managing the service made the consequences of an unclear definition harder to ignore. The question would return through support, training or a customer conversation even if the project team had regarded the application as delivered.

I became head of integration in January 2009. The role connected different operating systems and partner messages, with a team of sixty-four and four direct reports by the final year. My 2014 authority was USD18 million. Merovant had grown to forty-six depots and 5,100 staff, and a private-equity investor acquired 60% in 2013 while founders retained 40%. The ownership change occurred during this appointment, not before I entered it. Integration taught me how easily a technically valid exchange could conceal a difference in the business decision each side believed it represented.

The director of enterprise platforms appointment followed in January 2015. I led 126 employees through five reports by 2018, with USD46 million annual authority. The company had sixty-four depots and 7,300 staff in that period. My task was to make shared technology support the operating network without forcing its local realities into an overconfident summary. I paid particular attention to the definitions behind completion, the treatment of an unavailable connection and the evidence needed when a status passed from one team to another. The CIO appointment in January 2019 brought those concerns into enterprise-wide investment responsibility.

My current team comprises 216 employees through six direct reports, with fifty-eight contractors separately. The 2026 technology authority is USD84 million, including USD52 million operations and USD32 million change. Merovant's eighty-six depots, thirty contract warehouses and 9,400 employees provide the setting for my work across the United States and Canada. The 7.4 million consignments and USD2.26 billion revenue refer to 2025 company activity. They are not outcomes I attribute to a single platform programme or a measure of the resources under my personal control.

I work with Nolan Grevett as chief executive and Lucinda Merroway in operations. Our discussions often concern a result that looks less tidy after the technology account becomes more accurate. The piece-level review changed a dashboard from 500 complete consignments to 420 complete and eighty partial. That did not mean the application repair had caused eighty deliveries to fail. It meant the earlier representation had obscured unfinished physical work. I wanted the change explained clearly so colleagues could act on the real situation rather than debate an apparent performance decline created by the measurement correction.

Other cases have reinforced the same habit. Sixty shipment histories remained uncertain after event-sequencing work. Twenty conflicting replay attempts stayed held instead of being silently accepted during an offline recovery exercise. An arrival model improved its retrospective error while the actual delivery-window result remained unchanged. I regard those qualifications as part of the useful result. They tell the receiving colleague what they can rely upon and what still requires an operating decision or further evidence.

I have presented technology matters to the board as an executive but have not served as a director. A possible external contribution would need preparation in collective duties and the wider enterprise, not merely confidence in my own specialism. Twenty-four proposed days would require employer agreement and a realistic calendar, with relevant relationships examined for the actual seat. I would bring a practical concern for the meaning behind operational information and an equally practical respect for the people whose judgement turns that information into a responsible action.