Let us talk about a simple idea that can save a heart clinic a lot of headaches: the pre-mortem. You have probably heard of a post-mortem, where people work out what went wrong after the fact. A pre-mortem flips that around. Before you launch something new, you pretend it has already gone badly and ask, “What happened?” It sounds a little gloomy, but it is really a friendly way of catching small, ordinary problems while they are still easy to fix. On this page we explain a heart clinic pre-mortem in plain language, using an administrative example: a new appointment reminder and rescheduling service. There is no medical advice here, only everyday planning.
Why would a clinic need one?
Think about the last time you tried a new app or a new website for booking something. Maybe it asked for details you did not have to hand. Maybe the confirmation never arrived. Maybe you could not find the button to change your time. Now picture that experience for someone who is worried about their heart, or about a parent’s heart, and who is already juggling work, travel and family. A small hiccup can feel big. Clinics that want to be kind in practice, and not only in words, need to look for those hiccups before patients do.
The idea in everyday terms
Imagine you are planning a big family dinner. If someone asks, “What could go wrong?” you will probably shrug and say not much. But if they say, “It is next Sunday and the dinner was a disaster. Why?” you will suddenly think of a dozen things: the oven was too small, the guest with the dietary needs was forgotten, half the chairs were missing. The same facts were available the first time, yet the second question unlocks them. That is the whole trick.
A clinic example, step by step
Suppose a heart clinic is about to start sending text reminders and offering an online way to move an appointment. The team sits down and says, “Three months from now, we turned this off. Patients were annoyed and the front desk was overwhelmed. Why?”
Here are the sorts of answers that come up.
- Reminders went to an old mobile number because nobody asked patients to confirm their details.
- The message arrived in English only, and many patients and family members prefer another language.
- Elderly patients do not use text messages, so they got no reminder at all and missed visits.
- Two reminders were sent for the same visit, and a patient thought they had two appointments.
- When a patient rescheduled online, the front desk calendar was not updated, so two people arrived for one slot.
- The system sent messages at night, which worried people.
None of these is dramatic. Every one of them is the kind of thing that would have made patients sigh. And every one can be handled in advance with a little thought.
Turning worries into small fixes
After the list, the team picks the handful that seem most likely or most upsetting and writes down a simple fix for each. For the old phone numbers, a quick check at the next visit. For the language issue, short messages in the main languages the clinic hears every day. For patients who prefer a phone call, a choice of reminder method when they register. For double messages, a single schedule that every part of the system reads from. For night-time texts, a rule that messages go out only during daytime hours.
Notice how ordinary all of this is. Nobody needs special training. You only need a room, a few colleagues and the willingness to say the awkward things out loud.
Who should join in?
Anyone who will touch the new process: reception, the nurses who phone patients, the person who manages the calendar, the web or IT person. If you can, ask a friendly outsider to join, such as a volunteer or a relative of a staff member. They will notice jargon that everyone else has stopped seeing. Keep the group small so that everyone has a chance to speak, and make it clear that nobody is being blamed. The point is to improve the plan, not to criticise the people who proposed it.
What about the technical side?
Behind a reminder service there is always some software. Software can fail quietly. A connection to the calendar might break after an update, or a password might be shared among too many colleagues. Teams who build and release software spend a great deal of effort thinking about these risks, particularly around the automated steps that move code from a developer’s computer to a live website. If you are curious, the DevSecOps Now website has a blog on CI/CD pipeline security where practitioners write about this in their own words. You do not need to follow all of it to appreciate the underlying lesson: automated things deserve a little suspicion, and a quick imagined-failure session is a cheap way to give them some.
How long does it take?
About an hour is usually enough. Spend a few minutes explaining the imagined failure. Let everyone write down their ideas quietly. Share them, group similar ones, and vote on what matters most. Finish by choosing who will do what, and by when. Then put a reminder in the calendar to look back a month after launch and see which worries came true.
Common questions people ask
Is it the same as worrying too much? Not quite. Worry is vague and tends to loop. A pre-mortem is structured and ends with actions, which is a good antidote to worry.
Will it slow us down? A little, at the start. But it almost always saves time later, because the problems you avoid would have cost far more hours to fix once patients were affected.
Do we have to do it for every change? Not for tiny tweaks. Use it when a change touches how patients contact you, how they are informed, or how records move between systems.
If you like plain-language explainers
This blog also publishes short, readable pieces on cardiology terms, such as an overview of what the NYHA functional class means in everyday cardiology language and a primer on how murmur grading is described for heart sounds. They are there to help you understand vocabulary you may hear in a clinic; they are not a substitute for talking to your own doctor. In the same spirit, a pre-mortem helps a clinic explain its processes clearly, so that fewer people leave confused.
A final thought
Good care is not only about what happens in the consulting room. It is also about whether the reminder arrives, whether the form makes sense and whether a worried family finds a kind voice on the phone. A pre-mortem is a small, friendly habit that protects all of that. Try it before your next change, however modest. You may be surprised how much a short chat about an imaginary failure can improve the real thing.
