You can optimize a component of a system to near-perfect efficiency while the system as a whole gets worse.
The engineering team cuts cycle time in half. Customer satisfaction is at an all-time low.
The sales team closes more deals than any quarter on record. Net revenue retention is in decline.
The plant runs at 98% equipment efficiency. The plant is losing money.
This is local optimization — one of the most common structural failures in organizations. It produces clear, attributable wins while the system-level damage is diffuse and hard to connect to any single cause. It feels like winning. Usually, it isn't.
How to Know You're Inside One
Strong team metrics, weak overall outcomes. The team hits every internal target. The company's results don't reflect it. This gap is the signal — the team's definition of winning has diverged from the system's definition.
"We did our part." This phrase is a red flag. If your part is good and the outcome is bad, either your part wasn't actually what the system needed, or the system has problems that aren't visible from your vantage point.
The constraint is elsewhere. If your team has spare capacity and the system isn't improving, the constraint isn't in your team. Harder optimization of your resources just produces more queue in front of the real bottleneck — and increases the system's dependence on a non-critical path.
