The responsibilities I learned to find inside a short freight description

I started at fictional Tervalen Transport in July 1995, after completing operations design at Calvernith Institute that May. I worked in a nine-person service-analysis group with no independent spending delegation. The early work taught me that a transport description could be precise about movement and vague about the activities surrounding it. A customer might need an origin pickup, a receiving appointment or a decision after a return. Those requirements did not disappear when the carrier’s own part of the journey had been described neatly. I became interested in the product boundary where one party’s completed task became another party’s unfinished question.

In July 2002 I moved into returns product management. By 2008 I led twenty-six colleagues through three direct reports with S$2.3 million annual expense. Tervalen’s S$310 million revenue and 1400 employees were company context. The appointment includes a 2007 decision I approved too quickly: a single returned status triggered at collection. In the fictional arrangements concerned, the merchant still needed to receive and review the goods before deciding the refund. Of six hundred requests examined, 420 had been collected and 180 were awaiting collection. The 420 collection events did not establish that the merchant’s decision was complete.

Mei Lin Vellara challenged the label because it made the carrier’s event sound like the end of the whole return. We allocated S$420,000 to distinguish requested, collected, received and review-complete states, with the last shown only when the merchant supplied that decision. The work gave up the appeal of one simple completion message. It also required us to agree whose evidence could support the next message, rather than let the interface infer a commercial decision from the progress of a parcel. It did not claim a refund result or assume that every merchant uses the same rule. I learned to ask whose task a product status represents before allowing it to describe the customer’s entire experience.

I joined fictional Vellunor Logistics as product director in April 2009. By 2015 the function comprised forty-eight colleagues, four direct reports and S$7.8 million annual expense. The company had S$980 million revenue and 3800 employees. A 2014 receiving-calendar review covered eighteen customer sites: eleven could receive on weekdays and seven only on Saturday. We allocated S$3.2 million to an optional Saturday path subject to operating availability. Faster movement would not make a closed receiving site available, and the product needed to recognise that distinction before presenting speed as the only useful choice.

The service-portfolio vice-president role began in July 2016. In 2019 we examined 1200 reusable crates: 840 returned within twenty-eight days, 240 between days twenty-nine and forty-five, and 120 still unreturned at the forty-five-day cutoff. S$2.7 million funded development of a forty-five-day option with inventory planning appropriate to the longer cycle. The 120 unreturned units remained unresolved; extending an option did not make them available again. By 2020 my remit was eighty-two colleagues through five direct reports with S$16 million expense, within a company reporting S$1.9 billion revenue and 6100 employees.

I became CPO in July 2021 and began executive board presentations. The 2023 port-to-warehouse review contained forty shipper briefs: sixteen required origin pickup, while twenty-four began at port handover. We allocated S$4.8 million to a separately defined pickup option and declined an unqualified door-to-door name for the base offer. The decision concerned the product’s included work. It did not settle customs responsibilities or report completed bookings. I wanted the starting point visible before a convenient name invited the customer to assume a wider service.

My present responsibility is 118 colleagues through six direct reports with S$24 million 2026 function expense. Vellunor’s S$2.8 billion 2025 revenue and 7200 employees describe the institution, not my personal operating command. In 2025 an illustrative booking comparison showed a two-day movement after five days of waiting taking seven days overall, while a four-day movement after one day of waiting took five. S$1.8 million supported clearer elapsed-time and dispatch context rather than ranking options by movement alone. These were hypothetical assumptions, not actual route schedules. Across thirty-one years I have come to judge a freight offer by the responsibilities and periods its shorthand leaves out. I hold no statutory seat; a possible first appointment would require preparation beyond executive presentation experience.