Stop Choosing Between Efficiency and Empathy
Two people are staring at the same failing project. The operations lead sees chaos: no standard, no metric, no discipline — we need to tighten this up. The design lead sees something deader: nobody asked the user, nobody owns it, there’s no pulse — we need to make people actually care.
They are both right. And they will spend the next six months each convinced the other one is the problem.
I know this argument from the inside, because I was raised bilingual in it. Thirteen years in Lean, much of it beside a Kaizen master; eight years in Design Thinking, beside one of the people who built a school of it. Two lineages that are supposed to despise each other, learned by the same pair of hands. And the longer I worked in the gap between them, the more obvious one thing became: the choice everyone agonises over — rigour or humanity, efficiency or empathy — was never a real choice. It is a category error, and it has killed more good ideas than incompetence ever has.
Before the theory, get your hands on it. Here are both disciplines whole, the way their founders actually built them — now cut each down to the half everyone remembers:
Two disciplines, whole — exactly as their founders built them.
Now do what each tribe quietly did: cut the other half away. ✂
You just did what the tribes did. You didn’t weigh two disciplines against each other — you took two whole ones, cut each in half, and the leftovers are the famous enemies: the cold robot and the airy workshop. The entire “efficiency versus empathy” war lives in those amputated halves, and nowhere else. Put the pieces back and it dissolves. The rest of this piece is just that, slowly — so let me show you each cut, and what it really costs.
The two tribes, and the cartoon each keeps of the other
The split is old and tribal. On one side, the efficiency people: Lean, Six Sigma, process maps, the relentless war on waste. On the other, the empathy people: Design Thinking, human-centred design, the user interview, the wall of sticky notes. Each tribe carries a caricature of the other in its back pocket. To the efficiency camp, the design people run a lovely workshop and never ship. To the design camp, the efficiency people are cold robots optimising a spreadsheet no human wants to live inside.
Here is the part that should end the war: both disciplines were born whole, and each tribe quietly amputated half of its own founding doctrine.
Lean was always half empathy. The efficiency tribe forgot a pillar.
Ask most people what Lean is and you’ll hear “cut waste, raise throughput.” But the actual house Toyota built — the Toyota Way, the source code for everything we now call Lean — stands on two pillars, not one. The first is Continuous Improvement. The second, equal pillar is Respect for People. Toyota is blunt about the dependency: improvement without respect for people isn’t sustainable, and respect without improvement isn’t Toyota. The efficiency tribe kept the first pillar, framed it on the wall, and let the second one rot in the basement.
And it was never a poster slogan. Lean’s most sacred working habit is genchi genbutsu — “go and see.” The instruction to a leader is not read the report; it is get up, walk to where the work actually happens, and watch a real person do it with your own eyes. That is empathy, operationalised into a manufacturing religion. The rule around it was reportedly unforgiving: a leader who looked down on the people on the floor was gone. The most ruthless efficiency system humanity has ever built runs on standing inside another person’s reality. Lean was never not empathy. Half the tribe just stopped reading after chapter one.
Design Thinking was always two-thirds rigour. The empathy tribe forgot the other lenses.
Now the other side. Design Thinking gets caricatured as feelings and Post-its, but its own foundational model is a Venn diagram of three lenses, and only one of them is about empathy. IDEO’s own definition — Tim Brown’s — integrates “the needs of people, the possibilities of technology, and the requirements for business success.” In the language everyone learns on day one: desirability (do people want it?), feasibility (can we actually build it?), and viability (does it make economic sense?). The famous “sweet spot” is the small overlap where all three are true at once.
Desirability is the empathy lens. Feasibility and viability are pure execution and economics — can we ship it, will it pay. Two-thirds of Design Thinking, by its own definition, is rigour. So when a Design Thinking effort produces a moving insight that then dies in the room, that is not Design Thinking working — it is Design Thinking with two of its three lenses unscrewed. The empathy tribe kept desirability and quietly dropped the parts that would have forced the idea to survive Monday.
Set those two facts side by side and the whole turf war collapses. Lean already contains empathy. Design Thinking already contains rigour. Neither discipline ever asked you to choose — the tribes did. The fight was never between two methods. It is between two amputations.
You see the whole everywhere mastery shows up
This isn’t a management curiosity. The fusion of rigour and empathy is the fingerprint of mastery in almost any field where two supposedly-opposite virtues meet — and once you go looking, the half-versions are painfully easy to spot.
A surgeon with flawless technique and no human warmth is a butcher with good outcomes; one with warmth and no technique is a chaplain. You need the one who has both, and you can feel the difference the moment they walk in. A teacher with a rigorous curriculum but no eye for the kid in the third row never lands it; a teacher who sees every child but has no structure never teaches. A jazz musician is ten thousand hours of brutal technical discipline and the feel to break every rule on purpose — drop either and it’s noise, or it’s a scale. Even a bridge is the engineer’s load calculations and the plain human fact that someone has to want to walk across it. In none of these is it a trade-off on a dial. In each, it is one whole craft — cut either half away and what is left is a competent fragment that fails.
So why does the split survive?
If both halves are so obviously necessary, why do organisations keep buying one at a time? Because each half is easier to sell alone. Efficiency comes with a number — a percentage, a saving, a chart that goes up — so it is fundable, and a finance committee can approve it. Empathy comes with a feeling, which is real but doesn’t fit on the slide, so it gets bought as a one-off “innovation workshop” and quietly defunded the quarter things tighten. The org chart, the budget line and the procurement form all reward the half you can measure. So companies buy the amputated Lean or the amputated Design Thinking — and then, predictably, conclude that the other discipline was the thing that didn’t work.
It is the same failure I keep meeting from different angles: the recommendation that never becomes a result, the workshop mistaken for the work. Underneath all of them sits this one mistake — treating two halves of a single craft as rival teams.
Two questions, on anything you ship
You don’t need to pick a camp, and you certainly don’t need to buy another framework. You need to refuse the choice — and you can check whether you have, on any change you’re trying to make, with two questions.
One: is it rigorous enough to run without you? Is there a standard, a number, a clear owner — something that carries the idea after the energy in the room is gone? If not, you’ve built a feeling. Two: did the people who have to live with it help build it, and do they actually want to? Or are you about to install something correct that they’ll route around by Tuesday? If not, you’ve built a cost.
A “yes” to one and a “no” to the other isn’t a near miss. It is the two amputated halves you made above — and each fails just as completely as a flat no to both. Efficiency nobody adopts is an expensive way to fail. Empathy that doesn’t ship is a nice memory. The only thing that survives contact with a real team is the whole: a process precise enough to trust, built with the people closely enough to own it.
That is the secret neither tribe will tell you, because each is invested in being the half that matters. They are both wrong in exactly the same way. Stop choosing. You were never supposed to.
Want to know which half your organisation is missing? That’s exactly what the Innovation Mirror surfaces — whether your change has the rigour to run and the ownership to stick. Or let’s build the whole thing, not half of it.
Keep reading
Cascades: The Shape of Everything That Scales
From the shopfloor to the boardroom, from Lean huddles to agile Flight Levels, I kept meeting the same move — and it turns out your lungs, the internet and every army use it too. Cascades: break the whole into nested levels, push each decision to the lowest one that can make it, let only the exception travel. Why it's how complexity gets tamed — and how it rots into bureaucracy. With a small thing to try.
8 min readAI Made Building Free. Taste Is the New Bottleneck.
Andrej Karpathy can build an app in an hour, in a language he doesn't know. When anyone can build anything, why is so much of it still worthless? Because building was never the hard part — and now that it's free, the one scarce thing left is taste: knowing what's worth building, what "good" is, and what to cut. With a small test you can feel.
7 min readWhen "Fail Fast" Is Malpractice
"Move fast and break things" is the best advice in the world — until the thing you'd break is a patient, a balance sheet, or a number nobody can take back. Why "fail fast" is only half a sentence, what Bezos's one-way doors have to do with it, and how the best high-stakes teams keep the speed without the recklessness. With a small experiment you can feel.
7 min read