* Legal stuff (eg. some algorithm detected child porn in his account, is an employee legally allowed to look at it to confirm the algorithm was correct? no.)
* Internal Politics (eg. one team has found this account DoSing their service, while the account is perfectly normal in all other ways, but due to Googles systems being so complex a single-service ban is very hard to implement)
* GDPR/Privacy laws (The law requires the deletion of no-longer needed data. As soon as his account gets banned, the data is no longer needed for Googles business purposes (of providing service to him), so the deletion process can't be delayed.
* Stolen/shared accounts. All it takes is one evil browser extension to steal your user account cookie and go on a spamming spree. Figuring out how it happened is near impossible (user specific logs are anonymized). Usually just resetting the users logins doesn't solve it because the malware is still on the users computer/phone and will steal the cookie again.
* Falsely linked accounts. Some spammers create gmail addresses to send spam, but to disguise them they link lots of real peoples accounts for example via using someone elses recovery phone number, email address, contacts/friends, etc. In many cases they will compromise real accounts to create all these links, all so that as many real users as possible will be hurt if their spamming network is shutdown.
* Untrustable employees. Google tries not to trust any employee with blanket access to your account. That means they couldn't even hire a bunch of workers to review these accounts - without being able to see the account private data, the employee wouldn't be able to tell good from bad accounts.
* Attacks on accounts. There are ways for someone who doesn't like you to get a Google account banned. Usually there are no logs kept (due to privacy reasons) that help identify what happened. Example method: Email someone a PDF file containing an illegal image, then trick them into clicking "save to drive". The PDF can have the image outside the border of the page so it looks totally normal.
Yes, it's solvable, and Google should put more effort into it, but it's hard to do.
1. Ignore the downvotes. The reality (poor customer service perception) is what it is. Objectively looking at the problem and what can be done about it, without cynically assuming it's impossible, is the most practical focus going forward. Thanks very much for this insight, it was really interesting to read.
2. I've noticed various glitches and bugs over the years with various services - two I can remember right now are a) misspelling a search then clicking "did you mean" won't update the titlebar (been watching this one since ~2012), and b) accidentally sending an in-progress draft from one device will cause followup edits made on another device to sent to /dev/null. Well... I look at the kind of time-wasting junk input that makes it into Issue Tracker, I look at random app feedback, etc, and I know my feedback is never going to be seen. I can understand why things need to impact 10K people to be noticed. I thought I'd ask you: what's a good recommendation here?
3. Extremely specific question that I happen to be worrying about at the moment :) - I wasn't sure which Google account I wanted to use to play with GCP some months ago so I ended up enabling billing on more than one account using the same card. I have an idea I'd like to play which would call for a new account (since it would be tied to a YouTube channel) and would require me to use the same card yet again. All of this would be staying within the free tier, but I still wonder if I shouldn't run data takeouts first...? (I can't deny that the current state of Google services feels a bit like Russian roulette with extra servings of superstition - what doesn't kill your account, makes it stronger, or something??)