The Real Impact

March 1 was the day that the unthinkable became the inevitable, followed shortly by settling into the routine. It was the Day of Sequestration. 

On that day, $85 billion in federal spending was eliminated in one great across-the-board swoop. It was, as President Obama reminded Americans multiple times in January and February, the Policy That Was Never Supposed to Be Implemented. What was designed to be so unappealing that members of Congress and the administration would never allow it to go into effect had ended up setting off one great national shrug of the shoulders. 

And as another funding deadline loomed at the end of March, here’s what people were talking about: whether President Obama had overplayed his hand politically (pull that aircraft carrier back from the Persian Gulf!), the extent to which cuts actually would be felt by Americans (get ready for long lines at airports!) and, a distant third, the impact the sequester would have on federal employees facing furloughs (enjoy your unpaid time off!).

But here’s what wasn’t talked about much at all: The overall effect of implementing a sequester on the operations of government. Because that’s rarely part of the conversation.

If the discussion were to take place, it would have to start with acknowledging a dirty little secret: Government probably can absorb $85 billion in cuts without widespread ill effects on people other than its own employees. It wouldn’t be easy, or painless, but a genuine  exercise in identifying areas to cut or put off new spending could identify savings. Better yet, political leaders could sit down and have a serious conversation about what programs we simply must live without until our fiscal house is in order.

That’s unlikely to happen. Instead, the nation’s political leaders dumped an order on agencies that called for sweeping cuts and offered vague instructions about how to implement it. Federal managers then commenced spending large amounts of time figuring out what to do. They started negotiating with labor unions over every aspect of furloughs. They began determining what an across-the-board cut in “programs, projects and activities” actually means-—since it’s never been tried on this scale before. And they faced the prospect of addressing uncertainty across virtually the entire federal workforce.

Let’s be clear: None of this will add value for taxpayers. It will just be a long, complicated exercise in making the best of a ridiculous situation. That’s true whether or not you think government can afford to take an $85 billion hit.

In February, the Government Accountability Office released its high-risk list of federal programs. As usual, while a few items were dropped from the list (with almost no fanfare), new problems, such as dealing with the effects of climate change, were added. Can agencies expect to tackle them while absorbing across-the-board cuts? Not really.

However the exercise of implementing a sequester plays out, it’s almost guaranteed to result in the kind of vicious cycle that is all too common in Washington. As projects get put on hold or fall behind schedule, agencies will be subject to criticism from their overseers on Capitol Hill that they’re not getting the job done in an efficient and effective manner.

It’s hard not to view this as an absurd win-win for lawmakers: They get to create the circumstances under which it is very difficult for agencies to succeed, then hold hearings to spout righteous indignation when they fail. 

The real losers in this scenario aren’t just the federal employees and managers who try to run the programs. It’s the Americans who pay for them. 

Stay up-to-date with federal news alerts and analysis — Sign up for GovExec's email newsletters.
Close [ x ] More from GovExec

Thank you for subscribing to newsletters from
We think these reports might interest you:

  • Sponsored by G Suite

    Cross-Agency Teamwork, Anytime and Anywhere

    Dan McCrae, director of IT service delivery division, National Oceanic and Atmospheric Administration (NOAA)

  • Data-Centric Security vs. Database-Level Security

    Database-level encryption had its origins in the 1990s and early 2000s in response to very basic risks which largely revolved around the theft of servers, backup tapes and other physical-layer assets. As noted in Verizon’s 2014, Data Breach Investigations Report (DBIR)1, threats today are far more advanced and dangerous.

  • Federal IT Applications: Assessing Government's Core Drivers

    In order to better understand the current state of external and internal-facing agency workplace applications, Government Business Council (GBC) and Riverbed undertook an in-depth research study of federal employees. Overall, survey findings indicate that federal IT applications still face a gamut of challenges with regard to quality, reliability, and performance management.

  • PIV- I And Multifactor Authentication: The Best Defense for Federal Government Contractors

    This white paper explores NIST SP 800-171 and why compliance is critical to federal government contractors, especially those that work with the Department of Defense, as well as how leveraging PIV-I credentialing with multifactor authentication can be used as a defense against cyberattacks

  • Toward A More Innovative Government

    This research study aims to understand how state and local leaders regard their agency’s innovation efforts and what they are doing to overcome the challenges they face in successfully implementing these efforts.

  • From Volume to Value: UK’s NHS Digital Provides U.S. Healthcare Agencies A Roadmap For Value-Based Payment Models

    The U.S. healthcare industry is rapidly moving away from traditional fee-for-service models and towards value-based purchasing that reimburses physicians for quality of care in place of frequency of care.

  • GBC Flash Poll: Is Your Agency Safe?

    Federal leaders weigh in on the state of information security


When you download a report, your information may be shared with the underwriters of that document.