{"id":10865,"date":"2025-08-26T19:23:04","date_gmt":"2025-08-26T09:53:04","guid":{"rendered":"https:\/\/vietleadershipcoach.com\/?p=10865"},"modified":"2025-08-26T19:23:04","modified_gmt":"2025-08-26T09:53:04","slug":"the-amazon-fiasco-a-case-study-in-corporate-failure","status":"publish","type":"post","link":"https:\/\/leehopkins.com\/vi\/the-amazon-fiasco-a-case-study-in-corporate-failure\/","title":{"rendered":"The Amazon Fiasco: A case study in corporate failure"},"content":{"rendered":"

This was never supposed to be a saga. All I wanted to do was update my bank details so I could be paid the royalties I\u2019d already earned from books sold on Amazon\u2019s Kindle Direct Publishing (KDP) platform.<\/p>\n\n\n\n

Instead, that simple request detonated into one of the most sustained displays of corporate incompetence I\u2019ve seen in decades. And I\u2019ve seen plenty.<\/p>\n\n\n\n

What follows is not just a personal diary of frustration. It\u2019s a catalogue \u2014 a dossier \u2014 of how the world\u2019s biggest online retailer systematically fails its own authors, hides behind process, and mistakes theatre for service.<\/p>\n\n\n\n

The opening act: when \u201ccustomer-centric\u201d collapsed<\/strong><\/h2>\n\n\n\n

It began with a routine system prompt: \u201cYour bank details are incorrect. Please update them.\u201d<\/p>\n\n\n\n

Obediently, I tried. That\u2019s when I hit Amazon\u2019s two-step verification wall \u2014 an impenetrable block that locked me out from making the changes their own system demanded.<\/p>\n\n\n\n

I chronicled the absurdity in Astounding customer service failure<\/a>. It set the tone for everything that followed: scripted apologies, circular referrals, and no actual resolution.<\/p>\n\n\n\n

Handballing without ownership<\/strong><\/h2>\n\n\n\n

My next stop was support. Surely, I thought, a human could resolve what a machine could not.<\/p>\n\n\n\n

Instead, I was passed back and forth like a defective parcel. Retail support insisted it was KDP\u2019s problem. KDP support insisted it was Retail\u2019s. Each assured me the other had the power to fix it. Neither did.<\/p>\n\n\n\n

The loop was endless, and ownership was absent. I documented it in Amazon\u2019s failure of ownership<\/a>. It wasn\u2019t just poor service. It was cultural. Amazon staff seemed forbidden from exercising judgment or responsibility.<\/p>\n\n\n\n

AI knows you\u2019re angry \u2014 but no one cares<\/strong><\/h2>\n\n\n\n

Here\u2019s the irony: Amazon sells AWS Comprehend, a tool designed to parse sentiment in text. It can detect frustration, anger, escalation risk. If they\u2019re running it over my emails \u2014 and it would be negligence if they weren\u2019t \u2014 their dashboards must be glowing crimson.<\/p>\n\n\n\n

Sentiment: furious. Escalation risk: high. Resolution: zero.<\/p>\n\n\n\n

The AI knew. The culture didn\u2019t care. I spelled this out in When AI knows you\u2019re angry<\/a>.<\/p>\n\n\n\n

Kafka in a call centre<\/strong><\/h2>\n\n\n\n

As if the loop wasn\u2019t enough, escalation itself became a violation.<\/p>\n\n\n\n

When I copied multiple Amazon addresses into my emails \u2014 addresses suggested by Amazon staff themselves \u2014 the system spat out an auto-generated reprimand: \u201cYou copied an email address not associated with your account.\u201d<\/p>\n\n\n\n

At one point, their support inbox literally bounced my messages back, unable to accept mail. Kafka would have blushed. Monty Python would have laughed. I captured it in Kafka in a call centre<\/a>.<\/p>\n\n\n\n

Royalties withheld: the unconscionable core<\/strong><\/h2>\n\n\n\n

By now, the human cost was mounting. Days without sleep. Stress amplified by PTSD and autism. Hours wasted re-supplying evidence I\u2019d already provided.<\/p>\n\n\n\n

And all the while, Amazon continued to collect money from the sale of my books \u2014 while I remained locked out of my account, unable to access the royalties I had already earned.<\/p>\n\n\n\n

This was no longer just incompetence. It was unconscionable. That became the theme of Amazon is blocking me from accessing royalties I\u2019ve already earned<\/a>.<\/p>\n\n\n\n

The pi\u00e8ce de r\u00e9sistance: \u201cStart a new account\u201d<\/strong><\/h2>\n\n\n\n

Just when I thought the absurdity had peaked, Amazon\u2019s latest response arrived. Their \u201cmost efficient path forward\u201d?<\/p>\n\n\n\n

Create an entirely new KDP account, and trust them to migrate my books and royalties across.<\/p>\n\n\n\n

That\u2019s not a solution. That\u2019s abdication. Imagine your bank telling you: \u201cWe can\u2019t unlock your account. Just open a new one and we\u2019ll see if we can move your salary across.\u201d Regulators would laugh them out of the room. Yet Amazon presents it as best practice.<\/p>\n\n\n\n

I laid it bare in Amazon tells locked-out author to start over with a new KDP account<\/a>.<\/p>\n\n\n\n

Why this matters beyond me<\/strong><\/h2>\n\n\n\n

I\u2019m just one author. But this isn\u2019t just my story. This is a case study in how Big Tech treats creators:<\/p>\n\n\n\n