If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting!
"Project Quality Management must address the management of the project and the product of the project"
(p.180, PMBoK, 3rd edition)
In an earlier blog entry, I presented the Nine Wastes of Mismanaged Projects, according to Lean Project Management gurus (Howell, Macomber, Koskela, Bodek). I said then that I saw a 10th waste adversely affecting project success: Not Managing Perceptions. Today, I will briefly explain why I believe that not managing perceptions is a major project waste, and why it has to be taken care of for our projects to be successful.
The sentence from the PMBoK quoted above is one of the most important messages on successful project management. It means that project quality, a strong indicator of project success, does not only depend on the physical characteristics of project deliverables, it also depends on HOW they were delivered. It means that a project is not only a destination, it is also a journey. It means that in matters of quality, BOTH the journey and the destination are important.
"…only one out of three projects (29%) are considered to be successful by the stakeholders"
The success of a journey is really a matter of perceptions. Perception can be defined as "an individual's interpretation of the world and of one's experiences, this interpretation being coloured by that person's model of the world and past experiences." Obviously, unless they are shared, discussed and somewhat managed, individual perceptions of what’s going on during a project will be very different. Perceptions of why we do the project, of what is important, of how well things are going, of project completeness and success, etc. will all differ. The project management community already wonders how to manage risks in the face of individual risk perceptions. But perceptions differ not only with respect to risk issues; they differ with respect to every single project issue. And all project communications can also be plagued by this important factor, or waste, since what is communicated is not the message transmitted but, rather, the message perceived.
If the perceptions of individual project stakeholders are not confronted with facts and, if these facts are not then discussed, shared and interpreted collectively, it is close to impossible to agree, among other things, on the same perception of the project journey or on the same perception of what project termination means. Hence, the stakeholders cannot agree on project quality and ultimately on project success.
In North America, according to the Standish Group, only one out of three projects (29%) are considered to be successful by the stakeholders; individual perceptions of project success are just not aligned. Meanwhile, on the other side of the Atlantic, Britain's Constructing Excellence program concludes that, of the projects subjected to the project management approach proposed, 85% are successful; this approach focuses on ensuring better integration of all stakeholders by putting together extended project teams. Are these European projects more successful because they produce better deliverables (the product or the destination of a project)? I don’t believe so! I believe this is because the Constructing Excellence program ensures that project managers also take care of the quality of the management of their projects (the journey); they get all their stakeholders together, they share, they discuss and, ultimately… they manage perceptions.
Tags: PMpractice, PMBoK, lean, teams, Bodek, leanproject, projectmanagers
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=03314884-90d1-47e5-acf3-2821313e9fdc)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=4ce3f392-8989-448a-a97a-c1432dd3fce6)
{ 2 comments… read them below or add one }
As a project manager, I’m always interested in the statistics about how many projects are successful, and what exactly does success mean, anyway? I heard a speaker last week who stated the “Big Dig” and “DIA” (Denver Airport) were both total failures. From a cost/schedule point of view these projects definitely missed the mark. But I had to disagree with his conclusion, that they were total failures. Both projects produced something of worth in my mind.
Thanks to Claude for a good reminder of the importance of working closely with all the stakeholders to make sure my projects will be in those considered a success.
Diana, you sure give a good example of the problems caused in an organization by different perceptions of success. I ran into a very similar «sad» situation during one of my PM workshops for a Processed Food Company (mainly milk transformation). They have on the Canadian market now one of the most successful new soft cheese produced from raw milk: the star of their new products. However, the «new product development» project manager who delivered this wonder with his team was blamed for not respecting the initial schedule and budget. My feeling and that of the people reporting this situation to me was that, if he had focused on delivering the initial «constraints» (that is what schedule and budget are, not «objectives») instead of on delivering a market winner (which was the initial intention, the real objective to preserve), he would have been a hero…. and the marketing people, stuck with pushing a bad cheese on the market, would have been the ones blamed. Two different internal stakeholders, measured using two different success criteria that are not mutually exclusive but are often considered as such. Very sad indeed…So the final user, me (the consumer), will thanks this project manager for this fabulous cheese if ever I meet him.