Organisations confuse two fundamentally different types of simplicity when it comes to efficiency: the simplicity that emerges from deep understanding, and the simplicity that comes from not knowing enough yet. One creates clarity. The other creates problems you won’t see until it is too late.
The Mechanic’s Hammer
You have probably heard the story: A ship’s engine fails. A mechanic arrives, studies it briefly, taps one spot with a hammer, and the engine roars back to life. The bill: $10,000. Two dollars for the tap, $9,998 for knowing where to tap.
This story validates what leaders want to believe, that expertise looks effortless, that the right decision cuts through complexity instantly, and that analysis can be replaced with instinct.
What gets lost is that the mechanic spent decades learning how engines work.
The efficiency was not inherent; it was earned.
When organisations try to replicate this principle without the foundation, they get leaders who mistake hunches for informed judgment. They get strategies that work on paper but fail in practice.
Why Organisations Skip the Hard Part
Real efficiency requires something most organisations resist: extended time in complexity before achieving simplicity.
Genuine expertise means learning the rules, the exceptions, the exceptions to the exceptions. It means staying with ambiguity long enough to understand which factors actually matter and which just look important. This process is slow, expensive, and impossible to measure on quarterly timelines.
So organisations shortcut it. They hire for strategic thinking without building operational knowledge. They demand innovation from people who have not yet understood what currently exists. They celebrate leaders who move quickly while quietly managing the fallout.
The result is decisions that appear decisive but lack foundation, efficiency that is really incomplete thinking, and simplicity that reflects ignorance rather than mastery.
What Real Efficiency Actually Requires
When experienced practitioners make complex situations look simple, they are not accessing intuition or magic. They are running compressed pattern recognition, their minds scanning years of accumulated experience to identify what actually matters in this specific situation.
This compression requires something to compress. The doctor who diagnoses a rare condition in seconds has examined thousands of patients. The developer who fixes a bug by deleting code understands the entire system well enough to know what is structural and what is not.
The implication is that if you want your organisation to operate with this kind of efficiency, you must invest in the accumulation phase. That means accepting periods where people learn more than they produce. It means valuing depth alongside speed. It means recognising that the person who asks multiple questions before acting is not slow; they are building the foundation that makes intelligent action possible.
The Bottom Line
Before celebrating efficiency gains, ask: Is this simplicity born from understanding or from not knowing what we don’t know?
One earns the right to use the small hammer. The other just hopes the tap lands somewhere useful.
Want your leadership team to think and act differently?
Our facilitation, workshops and keynotes help leadership teams face hard questions and leave with decisions.
Explore Leadership Facilitation & Capability