Speak No Evil

The only thing more dangerous in government than trying to convey bad news up the hierarchy is going public with it.

Nobody likes to be the bearer of bad news. But in the career federal service, the job comes with the territory. While higher-ups talk of dreams, visions and grand plans, career executives, managers and employees must deal with the hard work of implementation-and point out when objectives are based on faulty data, lack sufficient resources or simply will fail to achieve desired results.

That's never an easy task. But it's becoming more and more difficult, because across government, a shoot-the-messenger attitude is beginning to prevail when it comes to challenging the conventional wisdom. The trend has dangerous consequences.

The most prominent recent example involves intelligence about weapons of mass destruction programs in Saddam Hussein's Iraq.

In the January/February issue of our sister publication, The Atlantic Monthly, Kenneth M. Pollack, who served on the National Security Council in the Clinton administration, provides a detailed account of intelligence efforts to determine the nature of Iraq's WMD programs prior to last year's U.S.-led invasion of the country. The intelligence community, he admits, greatly overestimated Iraq's capability to develop and deploy such weapons- especially nuclear weapons. Indeed, such analysis led Pollack to write a book, The Threatening Storm: The Case for Invading Iraq (Random House, 2002).

But that wasn't the only problem. Throughout the spring and fall of 2002 and well into 2003, Pollack received numerous complaints from friends and colleagues about how Bush administration officials were dealing with intelligence that didn't conform to the party line. "According to them," Pollack writes, "many administration officials reacted strongly, negatively and aggressively when presented with information or analysis that contradicted what they already believed about Iraq."

Bush officials repeatedly asked intelligence analysts to justify their work, gave great credence to dubious sources and demanded extensive, time-consuming studies of extraneous reports, such as the writings of conservative newspaper columnists. The administration eventually set up an organization in the Pentagon, the Office of Special Plans, to conduct its own analyses of Iraq intelligence.

Congressional and CIA investigators have concluded that analysts did not alter any of their findings as a result of political pressure. Nevertheless, it seems clear that dissent from the party line was at least discouraged.

Likewise, the space shuttle Columbia Accident Investigation Board determined last year that NASA's "culture of bureaucratic accountability" put "allegiance to hierarchy and procedure" ahead of challenges to accepted conclusions by technical experts. After the foam-debris strike during the Columbia launch, engineers at several NASA centers "showed initiative and jumped on the problem without direction from above," the board found. But the engineers' request for imagery from the Defense Department to determine the extent of damage to the shuttle was turned down because they hadn't shown a "mandatory need" for the information and hadn't run their request through the proper channels.

"For those with lesser standing, the requirement for data was stringent and inhibiting, which resulted in information that warned of danger not being passed up the chain of command," the board concluded.

The only thing more dangerous in government than trying to convey bad news up the hierarchy is going public with it. Just ask Teresa Chambers, the Park Police chief suspended late last year for telling a Washington Post reporter that the agency didn't have the resources to do its job.

National Park Service Deputy Director Donald Murphy charged Chambers with a host of violations, including improper disclosure of budget deliberations, failure to carry out a supervisor's instructions and-the classic offense-not following the chain of command.

It's clear that the crux of the issue was not the substance of Chambers' remarks. Rather it was, as Murphy said in a voicemail to Chambers prior to her suspension, that "the messages that you are sending out are not consistent with the department's message and what we want to be saying on our budgeting for the U.S. Park Police."

It would be easy to point fingers and say the increasing lack of tolerance for dissent in government is the fault of the Bush administration's political leadership. But the problem has been building for years and-remember, in the case of NASA-the problems that stifled disagreement had little to do with politics and much to do with an organizational culture in which "failure is not an option."

In this era of ballooning budget deficits, increased media scrutiny and decreased public patience for poor performance by federal agencies, it takes a lot of courage to stand up and challenge the conventional wisdom. But if those in the career federal service are serious about their obligation to be public servants as well as civil servants, they must.

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 GovExec.com.
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.

  • Sponsored by One Identity

    One Nation Under Guard: Securing User Identities Across State and Local Government

    In 2016, the government can expect even more sophisticated threats on the horizon, making it all the more imperative that agencies enforce proper identity and access management (IAM) practices. In order to better measure the current state of IAM at the state and local level, Government Business Council (GBC) conducted an in-depth research study of state and local employees.

  • Sponsored by Aquilent

    The Next Federal Evolution of Cloud

    This GBC report explains the evolution of cloud computing in federal government, and provides an outlook for the future of the cloud in government IT.

  • Sponsored by LTC Partners, administrators of the Federal Long Term Care Insurance Program

    Approaching the Brink of Federal Retirement

    Approximately 10,000 baby boomers are reaching retirement age per day, and a growing number of federal employees are preparing themselves for the next chapter of their lives. Learn how to tackle the challenges that today's workforce faces in laying the groundwork for a smooth and secure retirement.

  • Sponsored by Hewlett Packard Enterprise

    Cyber Defense 101: Arming the Next Generation of Government Employees

    Read this issue brief to learn about the sector's most potent challenges in the new cyber landscape and how government organizations are building a robust, threat-aware infrastructure

  • Sponsored by Aquilent

    GBC Issue Brief: Cultivating Digital Services in the Federal Landscape

    Read this GBC issue brief to learn more about the current state of digital services in the government, and how key players are pushing enhancements towards a user-centric approach.


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