WhyProjectsFailPMtodayMarch2014 PDF
WhyProjectsFailPMtodayMarch2014 PDF
Projects are always tricky to organise, but more often than not, the underlying causes boil down to
the basics we discuss here.
they’re even worse when you’re under
In this short article we have chosen to focus on the basic
pressure to deliver a successful outcome. causes for project failure as outlined in a study carried out
And they don’t get any easier in spite of all by Harvard Business School in 1982. Yes, that’s over 30
years ago! What is quite surprising is that most studies
the latest tools and techniques. In fact, the that have followed during the intervening period have
failure rate today is just about the same also come up with broadly the same causes:
as it was when we first started keeping l Inadequate definition
l Scope not fully defined
count. It is also a fact that a large number
l Poor or No planning
of projects today have a considerable l Unrealistic timescales “It seems that as
IT content and can often spell failure l Ineffective controls projects become
before they ever get started. The burning l Wrong leader
more complicated,
l Inappropriate team
question has to be: why do these stubborn so the reasons
l Poor communications
statistics refuse to improve? In 2000 the Industrial Society added three more: for their failure
We asked three eminent lead figures at l Unclear objectives become ever more
Cranfield School of Management, John l Lack of stakeholder consultation sophisticated. Can
l Inadequate training
Algar, Steven Carver and Bill Johnson, to we see the ‘Black
All of these use basic human skills and techniques that
comment on the key issues that continue have been recognised for many, many years. Swans’ on the
to inhibit project success. We can group the above as follows: horizon?”
1. Unclear objectives – Inadequate definition –
Scope not fully defined
Just to avoid confusion, it is worth remembering that
true IT projects are very rare indeed. The vast majority 2. Wrong leader – Inappropriate team –
are business projects that happen to have a large IT Inadequate training
component. Well, here’s one reason so many fail – 3. Poor or no planning – Unrealistic timescales –
Managements usually understand what the desired Ineffective controls
outcome is but have little idea of how to get there and 4. Poor communications – Lack of stakeholder
often fail to understand and manage the nuances of consultation
change. Niccolo Machiavelli however, understood the Looking at each of these shows a clear progression
difficulties of implementing change and that was in towards failure.
1532!
1. Many projects have multiple objectives which can cause
Is the problem that we’ve forgotten the words of Steven confusion as different stakeholders focus on different
Covey? ‘When you make a mistake, admit it, correct it, things. We think that there should be a single objective
and learn from it’. This may seem naïve in our age of with the rest of the desirables identified as success criteria
technology but again we remember the immortal words or factors. It stands to reason that if the objective is
of Grady Booch – ‘a fool with a tool is still a fool’. But unclear then the definition will be unable to set out what
is the nub of the issue as simple as not putting enough needs to be done - therefore sections of the scope will be
effort into learning the lessons of the past? missing at all levels. In some scenarios we know it will not
It seems that as projects become more complicated, be possible to fully define all of the scope at the outset.
so the reasons for their failure become ever more However, if a layered scope is developed using a WBS1
sophisticated. Can we see the ‘Black Swans’ on the approach, then it should be possible to define the entire
horizon? This is not to belittle our greater understanding project, early in its life cycle, at a high level, adding more
of the reasons for failure. But when we investigate these, detail as it becomes clear what needs to be done.
1 Work Breakdown Structure