My kettle once tripped the kitchen fuse three mornings in a row, and my first three fixes were all about the kettle. A new plug, a different socket, a stern look. The fuse kept going. It took a patient neighbour with a habit of repeating “but why?” to steer me toward the real cause, which had nothing to do with the kettle at all. That small domestic saga is how I came to take asking why five times seriously, and also how I came to notice how many half-truths float around about it. Here are six myths worth retiring.
Myth one: you must ask exactly five questions
The number is a rule of thumb, not a legal limit. My fuse mystery ended at question four; a friend’s stubborn spreadsheet problem needed seven. The real test is whether your last answer names something you can change. If it names the weather, the economy or somebody’s character, you have stopped too early or wandered too far, and either way you should adjust. Treat five as a prompt to keep going past the first comfortable explanation, not as a finish line to cross and celebrate.
Myth two: it is just a way of finding someone to blame
Quite the opposite, when done honestly. Blame lives at the surface, in sentences such as “he forgot” or “she was careless.” The method asks why forgetting was possible, and the honest answer is usually a missing reminder, a muddled handover or a rushed week. In my own case the early answer was “the kettle is faulty,” which was a convenient villain. The later answer was about how the kitchen circuits were shared out, and nobody was at fault. A good why-chain tends to dissolve blame because it keeps relocating the problem into the arrangement of things.
Myth three: it only suits factories and engineers
Trace any recurring annoyance and you will find the same shape. Consider money: someone notices the account is empty a week before payday. The symptom is the balance. The deeper steps lead through small repeating charges, then through no one reviewing statements, then through the absence of a monthly ten-minute habit. If that sounds familiar, you may enjoy this earlier look at finding the quiet leaks that drain a runway, which approaches the same territory from the spending side. Travel works too. A missed connection is rarely about the traffic; it is about how long the traveller believed the journey would take.
A side effect I did not expect: those who keep at this start to hear their own first answers differently. “It always happens on Mondays” stops sounding like fate and starts sounding like a clue about what changes between Friday and Monday. Over a few weeks that retrained ear gets quicker, and the chains get shorter because you skip the obvious dead ends. That shift in listening is worth more than any single fix, because it follows you into every later problem, from a noisy radiator to a stalled hobby project.
Myth four: the answers have to be complicated
The finest chains I have seen are almost embarrassingly plain. Each answer is a short, factual sentence: “because the alarm was set for the wrong time,” “because the phone updated overnight,” “because I never check it after updates.” Complicated answers usually signal that you are mixing two causes together. When that happens, split the chain in two and follow each branch separately. Plain sentences are also easier to test, which matters, because an answer you cannot test is only a theory wearing a costume.
Myth five: you can do it alone in your head
You can, but you will probably cheat. Our minds love a story that flatters us, and the chain tends to bend toward whatever feels least uncomfortable. Writing each answer on paper, in order, makes the bending visible. Better still, say each one aloud to someone who is allowed to ask, “and why is that?” Planning a road trip is a good practice ground. Suppose a rental never quite fits the plan; a talk-through like the one in that travelogue about crossing Colombia on two wheels shows how many assumptions hide inside an itinerary that feels settled.
One caution before the last myth: do not let the chain become an interrogation of whoever happens to be in the room. Ask the questions of the situation, not of the person, and phrase them as “why did that happen?” rather than “why did you do that?” The difference in tone decides whether people lean in or clam up, and a chain built on defensive answers is worse than none at all.
Myth six: once you find the root cause, you are finished
Finding the cause is the middle of the job. The remainder is choosing one modest change, trying it, and checking later whether the original symptom has gone quiet. With my kettle, the answer was a small reshuffle of which appliances shared a circuit, and then a week of simply watching. Without that last step the exercise is a pleasant conversation. With it, you get something rarer: a problem that stays solved. Put a date in your diary to look again, and be willing to reopen the chain if the symptom returns.
A short routine you can borrow tonight
- Write the problem as a plain observation, with no cause hidden inside it.
- Ask why and write one short sentence in answer.
- Ask why of that sentence, and keep going until the answer points at a habit, a rule or a missing step.
- Stop when you reach something you could change this week.
- Make one small change and note the day you will check on it.
An aside on how other websites organise things
While gathering examples I wandered through some specialist websites to see how each handles repeated questions from visitors. One was a directory for people researching orthopaedic care abroad, laid out with hospitals, physicians, a blog, a forum and a search by keyword and country. I am not recommending or describing what it offers; I only noticed that a site arranged around questions has to be tidy about where answers live, which is the same discipline a why-chain asks of us.
Keeping the habit light
Do not turn every minor hiccup into an inquiry. Save the method for things that recur, cost you something, or irritate you out of proportion. For the rest, shrug and carry on. When a problem does earn the attention, give it a calm quarter of an hour, some scrap paper and room for a surprise. More often than not, the surprise is how ordinary the root turns out to be, and how pleasant it feels to fix something once instead of apologising for it every week.

