The responsibility expanded while the counted object still needed explaining.

Mandate

Keep the enterprise’s freight claims connected to the promise versions, quantities and evidence they actually describe.

Outcomes

• Retained original and updated promise histories behind the 80% and 95% measures in the 2023 shipment review.
• Corrected the 2020 two-route account to 2.2 million short-ton-miles by preserving paired weights and distances.
• Separated signed proof, third-party scans and missing reviewed evidence in the 2025 delivery account.

Decisions in context

The present appointment connects measurement questions that used to arrive in separate operating reports. I want the data function to explain which promise, unit or evidence state supports a statement before it becomes part of the enterprise account. The work includes keeping an earlier undertaking visible when current information changes. My team and expense are specific to this supporting remit; company revenue and workforce describe the institution around it. Fleet operations, dispatch, safety, contracts, claims and finance retain their own leaders. Executive presentations to the board began with this role in July 2018, without a statutory-director appointment. The three cases recorded here changed how evidence was described rather than proving that freight moved faster or cost less. That distinction is central to the contribution I expect a search reader to assess.

Reason for the move

Appointed to the enterprise data remit after leading network analytics; current position.

Mandate

Align network measures with the actual events and activities observed in their source records.

Outcomes

• Distinguished the whole-visit interval for one thousand trailers from unloading observations in the 2014 review.
• Retained 620 visits with paired unloading timestamps separately from 380 without those observations.
• Completed US$1.6 million measurement work without presenting the three-hour gate median as unloading time.

Decisions in context

The vice-president role brought me closer to the operating question behind a requested measure. A complete set of gate timestamps looked attractive because every visit could be included, but completeness did not make it a measurement of unloading. I wanted the analytical team to explain that distinction without dismissing the usefulness of the whole-visit account. Operating colleagues needed to decide where further observations were worth collecting and which intervention could follow from them. My responsibility was to support that reasoning, not attribute unmeasured time to a particular task. The company’s later scale remained separate from the function’s delegation. This period prepared the CDO appointment by showing that a measure’s meaning must survive its movement into a broader management conversation, especially when a concise label can obscure the activity actually observed.

Reason for the move

Promoted to CDO as the remit expanded from network analytics to the wider enterprise evidence account.

Mandate

Maintain consistent relationships between recurring management definitions and their operating sources.

Outcomes

• Carried the consignment-versus-piece distinction into recurring freight-information reviews.
• Made source objects and measurement boundaries explicit when summaries were reused.
• Developed a wider network perspective before taking responsibility for analytics.

Decisions in context

This appointment extended the lesson of the hierarchy correction into the organisation’s continuing information work. A definition could be clear when first delivered and become ambiguous as its summary travelled into new reports. I asked colleagues to retain the object and source relationship that made the count meaningful. The director title described employment responsibility, not statutory board service. My remit funded the freight-information function while dispatch, safety and commercial leaders owned their decisions. I became more interested in the operating question behind each request, because a technically consistent account could still measure something other than the activity a manager wanted to understand. The move towards network analytics followed that interest. It was an expansion of interpretation and collaboration, without a claim that maintaining this freight account transferred authority over the entire freight operation to me.

Reason for the move

Moved into network analytics as the role expanded towards the interpretation of operating measures.

Mandate

Lead measurement work and explain the source structure behind operating totals.

Outcomes

• Accepted responsibility for approving the mixed-level 2001 export as a shipment count.
• Separated eighteen thousand consignment headers from thirty-four thousand piece-level records.
• Supported US$260000 correction and explained why the fifty-two-thousand-row total was not a consignment measure.

Decisions in context

Managing a measurement team made me accountable for interpretations I approved, including the one Caleb Vornesley challenged in 2001. I had accepted a row count without recognising that the export contained both parents and their pieces. The correction could not be reduced to a tidier file: operating colleagues still needed the piece detail. We retained the hierarchy and changed the account presented to management. I wanted the team to see that acknowledging the error was part of responsible delivery, rather than a threat to its credibility. The role’s team and expense figures describe 2003, while the correction belongs to the earlier review. Progression to director did not erase that episode. It made the lesson about preserving the counted object relevant to a larger set of recurring reports.

Reason for the move

Promoted to freight-information leadership with wider responsibility for recurring definitions and their use.

Mandate

Trace shipment measures to the objects and events represented by their source records.

Outcomes

• Learned the distinction between a consignment and the records used to describe its pieces.
• Examined source definitions before comparing operating volumes.
• Developed an interest in taking continuing responsibility for the measurement account.

Decisions in context

I began work two months after completing applied mathematics in December 1988. Freight records offered an immediate test of whether an apparently precise calculation corresponded to the work around it. A number needed an object and a period before it could become a useful comparison. I worked under a measurement supervisor within an eleven-person group, without line-management or expenditure responsibility. The later size of the data function should not be projected into this early role. What the period contributed was a habit of asking how the record related to the consignment, piece or event it described. That habit was not infallible, as the later error shows. It nevertheless supplied the foundation for taking responsibility for other analysts’ explanations and for staying within the business as the consequences of those explanations became clearer.

Reason for the move

Promoted into team leadership after developing experience in source interpretation and recurring measurement.