An earlier appointment offer is a question, not a completed change

## Two different commitments were wearing the same appearance

A waiting-list feature can seem straightforward. An earlier slot becomes available, the product offers it, and somebody decides whether to take it. In our forty-eight-person exercise, fourteen participants believed that receiving the offer had already replaced their existing appointment. The feature was asking a question, but its presentation looked too much like a completed answer. That distinction mattered before any discussion of clinical priority or service outcome. People needed to know which time represented their current commitment and what action would change it.

The original design used similar visual language for offered and confirmed states. That consistency looked tidy within the interface, but it concealed a difference in responsibility. An offer requires a decision from its recipient. A confirmation describes a decision already accepted. If those states look interchangeable, the person may reasonably assume that the product has done more than it has. Product teams should not rely on internal terminology to settle that misunderstanding. The relevant test is what the person understands about their appointment after using the flow.

There is also a third state:expiry. An offer can cease to be available without changing the existing appointment. If the product does not explain that clearly, the person may wonder whether doing nothing has cancelled something. A useful design needs an account of inaction as well as action. What remains true if the message is not opened? What remains true if it is opened but not accepted? Those questions are part of the product promise, even though they do not produce the most attractive conversion story.

Our software coordinates administrative appointments. It does not decide whose clinical need deserves an earlier slot. Provider policies and qualified staff retain that responsibility. The product must represent the agreed process accurately without implying that its offer is a clinical recommendation. Keeping that boundary clear helps the team focus on the task it can improve:making the current appointment, the proposed alternative and the effect of acceptance understandable. A more persuasive interface would not be an improvement if it made those distinctions harder to see.

The growth team preferred a single-tap replacement with a short expiry message. Their concern was that additional confirmation would reduce take-up and make a useful opportunity feel cumbersome. I considered that a legitimate product cost. Research argued that the existing ambiguity was more serious than the extra interaction. I chose an explicit separation of offer, acceptance and expiry, with the original booking preserved until the replacement was accepted. We approved ₹38 lakh and postponed a promotional feature to make room for the redesign.

## The result that still contained five unresolved users

In the repeat exercise, forty-three of forty-eight participants distinguished the states correctly. Five still needed assistance. I want both numbers in the account. The improvement matters, but the remaining difficulty is part of the product we released and supported. Removing those five from the narrative would create an inaccurate impression of certainty. It would also make it harder to justify continued research and assistance, because the leadership team might believe that the understanding problem had already been completed and could safely leave the roadmap.

The exercise did not establish shorter clinical waiting times. It examined understanding of an administrative flow within a defined group. We did not treat acceptance of an earlier slot as proof of a health benefit or as a universal preference for every person. Someone may have transport, work or caring arrangements that make the existing appointment preferable. The product should allow a meaningful decision, including a decision to keep the original booking. A declined offer is not necessarily a failed experience; it may be the correct outcome for that person's circumstances.

Staff assistance remained available, but its role needed to be honest. It was a support route for people who needed help, not a reason to describe the direct flow as universally understood. The receiving team needed to see which appointment remained valid and whether an offer had expired or been accepted. Otherwise the interface could become clearer for the individual while leaving staff with a contradictory account. Product states are useful only when the people responsible for the same commitment can interpret them consistently within their respective roles.

I also wanted the team to observe recovery. A person can begin considering an offer, leave the flow and return after its expiry. The product should not force them to reconstruct what happened from an old message and a changed calendar. The right explanation is specific:the offer is no longer available, and the original appointment remains in place unless an accepted change says otherwise. That clarity can require more careful design than a celebratory success screen, but it addresses an ordinary situation rather than an exceptional edge of the service.

The five unresolved users gave us questions for further work, not permission to invent a single cause. We needed to examine the difficulties they encountered before assuming that another sentence or button would solve them. A product team should resist explaining every misunderstanding as user inattention. Sometimes the flow contains a genuine ambiguity; sometimes the language or interaction is unsuitable; and sometimes assistance remains necessary. Research should distinguish those possibilities. The executive responsibility is to fund the examination and accept the result, including when it is less conclusive than the release narrative would prefer.

## What a conversion measure leaves out

A conversion measure can tell us how many offers were accepted under a defined rule. It cannot by itself tell us whether people understood what they accepted or whether keeping the existing appointment would have been better for them. Those are different questions. I want the product account to preserve the distinction rather than make one number stand for all three. Management can still track take-up, but should not use it to erase the evidence about comprehension, assistance and the practical consequences of a changed commitment.

For directors, the useful challenge is the definition of a completed transaction. Does management count an offer viewed, an acceptance recorded or a replacement appointment confirmed? Does the customer's understanding match that definition? The board need not decide the button label to ask these questions. It can require an intelligible account of the promise and the evidence supporting it. That account should include who retains responsibility when a state remains unresolved, including whether the product has enough operating support to make its chosen design workable.

The cost of clarity should be visible too. We accepted another interaction and displaced promotional work. Those choices have commercial consequences, and it would be misleading to describe the redesign as costless. The argument was that a dependable commitment justified the trade-off in this setting. Another product might use a different interaction while preserving the same distinction. The principle is not to add confirmation screens everywhere; it is to ensure that the step which changes an obligation is understood as that step by the person taking it.

I now review offer flows by asking what remains true at every stage. Before acceptance, the earlier slot is a possibility and the existing appointment remains valid. After accepted replacement, the new commitment should be clear. After expiry without acceptance, the old arrangement should not disappear by implication. That sequence sounds simple when stated in words, but the interface, staff tools and support account must all sustain it. The product succeeds when it helps someone make a decision they understand, including choosing not to change anything.