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? Send 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
- Nine Project Management Fallacies: Part III
- 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.
- The True Costs of Cost-Cutting
- The metaphor "trimming the fat" rests on the belief that some parts of the organization are expendable, and we can remove them with little impact on the remainder. Ah, if only things actually worked that way...
- TINOs: Teams in Name Only
- Perhaps the most significant difference between face-to-face teams and virtual or distributed teams is their potential to develop from workgroups into true teams — an area in which virtual or distributed teams are at a decided disadvantage. Often, virtual and distributed teams are teams in name only.
- The Injured Teammate: Part I
- You're a team lead, and one of the team members is very ill or has been severely injured. How do you handle it? How do you break the news? What does the team need? What do you need?
- Communication Traps for Virtual Teams: Part II
- Communication can be problematic for any team, especially under pressure. But virtual teams face challenges that are less common in face-to-face teams. Here's Part II of a little catalog with some recommendations.
See also Project Management and Workplace Politics for more related articles.
I offer email and telephone coaching at both corporate and individual rates.
Contact Rick for details at rbrenner@ChacoCanyon.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
- The Race to the South Pole: Ten Lessons for Project Managers
- 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 project managers, the story is fascinating. Lessons abound. Read more about this program. Here's an upcoming date for this program:
- The Politics of Meetings for People Who Hate Politics
- There's a lot more to running an effective meeting than having the right room, the right equipment, and the right people. With meetings, the whole really is more than the sum of its parts. How the parts interact with each other and with external elements is as important as the parts themselves. And those interactions are the essence of politics for meetings. This program explores techniques for leading meetings that are based on understanding political interactions, and using that knowledge effectively to meet organizational goals. Read more about this program. Here's an upcoming date for this program:
- Cognitive Biases and Workplace Decision-Making
- For most of us, making decisions is a large part of what we do at work. And we tend to believe that we make our decisions rationally, except possibly when stressed or hurried. That is a mistaken belief — very few of our decisions are purely rational. In this eye-opening yet entertaining program, Rick Brenner guides you through the fascinating world of cognitive biases, and he'll give concrete tips to help you control the influence of cognitive biases. Read more about this program. Here's an upcoming date for this program: