Janine Wedel's "Shadow Elite"--particularly her chapter on "U.S. Government, Inc."-- struck a familiar chord with me. She writes that our national and public interests risk being sold out because core government functions like running intelligence operations, controlling homeland security databases, and managing federal taxpayer monies doled out under the stimulus plans and bailouts are being outsourced to private contractors. Contracting is rampant: Today three-quarters of people working for the U.S. government are not government employees but private contractors. And it is no longer just printing and cleaning and food services that are being contracted out; it is the primary work of government.
Working for the last 17 years in information technology organizations for Missouri state government, I have seen a similarly alarming (and growing) trend on the state level. Over 25 years, as an information systems developer, manager, and administrator in both state and private organizations, I have increasingly come to the conclusion that we are putting our state's operations at risk and compromising the trust of the people of our state by outsourcing core government functions. And outsourcing does not come cheaply.
Let me explain from inside the world of IT. You might think that IT is one of those things like food services that can be easily spun off. Not so. When we talk about information systems and IT, we are not just speaking of geek technology. We are talking about the detailed mapping of an agency's operations into data and automated processes, which then embody and implement the functions of government. Information systems--encompassing software development, maintenance, and operations--hold the government's data, as well as the rules applied to that data and the business processes that make up government functions and services. These systems are also the source for most decision-making reports and analyses that guide decisions (other than those driven by politics or other power struggles). Almost always the analysts, designers, and programmers responsible for the software know the organization's business operations better than anyone else in the organization. When the IT function is outsourced, governments are put at risk. And so is the public's interest.
Here's why. In many of our agencies, at least one key software system was developed by an external organization with little substantial involvement from the state's IT staff. Once these systems are in place, there may be no one in the state's IT organization who knows the system well enough to maintain it. Thus I've witnessed, with alarm, such instances as these:
Amazingly, Missouri was one of only three states given an “A” in management of information by Governing Magazine in their 2008 state rankings, so one can imagine the situation in most other states. Missouri’s current IT leaders have indicated some intent to rely more on in-house IT staff and are making other attempts to improve control of IT systems. In addition, Missouri has often been fortunate to work with reliable IT contractors who employ local people, including some who have been state employees for part of their career, so the expertise stays “local” and some loyalty to the state may be preserved. But, if outsourcing expands or if different contractors are chosen, our current good fortune may end.
Tight budgets and political forces are driving Missouri and other state governments toward operating in an emergency mode and we respond by privatizing more government work. As illustrated by the examples given here, an increasing number of the people performing IT work are not state employees and therefore do not possess the unique knowledge of government functions and data and do not have the same priorities and loyalties. In the long run, this can't help but undermine the integrity and reliability of our government.