Identifying and managing troubled projects

team of attentive businesspeople

We all have troubled projects that are at risk of not achieving their expected business outcomes. These watermelon projects, which appear green on our project dashboards but are actually red if we dig deeper, are all too common in agencies' project portfolios.

CEB research shows that as many as 30 percent of projects in an average portfolio are troubled at some point during their life cycles. Some 20 percent of projects eventually fail, wasting significant time and money without delivering expected benefits to the agency or the public. Even more disconcerting is the fact that 20 percent of organizations don't know whether they have troubled projects. (It is fairly safe to assume that they do.)

In government agencies, troubled projects typically arise for three reasons:

  • Inadequate metrics. Project management offices typically base their assessments of project health on schedule- and budget-related metrics, but those metrics are lagging indicators that do not allow PMOs to spot problems proactively. Consequently, nearly three-quarters of PMOs report that more than 20 percent of their healthy projects actually conceal problems.
  • Cultural barriers that discourage escalation. Many project managers and members of project teams hesitate to escalate identified problems for fear of career repercussions. The result is an environment with low team morale, disengaged sponsors and stakeholders, recurring renegotiation of deadlines or expectations, and brewing tension between project teams and sponsors.
  • Strained communications between permanent and contractor staff. Agencies often have the added challenge of managing troubled projects with internal and external contractor-based teams. Differing objectives and management approaches generate significant challenges to effective collaboration across internal staff and contractor lines.

Our research with PMOs across industries suggests that more effective management of troubled projects can save organizations up to 8 percent of total annual portfolio spending. The most progressive organizations realize that early problem identification and escalation are among the best ways to bridge the gap between expected and actual project returns. And they use three key risk-mitigation techniques:

  1. Look beyond traditional project metrics to help identify trouble early. The best PMOs define a set of qualitative leading indicators of project issues and use them to identify troubled projects that would otherwise appear to be healthy. Those leading indicators generally fall into common categories -- for instance, stakeholder engagement issues, such as sponsors who are dismissive of project risks or stakeholders who are missing project team meetings and sending delegates instead.
  2. Remove cultural barriers that discourage escalation. The best PMOs work hard to create an environment where it is safe for project managers to raise issues without blame or personal attack. They educate sponsors and other executives on how to constructively participate in project review sessions, and create an independent communication channel to allow all project stakeholders to voice their concerns without fear of retribution.
  3. Expand the trouble-sensing network. Identifying and fixing troubled projects are not solely the responsibility of a project manager or PMO. The best PMOs work to expand their network for sensing trouble to include project team members, sponsors and other key stakeholders. They provide sponsors with training on how to spot potential problems and create mechanisms that allow the broader set of stakeholders to register their concerns.

Effective strategies to mitigate troubled projects can significantly expedite fixes that typically occur late in the project, increasing the likelihood of success and cost avoidance. To see returns on those strategies, PMOs need to actively engage project stakeholders in spotting and fixing problems and create a culture that encourages, rather than penalizes, early problem identification and escalation.

About the Authors

Benjamin Knopf is a senior analyst at CEB.

Brian Gagnon is a senior director at CEB.

FCW in Print

In the latest issue: Looking back on three decades of big stories in federal IT.


  • Anne Rung -- Commerce Department Photo

    Exit interview with Anne Rung

    The government's departing top acquisition official said she leaves behind a solid foundation on which to build more effective and efficient federal IT.

  • Charles Phalen

    Administration appoints first head of NBIB

    The National Background Investigations Bureau announced the appointment of its first director as the agency prepares to take over processing government background checks.

  • Sen. James Lankford (R-Okla.)

    Senator: Rigid hiring process pushes millennials from federal work

    Sen. James Lankford (R-Okla.) said agencies are missing out on younger workers because of the government's rigidity, particularly its protracted hiring process.

  • FCW @ 30 GPS

    FCW @ 30

    Since 1987, FCW has covered it all -- the major contracts, the disruptive technologies, the picayune scandals and the many, many people who make federal IT function. Here's a look back at six of the most significant stories.

  • Shutterstock image.

    A 'minibus' appropriations package could be in the cards

    A short-term funding bill is expected by Sept. 30 to keep the federal government operating through early December, but after that the options get more complicated.

  • Defense Secretary Ash Carter speaks at the TechCrunch Disrupt conference in San Francisco

    DOD launches new tech hub in Austin

    The DOD is opening a new Defense Innovation Unit Experimental office in Austin, Texas, while Congress debates legislation that could defund DIUx.

Reader comments

Wed, Apr 16, 2014

I'm sorry, but I feel this article totally missed the mark. In my experience (multi-agency, both as a fed and as a contractor), the issue is a failure of leadership. In too many cases, known problems are not fixed, failed processes are retained, and good processes are not used. Often, federal organizations are over managed and under led.

Please post your comments here. Comments are moderated, so they may not appear immediately after submitting. We will not post comments that we consider abusive or off-topic.

Please type the letters/numbers you see above

More from 1105 Public Sector Media Group