Why you should not try to improve how you do projects!
by jed simms on November 5, 2008
Many organizations are wanting to ‘improve how they do projects’ so as to get better results, more consistent results or even some results.
The task is then handed to a special team, IT or a PMO to ‘fix’.
They, understandably, look at how they do projects now and what can be fixed. If they have a project methodology, they’ll replace it with another. If they don’t have a methodology, they’ll get one.
They’ll do more training, more recruiting and more change management – all to ‘improve how they do projects’.
But this is not the right focus or outcome.
The key question for any project delivery capability improvement initiative is, “How does this increase the value delivered through our projects?”. If the improvement team cannot answer this, they have failed.
“We’ve got a better methodology” is not a valid answer unless it can be shown that (a) the former methodology (or lack of one) directly destroyed value and (b) that the new one directly delivers additional value.
“We select better projects” is not a valid answer unless you can actually fully realize the value these ‘better projects’ contain. Blundering forward with the right projects is not a recipe for success (albeit it may waste less money and effort).
At the end of the day the business does not want projects it wants results — new business end states that deliver in full the expected business benefits and value.
In this context, ‘improving how you do projects’ is only relevant in so far as you directly address the drivers of value loss. Having a better methodology that loses value faster is hardly a step forward!
So you need to change your language and focus.
- Talk of improving “project delivery” (or value delivery) but not project management. The latter is a skill-set, the former is a process. It’s the process you need to focus on.
- Focus on what drives or destroys project value in your organization. Where and when does the value get lost? How you do ‘work breakdown structures’ is not usually critical to your value delivery success. So what is? Know them and tackle them first. (It may surprise you that we found that the business case is often the single greatest destroyer of value!)
- Involve senior management early as too much value is lost through poor management decisions, reluctance to challenge management’s desires and ineffective project governance. If they’re not on side, cancel the project.
- Build a value proposition for the improvement program as early as possible so that you can always show why it is a valuable, viable priority. Otherwise you’ll be cancelled as soon as times get tough.
- Deliver (and publicise) real benefits early and frequently. You should always aim to demonstrably save 10 times your uplift project’s cost per annum. And as most projects miss, lose or destroy 50% or more of their potential value, this should be easy to achieve.
What do you think?
3 comments
Who is accountable for the financial and other aspects of organisation performance? The board of directors, the CEO and the top executve team. What happens when projects fail to deliver intended, relevant, valuable outcomes? The organisaton’s performance is reduced. Ergo – who is accountable for projects successfully delivering full to the organisation? The board, the CEO and the top executive team! When these people accep their viral role in governing the organisaitons use of IT, and its IT enabled change initiaitives, we will see projects properly resourced from the outset, with strong engagement of the relevant business leaders, and many of the common barriers to true success will disappear. Cost will come down, value will go up, and everybody should be happy!
So why isn’t this happening? Don’t the people at the top want success?
by Mark Toomey on November 5, 2008 at 4:22 pm. #
Totally agree Jed. Your article demonstrates full picture understanding of how projects/programs get thought of and developed in today’s business organizations. Sometimes even finance people do not fully comprehend the concept of “value realization”.
Thanks for the insights.
by Otba Alsboul on November 5, 2008 at 4:55 pm. #
We need to understand the relation between business drivers, objective /outcome of any IT enabled business investment, the benefits, the business changes [ i.e. working process changes], enabling changes [ one time permanent changes] and finally the tech enablers.
F/ws like Benefit dependency network diagram helps to drive this kind of relation.
Here we arrive at , rather see if there is any logic of investing in a tech enabler or not. That is the first step.
by Sankalan B on November 5, 2008 at 5:50 pm. #