Amazon Leadership Principles — Behavioral Stories (STAR)

Declining a customer request after evaluating tradeoffs

• Amazon LPs — Customer Obsession · Are Right, A Lot · Dive Deep · Earn Trust · Have Backbone; Disagree and Commit
• Situation — A newly onboarded school requested real-time attendance synchronization between mobile and web — mark attendance on mobile and it appears instantly on the web portal without a refresh. At first glance it sounded reasonable.
• Task — Instead of immediately accepting or rejecting, my job was to understand whether the problem justified the engineering investment and to find the best solution for both the customer and the product.
• Action — I ran a discovery call to understand their workflow and why real-time mattered, then discussed the technical implications with the engineering team.
• Action — True real-time sync would require significant architectural changes across frontend and backend — persistent connections, event-driven synchronization, conflict handling, and infrastructure changes. I also assessed breadth of benefit: it was unique to a very small number of schools, not a common product need.
• Action — Given the high effort and limited impact, I recommended not prioritizing it, and communicated the decision transparently — the technical tradeoffs, and why investing in more broadly beneficial features creates greater value for all customers.
• Result — The customer didn't get the exact feature they requested but appreciated the transparency and the rationale behind the decision.
• What I Learned — Customer obsession doesn't always mean saying yes. It means deeply understanding the problem, carefully evaluating options, and making decisions for the greatest long-term value — communicated honestly.