Design the commitment and the work that follows it

A practitioner can be available while the room or support resource needed for the appointment is not. In a sixty-appointment rehearsal we found nine such clashes. I funded ₹74 lakh of work on a combined reservation model instead of leaving staff to repair the mismatch after a visually successful booking. The method begins by identifying the resources required for the administrative commitment and the owner of each availability rule. It then examines what happens when one resource changes. A product should not describe the appointment as confirmed while quietly relying on an unresolved condition. The repeat rehearsal removed the nine known clashes across the same sixty scenarios, but did not establish universal coverage of clinic configurations. Providers still determine the clinical appropriateness and requirements of their services; our product represents the agreed administrative constraints.

An earlier slot offered to somebody on a waiting list is not a completed change to their appointment. Fourteen of forty-eight participants in our exercise believed the offer had already replaced their existing booking. We spent ₹38 lakh separating offer, acceptance and expiry states. The later exercise found forty-three of forty-eight participants distinguished them correctly, while five still needed help. I do not turn that result into a claim that every user understands the flow. The method asks what remains valid at each point, what action commits the change and what happens if the person does nothing. Staff must be able to explain the same sequence. A product that preserves the existing appointment until an explicit accepted change gives people a more dependable account of their commitment, even when it takes an additional interaction.

A usability exercise with thirty keyboard users found twelve could not complete the appointment-change task through the available controls. We funded ₹46 lakh for an alternative keyboard-operable route and associated review. In a repeat exercise twenty-seven completed the defined task and three still required assistance. That result concerns one task and one observed group; it is not a certification of the whole product or a claim that every accessibility need has been met. I want research to include the route people actually use, the point where they become stuck and the recovery available to them. Product leadership must budget for that work instead of treating it as optional polish after the preferred interaction is finished. The remaining difficulties stay visible in the roadmap and in the support account.

Saving a schedule change does not show that the affected clinic team has received and understood it. We examined 150 staff changes and found twenty-two without an acknowledged handoff. A ₹59 lakh revision made the receiving role and acknowledgement explicit. Eighteen known handoffs were closed and four remained under follow-up. The method distinguishes a database change from the working responsibility created by that change. It also asks what staff should do when the expected recipient is unavailable. Acknowledgement is not proof that a service was delivered or that a clinical outcome followed; it is evidence of a narrower transfer of administrative responsibility. I would rather retain an unresolved handoff than give managers a green status that conceals who still needs to act. That can make a report less comfortable while making the work easier to manage.