The responsibilities behind my transport career

Mandate

Align customer commitments, purchased capacity and operating responsibility across the network

Outcomes

• Revised a corridor booking cut-off with explicit customer consequences
• Established a shared equipment pool with additional lease cost disclosed
• Retained a specified terminal reserve and reviewed its unused share
• Developed a pooled departure offer for smaller shippers

Decisions in context

I became CEO with responsibility for the enterprise account and the service commitments made across the network. The business combines our forwarding and associated operations with capacity purchased from rail and terminal partners. The separately chaired board oversees my work, and my own board appointment is executive. My work has focused on the conditions behind the sold service: booking windows, equipment balance, contingency access and the meaning of customer status messages. I have accepted additional cost or reduced flexibility where the previous offer depended on unrealistic handovers. I also expect the result to be reviewed rather than defended permanently because the original intention was sensible. The current company scale is €214 million revenue and 680 employees; it is distinct from the smaller remit of earlier appointments. I remain responsible for the operating plan while considering one compatible outside board contribution.

Reason for the move

Current executive appointment

Mandate

Connect regional operations through clearer event definitions and handover responsibility

Outcomes

• Clarified arrival, availability and collection events
• Introduced joint corridor reviews across regional boundaries
• Connected capacity procurement with customer service commitments

Decisions in context

I joined an operation whose regions had developed different ways of describing the same movement. My first priority was to understand those differences before imposing a common report. An event called arrival could refer to several distinct points, each implying a different next action. I worked with regional colleagues and partners to clarify the definitions and the person responsible for the handover. I also brought capacity purchasing into the service discussion so that the operating plan reflected the promises being made to customers. The role did not give me the technical authority of contracted operators. It gave me responsibility for making our coordination work better across their interfaces. I prepared operating recommendations for the CEO and board, distinguishing those presentations from a director's appointment. The succession process later selected me for the chief executive mandate.

Reason for the move

Appointed CEO through the board's planned succession process

Mandate

Build service offers that reconcile customer schedules, partner capacity and equipment cycles

Outcomes

• Included planners before final tender commitments
• Separated standard offers from late-booking exceptions
• Reviewed directional equipment costs alongside outward revenue

Decisions in context

The corridor appointment brought the commercial and operating account together in my own remit. I managed customer relationships, partner discussions and the contribution of a defined network of industrial flows. Group authorities still governed major capital and contract commitments. I learnt to question an attractive tender before the offer became a public promise: which booking pattern had been assumed, where would equipment finish and what would happen if the receiving window was missed? Planners joined the discussion earlier, which sometimes made the proposal less convenient but more credible. I also worked to distinguish the customer's urgent exception from the standard product, so that repeated recovery effort did not hide an offer that needed revision. The role taught me to explain the cost of a whole service rather than defend individual legs whose local results looked satisfactory.

Reason for the move

Recruited to lead operations across a wider intermodal enterprise

Mandate

Plan coherent intermodal movements across collection, terminal, rail and delivery stages

Outcomes

• Included equipment repositioning in corridor comparisons
• Mapped customer windows against partner service conditions
• Escalated assumptions requiring commercial or operator approval

Decisions in context

I moved from examining completed failures to planning the conditions under which a movement should succeed. The work combined schedules, terminal windows, equipment position and customer requirements. I prepared options for senior colleagues rather than approving capacity contracts myself. Uneven demand between directions became an important part of my learning. A loaded outward journey could appear profitable while the equipment's next use created cost elsewhere in the network. I began to include that cycle in the comparison and to ask where a forecast depended on a return opportunity that was not yet secure. The role required collaboration with commercial teams and contracted operators, each holding different responsibilities. It developed my ability to explain a practical constraint in terms that a customer or commercial manager could use without reducing it to a technical detail to be solved later.

Reason for the move

Promoted to responsibility for a corridor operating business

Mandate

Establish service-failure sequences and return recurring causes to operating management

Outcomes

• Reconstructed handovers across customer and partner records
• Separated case resolution from recurring operational causes
• Escalated legal and technical questions to appropriate specialists

Decisions in context

Claims work showed me the difference between an internal delay measure and the consequence for a customer's business. I led a small team that gathered records, clarified the promised service and coordinated the company's response within delegated authority. Material legal or technical questions went to the appropriate specialists. I did not treat the role as a licence to settle every issue through a customer-service judgement. The most useful development was to take recurring patterns back to operations after individual cases had been addressed. Several failures concerned the gap between one team's completion and another team's ability to begin. I wanted the organisation to learn from that sequence rather than regard the closed case as the end of its responsibility. The move into planning followed my growing interest in changing those conditions before another customer experienced them.

Reason for the move

Moved into network planning to address service conditions before movements began

Mandate

Maintain accurate movement records and pass actionable status to the next responsible team

Outcomes

• Maintained shipment references and collection records
• Escalated missed windows to the supervising planner
• Prepared accurate responses to customer status enquiries

Decisions in context

I entered forwarding after my transport-management degree and learnt the work through shipment coordination. I maintained references, checked the available status and passed questions to the people who could act on them. The role was supervised; I did not independently instruct technical operations or commit the company to new purchases. I became attentive to the difference between repeating a reassuring message and establishing a fact useful to the customer. A movement could be described as progressing while an unresolved handover made the next connection unlikely. Asking a precise question early often helped more than offering a broad assurance late. I also learnt how much experienced coordinators carried in their own knowledge of partners and local conditions. That experience later shaped my interest in systems that support operational judgement instead of assuming it can be replaced by a status label.

Reason for the move

Promoted into leadership of the customer claims team