5 whys: find why your deals stall, and fix it once

The 5 whys is a way to find the cause of a problem. You write down one problem, ask why it happened, then ask why of that answer, and you keep going until you hit something you can change. Every answer has to come from a record you can open. Then you fix the cause once, and the same symptom stops coming back every week.

Sakichi Toyoda gets the credit. The American Society for Quality (ASQ) quotes him on its five whys page: "by repeating why five times, the nature of the problem as well as its solution becomes clear." Some problems give up their cause in fewer than five, ASQ says, and some take more.

So the five is a rough guide. The Lean Enterprise Institute says the exact number isn't the point. What counts is asking until you reach the root cause and remove it.

When you sell, the problems don't look like broken machines. They look like this:

• Proposals that get no reply, more often than they used to.
• Callbacks you promised and didn't make.
• A month with half your usual booked meetings.
• One step in your pipeline where deals pile up and sit.
• A lead who went quiet after a first call that felt great.

Most reps answer each of these with one more nudge. "Just checking in." The 5 whys asks a different question: what keeps producing the silence?

Sakichi Toyoda was an inventor, born in 1867, who built automatic looms and founded what is now Toyota Industries. Toyota Industries' history of him says he died in October 1930 after a life spent on invention.

Toyota traces its production system back to one of those looms. Toyota's own page on the system says the loom was built to judge when something had gone wrong, and it credits Taiichi Ohno with helping to build the system on top of that idea.

Most guides retell Ohno's chain about a machine that stopped, which the Lean Enterprise Institute quotes from his 1988 book. The fuse had blown from an overload. The overload came from a bearing that was short of oil. The bearing was short because the oil pump was weak. The pump was weak because its shaft had worn down. The shaft wore down because nothing filtered the oil, so bits of metal got into it.

Swap the fuse and the machine stops again next week. Fit a strainer and the problem is gone.

Now picture your own version. The quote went quiet, so you sent a nudge. That nudge is the new fuse. It gets you through today, and the same quiet comes back with the next five quotes.

You need ten to twenty minutes, a pen, and the records from your last few weeks of selling.

1. Write the problem as a gap. Say what should happen, what happened, and by how much. "Sales are slow" won't work. "Over the summer, six in ten of my proposals got a reply within a week. In October, three in twelve did" is a problem you can chase.
2. Open your records before you answer anything. Your call log, sent folder, chat history, calendar and task list. If you don't log calls yet, start a sales call log today, because next month's chain will need it.
3. Ask the first why, and answer it with something you can point to. "I think I followed up" isn't an answer. "My sent folder shows nothing after the proposal" is.
4. Ask why of that answer. Each new why goes to the last line you wrote. If an answer has two parts, split the chain in two and follow each one.
5. Stop at something you can change. That's a habit, a missing step, a rule you work by, or a setting in a tool. A person or the market is not a stopping point.
6. Write one fix, with a name and a date, and decide how you'll check it. Pick a date and a count you'll look at. "Feels better" isn't a check.

Step one is where most chains go wrong, because the problem is fuzzy. If you log your week in ActivityTracker, the funnel works out a rate for each step from what you log, and names the step with the lowest rate as the biggest leak. Write that step's rate this month beside last month's, and you have your problem sentence.

Then turn the cause into a fix with ASQ's five hows. How will every quote get a next date? I'll type the date before I hang up. How will I remember? It's the last thing I do before the phone goes back in my pocket.

Look at what Nadia didn't blame. Not the buyers, not her price, not October. Each answer pointed at a record she can open and read, and the chain ended at a rule she can write on a card.

Her second branch is common. If you send a proposal to anyone who asks, before a first conversation, the reply rate drops, and no follow-up rescues it. How to qualify prospects covers the questions to ask first.

A good why asks about the work and can be answered from a record. A weak one asks after someone's mood or the market, and the only answer is a guess.

One test settles most of them. If you can answer the why by opening a log, keep it. If you'd answer it by guessing how someone felt, rewrite it.

The 5 whys works best in a sales team when the manager and the rep run it together on the rep's own numbers. Two people spot a lazy answer faster than one, and the rep knows which record to open.

