Before you buy clinic software, write down what actually goes wrong

Software gets bought at the end of a bad week. Something goes wrong badly enough to be visible, somebody searches for a fix, and a demo happens. The tool is usually fine. The problem is that nobody wrote down what was actually going wrong before the demo, so there is no way to tell afterwards whether it helped.

These four questions take an afternoon between them and they are worth more than any demo.

What happens now, step by step

Take one thing, say a new patient enquiry, and write down every step from arriving to booked. Who touches it, what they do, where they write it down. Do it by watching, not by asking, because what people describe and what people do are different documents.

Most clinics find at least one step nobody knew existed, usually a personal notebook or a WhatsApp thread holding the process together.

Which step is slow, and which is fragile

Slow and fragile are different faults and they need different fixes. A slow step costs time every day and can usually be automated. A fragile step works fine until one person is away, and it needs writing down more than it needs software.

What would you have to stop doing

Every new tool adds work before it removes any. If you cannot say what your team will stop doing once it is in, you are adding a system rather than replacing one, and your staff will run both until the new one quietly loses.

How will you know in three months

Pick the number before you buy. Attendance rate, time to first reply, callbacks made, whatever the actual problem was. Write down today's figure even if it is a rough count from a spreadsheet. Without a starting number, every result afterwards is an opinion.

If you cannot say what you will stop doing, you are not replacing a system, you are adding one.

Do these four and you may well conclude that you do not need to buy anything, and that two habits and a shared inbox would fix it. That is a good outcome and a cheap one.