When something goes wrong in an operation, such as late medication passes, repeated billing errors or recurring complaints, the instinct is to fix the most obvious cause. Often that cause is only a symptom. Weeks later the same problem returns, and people wonder why the fix did not hold.
The "five whys" technique is a simple way to dig deeper: ask why the problem happened, then ask why again of each answer, until you reach a cause you can actually fix. Used alone, though, it can become guesswork. Pairing each why with a piece of data keeps the analysis honest. This post shows how, in a way that suits administrators, directors of nursing and operations managers.
The method comes from manufacturing quality practice. You begin with a clearly stated problem and ask "why did this happen?" Whatever the answer, you ask "why?" again, and keep going. Five is a rule of thumb, not a law. Sometimes three questions are enough and sometimes you need more.
For example, suppose a facility notices that many treatment entries are being completed late.
Why are entries late? Because nurses document at the end of the shift.
Why at the end of the shift? Because there is no device at the point of care.
Why no device? Because the tablets run out of battery or are not charged.
Why not charged? Because there is no charging routine or enough outlets.
Why no routine? Because nobody owns it.
The fix is not "remind nurses to chart on time." It is assigning ownership and a charging plan. That is a hypothetical, but it shows how the questions move from blame to cause.
Five whys relies on people's answers, and answers can be wrong. People may blame what is familiar, defend their own area or assume. Teams may stop at the first plausible explanation. Without evidence you can spend months fixing the wrong thing.
For each answer, ask: how do we know? Then pull a small piece of data to test it.
State the problem with a measure. Instead of "call lights are slow," write "median response time on the north hall is longer on evenings than days." Measure it first.
Ask the first why and write down the hypothesis. Several answers may be plausible.
Identify the data that would confirm or reject each hypothesis. This might be a report from your electronic health record, a staffing schedule, a log of equipment outages or a helpdesk ticket history.
Pull the data. Keep it focused. Look at a sensible time window and compare like with like.
Decide whether the evidence supports the answer. If yes, ask the next why. If no, return to the alternatives.
Repeat until you reach a cause that is actionable, something your organization can change.
Choose a fix and a measure of success. Decide what number should move and by when.
Reports from your electronic health record, such as documentation completion or order timing
Staffing and schedule records
Call-light or response logs
Helpdesk tickets and system outage records
Incident, grievance and near-miss reports
Supply, equipment or maintenance logs
Short staff surveys or conversations
Beware of a single cause. Many problems have several contributing causes. It is fine to branch.
Do not stop at a person. "Because the nurse forgot" is rarely the real answer. Ask what made forgetting likely.
Watch for small samples. A few cases may be coincidence. Look at enough data to see a pattern.
Correlation is not proof. Two things moving together does not mean one causes the other. Test with a change when possible.
Protect privacy. Use only the data you need, and keep resident and employee information secure.
Include frontline staff in the analysis. They know details no report captures, and they are more likely to support a solution they helped find. Keep the tone curious and blame-free.
Record the problem, the whys, the evidence for each, the chosen fix and the owner. After the fix is in place, check the same measure to see if it improved. If it did not, the analysis may have missed something, and you can revisit it.
The best analysis teams use this method regularly, not just after a crisis. A simple one-page template can keep it quick. UnityCare IT helps healthcare organizations gather and organize operational data, so teams can test their theories with facts and fix problems for good.
An outsourced IT department with proactive maintenance and one number to call.
Call or text: 405-285-3845
New customers: start@unitycareit.com
Existing customers: support@unitycareit.com
Address: UnityCare Technologies, 2524 N Broadway Ste 554, PMB 947974, Edmond, Oklahoma 73034-4172