Bureaucracy on loop
Amazon’s latest email landed this morning.
After eight weeks of correspondence, multiple escalations, and a detailed technical breakdown explaining exactly where their systems fail, they’ve decided the next step is… to ask me for another video.
Not a new explanation. Not a fix. Just another screen recording of the same error I’ve already documented and described in forensic detail.
It’s the corporate equivalent of déjà vu: when a system can’t fix itself, it asks the customer to repeat the ritual.
Their “Executive Customer Relations” department now sounds like a machine that’s been programmed to chase its own tail. Each email is a polite variation of “we need more information,” as if the act of collecting data were a substitute for solving problems.
But the data isn’t the problem. The process is.
Amazon’s backend validation service is tripping on its own code when handling international phone numbers. The error is internal, reproducible, and documented across their own forums.
Yet here we are, weeks later, with no resolution and royalties still frozen.
The irony is inescapable: the company that built AWS—the backbone of half the internet—apparently can’t debug a login form without crowdsourcing its QA to its own customers.
I’ve now made it clear: if they want me to keep doing unpaid system diagnostics for them, I’ll be happy to invoice at my new rate of USD 10,000 per hour.
Until then, I’ll keep the emails, the screenshots, and the timestamps—because at this point, the real story isn’t about a broken login. It’s about a company so large it can’t see where its own code ends and its customers begin.
Lesson for Amazon
When your system asks customers to do your engineers’ work, it’s not a workflow—it’s a warning. Accountability dies when “more information” becomes a substitute for action.
A world-class company isn’t defined by how it automates apologies, but by how quickly it takes ownership of failure.
The post The silence that speaks volumes, Part 5 appeared first on vietnam leadership coach.
