Analysis: New guidance creates contracting conundrum

In the span of just two days last week, three government offices issued advice about improving the $550 billion per year federal procurement system long plagued by waste and inefficiency.

On Sept. 14, the Office of Management and Budget outlined in a memo ideas about how to "save money, reduce risk and get better results" from government contracts. On the same day, the Defense Department released guidance for "obtaining greater efficiency and productivity in defense spending." On Sept. 15, a presidential task force published its recommendations for improving federal contracting opportunities for small businesses.

The flurry of top-level attention is a welcome sign that the Obama administration is serious about reforming procurement at a time of fiscal constraint and budget deficits.

But the recent directives also unintentionally underscore the immediate need for better coordination among agencies and a more coherent reform agenda. Examined side by side, they reveal conflicting guidance that could sow even more confusion in a world so complex it vexes the most sophisticated lawyers and accountants. "The rule set becomes further confusing through these many efforts, and makes me worry what exactly will be the 'real' rules as those leading these initiatives depart and new ones arrive," former Air Force Secretary Michael Wynne said in an interview.

Consider, for example, last week's guidance about how the government should go about finding the best vendors and suppliers. The OMB memo recommended "pooling the federal government's buying power" in pursuit of strategic sourcing. The president's small business task force, on the other hand, urged "strategies to prevent unjustified contract bundling," or aggregating in one contract supplies or services "previously provided or performed under separate smaller contracts."

So what should a procurement official do? Create efficiencies and drive cost savings through pooling, or create more opportunities for small business by eschewing bundling?

To be sure, there could be scenarios in which these two policies actually can complement each other, but that's not necessarily self-evident to procurement officers and others involved in government contracts on a day-to-day basis.

There are other potential conflicts in the directives. All three documents urge data standardization, for example. But the small business task force focuses on a coding system called the North American Industry Classification System while the Defense memo prefers the Product Service Code. And there are other standards out there, such as the United Nations Standard Products and Services Code used in two governmentwide systems. The documents' diverging guidance on competition and contract types also could confound government contracting officers.

To avoid such confusion there must be better coordination among the offices entrusted with the important work of reducing costs and eliminating waste in federal acquisitions. Here are some suggestions:

  • Governmentwide procurement reform should be centrally coordinated, preferably at OMB. That doesn't mean every initiative must be run from the White House, but there should be enough central oversight to identify and address potential conflicts.
  • The implementation of reform initiatives should be formally designed with other efforts in mind. "With the plethora of rules that govern the procurement system, it is important that we provide adequate implementation guidance to avoid creating more confusion on the part of the workforce," says Steven Kelman, a public policy professor at Harvard University's John F. Kennedy School of Government and a former administrator of the Office of Federal Procurement Policy.
  • The reform must speak in a unified voice. Ultimately, the success of these initiatives rests in the hands of thousands of government professionals, as well as the vendor community. Leadership across all agencies must commit to and deliver the same message with as little ambiguity as possible.

These communication problems are not insoluble, but left unaddressed they could hamper the administration's admirable and intense focus on improving procurement. The stars do seem to be aligned, for the first time in years, in support of meaningful reform. We must not miss this opportunity.

Raj Sharma is a visiting fellow at the Center for American Progress who focuses on improving government procurement and supply chain management practices.

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 Brocade

    Best of 2016 Federal Forum eBook

    Earlier this summer, Federal and tech industry leaders convened to talk security, machine learning, network modernization, DevOps, and much more at the 2016 Federal Forum. This eBook includes a useful summary highlighting the best content shared at the 2016 Federal Forum to help agencies modernize their network infrastructure.

  • Sponsored by CDW-G

    GBC Flash Poll Series: Merger & Acquisitions

    Download this GBC Flash Poll to learn more about federal perspectives on the impact of industry consolidation.

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

    A DevOps Roadmap for the Federal Government

    This GBC Report discusses how DevOps is steadily gaining traction among some of government's leading IT developers and agencies.

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

  • Sponsored by CDW-G

    Joint Enterprise Licensing Agreements

    Read this eBook to learn how defense agencies can achieve savings and efficiencies with an Enterprise Software Agreement.

  • Sponsored by Cloudera

    Government Forum Content Library

    Get all the essential resources needed for effective technology strategies in the federal landscape.


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