My route through depot applications, integration and enterprise information

Mandate

Make enterprise shipment information intelligible and dependable for the people responsible for freight and customer commitments.

Outcomes

• Resolved 420 of 480 uncertain sequences in a 2,400-history examination, leaving sixty explicitly unresolved
• Separated syntax acceptance from business confirmation in a 1,200-tender cohort
• Corrected a first-piece completion rule to expose eighty partial consignments among five hundred reviewed
• Kept retrospective ETA improvement separate from the unchanged 540 of 900 deliveries inside their promised window

Decisions in context

The CIO appointment made me responsible for the enterprise account of technology investment as well as the services themselves. I report to Nolan Grevett and lead 216 employees through six direct reports, with contractor capacity stated separately. The 2026 authority distinguishes USD52 million operating services from USD32 million change. I have concentrated on the meaning of the evidence moving through our systems: which clock a timestamp describes, what a tender acknowledgement establishes and when a consignment can truthfully be called complete. Lucinda Merroway and the operating organisation retain authority over physical dispatch and service interventions. My work helps them see and explain the position without confusing application success with freight performance. I present these choices to the board as an executive and have no director appointment. The current role has strengthened my habit of carrying the unresolved group and the next decision into an investment account, even when a simpler success statement would be easier to present.

Reason for the move

Current appointment; considering a carefully scoped first board contribution alongside the executive remit.

Mandate

Connect transport applications, warehouse systems and enterprise services without losing the operating meaning of their records.

Outcomes

• Established accountable owners for the business meaning of shared shipment fields
• Separated application availability from the service conclusions made from its records
• Introduced operating review of proposed enterprise status definitions

Decisions in context

Leading enterprise platforms broadened my responsibility beyond interfaces into the services on which several operating functions depended. I reported to the chief operating officer and led a team that reached 126 employees through five direct reports. My final-year authority was USD46 million; the employer's revenue and depot count describe the company at that date rather than resources personally controlled by me. I worked with transport and warehouse colleagues on definitions that had to remain useful when local records entered a common view. The difficult discussion was often about responsibility: who could decide what a status meant and what evidence should be required before it changed. I learnt to bring that question into the proposal before a platform team had already committed to a convenient implementation. The CIO opportunity followed because the enterprise needed the same connection between operating meaning, continuing service and investment decisions across its wider technology estate.

Reason for the move

Appointed CIO to lead the full enterprise technology portfolio and its investment account.

Mandate

Make exchanges between applications and partners useful to the operating teams who relied on them.

Outcomes

• Documented the distinction between successful message handling and the business state a recipient could confirm
• Brought partner and depot owners into exception design
• Established a route for investigating messages whose meaning could not be inferred from transport success

Decisions in context

Integration taught me to resist the word accepted when its meaning had not been specified. A technical exchange could succeed while the operating question remained open, and the next team could reasonably misunderstand a green status. I reported to the technology director and led sixty-four employees through four direct reports by the end of the role. The private-equity investment occurred in 2013, during this appointment; it was not the ownership context in which I began it. My final-year authority was USD18 million. I worked with depot and partner owners to make exceptions interpretable rather than simply visible in an integration queue. That required learning their language and accepting that technology could not settle every business question from a message alone. The move to enterprise platforms extended the remit to the applications producing and consuming those exchanges, where some of the underlying assumptions needed to be addressed.

Reason for the move

Promoted into enterprise platforms with responsibility for the applications and services beyond integration.

Mandate

Support transport application changes with a practical account of their meaning and continuing service needs.

Outcomes

• Connected application requests to the depot decision they were intended to support
• Made training and exception handling part of the service introduction
• Developed team responsibilities for investigating contradictory shipment accounts

Decisions in context

I joined Merovant to take responsibility for people and ongoing application service, rather than analysis alone. The team grew to twenty-eight employees through three direct reports during the appointment, and my authority reached USD5.2 million in its final year. I reported to the head of technology and spent time with depot colleagues who needed the system to explain work in progress, not just store a transaction. Managing the service changed how I evaluated a proposed improvement. A new field or screen needed training, an owner for exceptions and a way to reconcile the account when two teams described the same movement differently. The employer figures belong to 2008 and do not imply that the business had that scale when I arrived. The integration appointment offered a broader opportunity to address the exchanges through which many of those differences became visible between applications and partners.

Reason for the move

Promoted to integration leadership as partner exchanges became a larger enterprise responsibility.

Mandate

Analyse application requests while learning how depot events became a shipment explanation.

Outcomes

• Documented the operating questions behind requested status changes
• Learnt to distinguish the time of a movement from the time its record became available
• Traced application questions to colleagues with direct knowledge of the depot process

Decisions in context

I began at Belvarin in June 1993 after completing my computing degree at Aldervane College in May. I was one member of an eight-person applications team, reporting to the applications manager with no direct reports or authority to approve spending. A depot colleague's explanation of a delayed record changed the way I read a timestamp: the message could arrive after the movement it described. I learnt to ask what an event meant to the next person before recommending a cleaner display. The work depended on operating knowledge I did not yet possess, so listening was a practical requirement rather than a leadership slogan. In the final year, the company employed 1,200 people and reported USD180 million revenue. Those figures describe the employer, not an analyst's remit. The Merovant move appealed because it would make me accountable for the people and continuing services behind the recommendations I had learnt to develop.

Reason for the move

Accepted transport applications management at Merovant, adding people and service responsibility.