Although my company has prepared some preliminary procedures, we as a company are still having problems. It seems that some companies are doing business as usual, (setting up for failure). Businesses may or may not understand the reason why, but can you

Beyond the obvious high level reasons, I am beginning to see something that is devastating to me…Panic when issues arise, finger pointing, attempting to make the other dependent group look like the fall guy, having un-realistic timelines, resource issues, no clear plan, and a host of many other issues. Remember that before this point in time, you were, or suppose to be, a team. You still are and can get through this as a team to determine if the project is do-able.

Other reasons that can contribute to project failures:

• Processes (old or outdated processes that haven’t been reengineered or improved)
• Old habits (“We have been doing it this way for “a number of” years.” Yes, we know.)
• Profit before quality or doing the project/program right
• The culture (an attitude that is doing business as usual because they are not accepting change or preparing for it)
• The competing of egos and political shifting or power struggles

The Solution

The solution is that although one begins to reduce tasks, and that may be necessary to meet a business decision timeline, what should take place is the completion of a realistic plan and Work Breakdown Structure (WBS). Then, only reduce activities or processes that are based on realistic planning and estimates. It is okay to change a timeline when the timeline has been evaluated, and its impact assessed, as long as it’s negotiated and approved. Now if the timeline seems to be unrealistic it must be addressed and discussed but should not just be accepted to go with the change. Then, it’s a matter of communicating these changes to all the stakeholders having them realize that this is what it will take for an unsuccessful or successful project. I have found out through past experience that a realistic plan executed is not as drastic as one might think. The repercussions of a failed project/product, a negative business reputation, credibility, and the monetary loss, are much greater.

Any uncertainty will be eventually overcome; at least you have a successful project, quality product or system, and now you can meet current and future needs. You have a better perspective of reality doing the project or program right, and enough lessons learned, if documented, for improvements. …and a good start to build a knowledge base for project and process improvement.

So yes, it’s about doing it right and being realistic while identifying the other non technical and business root causes that can also contribute to project and program failure.