The Hidden Risk of Optimization
Executive insight
Organizations often optimize around the systems, customers, technologies, and assumptions that made them successful. That optimization creates performance — until the context changes.
The leadership challenge is not simply improving what already works. It is recognizing when yesterday’s strengths have become tomorrow’s constraints.
Optimization is usually treated as good leadership.
Leaders improve processes, reduce variation, clarify roles, build repeatability, and strengthen what works. Those disciplines create efficiency, consistency, and performance.
But optimization has a hidden risk: it embeds assumptions.
It trains the organization around a specific set of customers, technologies, economics, workflows, incentives, and definitions of success. When the environment is stable, that can be a strength. But when the environment changes, optimized processes can fuel rigidity.
The problem is not that the organization failed; the problem is that it succeeded long enough for yesterday’s logic to become deeply embedded.
It reminds me of Clayton Christensen’s central warning in The Innovator’s Dilemma: “even the most outstanding companies can do everything right — yet still lose market leadership.”[1]
Sometimes the things that made an organization successful are the same things that make its next stage difficult.
Local success creates enterprise friction
I saw this pattern recently while facilitating a workshop for engineering leaders whose businesses had come together through acquisition.
Each of these former operating companies had developed its own way of working: tools, terminology, file structures, spreadsheets, titles, resource practices, customer commitments, and management habits. Those processes had helped each company move quickly and serve their customers well.
But the parent company was no longer managing a collection of separate companies. It was building an enterprise that needed shared resources, better visibility, consistent data, and a larger growth platform.
The context had changed.
What once created local speed now created enterprise friction.
Leaders could not easily compare data across business units. Engineers could not easily find documentation. Resource sharing was difficult. Titles and expectations varied. Workload could not be balanced across the enterprise because there was no common way to see or describe the work.
The issue was not that these business units had bad processes; it was that they had been optimized for independence in an organization that now needed integration.
Market shifts expose hidden rigidity
The same pattern appears when markets change.
I once worked with a large, publicly traded oilfield exploration and production company whose operations had been optimized around diesel pumping. The company had built equipment purchasing, maintenance practices, vendor relationships, workforce skills, logistics, pricing assumptions, and operating rhythms around that model.
Then customer expectations began to shift. Oil and gas majors were looking for cleaner technologies to reduce their ESG footprint. With lower emissions and operating costs, natural gas and electric pumping options were becoming more attractive.
The company was not simply evaluating a switch to cleaner equipment; it was confronting the limits of an operating model that had worked long enough to feel like it was core to the business itself.
As I worked with their leadership team, the strategic question evolved: “Are we optimized around work customers still need — or around work we already know how to do?”
The system remembers what made it successful
Organizations do not become rigid because people dislike change.
They become rigid because the system is optimized around what made it successful.
Processes reinforce it. Metrics reward it. Skills develop around it. Customers expect it. Managers defend it. Capital plans extend it. Culture explains why it matters.
That’s why change can feel irrational to people inside the system: from where they sit, the old model is not obsolete — it is well proven.
Systems thinkers have long observed that structure drives behavior.[2] People often act in ways that make sense given the incentives, constraints, and feedback loops around them. When leaders misread that behavior as resistance, they miss the deeper issue.
Resistance is simply the system defending the logic it was optimized around.
And it means leaders have to discern when the context has changed enough that the organization must be optimized differently.
Knowing when to re-optimize
The answer is not to abandon discipline, consistency, or efficiency, but to understand what the organization is optimized for:
For independence or integration?
For today’s customer or tomorrow’s market?
For local performance or enterprise visibility?
For utilization or adaptability?
For cost control or strategic flexibility?
The danger is not the act of optimization itself; it's in continuing to optimize for conditions that no longer drive success.
This is where leadership requires discernment.
Leaders have to notice when a strength is becoming a constraint, when local success is creating enterprise friction, and when operational excellence is reinforcing a model customers are beginning to move beyond.
The work of leadership is not simply to make the current system perform better.
It is to know when the system itself needs to change.
References
[1] Clayton M. Christensen, The Innovator’s Dilemma: When New Technologies Cause Great Firms to Fail, Harvard Business School Press, 1997.
[2] Donella H. Meadows, Thinking in Systems: A Primer, Chelsea Green Publishing, 2008.
