The journey so far
Dinesh Teo
Chief Product Officer · Singapore / Southeast Asia
I started at fictional Tervalen Transport in July 1995, after completing operations design at Calvernith Institute that May.
31 years
Developing the freight-service proposition
July 1995 to October 2026 across two fictional employers and five executive appointments.
118
Colleagues in my product function
Six direct reports; distinct from the employer’s 7200-person workforce.
S$24 m
2026 function expense
Personal delegation; company 2025 revenue of S$2.8 billion is separate institutional scale.
0
Statutory directorships
Executive board presentations from July 2021; first-seat preparation remains prospective.
The compass
I want a freight offer to say what happens before the carrier receives the goods, what happens after delivery and which decisions remain with the customer or another party. A short product name should not absorb responsibilities the service cannot fulfil. My work is to make the boundary clear enough that the offer can be chosen for the journey the customer actually needs.
The route
Waypoint 01 · July 1995 — June 2002
Tervalen Transport
I entered a nine-person service-analysis group after operations design, learning the handovers around transport without independent budget or team authority.
Waypoint 02 · July 2002 — March 2009
Tervalen Transport
I led twenty-six colleagues through three direct reports with S$2.3 million 2008 expense and corrected a returned status that I had approved at carrier collection.
Waypoint 03 · April 2009 — June 2016
Vellunor Logistics
I directed forty-eight colleagues through four direct reports with S$7.8 million 2015 expense, connecting regional freight propositions with receiving calendars.
Waypoint 04 · July 2016 — June 2021
Vellunor Logistics
My 2020 responsibility covered eighty-two colleagues, five direct reports and S$16 million expense, including reusable-equipment offers with explicit return-cycle consequences.
Waypoint 05 · July 2021 — present
Vellunor Logistics
I lead 118 colleagues through six direct reports with S$24 million 2026 expense, defining freight-offer boundaries and the elapsed-time context behind selection.
Expeditions
01
The proposed port-to-warehouse offer at Vellunor Logistics had acquired a convenient door-to-door name before the starting handover had been resolved. The base service began with goods handed over at the port. Among forty shipper briefs examined, sixteen also required origin pickup and twenty-four did not. Those were different scopes of work, even if the movement after port handover could share a product structure. The name invited a customer to assume that the earlier activity belonged inside the base offer. Arun Kelveth wanted to keep the short name and explain the detail during the commercial discussion. He argued that a more qualified description would make the proposition harder to introduce. I thought the qualification concerned the beginning of the service, not a minor detail that could safely wait. A customer comparing offers might form an expectation before reaching the explanation. The product should not depend on every conversation correcting an implication that its own name had created. We allocated S$4.8 million to developing a separately defined origin-pickup option and a base description that began at port handover. This gave up the appeal of one broad name and required the selection process to identify the intended starting activity. It also made the relationship between the base and optional work clearer for colleagues who would have to arrange it. The decision did not settle customs responsibilities or announce completed bookings; those matters required their own applicable arrangements and evidence. The forty briefs established a scope distinction in the reviewed material, not a universal market share for the two offers. I kept that limit in the product account. The consequence was a proposition with a narrower base promise and a visible additional choice, rather than a claim that the service had become operationally broader for everyone. My judgement was that explaining the boundary early was worth the extra commercial work. If the customer needs origin pickup, the offer should let them choose it knowingly, with the relevant conditions examined before a commitment is made.
02
At Tervalen Transport I approved a single returned status that appeared when the carrier collected a parcel. It gave the product a clean completion message. The fictional merchant arrangements involved still required receipt and review before a refund decision, so collection did not complete the customer’s entire return. In the six hundred requests we examined, 420 had reached collection and 180 were awaiting it. The 420 events established a transport stage; they did not establish that the merchant had accepted the goods or decided the refund. Mei Lin Vellara challenged my approval because the label crossed that responsibility boundary. I initially favoured retaining the simple status with explanatory help text. She argued that the main message itself carried the stronger meaning and would be seen before the explanation. I accepted that the brief needed to change. The issue was not a failure by customers to read carefully; we had chosen a word that made our completed task sound like completion of work still owned by someone else. S$420,000 funded four distinct states: requested, collected, received and review complete. The last could appear only when the merchant explicitly supplied that decision. We surrendered the single completion message and accepted the work of coordinating the product with a separate merchant account. This was not a rule that all retailers must wait for inspection before refunding. It described the arrangements in this case; other programmes can agree other triggers. The product needed to represent the actual relationship rather than infer a universal one. The correction did not establish refund amounts or claim that all six hundred requests had progressed. The 180 awaiting collection remained at that stage. I kept my original approval in the narrative because it explains why the simpler label had become the accepted design. The lesson was to ask whose action a status records and what the customer may reasonably understand from it. A transport product can report its own event accurately while still misleading through the completion it implies, unless the responsibilities on both sides of that event are considered.
03
The regional freight offer under review emphasised a faster movement. Eighteen customer sites in the product study had a different practical distinction: eleven could receive on weekdays, while seven could receive only on Saturday. For the latter group, arriving sooner on a closed day did not answer the need. The product question concerned the receiving calendar as well as transit duration. I wanted the offer to state that condition rather than let speed stand in for usefulness. Arun Kelveth preferred a single expedited proposition, with individual receiving arrangements discussed after selection. He was concerned that a separate Saturday path would complicate the offer and create an expectation the operating network could not always meet. I shared the concern about availability. My answer was to make the path conditional on assessment, not to conceal the receiving requirement until after the customer had selected an apparently suitable product. A visible condition can be examined; an unstated assumption can travel much further before someone notices it. We allocated S$3.2 million to developing an optional Saturday receiving path with the relevant operating checks. The weekday offer remained for the eleven sites whose arrangements supported it. We did not promise that every lane or date could provide the Saturday option. The decision accepted extra selection and coordination work in order to distinguish the customer situations before commitment. It gave up the idea that one faster product could serve every receiving calendar merely through a stronger speed message. The eighteen-site review was not a completed-delivery audit, and the development allocation did not establish an on-time result. I describe the consequence as a more explicit product choice whose availability still required confirmation. The case illustrates the boundary between a movement and a usable handover. A receiving site has people, schedules and conditions of its own; the transport proposition should not make them disappear because they sit beyond the vehicle journey. I wanted the customer to choose with that whole receiving situation visible, and the operating team to retain the authority to confirm what could actually be arranged.
04
The reusable-crate proposition assumed a short circulation period. A review of 1200 units showed 840 back within twenty-eight days, 240 returning between days twenty-nine and forty-five, and 120 still unreturned at the forty-five-day cutoff. The middle group suggested that some customers’ use extended beyond the shorter assumption. The last group raised a different problem: those units were still unavailable. I did not want a product revision that solved the description of one group by making the unresolved position of another less visible. Mei Lin Vellara supported retaining the shorter option and handling longer use as an exception. Her concern was that a longer standard choice would tie up more equipment and make availability harder to manage. That was a real consequence. I supported a forty-five-day option only with inventory planning that recognised the longer cycle. The product could respond to observed use, but the additional time had to appear in the resource account rather than be treated as a wording change with no physical effect. S$2.7 million was allocated to developing that option and its associated planning. The shorter route remained where appropriate, and the 120 unreturned units remained separately unresolved. Extending a permitted period did not bring them back into available inventory. Nor did it establish why they had not returned. The product review retained those distinctions so that the new choice could be evaluated without an apparent improvement manufactured by changing the category in which the missing equipment sat. The consequence was a broader duration choice with an explicit resource cost, not a report of reduced loss or proven environmental benefit. Reuse describes an intended cycle; it does not on its own establish the effects of that cycle. My contribution was to connect the customer’s period of use with the continuing product obligation and the physical equipment needed to support it. I wanted the offer to remain understandable beyond outbound delivery, including what the customer needed to do, what the service had to plan and what the review still could not explain about the units absent at its cutoff.
05
A product comparison ranked the shorter movement first. In the illustrative booking scenario, option A involved two days of movement after five days of waiting for dispatch, giving seven days overall. Option B involved four days of movement after one day of waiting, giving five overall. These were deliberately hypothetical assumptions, not real lane schedules. They showed that movement duration alone could rank the options differently from the elapsed period the customer actually needed to consider. Arun Kelveth favoured retaining transit duration as the primary sort because it was familiar and easy to communicate. He worried that adding dispatch context would make the comparison dependent on circumstances that could change. I agreed that dispatch assumptions could change; that was precisely why the product should show them. Hiding the variable period did not remove its effect on the customer’s decision. It only made the shorter number appear more complete than it was. We allocated S$1.8 million to displaying elapsed-time context and the dispatch assumptions behind the comparison. The product would need the relevant availability assessed for an actual request rather than reuse the illustration as a service promise. We gave up the simplicity of one apparently universal ranking. The selected presentation allowed the customer to see why a longer movement might fit the current journey better when the period before departure was included. The case makes no claim that any shipment arrived two days earlier or that one transport mode is generally superior. Its result is the product decision and the work funded to make the comparison more informative. The arithmetic is small, but the responsibility is substantial: a commercial option should not acquire an advantage by omitting the part of the journey that makes it less useful in the circumstances shown. I wanted the review to examine which clock the offer starts, what it leaves before that clock and whether the customer is being asked to choose on a measure that answers their actual question.
Terrain
Languages
Fellow travellers
Dinesh accepted that the return status he had approved said more than our collection event could establish. He changed the proposition around the merchant’s actual review responsibility rather than defend the simplicity of the original label.
I supported the door-to-door name because it was easy to sell. Dinesh insisted that the starting handover and optional pickup be visible before the name implied work the base offer did not include.
Dispatches
I examine how a convenient service name can imply an origin activity the base offer does not include, and why that boundary belongs in the customer’s choice.
Read the essayI revisit the returned label I approved and explain why a service status must identify whose action it records before it announces completion to the customer.
Read the essayI examine an illustrative freight comparison in which dispatch waiting reverses the transit-time ranking, and ask which clock the product is inviting the customer to use.
Read the essayAn invitation
I would discuss freight proposition design, reverse-service boundaries or a possible first-board contribution where the question fits this record. External commitments require consideration of employment and commercial relationships. The demonstration is fictional and offers no transport booking, customs interpretation, refund decision or assurance about a live shipment. An initial conversation can begin with the product question without sharing customer consignment data.
office@dineshteo.example