Staying with the business meant staying with the consequences of the account.

I joined Velraven Freight in February 1989 because I wanted to see mathematics applied to work whose consequences arrived at a depot every day. I had completed applied mathematics at the fictional Lethrivan College in December 1988. My first job was shipment analysis inside an eleven-person group. I did not manage the group or control expenditure. The lesson was to follow a number back to the consignment, piece or event it represented before deciding what a comparison meant.

The company is the single employer in this invented thirty-seven-year career. Staying did not mean doing the same job repeatedly. In July 1996 I became head of operations measurement, taking responsibility for how a team explained its account to operating colleagues. By 2003 I led twenty-four people through three direct reports with US$1.1 million annual function expense. The employer’s US$720 million revenue and 4100 employees described a much wider business than my own remit.

In 2001 I approved an export containing fifty-two thousand rows as a shipment count. Caleb Vornesley challenged it: the file contained eighteen thousand consignment headers and thirty-four thousand piece-level rows. I had added two levels of the same hierarchy. US$260000 supported the correction, preserving the parent and piece accounts rather than deleting useful detail. I explained why the original statement was wrong without implying that the correction created revenue, removed real freight or established a refund.

The director of freight information appointment began in April 2004. It made the relationship between operational events and management definitions a continuing responsibility. I learned that a familiar label could survive long after the source beneath it changed. The position was an executive employment role, not a statutory-director seat. Fleet operations, dispatch, safety and commercial decisions retained their own accountable leaders. My team supplied an account they could examine, rather than claim to own every outcome their work produced. I also learned to separate a correction in our report from a change in the operation. Recipients needed to know whether a lower count reflected less freight or a better definition. Explaining that distinction became part of delivery itself, because an unexplained correction could create a second misleading story after the first one had been withdrawn.

I became vice-president of network analytics in July 2011. A 2014 review of one thousand trailer visits showed why a timestamp’s boundary matters. The three-hour median between gate entry and exit had been described as unloading time, although only 620 visits had paired unloading-start and unloading-end observations. The full visit could include waiting and other activity. We separated the observed intervals instead of letting the readily available gate data answer a different question about the work inside them.

Since July 2018 I have served as CDO. My current team has 132 colleagues through six direct reports, with US$19.8 million delegated 2026 expense. Velraven’s US$3.6 billion revenue in 2025 and 12400 current employees remain separate company context. I present to the board as an executive, with no statutory-director service claimed. The same care about scope applies to the career as to the freight record: proximity to a company-wide account does not give me company-wide operating authority.

The 2023 delivery-promise review remains a defining case. Twenty thousand shipments were 80% on time against their original promises. Revising promises for three thousand originally late shipments made the updated-date account show 95%, without any of those physical journeys becoming faster. Mara Ellervane challenged the revised-only presentation. We kept original and updated commitments alongside their change history, allowing a current service conversation without erasing the earlier undertaking. The outcome was a more honest account, not a measured delivery improvement.

Other cases examine freight weight and distance and the different evidence behind a recorded delivery. They share an interest in the relationship between the operational story and the data used to tell it. I would bring that perspective to a possible first board role after preparation, employer agreement and an assessment of relationships and workload. Every example here is fictional. The account is intended to show how a logistics data leader can remain useful to operations while refusing to let a cleaner report stand in for an improvement the underlying service has not demonstrated.