A useful calendar explains the commitment

I study how a venue prepares, uses and returns a space, rather than assume that the booked session describes its whole occupation. In a prepared set of 240 bookings across twenty-six spaces, eighteen conflicts arose from setup or clearing time. Those examples helped us define explicit windows and the way a conflict should be explained. They were not a representative measure of every customer's operation. Product researchers worked with operators to distinguish a configurable rule from a judgement that staff still needed to make. I want the system to show why a slot may be unavailable and who can review it, without suggesting that software has assessed physical suitability or event safety. The value is a more faithful account of the commitment, with local responsibility remaining visible.

I ask staff to complete actual booking work using the keyboard so we can observe where focus, labels and interaction order obstruct them. Thirty participants attempted representative tasks; twenty-one were blocked and nine completed them. A ₹44 lakh programme addressed the observed problems. On repeat testing with the same group, twenty-seven completed and three still needed assistance. That is useful evidence about a defined set of tasks and participants, not an accessibility certification or a claim covering every disability and device. I want the remaining difficulties reported alongside the improvement, with engineering and design clear about the next change to test. Product leadership means treating the people who cannot finish as part of the release conversation, even when the majority result has become more encouraging.

A recurring reservation is a pattern with exceptions, not simply a convenient way to create many identical appointments. Our review of 140 series found twenty-three holiday exceptions that differed from the operator's intended dates. We introduced a preview of the occurrences affected by a change and asked for confirmation before applying it. The product needs to distinguish one occurrence, later occurrences and the whole series, while preserving the account of what was actually changed. I work with researchers and engineering to make that distinction understandable to a busy operator. A clear preview does not replace staff judgement about opening days or customer agreements. It gives that judgement a better place to happen, before a broad edit quietly changes commitments that somebody intended to leave alone.

Tentative reservations can be useful when an organiser is still deciding, but their status must be understandable to everyone reading the calendar. We examined sixty-four holds and found seventeen still displayed after their stated expiry without a clear expired label. Operators could not reliably tell whether the space was committed, being discussed or available for a new enquiry. I sponsored a ₹29 lakh change that made expiry and the responsible staff member explicit and required an operator decision before converting a hold into a confirmed booking. It did not automatically cancel a customer's agreement or release a room under rules we had invented. My aim was to make an unresolved commercial conversation visible, so product behaviour supported the venue's decision instead of appearing to make that decision for it.