Four Early Warning Signs of a Project in Trouble

August 17, 2010 | Author: PM Hut | Filed under: Miscellaneous

Four Early Warning Signs of a Project in Trouble
By Ty Kiisel

Underground mining is a dangerous occupation. What’s more, before the advent of sophisticated breathing apparatus, methane and carbon monoxide made it even more dangerous for the men working in the mines. In the early days of underground mining, because their metabolism was susceptible to methane and carbon monoxide poisoning, canaries played an important role in keeping miners safe.

  1. They provided an audible warning: Canaries typically sing most of the time—when they stopped singing, it was a warning sign that they were being overcome by the toxic gas.
  2. They provided a visual warning: When they started to sway and fall from their perch, it was a signal that they were succumbing to the poison gas.

Miners who paid attention to the early warning signs owed their lives to the canaries—they were able to recognize the danger and get out of the mine before it was too late.

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. Not too long ago, I came across this list of early warning signs that every project manager should be aware of:

  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 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 those goals aren’t clearly articulated or understood by the project team. Occasionally, the business objective is thought to be so obvious it’s never clearly stated. Unfortunately this 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 to do you watch for?

About Ty Kiisel

Writing about project management for @task gives Ty the opportunity to share his personal experiences as an “accidental” project manager along with the lessons learned from conversations with customers, hopefully demonstrating that it really doesn’t matter what industry you’re in, the rewards of successfully executing project-based work are universal.

About @task

@task helps organizations focus on being more effective, innovative, and more competitive with a rich project and portfolio management solution that enables decision-makers to maximize their resources by implementing those initiatives that provide the greatest business value. @task helps align the strategic goals of objectives with the implementation and execution goals of project teams.

Share this article:
  • Digg
  • del.icio.us
  • Facebook
  • Google
  • blogmarks
  • LinkedIn
  • Reddit
  • StumbleUpon
  • TwitThis
  • Yahoo! Buzz

1 person has left a comment

You may also want to consider that some team members have agendas that could be very beneficial during the next project cycle but could be harmful to meeting project objectives at this time. They are stakeholders, after all, and managing THEIR expectations is important too.

Laura Bamberg wrote on August 19, 2010 - 2:58 pm | Visit Link

feel free to leave a comment

Comment Guidelines: Basic XHTML is allowed (a href, strong, em, code). All line breaks and paragraphs are automatically generated. Off-topic or inappropriate comments will be edited or deleted. Email addresses will never be published. Keep it PG-13 people!

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

All fields marked with " * " are required.

Project Management Categories