Success

threew's picture

In the world of projects, a lot of time and effort is devoted to the question of why projects fail. There are top ten lists, research reports, and endless discussions on forums everywhere as well as in conference rooms around the world. There's a reason for this but it's probably not the one most people think.

Projects can and do fail for every conceivable reason. The list of reasons is virtually infinite even with a great deal of abstraction applied. Given the scope of failure data points, how useful is it?

Overall: If we're good at risk management, the data is of some use. If we're not good at risk management, there is little value.

Knowing that the "number one" reason projects fail is "lack of communication" or some other [configurable value], doesn't help if we (the organization) are terrible at executing that particular process. We're still going to do the project, right? We're not going to stop all projects and implement "communication training" or [configurable value] before proceeding. In other words, what are the real options?

Those lists of reasons projects fail--even in their infinite magnitude--are "knowns." Not every reason applies to every project but every single item on the list is capable of derailing an expensive, time consuming effort. Some analysis is required to understand the risk to a particular project... a specific group of people... this organization. Do the analysis right and we have a list of known risks for a specific project. It will not be infinite.

There is a saying (perhaps a quote) that goes something like: "The biggest obstacle we will face is one we did not anticipate."

That obstacle is not on our lists of "knowns."

More important, to my mind at least, than the reasons projects fail are the reasons projects succeed. In my experience there is one... the Grand Daddy of project success... the Mother of All Reasons.

Project failure is more about mismanaging or failing to manage the knowns than anything else. Project success is about managing the obstacles we did not anticipate.

No matter how long our risk list; no matter how good our analysis, contingency and mitigation plans, if we lack process, people, and leadership to handle the unanticipated, the likelihood of project success is quite low. There are always unknowns and unanticipated events.

If we don't flush out all the knowns and don't have contingency/mitigation in place for every possible risk event but we are following a process with people and leadership in place to handle unanticipated events, the likelihood of project success is quite high.

Lack of failure is no indication of success.

Comments

jdunham's picture

This is really excellent.

This is really excellent. You ought to publish it somewhere ... oh, wait ... you just did.

I can't help but relate this to my dog rescue activities, since I see all of this in spades there. Sitting in Texas, rescuing a dog in a kill shelter in Missouri, finding a foster home in Wisconsin, and then getting the dog moved there before the shelter times out and kills the dog, all for free (since almost no one in rescue has any money) is a challenging project management task. The people who are good at such things may have no training as project managers, or even know the term, but they apply a lot of the principles, and PMI would be proud of the best of them.

The whole process is fraught with the potential for disaster, and a life is on the line, often several lives. No matter how many known risks one plans for, there are many more that no one is thinking of. Those who succeed at these rescues are good at planning, communicating, risk management, team building, etc., but they also have to be good at reacting quickly to unknown risks when they manifest themselves. The whole world is not under your control, so you have to know what is, and how to use what you can control on very short notice.

Long before formal project management, people were succeeding at getting projects done. There may have been budget and schedule overruns and some unnecessary failures, but SOME people were succeeding. At least to some extent these were people who were better than average at reacting to the unexpected. I don't recall it ever being in anyone's job description, but it was often a critical success factor.

Of course it's always better to be lucky than good. :-)

--
Jerry Dunham
Not depending upon luck

JoeSeale's picture

Denial = Failure

Denial = Failure

This is far from a comprehensive comment, but, in a nutshell, the number one reason projects fail is denial. "Project failure is more about mismanaging or failing to manage the knowns" because people are afraid to admit that something is going wrong because then they may have to take responsibility for fixing it and if they fail to do so, they'll get blamed.

I coach people who work for me to take the risk and speak up and assure them time and time again that 'the only people who don't make mistakes are the people who don't do anything'. And then I back it up with my actions. It works.

threew's picture

Thanks Jerry. Nice

Thanks Jerry. Nice example.

William W. (Woody) Williams
Senior Project Management RenewData PMO (Consultant)
| Blog | Twitter |
w3src Consulting