It really is one of the dumbest things in government work. Politicians want to "shrink government" so they don't want many actual employees that would probably be well paid, stable, but someone needs to do the work. Thus, enter the I-too-want-to-shrink-the-government politicians who agree but then farm it out to contractors, some whom they might work for one day (or even come from in some cases in the US!). And so the actual government employees are few and far in between while everything else is farmed out to contractors, some who are good and many who do fly by night jobs on grants and have no incentive to do better otherwise.
For the sake of debate, lets assume an equal level of incompetence between contractor run projects and government run projects.
In that case at least
a) There's no need to pay extra for the profit margins of the contractor companies (and the inevitable sub-contractors they use)
and
b) The incentives of the people doing the work are likely to be closer to the original project, in that the people doing the work are in the same organization as the project.
For me, outsourcing makes sense if the organization doesn't have enough of the specific type of work to have a fully staffed internal team, so specialist services, or if they are obliged to get an external opinion (e.g. auditing/pen testing). Otherwise you're just adding more layers of profit seeking middle-people...
"Overhead" is a large part of costs, and profit is often contractually limited in government contracts. But much of the profit is hidden in the markup, which can sometimes be 50%, meaning you pay $1.50 for $1.00 of supplies, labor, etc.
To add to this, the gov requires that all the markup is broken out, so it can be audited. I think usually contractors are allowed things like R&D budgets, salary (maybe not bonuses?) etc. I'd love someone more knowledgeable than I am to chime in.
The Apollo program was run by NASA, who had lots of government employees, but at the same time all the hardware and much of the software was built by contractors. The Apollo program was behind schedule and over budget for most of the project period.
NASA originally estimated the cost to somewhere between 7 and 12 billion USD; NASA Administrator increased this to 20 billion USD in 1961, but it ended up costing more than 25 billion USD in 1973 dollars.
When allowed to do the job well, yes. The UK’s Government Digital Service led the way in this, and have massively improved the online experience of everything from finding information about the current Parliament to booking vaccinations. Their entire approach is focused on “what does the user need” as opposed to “what does the thousand page spec doc say”. The USDS was founded on the same basis and from what I’ve heard are similarly impressive.
That's heart-warming to hear, but alas cherry-picking examples won't sway anyone much?
Have a look at eg the outsourced Danish firefighters. Seems to work just fine, but would be unthinkable in most countries, including the US. (Btw, Americans have more firefighters per capita than about anywhere else.)
Let me offer an alternative version of why people take the presumably-government roles and do them as private contractors: avoidance of byzantine requirements and cynical implementations of laws aimed at preventing fraud, waste, and abuse (FWA). People drastically overestimate FWA because they commonly describe or conceive as FWA government projects which they don't like. A couple examples:
It's relatively hard to get any work done at my job during the month of April, because about half the building is 85-88F (in a temperate mid-atlantic climate). That means that people will work in other cooler offices (problem when no one carries a cell phone) or just find reasons to leave early. I used to battle about this, but then I learned that it was for the unmovable ideal of economizing. Unfortunately, I'm a victim of economizing a 1970s building with huge plate glass windows that don't open.
Second example:office supplies. A supervisor asks me to have a room set up for a meeting. After determining that what I need is not kept on hand, I try to buy them through the government catalog as I'm supposed to. My internet connection fails, so I reboot my desktop (roughly 20-30 minutes). When it fails again, I lament that I probably have a dozen faster computers at home, ranging from 10 year old tablets to a raspberry pi, and with that I take the opportunity to step away from my office (low 80s in the summer, when this takes place, because the AC can't keep up.) I go down to my car where I can use my own air conditioning and my phone to look at the same website. The supplies aren't on the catalog, so I just order them for $10 on Amazon. Fast forward one week, when my supervisor asks how I have it ready so soon, and I get criticized for buying the supplies outside of the supply system with my own money. I place too high a value on my sanity, apparently.
Edit: I should mention that most people at this office are paid quite well relative to the area
This isn't an alternative version, this is what I mean about the horrible requirements which are aimed at FWA but just off-loading it to a contractor doesn't make it disappear.
I'm a government employee. I work with a few dozen people across multiple locations doing actual work. Not one of us is a contractor. Zero contactors are involved in any real work. The few we have are in support positions. We have some contracted IT people who manage some of our computer systems but don't have any access to what those computers actually do. We have contacted security guards at the front gate. And I think the cleaners are contracted out but as they have NEVER cleaned my office I don't see them much.
I think there is some observational bias going on in this thread.
When I was a defense contractor it always struck me as weird that the guardhouse at USMC HQ at the Navy Annex was staffed by $12/hr private security guards.
On the other hand the commander of the group I was doing work for pointed out that a fully trained Marine private was far to costly an asset to waste checking visitor ids.