Chris pushed back from his desk and stared at his display. The earliest completion date was now three months later than before his latest schedule changes. Resting his chin on his left fist, he let out a deep sigh.
Just then, Warren walked by, waving as he went. 'Uh-oh,' Chris thought.
Sure enough, Warren stopped, turned back, leaned into Chris's office and said, "You don't look happy."
Chris looked up. "Dropping the Bluefield requirements didn't help. Actually, it got worse."
Warren looked at his watch. "Well, if you don't figure this out by Eleven, let's all meet in my conference room."
Chris and Warren are having a familiar conversation. When we make changes that ought to speed things up, things usually slow down.
Knowing about impending negative progress can be helpful. Here's a collection of tactics and events that can indicate the potential for negative progress.
- Denying negative surprises
- When you deny the significance of bad news, you start losing time immediately. Review carefully all denials of the significance of surprises.
- A drumbeat of bad news
- When you deny the
significance of bad news,
you start losing
- Troubles often travel in herds. When things aren't going well, staying the course could be a questionable strategy. See "Flanking Maneuvers," Point Lookout for September 8, 2004.
- Outdated, inadequate, or shared equipment
- Using obsolete or worn out equipment, or having to schedule the use of essential equipment, costs time and creates delay. See "The Cheapest Way to Run a Project Is with Enough Resources," Point Lookout for March 21, 2001.
- Extremely tight or very lax deadlines
- Reasonable deadlines encourage risk-taking, which is essential for discovering innovative solutions. Extreme pressure — or the absence of all pressure — threaten both creativity and quality. See "Make Space for Serendipity," Point Lookout for September 25, 2002, and "Critical Thinking and Midnight Pizza," Point Lookout for April 23, 2003.
- Fractional people
- When too many projects depend on a few people with critical skills, their time becomes fragmented, and they must constantly switch between tasks. Often their productivity falls as fast as the quality of their work. See "When Is Change for a Dollar Only 82 Cents?."
- Relaxing requirements to maintain schedule
- In today's environment, requirements do change. But relaxing requirements solely to maintain schedule could be a warning of trouble ahead. The tactic rarely saves time, and it often has the opposite effect.
- Adding staff
- Adding staff always slows things down, even if your intention is to speed up.
- Meetings consistently running overtime
- In a well-run project, some meetings run over — but some finish early. If you always run over, look out for trouble.
- Underused consensus
- Consensus produces the most durable decisions. If you never use consensus, even when time does permit, some decisions could be flawed. More important, avoiding the use of consensus could be an indicator of trouble on the team. See "Decisions, Decisions: I," Point Lookout for November 17, 2004.
- Closed communications
- If an elite group deals with bad news, making critical decisions without participation of the team at large, and controlling the circulation of information about the bad news, then it's possible that the bad news is worse than many people believe. See "See No Evil," Point Lookout for March 30, 2005.
Most projects exhibit at least some of these traits from time to time. Track their incidence. When many are present, and when they settle into a stable pattern, you might be in for a wild ride. Spend a little extra time looking around the next turn. Top Next Issue
Are your projects always (or almost always) late and over budget? Are your project teams plagued by turnover, burnout, and high defect rates? Turn your culture around. Read 52 Tips for Leaders of Project-Oriented Organizations, filled with tips and techniques for organizational leaders. Order Now!
- Ron Thompson, Eiscon Group, Ltd. (www.eiscon.com)
- One of your best yet! I have stories about all of your nine indicators (I think eight of them come from the same project). I wanted to pass along a couple.
- On adding staff I was once able to head this off. I was leading a pressure project where we were tracking on time, but tight. The manager asked me when we could deliver if he gave me another person. I looked him in the eye and said two months later. He never brought it up again (and we delivered on time).
- On meetings consistently running overtime I was on a project that was running extremely late, so the manager started holding daily status meetings that usually ran at least an hour. At one, he asked if anyone had ideas to get the project back on track. A co-worker (and friend of mine) quietly says from the other end of the table, "We could try getting back to work instead of sitting in this ******* meeting." The manager never did get a clue and the project ended up dying a slow death.
- On closed communications Even worse, the project team invents rumors that the bad news is worse than many people believe, even if the "elite group" isn't even dealing with bad news!
Your comments are welcome
Would you like to see your comments posted here? rbrenmhXARWRMUvVyOdHlner@ChacxgDmtwOKrxnripPCoCanyon.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.
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:
- Restarting Projects
- When a project gets off track, we sometimes cancel it. But since canceling projects takes a lot of courage,
we look for ways to save them if we can. Often, things do turn out OK, and at other times they don't.
There's a third choice, between pressing on with a project and canceling it. We can restart.
- Beyond Our Control
- When bad things happen, despite our plans and our best efforts, we sometimes feel responsible. We failed.
We could have done more. But is that really true? Aren't some things beyond our control?
- Design Errors and Groupthink
- Design errors cause losses, lost opportunities, accidents, and injuries. Not all design errors are one-offs,
because their causes can be fundamental. Here's a first installment of an exploration of some fundamental
causes of design errors.
- Team Risks
- Working in teams is necessary in most modern collaborations, but teamwork does carry risks. Here are
some risks worth mitigating.
- Down in the Weeds: I
- When someone says, "I think we're down in the weeds," a common meaning is that we're focusing
on inappropriate — and possibly irrelevant — details. How does this happen and what can
we do about it?
Forthcoming issues of Point Lookout
- Coming October 23: Power Distance and Teams
- One of the attributes of team cultures is something called power distance, which is a measure of the overall comfort people have with inequality in the distribution of power. Power distance can determine how well a team performs when executing high-risk projects. Available here and by RSS on October 23.
- And on October 30: Power Distance and Risk
- Managing or responding to project risks is much easier when team culture encourages people to report problems and question any plans they have reason to doubt. Here are five examples that show how such encouragement helps to manage risk. Available here and by RSS on October 30.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenmhXARWRMUvVyOdHlner@ChacxgDmtwOKrxnripPCoCanyon.com or (650) 787-6475, or toll-free in the continental US at (866) 378-5470.
Get the ebook!
Past issues of Point Lookout are available in six ebooks:
- Get 2001-2 in Geese Don't Land on Twigs (PDF, )
- Get 2003-4 in Why Dogs Wag (PDF, )
- Get 2005-6 in Loopy Things We Do (PDF, )
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, )
- Get 2009-10 in The Questions Not Asked (PDF, )
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, )
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: Lessons in Leadership
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 leadership and its application to organizational efforts. A fascinating and refreshing look at leadership from the vantage point of history. Read more about this program.
Here's a date for this program:
- Baldwin-Wallace University, 275 Eastland Road, Berea, Ohio
44017: November 7,
Kerzner Lecture Series/International Project Management Day, sponsored by Baldwin Wallace University and the Northeast Ohio Chapter of the Project Management Institute.
- Baldwin-Wallace University, 275 Eastland Road, Berea, Ohio 44017: November 7, Kerzner Lecture Series/International Project Management Day, sponsored by Baldwin Wallace University and the Northeast Ohio Chapter of the Project Management Institute. Register now.
- The Power Affect: How We Express Our Personal Power
Many people who possess real organizational power have a characteristic demeanor. It's the way they project their presence. I call this the power affect. Some people — call them power pretenders — adopt the power affect well before they attain significant organizational power. Unfortunately for their colleagues, and for their organizations, power pretenders can attain organizational power out of proportion to their merit or abilities. Understanding the power affect is therefore important for anyone who aims to attain power, or anyone who works with power pretenders. Read more about this program.