This column was originally published on Jeff Neal’s blog, ChiefHRO.com, and was republished here with permission from the author.
The short answer is yes. But there is a lot more to it than that, so let’s take a look at what artificial intelligence (AI) may do to and for the federal workforce. There is a lot of talk about the coming wave of AI (like the previous coming waves of AI) and how it will finally revolutionize virtually everything. Lots of AI hype frequently means lots of gloom and doom about a dystopian future, or glowing stories about an idyllic dream world driven by technology. I prefer to look at what the reality of today is telling us, and for the most part, at least with respect to the federal workforce, it is not bad.
As our use of technology has grown, and the capabilities of technology have accelerated, we have started to see some of the benefits of AI in many types of work. Technology can allow knowledge workers to devote more time to the substance of their work and less to administrative details. For example, an ICF analysis of data for the state of Colorado found that “Of the 15 task categories studied, time study participants spent the highest percentage of time (38 percent) on documentation and administration.” The obvious outcome of the study was the need for more people, but it also identifies areas that are ripe for better use of technology. Other areas where we are already seeing use of basic AI are help desks. Most of us have probably called a service provider and had the call answered by a computer rather than a human. A few years ago, such calls could be maddening. Now they are becoming more usable and more useful. I made such a call yesterday, and although my immediate reaction to talking with a bot was to get irritated, the system quickly identified what I needed and I was off the phone faster than I might have been otherwise. In that case, it was most likely a good rules-based bot. As AI-based bots become more common, we should expect more and more routine customer service interactions to be with technology rather than people.
Other uses of AI include law enforcement. Facial recognition, analysis of financial data from multiple sources, increased use of sensors to detect movement in remote areas, and use of sensors in general have the potential to revolutionize law enforcement. Imagine walking through a screening line in an airport, bags in hand, and stopping only if the AI detects an anomaly. While that sounds like science fiction (the movie, “Total Recall” to be specific), it is actually a combination of sensors, biometrics (such as facial recognition) and AI that is finally beginning to come to market. There are countless other ways that AI can be used in government, including border security (a “wall” of sensors and AI rather than a conventional barrier), medicine, research, and reducing the need for human interaction to obtain information.
Insight by GitLab: During this webinar executives from the State Department, U.S. Securities and Exchange Commission, U.S. Patent and Trademark Office and GitLab will discuss how institutionalizing a DevSecOps approach to software development is a journey that must bring together the technology and business sides to change an organization’s culture.
So what does that mean for the federal workforce? Should we automate as much of the federal workforce as possible out of existence? That is a potential outcome, but it is not the most likely or the best. If we look at the history of adoption of technology, we find the disappearance of one type of job leads to the emergence of others. For example, if we go back 50 or 60 years and look at a typical federal office, we would find row after row of clerks. In fact, during the 1950s, the federal government employed more than a million of them. Those jobs were mostly automated out of existence. By 2014, the number was down to 123,000. In 2018, the number is down to 106,000. So, a million federal jobs went away and the government workforce shrank by a million? No. In the 1950s we had about 1.8 million federal employees. Today we have 2.08 million. We lost over 900,000 jobs, mostly due to technology, but the workforce did not shrink.
What happened is a combination of forces that kept the workforce stable as technology changes might have enabled it to shrink, First, federal jobs are important to members of Congress. They do not want to be the ones who did away with jobs in their districts. Second, the population served by the government grew by 86 percent. Third, demand for government services increased. During the 1950s, there was no Medicare. There was no Environmental Protection Agency, or Department of Energy, or Education, or many other federal programs that people have come to expect. Clerical workers were replaced with knowledge workers. Now we are seeing knowledge workers beginning to be supplemented with or replaced by AI.
So what will be the effect of the coming wave of AI? Shrinking government? Overly intrusive and powerful government? Or a better government that is able to accomplish far more than it can today? Maybe all of those? Let’s take a look at a few of those options.
Cut, Cut, Cut. Nope. The size of the federal workforce is remarkably stable. The Vietnam War did not cause tremendous growth in the workforce. Ending the war did not cause big drops. The Defense buildup during President Reagan’s Administration was offset by reductions in the nondefense workforce. The opposite happened after the end of the Cold War. Even though we read a lot about the Trump Administration shrinking the government, the reality is that at the end of the Obama Administration we had 2,093,868 federal employees and at the end of March 2018 (the most recent data available from OPM’s FedScope) we had 2,075,006. That is a reduction of only 0.9 percent. Surveys of the U.S. population show widespread support for most federal agencies and the work they do. The only mission area that gets less than a 50 percent approval rating is foreign aid. Politicians may like to criticize government, but they have not shown a big appetite for cutting it. Public approval of government programs and agencies, combined with the jobs they create, make wholesale AI-driven reductions in the workforce unlikely. What is more likely is that money will be shifted to other uses and the workforce will stay within a few percent of where it is now (and has been for 60 years).
Big Brother is Watching. The jury is still out on this one. The tension between advocates for civil liberty and privacy on one hand, and advocates for security on the other, is growing. Do we want facial recognition tech to be able to detect potential terrorists? Or criminals? Of course we do. Do we want the same tech following us around and amassing data on every move we make? Probably not. This one will take years to reach some level of balance that is acceptable to the American people. It is ironic is that we generally do not want the government intruding into our business, but we routinely post our every move on Facebook, Instagram, Twitter and other social media platforms. And those platforms use that information to sell us advertising and market the data to others for advertising, political campaigns, and more.
The Sky’s the Limit. I believe the more desirable outcome is to use AI to greatly improve services to the people. If we use the example of understaffed organizations who employees spend too much of their time on administrative tasks, the goal is not to cut jobs, but to enable that staff to accomplish the mission by letting the systems handle the routine or administrative work. It is not a sexy way of looking at AI, but it is a way that we can enhance the capabilities of government without increasing the cost. There is far more that can be done. Analysis of more and more data by AI may mean the Transportation Security Adminstration can offer superb security with virtually no intrusion or delays. It may mean that Customs and Border Protection can provide a far less permeable border without resorting to physical barriers and with fewer Border Patrol Agents put in harm’s way. It may mean safer food and medicine though analysis of data from various sources and in ways that we cannot do with people. It might mean consulting an AI virtual physician for a diagnosis rather than driving to a VA hospital. It might mean combining AI with virtual reality to deliver training that is responsive to the learner in ways conventional training is not. We could spend a month imagining the possibilities and only scratch the surface. It might even mean that Siri could dial a phone number for me without saying, “I’m sorry Jeff, I don’t understand.” But maybe I should not hold out hope for that one …
So how do we get to that version of the future? We could start by viewing AI as an opportunity to improve capabilities and services, rather than to cut costs. One of the obstacles to the adoption of technology has always been the fear that it might cost someone a job. We should just accept reality and move in that direction in a way that helps workers learn new skills for the changing world of work. The truth is that work has been evolving from the beginning of civilization and it will continue to evolve. Will some jobs go away? Absolutely. But they can and will be replaced with other jobs.
We also have to break our ties to the way things are today. The blinders placed on us by what we see today are among the greatest enemies of progress. We look at how work is done and view the future through that lens and let our decision-making be bound by it. The better approach is to look at what we want to accomplish, rather than how we might change what we are doing today. That means we should not delegate the design of the future to the stovepipes of today. Self-perpetuating stovepipes typically try to preserve their power, their numbers, and their existence.
The answer to the question: “Will AI replace many federal workers?” is definitely yes, it will. But it will also open up more opportunities for work in government, and it is likely to make government far more effective and able to serve the American people in a more personal way.
Jeff Neal is a senior vice president for ICF and founder of the blog, ChiefHRO.com. Before coming to ICF, Neal was the chief human capital officer at the Homeland Security Department and the chief human resources officer at the Defense Logistics Agency.