Behavioral: Root-Causing a Customer Problem with the Five Whys Technique

In a product manager interview at Amazon, you are asked for an example of using the "five whys" technique to get to the bottom of a customer problem. Describe the situation and the symptom you started from, walk the interviewer through each "why" you asked and what answered it, name the root cause you reached, and explain what you changed as a result. ```hint Back every answer with evidence Each link in the chain should be answered by something you actually checked, such as usage data, support tickets or a conversation with a customer, not by an assumption. Ask yourself where the chain should stop and why. ``` ### Clarifying Questions - Must every "why" be put to customers directly, or can some be answered through data analysis and conversations with your own team? - Should the example come from your own past work, or may you walk through how you would apply the technique to an Amazon product? - Does the interviewer expect exactly five steps, or a chain that stops once the root cause is clear? ### What a Strong Answer Covers - A specific, measurable starting symptom described from the customer's point of view. - A causal chain in which each answer is backed by evidence and narrows the problem, without jumping to a favored conclusion. - How the candidate handled steps where more than one cause was plausible, and how they confirmed the root cause before acting. - An action aimed at the root cause rather than the symptom, with a result showing the symptom actually improved. - Awareness of the technique's limits, and of how to ask customers "why" without sounding accusatory. ### Follow-up Questions - At one step two causes looked plausible. How did you decide which one to pursue, and what happened to the other? - How did you know you had reached the root cause, rather than stopping too early or digging past anything you could change? - If what customers told you in conversations contradicted your usage data, which would you trust and why?