Made-up example: Omar, one of six reps on a team, booked nine meetings a week through September and four a week in the first half of October. In their 1:1, the question his manager reaches for is "why are you behind?" That gets an excuse. So they open his log and ask why of the gap:

1. Why fewer meetings? Fewer conversations. His log shows 31 a week in September and 14 in October.
2. Why fewer conversations? He made far fewer calls before noon, the hours when his buyers pick up.
3. Why fewer morning calls? Since 1 October he's spent his mornings building quotes in the new quote template, at 40 minutes each.
4. Why 40 minutes each? Nobody showed him the price list import, so he types every line by hand.

Four whys, and they stopped because the fourth answer was something the manager can fix. The fix: a 20-minute walkthrough on Thursday, quotes moved to the afternoon, and a look at his morning call count a week later.

Notice where the chain landed: on a gap in training. Omar's effort never came into it. If a chain ever ends on "he's lazy" or "she's not hungry", ask one more why: what in the week let that happen? There's nearly always a process answer, and it's the one you can fix.

The same chain works in a weekly pipeline review. Pick the step where deals stall, and run one chain on the step instead of one per deal. Six stalled deals with the same cause need one fix. Then put the next step in your sales follow-up process, so the fix outlives the meeting.

Copy this into a note, a sheet or onto paper. The last three lines are the ones people skip, and they're the ones that change anything.

Keep every one you fill in. After three months you'll see which causes come back, and those are the habits worth fixing for good.

The method rarely fails because the idea is wrong. It fails when the chain is lazy. Watch for these:

• Stopping at the first answer. "They're busy" is where most reps stop, and it's where you send another nudge.
• Answering from memory. "I'm sure I called her back." Open the log. If there's no record, that's your answer.
• Following one chain when there were two causes. When an answer has an "and" in it, branch.
• Padding the chain to reach five. A weak fourth and fifth why, added to hit the number, send you off course.
• Ending on a person or the market. You can't fix either quickly.
• A neat chain and no fix. Close the page without an owner and a date, and next month looks like this one.

The method has limits, too. It follows one line of cause at a time, and ten tangled causes need a fishbone first. A one-off doesn't need it at all. The client who went quiet because she was on holiday just needs a message when she's back. Save it for the problem that shows up twice.

The 5 whys suits one clear problem with a likely line of cause. Two other quality tools fill the gaps on either side.

Reach for a fishbone diagram when you have a dozen suspects. ASQ's fishbone page describes it as a way to sort the possible causes of one problem into categories. Kaoru Ishikawa created it, so you'll also see it called an Ishikawa diagram. He gave generic categories, and he encouraged people to name their own. For a seller, good categories are your list, your message, your timing, your offer and your follow-up. Use the fishbone to find the biggest branch, then run the whys down it. ASQ's five whys page suggests using the two together.

FMEA, short for failure mode and effects analysis, looks forward instead of back. ASQ's FMEA page says the US military developed it in the 1940s, and that it ranks possible failures by how serious they are, how often they happen and how easily you'd spot them. Run one before a new prospecting sequence goes out, while a change costs you an edit.

Fix one cause, check it, then pick the next problem. That loop is kaizen, which the Lean Enterprise Institute defines as continuous improvement, and the institute's 5 whys entry points straight to kaizen and to plan-do-check-act. To run the loop on a seller's week, start with kaizen for salespeople.

Pick one problem that showed up more than once last month. Write it as a gap, with the numbers. Open your records, run the chain for ten minutes, and stop at the first cause you can change.

Then put the fix on a day. In ActivityTracker, a task typed with a day name, like "recount October proposals fri", is dated for that day, so the check lands on Friday's list instead of in your head. When Friday comes, count again. Keep the fix if the number moved, and if it didn't, run the 5 whys again from the answer you trusted least.

• American Society for Quality, Five Whys and Five Hows, read 28 October 2026
• Lean Enterprise Institute, 5 Whys, read 28 October 2026
• Toyota Industries, The Story of Sakichi Toyoda, read 28 October 2026
• Toyota Motor Corporation, Toyota Production System, read 28 October 2026
• American Society for Quality, What is a Fishbone Diagram?, read 28 October 2026
• American Society for Quality, What is FMEA?, read 28 October 2026
• Lean Enterprise Institute, Kaizen, read 28 October 2026