By Steve Kelman

Blog archive

Steve's peeve about a common contracting phrase

Regulation (Image: Shutterstock / Garagestock)

Ask yourself the following question: What is the adjective most commonly used to modify the phrase “government contracts” in mainstream-media articles?

The answer, I’m pretty sure, is “lucrative.” As in, “X company or individual won lucrative government contracts for…”

Pay attention to the next few times you see coverage of government contracts in the media. I’ll bet you that typically you will see the "L word." I don’t know how the use of this adjective spread so widely, but my impression is that this is a fairly recent development. (The Google Trends app, which allows one to track word usage in the media, allows disaggregation to the level of “government contracts,” but not “lucrative government contracts.”)

Many of us who actually deal with government procurement are likely to say, “Lucrative compared to what?” To be sure, contractors typically make money on their government contracts. But as those who know the business are aware, returns on government business are generally lower than on commercial business. The publically traded companies that report government and commercial sales separately typically report noticeably lower margins on government business.

In fact, one prominent reason commercial companies, particularly smaller tech firms, give for shunning government business is that margins are so low. And despite a common view that defense contractors regularly take government to the cleaners, weapons systems margins are very modest, especially on cost-plus development contracts and fixed-price sole source production contracts. (Though, to balance this, the risks in defense business, once one has won a contract, are much lower than in the commercial world.)

So the attachment of the adjective "lucrative" to the noun” government contracts” is a pet peeve of mine -- it bothers me every time I see it.

I believe we as a community should care about this characterization. Words have meaning, creating (often unconsciously) certain associations or reactions. If what comes into a person’s mind when they hear “government contract” is “lucrative,” that person is likely to be suspicious or even hostile to contractors and contracting.

If we think about the balance in good government contract management between oversight and cooperation, the word lucrative will nudge people in the direction of thinking contractors need more oversight. By contrast, if the word that comes to mind is “competitive,” the reaction to contracting is likely to be favorable, and the need for oversight diminished. When we battle for what adjective is used to describe government contracts, we are battling for people’s brains.

When I teach performance measurement at the Kennedy School, I discuss early on two different words that might come to a government official’s mind when they hear the phrase “performance measurement.” One is “accountability,” the other is “performance improvement.”

I argue that if federal managers first think of accountability when they hear the phrase "performance measurement," their reaction is likely to be negative -- performance measurement is about punishing them or their organization for falling short. "I may realize I need to do it," the thinking goes, "but I am likely to try to keep this as far away from me as possible."

On the other hand, if what comes to mind is performance improvement, managers are likely to embrace this. So in arguing for an association of performance measurement with performance improvement, I am fighting to give people a positive association with the concept, not a negative one.

The fight against the word lucrative is similar.

The problem is that we have only limited influence over the associations people make with a word like “government contract.” But we can be aware of, and discuss in public contexts and with our employees, the negative associations that come with that word “lucrative.”

We have just started a new fiscal year. I suggest contracting officials make a new year's resolution: To organize conversations at their workplaces around this word – and any other dysfunctional terms out there regarding contracting that our community needs to take on.

Posted by Steve Kelman on Oct 02, 2018 at 6:51 AM


Featured

  • Contracting
    8 prototypes of the border walls as tweeted by CBP San Diego

    DHS contractors face protests – on the streets

    Tech companies are facing protests internally from workers and externally from activists about doing for government amid controversial policies like "zero tolerance" for illegal immigration.

  • Workforce
    By Mark Van Scyoc Royalty-free stock photo ID: 285175268

    At OPM, Weichert pushes direct hire, pay agent changes

    Margaret Weichert, now acting director of the Office of Personnel Management, is clearing agencies to make direct hires in IT, cyber and other tech fields and is changing pay for specialized occupations.

  • Cloud
    Shutterstock ID ID: 222190471 By wk1003mike

    IBM protests JEDI cloud deal

    As the deadline to submit bids on the Pentagon's $10 billion, 10-year warfighter cloud deal draws near, IBM announced a legal protest.

Stay Connected

FCW Update

Sign up for our newsletter.

I agree to this site's Privacy Policy.