The clock starts somewhere
A transport comparison can be perfectly clear about movement duration and incomplete about the journey the customer is choosing. The clock may begin at dispatch, leaving the wait before departure outside the displayed measure. A shorter movement then appears to be the faster option even when the customer must wait longer for it to begin. The arithmetic is not difficult. The product judgement lies in deciding which period the comparison should make visible and how to explain the assumptions without turning an illustrative choice into an unsupported service promise.
Our fictional 2025 example used two deliberately hypothetical options. The first involved five days of waiting followed by two days of movement, giving seven days overall. The second involved one day of waiting followed by four days of movement, giving five overall. Ranking only the movement durations placed the first option ahead. Including the preceding wait reversed that order. These are not actual lane schedules or reported shipments. They are a simple way of exposing the difference between the measure the product offered and the elapsed period a customer might need to judge.
Arun Kelveth wanted to keep transit duration as the primary comparison because it was familiar and easy to communicate. He also pointed out that dispatch assumptions could change. I agreed with both observations. Familiarity can help a customer understand a choice, and a changing departure position requires care. Yet leaving the waiting period out does not remove it from the journey. It removes it from the comparison. If the omitted period can alter which option best fits the need, its variability is a reason to explain it accurately rather than allow the shorter movement to stand for the whole account.
We allocated S$1.8 million to showing elapsed-time context and the dispatch assumptions behind selection. The product would still require the relevant availability to be assessed for an actual request. I did not want the seven-day and five-day illustration reused as a published commitment. The decision concerned the structure of the comparison: movement duration should remain visible, but it should not silently answer a broader question about the period from the customer’s current position to the intended handover. The option needs to be understood with the conditions that make its timing meaningful.
A changing assumption still belongs in the choice
Teams sometimes omit a variable because it is difficult to state with certainty. That can make the interface look more stable while making the decision less informed. The better question is how the product should represent what is known, what is provisional and what requires confirmation. A dispatch assumption may need a date or an explicit condition. A real service may require a different account altogether. The product leader’s responsibility is to make the relevant uncertainty understandable, not to remove the period from view simply because a single enduring number would be easier to maintain.
I would distinguish the comparison from the operating commitment. The comparison helps the customer consider the available types of journey under stated assumptions. The commitment requires the actual request and the responsible team’s confirmation under the applicable arrangement. Confusing the two can create overstatement in either direction. An illustration can be mistaken for an available service, or the need for later confirmation can be used to justify a comparison so incomplete that it offers little help. The product needs a useful account of choice and a clear route to the evidence required before commitment.
The receiving end can change the question again. In a separate 2014 review, seven of eighteen sites could receive only on Saturday. A shorter elapsed period would not necessarily create a usable handover if the site was closed when the goods arrived. I do not combine that case with the 2025 arithmetic as though they were one dataset. They illustrate related but different conditions: the wait before movement and the calendar at its end. A freight proposition should know which of these conditions is material to the customer’s situation rather than treat speed as an answer that requires no further context.
There is a genuine design cost here. More context can make the comparison denser, and a customer should not have to interpret an operating manual to select a service. I favour a clear primary account of the relevant period, with its assumptions accessible and the next confirmation step explicit. The exact presentation depends on the actual offer. The principle is that simplification should preserve the distinction that changes the decision. If removing a period reverses the apparent order of the options, the omission has changed more than the visual density of the page.
Show the period the customer is deciding about
In a product review, I ask where the displayed clock starts and stops. I then ask which tasks or waits sit just outside those points. This often reveals that a team has chosen a measure convenient for its own service boundary. That measure may be useful, but it should not be allowed to represent the customer’s full period without explanation. The exercise is especially valuable when a familiar label such as fastest carries a broader meaning than the number beside it. A precise number can still answer a narrower question than the label appears to ask.
The account of the work should be equally careful. The 2025 case reports a hypothetical comparison, a product decision and the expense allocated to improving the presentation. It does not report that shipments arrived two days sooner, that a mode is always preferable or that service reliability improved. Those claims would need different evidence. Keeping the outcome bounded allows the example to do its actual job: demonstrate how a product can invite a better choice by restoring a period that the earlier ranking omitted. The strength of the argument comes from that relationship, not from an invented delivery result.
I want the customer to understand the period they are deciding about. Sometimes movement duration will be the relevant comparison, and sometimes waiting or a receiving calendar will change the practical answer. The product should make room for that distinction before a familiar number settles the choice by default. The shorter movement remains a useful fact once it has stopped pretending to describe every part of the journey. A responsible freight offer places it inside an account whose starting point, remaining conditions and intended handover the customer can actually recognise.