Promising Practices Promising PracticesPromising Practices
A forum for government's best ideas and most innovative leaders.

The 7 Essentials of Cross-Agency Collaboration

ARCHIVES
Image via Michael D Brown/Shutterstock.com

How do you organize a cross-agency collaborative effort to get results no single agency could accomplish on its own?  The Government Accountability Office (GAO) has developed an inventory of “mechanisms that the federal government uses to lead and implement interagency collaboration,” along with a self-assessment checklist to consider when using them.

GAO’s latest study on collaborative governance is based on an analysis of more than 300 past GAO reports covering issues such as homeland security, agriculture, and health, as well as a series of interviews with experts on the topic.

GAO previously reported in 2005 on eight “key practices to enhance and sustain interagency collaboration,” including leadership, trust, and organizational culture. That report lays out how network managers should behave. But it was largely silent on the structural mechanisms for organizing such collaborative efforts.  In 2010, a new law requires the Office of Management and Budget (OMB) to develop and implement cross-agency priority goals that rely on a great degree of collaboration.  These more formal collaborations require mechanisms for accountability, measures of progress, and resource sharing.  This spurred congressional interest in understanding more about various mechanisms that the executive branch might use.

OMB identified 14 cross agency priority goals in the 2013 budget and has begun to implement them. These include goals such as doubling exports, which involves more than eight contributing agencies and over 40 programs within these agencies; and improving cybersecurity, which involves virtually every agency in the government. How should the executive branch best organize these agencies and programs to achieve results?

The new GAO report catalogs a dozen specific mechanisms the government currently uses to collaborate across boundaries, ranging from special presidential assistants to the use of social media technologies. More significantly, the report offers a self-assessment checklist (Appendix III) of seven key design features that collaborative network leaders need to consider when using these approaches. These features include:

  1. Outcomes and Accountability: Have short-term and long-term outcomes been clearly defined? Is there a way to track and monitor their progress?
  2. Bridging Organizational Cultures: What are the missions and organizational cultures of the participating agencies? Have agencies agreed on common terminology and definitions?
  3. Leadership: How will leadership be sustained over the long-term? If leadership is shared, have roles and responsibilities been clearly identified and agreed upon?
  4. Clarity of Roles and Responsibilities: Have participating agencies clarified roles and responsibilities?
  5. Participants: Have all relevant participants been included? Do they have the ability to commit resources for their agency?
  6. Resources: How will the collaborative mechanism be funded and staffed? Have online collaboration tools been developed?
  7. Written Guidance and Agreements: If appropriate, have participating agencies documented their agreement regarding how they will be collaborating? Have they developed ways to continually update and monitor these agreements?

The GAO report also provides concrete examples of the various collaborative mechanisms it has cataloged, ranging from the federal government’s climate change activities, to the use of working capital funds, to the federal response in 2007 to the pandemic flu scare.  It also describes how some collaborative mechanisms are used for various purposes, such as policy development, program implementation, oversight, and information sharing.

Interestingly, in a recent blog post, my colleague Dan Chenok notes that effective collaboration in networks used to implement results-oriented initiatives should rely on more than just practices and mechanisms.  He says that government leaders should move beyond collaboration to “joint management.”  He observes that “successful leaders in government can follow the enterprise model of the private sector, using technology and information to manage ‘jointly’ across agencies – building from collaborative networks to shared operations.”

What things have you found essential for cross-agency collaboration? 

(Image via Michael D. Brown/Shutterstock.com)

John M. Kamensky is a Senior Research Fellow for the IBM Center for the Business of Government. He previously served as deputy director of Vice President Gore's National Partnership for Reinventing Government, a special assistant at the Office of Management and Budget, and as an assistant director at the Government Accountability Office. He is a fellow of the National Academy of Public Administration and received a Masters in Public Affairs from the Lyndon B. Johnson School of Public Affairs at the University of Texas at Austin.

FROM OUR SPONSORS
JOIN THE DISCUSSION
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)

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

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

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

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

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

    Download
  • GBC Flash Poll: Is Your Agency Safe?

    Federal leaders weigh in on the state of information security

    Download

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