Efficiency vs Robustness
Actually you might not want everything to be perfectly efficient…
It is human nature to want to reduce the world around us to simple rules that give us a sense of understanding and control.
When “A” happens, you should do “B”. If you see “C”, respond by implementing “D”
Unfortunately whilst this logic is true for some situations, it is anything but true in others and it becomes counterproductive or even dangerous when being too reductionist in how you manage a complex environment.
Systems thinking and the Cynefin framework are mental models that highlight that the world can be very complex and unpredictable and just because there is a view in hindsight about the root causes of a particular situation, does not mean the same lessons can successfully apply to the future.
I was reminded of this in a recent podcast interview on the Mind the Product podcast with Margaret Heffernan. In the interview Margaret highlights the difference between Complex vs Complicated situations (from the Cynefin Framework)
… We live in a world that is complicated and complex
Complicated things are linear, very cause and effect, think of them like an assembly line. You can control those things because you can control and influence all of the inputs, and so you can predict the output. They are systems that are well honed by efficiency.
Complex environments are quite different. They have lots and lots of factors influencing them, some of which you can control and some of which you can’t. and so what that means is that while there may be patterns within these complicated systems, they don’t repeat themselves predictably. It also means that very small things can have a gigantic impact.
The other thing about them is that because they are so dynamic, often expertise cannot keep up because the system is changing too fast. If you try to force these systems to become efficient, a it doesn't work and B you eliminate all of your margin for adaptation and response.
When you apply efficiency to a complex system you make them more dangerous.
It is really important in companies or products to understand what system you are in (right now). One system you want to manage to be efficient, one system you want to manage to be robust, that is where there is a margin for surprise.
A great example is whey you fly, lots of complicated systems such as checking your bag, lots off efficiency’s to be had through better technology. Once you get into the air there are lots of forces acting on the plane which are inherently unpredictable… the consequence of this unpredictability is that you build them to be robust, for instance running 4 engines on different operating systems, but they are robust so that if one of them fails. The impact of a tiny mistake.
You would never want to get onto a plane designed for efficiency — see what has happened to the Boeing 737MAX.
Our bias as humans is to force things towards a complicated frame, making them ever more efficient. If this frame is misdiagnosed, and you actually find yourself in a complex frame, the actions implemented may well be speeding your business towards disaster.
Let me know what you think? I’d love your feedback. If you haven’t already then sign up for a weekly dose just like this.
Get in touch… — linktr.ee/Tomconnor
More like this from 10x Curiosity
- Systems Archetypes- Places to intervene — An advantage with using systems archetypes as a problem solving methodology is that places to intervene in the system can be thought through and played with.
- Using system archetypes to shortcut problem solving — The use of systems thinking archetypes provide a powerful framework to approach problem solving.
- The Flywheel Effect
Exploring the power of simple reinforcing loops executed over time - Know your Domain — The Cynefin Framework
- Achieving Diversity — why being unbiased is not enough — Diversity is something we aspire to, but are we paying more than lip service to it? Are individual good intentions enough to achieve a diverse group setting, at work, socially or through the community?
