Make the next step clear without promising its result

A bicycle owner can know that a tyre loses air without knowing why. Our earlier flow demanded a repair category before assessment, and I approved it because it appeared to make the request easier to route. The selected thirty-case review showed why that convenience was misleading. Eighteen cases were tube-related and twelve had other causes, but the owner had not been qualified to make that distinction at booking. We changed the request to preserve the observed symptom and leave diagnosis with workshop staff. I want a product to collect what the customer can reasonably know rather than turn a compulsory answer into supposed technical evidence. The result should help the service conversation begin accurately. It should not imply that a symptom description establishes the required repair, the final quotation or whether the bicycle is suitable for use.

A thirty-minute booking can describe a window for arrival without describing how long the repair will take. In a selected group of twenty-four visits, ten were completed within thirty minutes and fourteen needed longer. The product had made those different stages too easy to confuse. We separated the arrival arrangement from an estimate supplied after assessment, with responsibility for that estimate remaining at the workshop. The selected observation did not establish a universal turnaround rate. I wanted owners to understand the next step before arranging their day around a completion promise no qualified person had yet made. Product design must make uncertainty specific enough to act on. A clear appointment can still be valuable when its purpose is receiving and assessing the bicycle, provided the customer can see that meaning before confirmation.

Appointment capacity and parts readiness answer different questions. In our selected twenty-request account, all had available appointment times, but thirteen had the specified replacement part reserved and seven still required sourcing. A single ready label concealed that difference. We kept the appointment state separate from the part state and let workshop owners explain what could happen at the visit. The seven cases were not automatically impossible appointments; assessment or another agreed next step could still be appropriate. Nor did the thirteen reservations establish completed repairs or technical suitability by themselves. I want the product to show the condition relevant to the customer’s plan without making a procurement promise on a workshop’s behalf. A bookable time should remain a time, while the additional requirements for the proposed work are represented with their own owner and evidence.

The product team can shape what an owner expects without controlling every action required to fulfil that expectation. Imran leads workshop-service partnerships, qualified staff assess and repair bicycles, and Kavita retains enterprise decisions. My twenty-two colleagues must work with those owners when a screen appears to promise diagnosis, completion or parts availability. I ask the team to describe the customer’s next action and the condition that still needs another person’s judgement. That is more useful than filling the interface with broad reassurance and leaving the workshop to explain exceptions later. Product leadership includes accepting a less conclusive confirmation when it is the more accurate one. The ambition is a service exchange that both sides understand, with the responsibility for each decision visible before the owner commits time or assumes the bicycle will return in a particular condition.