Too Many Chiefs? Do We Need to Change the Way We Govern Our Federal Government Support Operations?
By Patricia E. Healy, CGFM
Patricia E. Healy, CGFM, is an executive consultant at CGI Federal. She recently retired after serving almost nine years as deputy CFO of the U.S. Department of Agriculture. She is a fellow of the National Academy of Public Administration.
I recently retired from the federal government having most recently served as the deputy chief financial officer of the U.S. Department of Agriculture. Before I left, many of us were already discussing the upcoming transition to a new administration. Since I left, I have been part of or attended forums sponsored by the Council for Excellence in Government, the National Academy of Public Administration and others intended to examine where we have been, where we need to go and how best to represent this to the new administration.
In these forums, or accompanying hallway conversations, participants begin to reflect on the role of the Chief Financial Officers Act of 1990 in reforming financial management in the federal government. Invariably this leads to a discussion of the role of the chief financial officer (CFO) in our agencies and whether the CFO is now only focused on compliance issues (such as financial statements, internal controls) and not enough on supporting overall agency program objectives. These conversations are important, as it is always good to engage in self-examination and to respond to the ever-changing, evolving environment of the federal government. However, rather than focus solely on the role of the CFO, I wonder if we might not need to take a larger view of how we govern our support infrastructure in the federal government.
Since 1990, we have seen the emergence of chief financial officers, chief information officers, chief technology officers, chief human capital officers, chief acquisition officers and chief performance officers. They all represent infrastructure operations intended to efficiently and effectively support program mission. Yet in most cases, these operations are by law, regulation or past practice, stovepipe functions tasked with compliance objectives of their own. They are funded by ever-decreasing discretionary dollars, and compete for these dollars among themselves and with agency mission programs funded from discretionary accounts. This can create an atmosphere where the efficiency and effectiveness of the overall agency operations, infrastructure and programs, are not being addressed. Further, opportunities to leverage funds and staff resources across functional areas to solve common problems are often lost. There is no single executive in charge of the entire enterprise infrastructure, one who can view operations holistically and facilitate solutions and set the priorities across the enterprise.
So given this reality of the federal government management condition, how can we manage effectively and efficiently for strategic outcomes across multiple functions and “chiefs”? Peter Weill of the Massachusetts Institute of Technology, in his book (with Jeanne W. Ross) entitled IT Governance: How Top Performers Manage IT Decision Rights for Superior Results, reported on a study of more than 250 large global organizations and found that top-performing organizations succeed where others fail by implementing effective IT governance. My experience, and that of my colleagues here at CGI, has shown that governance functions such as effective and recurring planning, structured steering and operating committees across multiple chiefs, clear division of roles and responsibilities, and rigorous processes and monitoring lead to increased performance, accountability and control of business and IT functions.
What has your experience been in regard to successfully navigating cross-domain collaboration for strategic results? What practices have you seen work?
MONDAY: Sheila Weinberg, Truth in Accounting, on "Running Deficits When Your Balance is Balanced"
Questions on posting comments or wish to subscribe to the feed that sends blogs right to your e-mail? Find instructions here. Want to be our guest on the Blog? Contact Marie Force, AGA communications director, at mforce@cox.net.