Rekha manages the front office of a busy cosmetic clinic, and last spring she announced a change that sounded harmless: enquiries would move from phone calls to an online form, with automated confirmations. Within a week, three people had turned up on the wrong day, a family travelling from another city had received no confirmation at all, and the phone, which was supposed to be quieter, rang off the hook. Nothing clinical had changed; the administration had simply been launched on a wave of optimism. This article turns Rekha’s lesson into a practical checklist you can use before changing how any clinic or hospital handles bookings. It is strictly about administration. It offers no medical advice and says nothing about treatments or outcomes.
Why Rekha tried a pre-mortem the second time
When the clinic decided to change its reminder messages a few months later, Rekha did something different. She gathered four colleagues and said, “Imagine it is a month from now and the change confused people. Tell me how.” In fifteen minutes they produced nineteen reasons. Ten were duplicates or trivial. Nine were real, and four of those would have caused the same mess as the first launch. She stopped thinking of the exercise as pessimism and started thinking of it as cheap proofreading.
The checklist: five areas to walk through
Use this as a script for your own session. For each area, ask the group to complete the sentence “It went wrong because…” and write every answer down.
1. The first message a person receives
- Does the confirmation say clearly whether a booking is confirmed, pending or only requested?
- Does it include date, time, place and the name of a person or desk to ask for?
- Is the wording understood by someone reading on a cracked phone, in a second language, or in a rush?
- What happens if the message goes to spam, or the phone number has a typing error?
2. People who cannot or will not use the new route
- Is there a plain alternative for people without a smartphone, with weak signal or with limited confidence?
- Does the staff member answering a call know exactly what the online flow shows?
- Can an older relative booking on someone’s behalf complete the process?
3. Travellers and long-distance visitors
Clinics that welcome people from other cities carry extra responsibility for clarity. A guide to organising medical travel for a planned procedure and a walkthrough of preparing for online cosmetic consultations both highlight how much organisation sits around the clinical part. Ask: do visitors learn the date and arrival instructions early enough to arrange travel? What if a slot moves after they have bought tickets? Who tells them, and how?
4. Staff and handovers inside the clinic
- Has everyone who touches bookings been shown the new flow, including part-time and weekend staff?
- Do two people understand how to fix a stuck or duplicate booking?
- If the system fails for a day, is there a paper or spreadsheet backup that people have actually practised?
5. Records, privacy and tone
- Is the information collected on the form limited to what the booking needs?
- Who can see submitted forms, and for how long are they kept?
- Do automated messages sound respectful and discreet, remembering that people may read them in public?
A parallel from software teams
Rekha’s brother-in-law works with release pipelines and told her that his colleagues play a similar game. She looked up DevSecOps Now, a DevSecOps blog devoted largely to protecting CI/CD pipelines, and was struck that an entirely different industry shared her instinct to list the ways something could break before it did. She did not need the technical detail. She wanted the reminder that the habit is ordinary, not paranoid.
Turning answers into an action sheet
After the brainstorm, Rekha uses a plain table on a single page with four columns: the imagined failure, the early warning sign, the one change that prevents it and the name of the person who owns that change. She limits herself to the top seven. The rest stay on the whiteboard photo in case they matter later.
- Cross out reasons that are duplicates or clearly impossible.
- Rank what remains by how many people it would affect.
- For the top items, write one concrete change, such as rewording a message or adding a phone option.
- Assign one owner and a date for a quick check before launch.
- Re-read the sheet two weeks after launch and note which warnings appeared.
One more habit is worth borrowing: end every session by asking, “What did we all assume without saying?” Rekha found that the most dangerous items were rarely the ones people argued about. They were the quiet assumptions, such as everyone believing someone else had already informed the night staff, or that every visitor already knew which entrance to use.
How it went the second time
The reminder change launched quietly. One unexpected issue appeared, a message that displayed oddly on a particular phone, and because the team had already agreed who would handle problems, it was fixed within the day. Calls to the front desk did not spike. Rekha received a thank-you note from a visitor who had travelled a long way and said the instructions had been the clearest of any clinic she had contacted. It was a small compliment about an administrative message, and it meant more to Rekha than any metric.
What the front desk can add on a normal Tuesday
The best pre-mortems do not stop at launch day. Rekha now keeps a small “wobble log” at the desk where staff jot down any odd question a visitor asks, such as “Where do I park?” or “Is this the final time?”. Once a month she reads the log aloud at the team meeting. Patterns in those small questions reveal where messages are unclear long before anyone files a complaint. Visitors who are still comparing clinics, perhaps after reading a patient-oriented guide to picking a cosmetic hospital, form their first impression from exactly these small administrative details.
Keep the boundary clear
A pre-mortem like this belongs to the office, not the consulting room. Questions about suitability, risks or aftercare of any procedure are for qualified clinicians, and the administrative tidy-up should never blur that line. What good administration can do is make sure that people reach the right conversation on the right day, calm and informed. That is the entire ambition of the checklist, and it is a modest one worth meeting.