Unfortunately this doesn’t work either. Contracting is risk adverse and tries to avoid legal battles at all costs so even bad reviews often get scrubbed and edited until they look glowing.

The risk adverse nature of the govt needs to be fixed before the incentives align.

Do any governments employ a competitive approach to awarding contracts that isn't winner-take-all? If there were a way to build an ATC system utilizing both Verizon and Starlink we might get the benefits of price competition and redundancy.

Yes. The US does this with some larger programs ("systems of systems") if the components are sufficiently distinct. An aircraft? Not so much. A comms system? Absolutely, if it's not sold as one complete system. For instance, radios might be contracted to multiple vendors with the intent to drive down cost.

It's not universally done, though. It depends on how the program office(s) involved decide to run things.

EDIT: To expand. Look at space systems. The ground stations are not tied to specific space systems (though some space systems develop their own ground networks), that is a separate program from the satellites and SOCs. There is no one "space program". And even for a particular satellite system the SOC may be under a separate contract vehicle than the satellite itself.

>An aircraft? Not so much.

NASA did this with the commercial crew program, awarding to both SpaceX and Boeing to reduce risk.

Right, that's similar to the radio example I gave (multiple vendors so that there was no single point of failure, it mitigated risk and, in theory, reduces cost by introducing competition). What I meant by aircraft though was that for a specific aircraft, it'll be run by a specific contractor for all or nearly all its subcomponents. Though there could be exceptions. See the way that heavies (cargo, AWACS, and the like) are given multiple missions and some of the mission specific components may be separate programs rather than executed by the prime for the aircraft. But you won't have the government contract for the engine and the airframe separately.

Though you also have that done for aircraft. The F-35 was selected among several aircraft that were being developed by various contractors as the one to move forward as the JSF. This is where the lifecycle of a program comes into play. In the R&D stages you'll see multiple options quite commonly because they want to compete different vendors. Eventually it whittles down to one for things like aircraft to move forward. Though, using the JSF as an example, maybe they should select multiple. LM were the geniuses that thought you could increase software productivity by hiring more programmers and having them work in shifts.

Isn't the logical way to do that for a contractor to make a bid intending to use multiple subcontractors to provide a better service than any one contractor could provide alone?

That is one way it's done, yes.

even conceding that, letting one guy decide it using executive power is problematic. And illegal