Business Sense

Maybe Defense's deputy chief management officer can reverse unproductive reforms

David M. Walker has left the building, but his ideas for managing the Defense Department live on. As comptroller general and head of the Government Accountability Office, Walker regularly called for the appointment of a chief management officer to oversee Defense's business affairs. Now the fiscal 2008 National Defense Authorization Act has mandated the appointment of a deputy chief management officer for the department. Operating at the undersecretary level, the deputy CMO would advise the deputy secretary (the CMO) and other Defense leaders on ways to improve business operations.

Those operations include human resources, acquisition, real property and installations, logistics, and financial and information management. Reform efforts aimed at those activities began with the Defense Management Review in the 1980s, followed by acquisition reform and the Defense Reform Initiative in the 1990s, and continue today with the Business Transformation Agency effort that started in 2001. After almost 20 years, however, the major improvements long promised still have not been realized. Congress is unhappy with the rate of change and believes that establishing a full-time senior executive post accountable for results is the only way to achieve results.

Like the current legislation, the 1990 Chief Financial Officers Act and the 1996 Clinger-Cohen Act were enacted in response to GAO recommendations. Both laws called for the establishment of chief officers and required them to take specific steps to achieve business reforms. The chief financial officer would work toward auditable external financial statements and the chief information officer would set up an integrated information technology architecture to support the production of such statements at a reasonable cost.

The result has been the never-ending development of business enterprise architectures, which has done nothing to improve operations. To make matters worse, it never will-even if Defense were to achieve CFO Act compliance. Unlike profit-seeking businesses in a competitive marketplace whose ability to attract capital depends on their production of auditable financial statements, Defense's business activities are publicly funded, nonprofit government operations that rely on annual appropriations from Congress. And Congress' decisions about those activities never will depend on the kind of financial information that the CFO Act calls for.

The private-sector-style financial statements the CFO Act requires provide three kinds of information: what a business is worth, its income and its cash flow. None of that has anything to do with Defense's business activities because they aren't bought or sold, they don't exist to make profits, and they don't rely on cash to pay their bills (they use obligation authority from approved budgets to do that).

The one external financial report required by the CFO Act that does make sense is the annual statement of budgetary resources. That report tells Congress whether obligations were made in accordance with authorization legislation. But that kind of financial accountability is no different from the accountability called for almost 90 years ago by the 1921 Budget and Accounting Act. Thus, what is helpful in the CFO Act (the requirement for audited statements of budgetary resources) is not new, and what is new (the requirement for audited private-sector-style financial statements) is not helpful.

This is not to say Defense doesn't need better accounting. Textbooks make a clear distinction, however, between financial accounting-which serves external decision-makers such as stockholders, investors and creditors-and managerial cost accounting, which serves internal decision-makers such as managers. The Defense Department needs better managerial cost accounting, not financial accounting. Yet the comptroller's office, the Defense Finance and Accounting Service, and the department's new Business Transformation Agency have been unable to focus on managerial cost accounting because they've been required to build financial accounting systems.

But systems able to meet external reporting requirements are inadequate for "estimating the costs of activities and business processes" or for "providing useful feedback to improve business processes," writes Robert S. Kaplan of Harvard Business School in Cost and Effect (Harvard Business School Press, 1997). Choices have had to be made, therefore, between complying with the financial accounting demands of the CFO Act and developing managerial cost accounting. So far, managerial cost accounting is losing.

If the new deputy CMO is going to have any chance to succeed, he or she must find a way to work with Congress to mitigate the unproductive requirements in the CFO Act. Fortunately, language in the 2008 authorization bill does not explicitly require CFO-style financial accountability. Rather, it calls for the deputy CMO to work with Defense leaders to make business operations more effective and efficient-and that means there is hope.

Christopher Hanks is a mathematician and defense analyst. He can be contacted at

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.

  • 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.