Deep Trouble and Getting Deeper
by Rick Brenner
Here's a catalog of actions people take when the projects they're leading are in deep trouble, and they're pretty sure there's no way out.
Ross Marshall, left, Oklahoma City Air Logistics Center Executive Director, and Don Pugh from Air Force Materiel Command Headquarters, at the kickoff meeting for the Expeditionary Combat Support System (ECSS) at Tinker Air Force Base, in Oklahoma, on August 17, 2011. ECSS, an Enterprise Resource Planning system conceived at the turn of the century, was to be operational by 2012. But it was cancelled in November, 2012, after consuming USD 1 billion, even though its objectives had been reduced to 25% of the original concept, and its delivery date had been extended to 2020.
According to Brig. Gen. Kathryn Johnson, the Air Force's director of system integration, and Robert Shofner, the Air Force's program executive officer for business and enterprise systems, one of the problems was that Computer Sciences Corp. (CSC) of Falls Church, Virginia, the prime contractor, was not able to adapt the Oracle software to meet the system requirements. CSC, which had been fired in March 2012, was thus being blamed in absentia for at least part of the failure of the project.
Air Force photo by Margo Wright.
When projects founder, their leaders, sponsors, and champions sometimes experience the foundering personally. Even if they don't experience the failure as personal, their experience of how others see the failure can have similar effects. When this happens, an overwhelming urge to repair the failure can develop. If repairs succeed, both organizational and personal needs are fulfilled. But when repair is impossible, things get more interesting.
In such cases, the project's leaders have already exhausted the obvious solutions: trying other approaches, or asking for more budget or time. They must therefore resolve the tension between the initially promised objectives and the current disappointing reality by means other than delivering what was promised, because that's plainly impossible.
Recognizing the techniques they use in such quandaries is helpful to both members of the project team, and the supervisors of the project's leaders, sponsors, and champions. Here are some techniques in common use.
- Confessing failure
- Confession is almost certainly the only honest approach. It's always available, but because, in most organizations, it presents significant risk to one's career, there is a tendency to avoid confession.
- Expanding the project's objectives can both conceal the failure and justify additional budget and schedule. Expansion in this form can be a cause of scope creep. See "Some Causes of Scope Creep," Point Lookout for September 4, 2002, for more.
- Fleeing the scene
- Flight, usually without admitting failure, works well if its true motivation can remain concealed long enough. It can take the form of promotion, transfer to another project or business unit, or "accepting new challenges" elsewhere.
- Embellishing, or "spinning," is a technique for representing in a misleadingly positive way the results that actually were achieved. If successful, embellishing buys time — at best.
- Declaring victory
- The extreme form of embellishment is announcing that the effort's primary objectives have been achieved and we're now ready to focus our energies on the next challenge. Since everyone knows the current effort is a disappointment, this announcement is rarely questioned overtly.
- Blowing smoke
- Blowing smoke, Embellishing, or "spinning," is
a technique for representing
in a misleadingly positive
way the results that were
actually achievedor obfuscating, can confuse decision-makers and team members alike. Making others believe that the effort is going better than it seems to be is usually just another delay tactic.
- Misrepresenting status fraudulently
- Outright lying is always possible, but because the risk of exposure is ordinarily so high, and the consequences so severe, this method is most practical for those who work in very secure or highly compartmentalized environments, where "knowledge firewalls" limit the chances of exposure.
- Placing responsibility for the project's troubles at the feet of the defenseless is a useful technique, because it so clearly absolves those who are doing the blaming. Defenseless individuals include those who have already departed the organization and those whose credibility is already so eroded — sometimes unjustly — that they cannot refute the claims made against them.
Do you know of a project in trouble? How many of these tactics have you seen? Top Next Issue
Is every other day a tense, anxious, angry misery as you watch people around you, who couldn't even think their way through a game of Jacks, win at workplace politics and steal the credit and glory for just about everyone's best work including yours? Read 303 Secrets of Workplace Politics, filled with tips and techniques for succeeding in workplace politics. Order Now!
Your comments are welcome
Would you like to see your comments posted here? rbrenDnMPDKryzymEfaxJner@ChaceLMxnTcswGXxrkZwoCanyon.comSend me your comments by email
, or by Web form
About Point Lookout
Thank you for reading this article. I hope you enjoyed it and found it useful,
and that you'll consider recommending it to a friend
Point Lookout is a free weekly email newsletter. Browse the archive
of past issues. Subscribe for free.
Support Point Lookout by joining the Friends of Point Lookout,
as an individual or as an organization.
Do you face a complex interpersonal situation? Send it in,
anonymously if you like, and I'll give you my two cents.
More articles on Project Management:
- Toxic Projects
- A toxic project is one that harms its organization, its people or its customers. We often think of toxic projects as projects that fail, but even a "successful" project can hurt people or damage the organization — sometimes irreparably.
- Films Not About Project Teams: Part I
- Here's part one of a list of films and videos about project teams that weren't necessarily meant to be about project teams. Most are available to borrow from the public library, and all are great fun.
- Nine Project Management Fallacies: Part II
- Some of what we "know" about managing projects just isn't so. Identifying the fallacies of project management reduces risk and enhances your ability to complete projects successfully.
- Nonlinear Work: Internal Interactions
- In this part of our exploration of nonlinear work, we consider the effects of interactions between the internal elements of an effort, as distinguished from the effects of external changes. Many of the surprises we encounter in projects arise from internals.
- Scope Creep and the Planning Fallacy
- Much is known about scope creep, but it nevertheless occurs with such alarming frequency that in some organizations, it's a certainty. Perhaps what keeps us from controlling it better is that its causes can't be addressed with management methodology. Its causes might be, in part, psychological.
See also Project Management and Workplace Politics for more related articles.
Forthcoming Issues of Point Lookout
- Coming October 7: Contextual Causes of Conflict: Part I
- When destructive conflict erupts, we usually hold responsible only the people directly involved. But the choices of others, and general circumstances, can be the real causes of destructive conflict. Available here and by RSS on October 7.
- And on October 14: Contextual Causes of Conflict: Part II
- Too often we assume that the causes of destructive conflict lie in the behavior or personalities of the people directly participating in the conflict. Here's Part II of an exploration of causes that lie elsewhere. Available here and by RSS on October 14.
I offer email and telephone coaching at both corporate and individual rates.
Contact Rick for details at rbrenorOavXXLAsOFCUIZner@ChacIvInzTjtipUCAlIroCanyon.com
or (617) 491-6289, or toll-free in the continental US at (866) 378-5470.
Get the ebook!
Past issues of Point Lookout
are available in six ebooks:
Reprinting this article
Are you a writer, editor or publisher on deadline?
Are you looking for an article that will get people talking and get compliments flying your way? You can have 500 words in your inbox in one hour. License any article from this Web site. More info
- Ten Project Management Fallacies: The Power of Avoiding Hazards
- Most of what we know about managing projects is useful and effective, but some of what we know "just ain't so." Identifying the fallacies of project management reduces risk and enhances your ability to complete projects successfully. Even more important, avoiding these traps can demonstrate the value and power of the project management profession in general, and your personal capabilities in particular. In this program we describe ten of these beliefs. There are almost certainly many more, but these ten are a good start. We'll explore the situations where these fallacies are most likely to expose projects to risk, and suggest techniques for avoiding them. Read more about this program. Here's an upcoming date for this program:
- Managing in Fluid Environments
- Most people now work in environments that can best be characterized as fluid, because they're subject to continual change. We never know whats coming next. In such environments, managing — teams, projects, groups, departments, or the enterprise — often entails moving from surprise to surprise while somehow staying almost on track. It's a nerve-wracking existence. This program provides numerous tools that help managers who work in fluid environments. Read more about this program. Here are some upcoming dates for this program:
- Download to
your calendarCrowne Plaza Hotel, North Charleston, South Carolina: October 15, Monthly Meeting, Charleston Chapter of the Project Management Institute. Register now.
- Download to
your calendarMITRE, in Bedford, MA: November 17, Monthly Meeting, Boston SPIN. Register now.
- Wherever you are: it's a webinar: May 4, 2016, Webinar, IT Metrics and Productivity Institute. Register now.
- The Race to the South Pole: The Organizational Politics of Risk Management
- On 14 December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough. But to organizational leaders, business analysts, project sponsors, and project managers, the story is fascinating. We'll use the history of this event to explore lessons in risk management, its application to organizational efforts, and how workplace politics enters the mix. A fascinating and refreshing look at risk management from the vantage point of history and workplace politics. Read more about this program. Here's an upcoming date for this program:
- Team Development for Leaders
- Teams at work are often teams in name only — they're actually just groups. True teams are able to achieve much higher levels of performance than groups can. In this program, Rick Brenner shows team leads and team sponsors the techniques they need to form their groups into teams, and once they are teams, how to keep them there. Read more about this program. Here's an upcoming date for this program: