Early Warning Signs Your Project Might be in Trouble

 

I remember watching this video of the 1964 Alaska earthquake as an elementary school student.  At 5:30 pm on Friday March 27, 1964 the 9.2 magnitude quake that pummeled Alaska was the most powerful earthquake ever recorded in North American history and the second largest earthquake ever recorded in the history of the world.

In Prince William Sound, a 27-foot tsunami destroyed the village of Chenega, killing 23 of the 68 residents.  Post-earthquake tsunamis severely hit Veldez, Whittier, Seward, Kodiak, and other Alaskan Communities.  The video includes live footage captured by a couple of sailors on board a freighter being unloaded at the dock.

Unfortunately, there isn't a reliable way to scientifically predict (with any accuracy) a coming earthquake. 

Luckily, there are early warning signs when a project is in trouble.  I think everyone would agree that missing deadlines or exceeding budgets is evidence that a project is probably in trouble.  However, those symptoms are often recognized after it's too late to do anything about it.  Anyone doing project-based work knows how important it is to recognize a project in trouble before it's too late to do anything about it.  Not long ago I came across this list of early warning signs that every project manager should watch for:

1. Direction from management is either missing or inconsistent: The only thing worse than project leadership that is missing in action, is direction that contradicts itself and changes frequently.
2. Business management and project management aren't on the same page: If the project gets consistent direction, but it's at odds with the company business objectives, there is more than likely a problem.
3. Project goals are not clearly articulated and understood by the project team: Although every project usually has a business goal or two—projects without a business objective should probably be reconsidered, right?  Often, project goals are not clearly articulated or understood by the project team.  Occasionally the business objective is thought to be so obvious it's never clearly stated.  (It reminds me of when my wife asks me if I noticed anything different when I get home.  I'm a guy.  Of course I didn't notice.)  Assuming that the objectives are obvious could lead to misunderstanding and inconsistent presumptions about priorities.
4. Team members don't communicate with each other: Sometimes, even teams that get along well don't communicate well.  Communication and collaboration are essential to any successful project.

Recognizing problems before it's too late to do anything about them is critical to work management success.  Addressing issues early is the best way to save a lagging project, as well as a project manager's career.  What early warning signs do you look for to insure project management success?