It started with a subtle shudder under the hood—right as the green “ECO” light flickered on in the instrument cluster.

Because I work on my own vehicles, I skipped the dealership line and pulled the data myself. That rabbit hole led straight to Variable Cylinder Management (VCM)—a clever answer to fleet efficiency standards. The pitch was simple: Why fire six cylinders when you only need three?

It sounds great in a board meeting. In execution, it’s an engineering farce.

Shutting off half a V6 on the highway creates a violent mechanical imbalance. To fix the vibration, engineers added active, fluid-filled electronic engine mounts. To hide the cabin drone, they added active noise-canceling audio profiles. But to handle the long-term mechanical strain? They didn’t. Dragging cold, uncombusted cylinders down the interstate just to keep a green light glowing leads to oil consumption, fouled spark plugs, misfires, and premature engine failure.

We optimized a laboratory metric, but we wrecked the system.

When a measure becomes a target, it ceases to be a good measure.

VCM isn’t an isolated mistake; it’s the design language of modern automotive engineering:

• Direct Injection improves fuel metering, but starves intake valves of washing spray, clogging them with carbon.

• EGR valves reduce NOx, but deliberately route dirty exhaust back into clean air intakes.

• Start-Stop systems save a drop of gas at a red light, while putting thousands of brutal heat cycles on starters and batteries.

When compliance hinges on a single tailpipe number in a sterile lab, manufacturers don’t engineer for a 200,000-mile vehicle. They engineer to pass a cycle.

Meanwhile, the owner inherits a fragile ecosystem where an engine can suffer catastrophic ring failure at 45,000 miles. The environmental cost of manufacturing a replacement engine completely wipes out a decade of fractional fuel savings.

Beyond the Garage: A Universal Failure Mode

This isn’t just an automotive problem—it’s an organizational one.

Whether you are tuning an engine to pass a test cycle or driving an enterprise team toward an isolated KPI, the trap is identical:

• Measure sprint velocity, and you get rushed code loaded with technical debt.

• Measure support handle time, and you get unresolved tickets shuffled across queues.

• Measure deployment frequency, and you push fragile microservices that collapse under load.

When leadership manages to a proxy metric instead of the health of the whole ecosystem, short-term performance looks stellar. The compliance team pops champagne. But eventually, the customer or the downstream team inherits the system failure.

Before celebrating the next breakthrough metric—in engineering or in business—we have to ask: What complexity did we force into the system? What new failure modes did we invent? And who pays for it when the warranty expires?

Engines don’t live on a chassis dynamometer, and platforms don’t live in a presentation deck. They live in production.

And right now, we keep optimizing the metric while punishing the machine.

Sami Joueidi holds a Master’s degree in Electrical Engineering and brings over 15 years of experience leading AI-driven transformations across startups and enterprises. A seasoned technology leader, Sami has led customer adoption programs, cross-functional engineering teams, and go-to-market strategies that deliver real business impact.

He’s passionate about turning complex ideas into practical solutions, and about helping teams bridge the gap between innovation and execution. Whether architecting scalable systems or demystifying AI concepts, Sami brings a blend of strategic thinking and hands-on problem-solving to every challenge. © Sami Joueidi and www.cafesami.com, 2025. Feel free to share excerpts with proper credit and a link back to the original post.