You are hereDialogue - Narrative Blog / Aiden Choles's blog / How a heavy mallet solves a complex problem
How a heavy mallet solves a complex problem

You might have seen that the slogan we have up on our website is this:
"The common ground between complex problems and simple solutions."
In explaining what this means we often refer to the use of an efficiency rudder used to improve the turning circle of ships (read about it here). In a similar light, I've discovered the story of John Snow as an example of how a simple solution can solve a complex problem ...
In 1854, cholera broke out in a London district. It killed hundreds of people within a few days and the authorities were stumped as to the source of the cholera and how to stem it. John Snow had a suspicion that it was water borne and that by identifying the water pump the cholera was emanating from, and by neutralizing the pump, the outbreak would be curbed.
After discovering the Broad street pump as the source, he went to the authorities to report this and suggested they shut down the water pump. They demurred, but then agreed. From the prologue of Jeffrey Kluger's Simplexity:
"The next day, a workman was sent to the the offending pump, heavy mallet in hand. He took several clanging swings at the fittings holding the handle in place. The metal peg popped free and the handle itself clattered to the street, rendering the pump useless." .
"The complex illness could collide hard with the simple fix. And on this day at least, it was the simple fix that held its ground."






ok, so now i take you seriously and trust that the answer to my complex set of organisational problems - which include a history of seperate development, prejudice, culture and linguistic diversity and issues of economic disparity - is actually quite simple...
what should i do next?
take out my mallet and start eliminating some of the people who talk drivel in my church?
Um, Anonymous, that might work, but in my experience church folk don't respond favourably to that approach.
Rather, this post was illustrating how there's a pretty rigorous process one can follow in identifying the root cause/driver of a complex problem, and how the solution to that problem is often counter-intuitive or just cheap.
You've just got to make sure you don't pull out your mallet (best practice solution) as a first response to the problem, but that you rather probe the patterns of the problem, elicit feedback from the system that will guide you indentifying potential solutions and then implement/prototype them.