Completion belongs to a particular task
Completion is an attractive word in a service journey. It tells the user that progress has reached a meaningful endpoint and gives the organisation a clear event to report. The difficulty is that one party’s task can end while the customer’s purpose remains unresolved. A carrier may collect a parcel that a merchant has yet to receive and review. If the product describes the whole return as complete at that point, the message can be accurate about the carrier’s event and still imply something the carrier does not know. The product leader needs to ask which task the word has completed.
I learned this through a fictional 2007 decision at Tervalen Transport. I approved a single returned status triggered by collection. For the merchant arrangements in that case, receipt and review still preceded the refund decision. We examined six hundred requests: 420 had been collected and 180 were awaiting collection. The first group had crossed an important transport stage, but it had not thereby completed the merchant’s later work. The status made a clear internal event look like a broader customer outcome, and my approval had allowed that meaning to become part of the proposed product.
The distinction does not depend on a claim that every merchant follows the same sequence. Some returns programmes can authorise a refund at an earlier point under their own agreed arrangements. That is precisely why the product must represent the arrangement it actually serves. A universal-looking status can hide differences among programmes and suggest that one event has the same consequence everywhere. In our fictional case, the later merchant review mattered. The carrier could report collection, but it could not infer the merchant’s decision merely because its own part of the journey had advanced.
Mei Lin Vellara challenged the label rather than the existence of the collection event. Her point was that a customer could read returned as an answer to the wider question they cared about. I initially thought help text could explain the remaining stage. That would have preserved the main status and placed the qualification elsewhere. It was an inadequate response because the stronger meaning would still arrive first. We needed to change the product’s central account, not ask a secondary explanation to cancel what the headline had already encouraged the reader to believe.
The label I approved crossed that boundary
My role in approving the status belongs in the story. A polished account could begin with the challenge and end with four improved states, presenting the correction as a natural product evolution. That would remove the decision that made the simplification authoritative. Colleagues had been working within a brief I accepted. When the boundary became clearer, I needed to change the brief and accept the additional work, rather than treat the problem as an unfortunate interpretation by users or a communication detail someone else should repair around the original design.
We allocated S$420,000 to distinguishing requested, collected, received and review complete. The final state depended on an explicit message supplied by the merchant. The product could therefore describe the carrier stages without independently deciding that the merchant’s review had happened. This gave up the appeal of a single endpoint and required coordination across the parties. I regard that cost as part of the judgement. A more accurate account can need more work, and the sponsor should explain why that work is justified by the responsibility the earlier simplification had obscured.
The four states should not be read as evidence that all six hundred requests progressed through them. The 180 awaiting collection remained at that stage in the examined account. Nor did the product correction establish refund amounts or report a completed merchant review for the 420 collected parcels. It changed the meaning the service was permitted to present and the evidence required for the later message. Those are substantial consequences, but they are different from claiming the customer’s commercial outcome. I want both the status design and the leadership narrative to retain that difference.
The case also changed how I think about an event that arrives from another organisation. Its presence needs an agreed meaning. A message described as review complete should represent that decision under the relevant arrangement, rather than be inferred from elapsed time or a nearby transport event. The product team does not gain authority over the merchant’s judgement by creating a place to display it. It needs the relationship through which the message is supplied and understood. Otherwise the extra state can reproduce the original problem under a more elaborate interface.
Different arrangements need different accounts
The lesson is not to make every return journey longer or to prescribe one commercial policy. It is to identify whose decision the customer is waiting for and how the product can accurately describe its status. A programme with an agreed early refund trigger should represent that trigger. A programme requiring later review should preserve the later responsibility. The service can share visual conventions while retaining the differences that matter. Uniformity becomes harmful when it makes separate agreements look equivalent simply because one common label is easier to maintain across them.
I would ask a product team to review its statuses with several concrete questions. What event has occurred? Who can establish it? What might the customer reasonably infer from the chosen word? Which part of that inference belongs to another party? These questions do not require the team to disclose live customer records in a general review. Fictional examples can expose a meaning problem early, and authorised evidence can later establish how the actual service behaves. The important point is to examine the relationship between the event and the implied outcome, rather than inspect the label in isolation.
The continuing value of the 2007 case is that it places accountability beside a small-looking product decision. One word can close a journey in the customer’s mind before the responsible organisation has made the decision that matters to them. I had approved that shortcut. Correcting it required a different product account, resources and an explicit relationship with the merchant’s evidence. The result I claim is the correction of that boundary. The refund remains the merchant’s decision under the agreed arrangement, and the carrier’s completed event should not be asked to speak on its behalf.