If you write the perfect rule, you will get the desired outcome. Authoring a specification that is robust and watertight will assure success. Having the best possible plan will deliver the best possible results. All sounds reasonable – doesn’t it? It’s not surprising that someone like me, having been schooled in project management, and working in engineering, would have a rational and systematic approach to problem solving. A proven highly successful way of implementing complex technical projects and delivering successful outcomes.
As an analogy I’ll start with mathematics. Nature is a curious beast. What we lean about complex systems is that what happens is highly dependent upon a start point. The initial conditions. Graduate level mathematics about control systems with feedback show that their behaviour changes a lot with a change of initial conditions. So, it’s reasonable to extend that to a systematic approach to just about anything. It’s often true.
Fail to plan – plan to fail. That idiom is a simple few words to sum up this cause and effect. Used by famous names and often quoted. Management training books are littered with this notion.
20-years ago, my team introduced the first European Aviation Safety Plan[1]. This initiative was built around the idea that to achieve a common objective a plan is the best and quickest way to get there. A roadmap, a pathway, a strategy, call it what you will.
Start by identifying problems and then propose a fix for each one. Not all problems but the ones that fit that awkward Americanism – the low hanging fruit. Namely, the biggest problems (fruit) that can be solved with the least effort (easily picked).
Here’s where I’ve changed your mind. Maybe not changed in a dramatic sense but shifted perspective. It’s essential to have a plan, even if it’s just in my head, but it can be overstated as the most important part of a process of change.
The Plan, Do, Check, and Act (PDCA) cycle, starts with a plan. It must start that way. However, each of the four steps is equally important. Seems obvious to say. Even so, it’s often the case that a press release, or alike, will state – we have a plan, roadmap, pathway, strategy, as if that’s the job done.
Management teams will smile with a sense of achievement and show off their plans. A decade down the line that celebration might seem less momentous as the “do” part of the process turns out to be harder than anticipated.
This basic model for systematic change is a good one. Where I’ve changed my emphasis is in the distribution of effort. Don’t put all available energies into constructing the perfect plan. Yes, the initial conditions are important but they are not everything. The key part of the process is the cycle. Going around it with regularity is a way of delivering continuous improvement. Afterall, when it comes to a subject like aviation safety, that’s what’s needed.
[1] 2005 – DECISION OF THE MANAGEMENT BOARD ADOPTING THE 2006 WORK PROGRAMME OF THE EUROPEAN AVIATION SAFETY AGENCY
John Vincent 