If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting!

Hank Winters, gantthead.com, penned two articles on The Top 10 Reasons Projects Fail (Part One). He identified the top reason as Inadequately trained and/or inexperienced project managers. Surprise…people took exception to that! Read his follow-up in Part Two.

I think Winters is right. Only I will be more specific: projects fail due to neglect. That neglect results in projects drifting out of integrity. Who neglects? Certainly it is the project manager, but why stop there? Most team members are in the position to notice the inconsistency of words and deeds. If they notice, then where are they speaking about it (because we know they are speaking about it)?

• The meeting after the meeting?
• The conversation in the hallway?
• The side comment in an email message?
• The conversation with the trusted colleague?

These conversations move the project further out of integrity.

We need everyone in a position to notice to take action. This is where I agree with Winters. It is due to poor training that our projects managers and their teams are not noticing the inconsistencies and taking appropriate action. We need to set this as a standard on our projects:

We will do those things we say we will do, or we will take action to rectify the situation whenever we stray.

Let's use the up-coming Project Integrity Day to learn how to take action.

BTW, Tom Mochal at Builder.com offers a different perspective in Project failures are less common than you think. Both authors reference the same Standish Group's findings. In their 1998 report, The Standish Group cited the success rate for that year was only 26 percent. Mochal contends because project schedules and budgets are set arbitrarily and scope changes we need to give ourselves some slack when declaring success or failure. Still, projects do fail and Winters' Top Ten list is a great way to understand why.