Find the idea of all that estimating and benefit measurement a bit tiresome?  Well, best have a chat to one of the original Channel Tunnel investors who saw their investment decimated and even the promise of free use of the tunnel removed, because their business case turned out to be badly flawed.

Clearly this would have been a difficult business case to put together, it’s not as if someone had already dug a channel tunnel for them to base their estimates on, so there must have been a lot of unknowns and risk as well as a whole lot of politics.

The tunnel delivered 1 year late and with an 80% cost overrun.  This changed the basis of the original business case and meant that the company operating the tunnel had to put charges up to try to pay off the debt.  This didn’t work too well, because fares were then so expensive that no-one was using the tunnel.

So it was hit by a perfect storm of overly optimistic development costs, overly optimistic revenue forecasts and an inadequate assessment of risk.

For a while bankruptcy loomed, but in the end the issue was solved by a financial restructuring, which meant giving a lot of the company away to their creditors and diluting the existing shareholder ownership.

I’m sure the guys putting the original business case together believed they had done a good job, but clearly it wasn’t good enough.

So when you build a business case:

  • Don’t rush getting the business case together – this is a classic mistake – give yourself the time to get to good numbers
  • Use a systematic method to arrive at estimates and then challenge the estimates. Over optimism can be very costly – in the channel tunnel contractors’ case £2 Billion!
  • Make sure it’s clear what is and what is not being delivered for the money
  • Ensure you properly assess Risks, Dependencies and Assumptions
  • Make sure you apply contingency to your estimates based on the risks that you have assessed – not a blanket application of contingency – the people signing off the business case need to know why you’ve applied contingency
  • Make sure you apply risks to the benefits as well as to the estimates – benefits can reduce as well as estimates increasing
  • And for the people approving business cases – if the business case doesn’t work, playing around with the figures usually isn’t the answer.  I’ve seen two very large projects come to grief because approval was only given after huge pressure had been applied to drastically reduce estimates, only for panic to ensue as costs escalated once they got underway.

Once the business case has been approved, it’s important to keep updating it at each stage of the project to make sure it remains valid, especially if scope is changing or costs increasing.

The channel tunnel was a multi-billion pound project, but the principles are just as relevant to a small or medium sized company undertaking a project in the tens or hundreds of thousands.  If the project goes wrong, the consequences can be severe.

The tunnel is still there and making money now, after a big mistake the same might not be true for your business.

Enjoyed reading this, why not sign up for more free project management tips.                                       

Read more advice on Project Management in Project Management for SMEs – available in print and ebook format.

Gren Gale is a consultant specialising in Project Management and Procurement and is owner of PM Results

 

#PM4SMEs

 

Join our mailing list and receive our Free White Paper 'Choosing the Right Project Management Software'

 

Plus free project management, product development and procurement tips.

Thanks for subscribing - look out for the confirmation e-mail!