Book Appointment

Hip Hospital Pre-Mortem: Eight Ways a New Booking Flow Fails

Healthcare IT

A hip hospital rolls out a new online booking and enquiry flow. Three weeks in, the front desk is firefighting, families are phoning to check whether their request arrived, and the project lead is wondering what happened. Nobody was careless. The trouble is that nobody asked, before launch, how it would break. This post sets out a hip hospital pre-mortem in a blunt problem-and-fix format: imagine the new process has failed, name the problems, and attach a fix to each one. It is about administration only. It contains no clinical advice and does not discuss treatment.

The setup: assume it already failed

Before anyone defends the design, say this out loud: “Twelve weeks from now this flow has been shelved. List the reasons.” That framing is the whole method. People who would hesitate to criticise a colleague’s plan have no trouble explaining a failure that is already in the past. Give the group ten quiet minutes to write, one reason per note. Then work through the problems below, which come up again and again in hospital administration.

Problem 1: The form asks for too much, or the wrong things

What happens: Families abandon half-completed forms, or paste long personal stories into a box meant for a short category. Staff then spend time sorting through free text.

Fix: Cut the form to what the desk needs to make first contact: a name, a way to reach the person, a preferred contact time and one short drop-down for the type of enquiry. Everything else belongs in the conversation that follows. Test the form on a phone with a weak connection, because that is where many families will meet it.

Problem 2: Nobody owns the inbox

What happens: Requests arrive in a shared mailbox. Each person assumes someone else is watching it. Replies slip by days.

Fix: Name one owner per shift and one backup. Write a rule for what happens to anything unanswered after a set time, such as a reminder to the supervisor. Make the rule visible to the whole team, not hidden in a document.

Problem 3: Promised response times are fiction

What happens: The confirmation message says “we will reply within a few hours,” but weekends, public holidays and staff absences were never counted. Families judge you against the promise, not against your intentions.

Fix: Measure real reply times for two weeks before promising anything, then publish a figure you can beat comfortably. An honest “one working day” is better than an exciting claim that fails.

Problem 4: Information is retyped between systems

When the web form, the call log and the appointment calendar are separate, somebody copies details between them, and copying introduces errors: a transposed digit, a misspelled name, a missed note about a preferred language.

Fix: Choose one place where the enquiry lives from first message to appointment and make every other tool read from it. If that is not possible yet, add a short double-check step and track how often mismatches are caught. If the count is high, treat it as a signal to invest in an automatic link.

Problem 5: Travelling families fall through the gaps

What happens: Time zones, language preferences and arrival logistics were never part of the design, so families from other cities or countries find the process baffling.

Fix: Add a field for time zone and language, state call-back windows in a way that includes the zone, and agree on a standard message for people who will be travelling a long way. Keep it informational; the clinical team remains the only source of medical guidance.

Problem 6: The technology fails quietly

This one is easy to miss because nothing visibly breaks. A plug-in updates and stops sending notifications. A staff login that was meant to be temporary is still active months later. A connector between the website and the records system stops syncing on a Friday night. Nobody notices until Monday, or later.

Fix: Ask your IT contact the awkward questions. Who is alerted if form submissions stop arriving? Who reviews access rights, and how often? What is the plan if the website host has an outage? Software teams think a great deal about these matters when they protect the automated routes that carry code into live systems; for an example of how practitioners discuss it, a good window is the DevSecOps Now site, where the blog mostly tackles how to keep build-and-release pipelines safe, though it is written for engineers. A hospital web team can borrow the mindset without borrowing the toolset. It is also worth reading a general piece on building dependable IT operations if you want a wider view.

Problem 7: Success was never defined

What happens: The project launches without any agreement on what good looks like, so every complaint becomes a debate and every compliment is dismissed as luck.

Fix: Pick two or three plain indicators before launch, such as the share of requests answered within the promised window and the number of families who phone to ask whether their request arrived. Review them at fixed points. If the numbers worsen, you have agreed a trigger for pausing and looking again.

Problem 8: The old way is switched off too early

What happens: The phone line and walk-in desk are quietly deprioritised the day the new flow launches. Families who cannot or will not use the web page find themselves with no route at all, and the first few weeks of complaints come from exactly the people the hospital most wanted to reassure.

Fix: Keep every existing route open during a defined overlap period. Retire a route only when the numbers show that few people still use it and the desk has a plan for the remainder. Tell families plainly which options are available, so nobody has to guess.

Turning the list into a plan

  1. Rank the problems by how likely they are and how much they would damage trust.
  2. Choose the top five. Pick fewer fixes and finish them properly.
  3. Write each fix as a specific action with a named person and a date.
  4. Rehearse the flow with a colleague posing as a family member, using a real phone.
  5. Launch to a small group first if you can, and keep the old route open until the new one has earned trust.
  6. Review after a month and compare real problems to the imagined ones.

How it fits with what families already read

Families often arrive at the enquiry page after reading background material such as an article on typical reasons people look into hip concerns. They carry that context into the form. If the process feels slick on one side and shambolic on the other, they notice. Consistent clarity from the first article to the final confirmation is a quiet but real advantage.

The bottom line

You do not need a consultant or a big budget to run a pre-mortem. You need an hour, a whiteboard and colleagues who are allowed to be candid. The problems you find will mostly be small and ordinary, and that is exactly the point: small and ordinary failures are the ones that cost trust and are cheapest to prevent.