I buy that... but real talk, there's gotta be a ton of bloat in the engineering org, no?
I've never worked at Google but I know shitloads of Googlers. And listening to their work problems... it sounds like engineers outnumber the other functions like 10:1 (at a minimum) but still produce mind-bogglingly slow estimates for the simplest shit. Like... 9 months to create a settings page. 6 months to change a few pages cumulatively simpler than a CRUD app.
Is it the systems they have to work with? The approvals to connect to this or that? Is everything within Eng bureaucratized to fucking hell and back? Or are >50% of them completely faking it and utterly useless? What the hell's going on there?
Edit: for context... yes, the abstracted examples I'm giving are coming for the perspective of PM / Design / Marketing folks. And when I ask my Eng Googler friends they get awkward and cagey and seem to not want to say anything mean about anyone.
All of the above. Sometimes the system you need to change was written six years ago by an intern from another team that was defragged, in a framework that isn't supported anymore, and everyone keeps piling the tech debt higher.
Some parts of Eng are mind-blowingly incompetent. Google is remarkable not for "hiring the best people" but for how widely the quality varies by org. Some orgs have a reputation for incompetence.
Security and Privacy is a great example. Half the org is fanatical about protecting users, smart, effective, the works...and the other half is fanatical about ticking the right boxes on their forms and putting roadblocks in front of product teams because it makes them look important. Try getting something done when someone from the second group is paying attention to you, and yeah, it'll take nine months to launch a settings page.
Yes, there's bloat, but it's not as simple as "there are too many people so MMM ruins your productivity".
