I was watching an episode of “Air Crash Investigation”, a great programme for understanding what can go wrong and how, in the very public and challenging world of civil aviation.
An airliner ran out of fuel and crash-landed more than 700 miles from its destination, having flow in the opposite direction to its destination.
The pilots blamed technical failure, but there was none – they had mis-set the autopilot and set off in completely the wrong direction, and when they realised they were really lost, instead of asking air traffic control for help, tried to sort it out themselves, making the problem even worse, because they interpreted what they saw as what they wanted to see, not what was really there (confirmation bias).
Many project teams start with a low expectation of success because they have always fallen short of delighting the customer. Repeated failures confirm their bias that they will always fail, so why bother?
Since they are not expecting to succeed, they don’t look how they could do things differently to improve their chances of success. I had a very serious argument with the existing team I inherited when asked to recover a failing programme. “We always do it this way” they said, to which I replied “and you always fail!”
I won the argument, losing one team member in the process, and we tried a completely different approach, very focused on customer experience, and succeeded beyond all expectations.
Taking a fresh look at the complete problem, understanding the true success criteria and designing the whole approach to achieve success, quickly transformed project performance, lifting the team’s self-esteem in a virtuous circle!
This isn’t a one-off – tackling the root causes of frequent problems in a railway infrastructure company saw a 25% reduction in recurrent problems in just 4 weeks!