“IT Modernization”

For an organization whose stated purpose is “IT modernization” and which claims to be staffed with only the best and brightest software engineers, you would expect DOGE to have shipped multiple major software projects. Here are the projects I know of so far:

By this count, the only original work has been two websites, an email server, a few demos, a few “fixes,” and one more ominous project. Is that all there is? This might seem perplexing, especially since Musk has bragged repeatedly that DOGE’s superpower is that its members are working 120 hours a week and DOGE staff have clearly not been constrained by the same pesky privacy and cybersecurity rules that constrain other software development projects. Besides the obvious answer that working insane hours has been shown to reduce the quality of teamwork, I think this mystery is answered by looking at the skills of people in DOGE (skill assignments are my own assessments).

Administrator 14
Analyst 15
Coder 43
Designer 2
Executive 35
Lawyer 16
Recruiter 8

There are a lot of lawyers and executives and a few HR administrators, of course. This follows from the DOGE design of embedding lawyers and coders and HR representatives within agencies. What’s lacking are all the other disciplines necessary for agile software development. Modern software teams will often include a product manager, a project manager (often a scrum lead) to track goals and progress in each sprint, a designer to create useful user interfaces and discuss research, data analysts to process and understand source data, subject-matter experts to understand the problem domain and business logic, infrastruture engineers to help the team deploy its software and practive DevOps. None of those skills are listed here - the analysts are financial quants from banks and the 2 designers were hired to work on a single website at GSA. There are certainly a lot of coders, but many of them are young and by all indications are used to working alone rather than as part of a team that has built a product.

In an extended interview with Planet Money, Sahil Lavingia reported essentially being given a laptop and occasional instructions by Steve Davis, but there was no coordination with DOGE as a whole or even other DOGE engineers at the VA. When he attended a monthly all-hands, he reported that Elon just used the opportunity to complain about government and not provide the direction he was hoping for:

I was expecting, like, a lot more of a plan of attack, like a sort of war room where we’re like, this is what we’re trying to get done. This is where we’ve failed. This is where we’ve succeeded. You know, a little bit more of, like, a team effort.

Of course, DOGE could possibly have partnered with existing agency staff for this work, in which case looking just at the DOGE staffing alone would be highly misleading. But the record suggests they usually have not. 18F wrote the definitive guide to building agile software in government; DOGE’s answer was to fire them all. At Social Security, rather than lean on subject matter experts for help, DOGE CIO Mike Russo declared that he could not trust civil servants and farmed out the task to Akash Bobba. If you didn’t write code and you weren’t loyal to Elon Musk, you weren’t valuable to DOGE.