Amazon Order Volume Falls 25%: Root-Cause Diagnosis and Response Plan

You are a product manager at Amazon, and orders have dropped by 25%. How would you work out what happened, and what would you do next? ```hint Split before you explain Before naming causes, decide which cuts of the 25% would tell you fastest whether the number itself is wrong, whether something Amazon changed broke it, or whether customers are genuinely buying less. ``` ### Clarifying Questions - Is the 25% measured against the previous week, the same period last year or the forecast, and is it a count of orders or their value? - Did the drop appear overnight, or did it build over several weeks? - Is it spread across every marketplace, device and category, or concentrated in one, such as the mobile app in a single country? - Does "orders" include third-party seller orders and recurring subscription deliveries, or only Amazon's own retail sales? ### What a Strong Answer Covers - Confirming the drop is real: the metric definition, the comparison baseline, calendar effects such as Prime Day or the holiday peak, and data-pipeline or tracking problems - Decomposing orders into traffic, conversion through the shopping funnel and order frequency, and segmenting by marketplace, platform, customer type, category and seller type - Separating internal causes from external ones and ranking hypotheses by how well they fit the timing, breadth and size of the drop - A concrete response: immediate mitigation, the owner and fix for the root cause, and how leadership is kept informed - The metrics and guardrails used to confirm recovery without trading away margin or customer trust ### Follow-up Questions - You find the entire drop sits in Android app checkouts in one country, starting the day of a release. What do you do in the next hour? - Orders are down 25% but revenue is flat. What does that suggest, and is it still a problem? - How would you brief leadership on the first day, before you know the cause?