3 ms·
One thing you should understand about the biggest Government IT contractors is that they put one of their few 'A' teams (really a 'B' team by big tech standard
by hn8305823 3y ago
One thing you should understand about the biggest Government IT contractors is that they put one of their few 'A' teams (really a 'B' team by big tech standards) on the project during the sales process, then swap out to one of their many 'D' teams after the win dinner.
Many of the people actually implementing the project wouldn't last long in the private sector and that's why you end up with results ranging from disappointing to epic disaster though bureaucrats inside the Government often do their part to make things worse.
It seems that by giving a significant take of each transaction to the contractor they were incentivized to actually do good work. This might be a feature instead of a bug except for how gross it is when dealing with public resources.
There are exceptions to this but they tend to be smaller companies working on smaller projects or subcontracting to the big guys, where performance on the contract is important to future wins.
- _djo_ 3y agoOne thing you should understand about the biggest Government IT contractors is that they put one of their few 'A' teams (really a 'B' team by big tech standards) on the project during the sales process, then swap out to one of their many 'D' teams after the win dinner. That's not just true for big government IT contractors, it's standard practice for any large contracting/consulting firm in the private sector too. The A team does the RFP response, the C or D team does the implementation so as to protect margins.