The Legacy of Fake Innovation: Why Efficiency Isn’t Enough Anymore

Companies spent the last couple decades getting really good at efficiency. They moved work offshore, flattened headcount, tightened up operations. Leaders talked about “doing more with less” as if it were a strategy rather than a temporary condition. Margins improved, and for a while that seemed like enough. 

The problem is that much of what passed for innovation during this period wasn’t innovation at all. It was optimization. We got better at doing the same things cheaper and faster without actually rethinking whether we should be doing those things at all.

That mindset built organizations that are very good at efficiency—and increasingly bad at reinvention.

When Cost-Cutting Became the Stand-In for Progress

The outsourcing boom of the late 1990s and early 2000s is a useful place to start. Moving back-office operations overseas was hailed as forward-thinking. Technology made it possible and labor arbitrage made it attractive. Shareholders rewarded it.

Here's what nobody really stopped to ask: Does this work need to exist in its current form? Because the processes themselves didn't change. The complexity didn't change. The only thing that changed was who was doing the work and how little we could pay them for it. We didn’t reinvent the model; we wrapped it in better connectivity and called it progress.

That pattern repeated itself over and over again. Legacy systems were “modernized” by bolting on new tools. Data pipelines were “transformed” by layering more orchestration on top of shaky foundations. Entire technology strategies became exercises in making old assumptions run faster.

Efficiency became the safest version of innovation because it didn’t threaten existing power structures or ways of working. You could point to measurable gains without challenging the core of how the organization operated. Now we’re living with the consequences.

Organizations Built to Trim, Not to Change

The skills rewarded in that era shaped today’s leadership benches. Many organizations are led by people who know how to optimize a system, negotiate contracts, and squeeze waste out of operations. Fewer have experience rebuilding something from first principles once it stops serving its purpose.

When new demands emerge—real-time decisioning, AI-driven workflows, platform ecosystems—the instinct is often to ask how existing infrastructure can be stretched to support them. Teams are told to “make it work” with what’s already in place. 

Over time, the organization becomes very good at surviving change without ever truly adapting to it.

The irony is that the habits that once drove success often end up holding progress hostage. Systems built to prize stability make experimentation feel risky, processes designed to eliminate variance start to strain when change becomes constant, and people who’ve been rewarded for avoiding disruption gradually learn to fear it rather than work with it.

The Comfort Trap of “Good Enough” Systems

One of the most dangerous legacies of fake innovation is complacency. Systems that mostly work create a powerful illusion of adequacy. The dashboards still refresh, the reports still go out, customers aren't complaining loudly enough to trigger any alarms. So the natural conclusion is that things must be basically fine.

Nothing breaks. That’s the problem. Things just slow down. Momentum fades because no one wants to be the one who triggers a mess.

When organizations get used to that level of friction, they eventually stop asking whether their systems enable the kind of ambition they claim to have, or whether those systems put a ceiling on what's possible.

Real Innovation Starts With Unlearning

True transformation begins with letting go. It starts when leaders admit that some of the ideas they’ve been protecting—about speed, stability, and efficiency—aren’t helping anymore.

This is the hard part. New technology is easy to justify. Rethinking long-held assumptions isn’t. It means asking leaders to revisit what made them successful and asking teams to let go of processes they’ve already mastered. It also means accepting a lot more uncertainty than most efficiency-driven cultures are comfortable with.

That discomfort is the signal that something meaningful is happening.

The organizations that seem to be handling this moment better aren’t chasing novelty for its own sake. They’ve simply accepted that change is part of the operating environment and stopped pretending their systems can remain static. When that tension eases, teams spend less time protecting what exists and more time building what comes next.

Moving Into the Next Era

Cutting costs used to look like discipline. That’s not what separates companies now. What matters is whether the organization can change direction without triggering a mess somewhere else. When it can’t, speed and ambition don’t really matter.

Efficiency had its moment. It solved real problems for a different time, but the habits it left behind are no longer enough.

This is the problem EASL was built to address. Not efficiency for efficiency’s sake, but the structural drag that keeps organizations locked into past assumptions. When systems penalize change, teams default to maintaining what exists. When change becomes easier to absorb, people start building again.

If this tension feels familiar, it’s explored more fully in “Caveat Innovator,” which looks at how status-quo thinking took hold and why adaptability, not optimization, is now the real constraint.

Website blurb

Efficiency built disciplined organizations. It also built organizations that struggle to reinvent themselves when the world demands it. In this piece, we trace how fake innovation took hold and why the skills that drove success for decades are now holding progress hostage.