The 5 whys for customer complaints

The method

The 5 whys for customer complaints is simple: state the complaint, ask why it happens, then ask why that happens, and keep going until you reach something the business can change. It works best on a specific, recurring complaint and with evidence for each step.

Rules for a good chain

• Start with a specific complaint, not a category.
• Each answer must be supported by evidence: reviews, data, observation.
• Stop at a process, policy, system or resource decision, not at a person.
• If there are two answers at a step, follow each.

Example: a store

1. Why do customers complain about waiting to pay on Saturdays? Queues build between 5 and 8 pm.
2. Why? Only one counter is open.
3. Why? The second cashier's shift ends at 5 pm.
4. Why? Weekend rosters copy weekdays.
5. Why? Rosters were never revised when weekend footfall grew.

Cause: roster design. Fix: weekend rosters by footfall.

Example: an app

1. Why do users say money was deducted but no order placed? Orders fail after payment.
2. Why? The app times out waiting for payment confirmation.
3. Why? The timeout was shortened in the last release.
4. Why? To speed up checkout for fast payment methods.
5. Why was the impact on slower methods missed? No test for them.

Cause: timeout and missing test. Fix: restore timeout, add tests.

Common traps

• Stopping at a person: "the cashier was slow".
• Answers based on assumption.
• One chain when there are several causes.
• Going so far up that the cause is "the economy".

Testing the answer

Check whether stores, times or versions without the cause also lack the complaint. If they have the same complaint, the chain is wrong somewhere.

Common mistakes

• Blaming individuals.
• No evidence per step.
• Skipping the test.
• No follow-up after the fix.

Common questions

Checklist

• Specific complaint.
• Evidence per answer.
• Stops at a changeable cause.
• Cause tested.
• Fix checked.

In short

Ask why until you reach a process, policy or system you can change, support each answer with evidence, test the cause against contrasts, then fix and check.

Example: a restaurant

Why do diners complain that food arrives cold? Dishes wait at the pass. Why? Runners are busy clearing tables. Why? The restaurant cut a runner on weeknights. Why? Labour budgets were set from last year's covers. Why were they not updated? Weeknight covers grew after a new office opened nearby, and nobody reviewed the budget. Cause: an outdated staffing budget. Fix: staff to current covers and add a pass time limit.

Recording the chain

Write the chain down with the evidence for each step and keep it with the action and check date. Months later, when someone asks why a rota changed, the record answers, and it shows whether the fix worked.

Doing this with Falcon

Falcon labels each topic in scope as needing attention, emerging or a strength. Each insight names the issue, why it matters and a next step that names the taxonomy owner; actions can be tracked to done, and because reviews keep being classified, the same signals show whether the issue's negative share falls afterwards.