The Need for Greater Technical Talent in the Government: A Case Study | Belfer Center for Science and International Affairs
We know government tech projects often fail. Timelines get pushed out, contractors rapidly turn over, costs increase, and, ultimately, public services fail to meet the needs of the American people—often just as they need them most. One of the major reasons for these problems is that the federal government does not have the modern technical talent necessary to deliver large-scale IT programs that consistently work for the end user. This does not just include software engineers, but designers, researchers, and product managers too. In this case study, we’ll look at this issue through the lens of one of the most storied federal IT programs—the U.S. Citizen and Immigration Services (USCIS) Electronic Immigration System (ELIS). We found that the program had challenges with its technical talent through the burdensome, nontechnical oversight and the lack of technical expertise on the ground. This case study pulls information from 13 GAO and OIG reports between 2005 and 2021, as well as interviews with 6 current or former senior leaders within USCIS, with a particular focus towards the technical talent associated with the project.
Lessons from the software behind America’s immigration system show us why modern technologists, from product managers to designers, are needed in government now more than ever. We know government tech projects often fail . Timelines get pushed out, contractors rapidly turn over, costs increase, and, ultimately, public services fail to meet the needs of the American people—often just as they need them most. One of the major reasons for these problems is that the federal government does not have the modern technical talent necessary to deliver large-scale IT programs that consistently work for t
Explore this link on the map →related reading
- How government can succeed in the digital age, with Jennifer Pahlka - Niskanen Centerniskanencenter.org
- Government tech projects fail by default. It doesn’t have to be this way. | The Belfer Center for Science and International Affairsbelfercenter.org
- ArriveCAN Was a Fiasco—and Just the Tip of Ottawa’s Failing Tech Strategy | The Walrusthewalrus.ca
- Culture eats policy - Niskanen Centerniskanencenter.org
- It's Time to Govern — Letters to a Young Technologistletterstoayoungtechnologist.com
- Home | Levers for Progressleversforprogress.com
- How to Attract the Next Generation of Civic Technologistsgovtech.com
- Bringing Elon to a knife fight - by Jennifer Pahlkaeatingpolicy.com
- Why I quit working at an AI startup to join the Department of Energycharlesyang.substack.com
- ‘Two hands are a lot’ — we’re hiring data scientists, project managers, policy experts, assorted weirdos… – Dominic Cummings's Blogdominiccummings.com
- 20180904 ARPA PARC paper.pagesdominiccummings.files.wordpress.com
- How I ship projects at big tech companiesseangoedecke.com