I think a lot of the objections here aren't really bureaucracy in terms of government employees doing things. A lot of what people mean when they complain about "government bureaucracy" is really that it often seems to be 20 people taking 6 months to do something that should take 5 people 6 weeks. So discussions on this tend to get confusing.
The reason bureaucracies seem efficient is that they must be able to (1) complete the mission reliably over long periods of time, in the face of (2) staff churn and loss, without (3) collapsing the first time a critical mass of experts leaves the org. This means you have to sacrifice systems that rely on the enthusiasm of "10x experts" in favor of systems that can reliably recruit talent (at GS salaries.) And this is before you get to the mountains of political crap placed on an org by elected leaders.
It is incredibly challenging to create orgs that reliably stay on-mission over many years.
> it often seems to be 20 people taking 6 months to do something that should take 5 people 6 weeks
Sounds just like "enterprise" IT to me, tbh.
Regular people (including me) think the same thing about why software projects take so long. In fact I consider engineering to be a form of bureaucracy. And I've had long conversations about it with friends who are developers, but it's still hard for an outsider to fully grasp why it's so hard. In turn, they can't understand why my job can't be replaced by AI.