Setting ambitious goals is an essential part of business strategy. Companies push for innovation, higher performance, and competitive advantage every day. But when leadership sets expectations that employees believe are impossible to achieve legally, those goals transform into severe enterprise risk.
When Volkswagen set out to become the world’s largest automaker, engineers faced intense pressure to deliver on “clean diesel” vehicles that met strict US emissions standards without sacrificing power or fuel economy.
What followed became a $30 billion lesson in operational failure: engineers modified software to deceive regulators during testing, leading to massive fines, criminal charges, and lasting reputational damage.
While the software manipulation was executed by technical teams, the crisis was driven by systemic failures across the organization. I use Dr. Mark Abkowitz’s Operational Risk Management framework to evaluate the Volkswagen ERM case study.
1. Economic Pressures
Organizations often rely on financial incentives to drive growth, but unmanaged economic pressure breeds extreme operational risk.
Volkswagen’s corporate leadership established an aggressive strategic initiative (Strategy 2018) to overtake Toyota as the world’s largest automaker. Winning over the US passenger car market via “clean diesel” was the financial cornerstone of this strategy. When executive compensation, market share targets, and corporate dominance depend on a single product line, teams face immense pressure to deliver revenue targets at all costs.
The ERM Takeaway
Aggressive growth targets lose their value when disconnected from operational reality. When leadership demands market dominance without acknowledging technical constraints, teams will bridge the performance gap through unmanaged risk.
2. Design & Construction Flaws
A process designed without built-in verification safeguards will inevitably fail when put under pressure.
The underlying EA189 diesel engine architecture was fundamentally incapable of meeting US emissions limits while delivering advertised performance. Rather than redesigning the engine hardware or incorporating costly urea-injection systems, engineers designed a software-based “defeat device.” The engine system was constructed with code that detected when a test was occurring and temporarily dialed down emissions, creating a flawed system built on deliberate deception.
The ERM Takeaway
Product architectures must embed compliance controls directly into technical validation. If a system allows performance metrics to be simulated or bypassed without independent verification, structural failure is inevitable.
3. Scheduling Constraints
Unrealistic deadlines and tight timelines force employees to take shortcuts, compromising quality and compliance.
The launch window for Volkswagen’s new US diesel fleet was fixed and uncompromising. As the 2008 launch date approached, technical teams realized they could not resolve the emissions-performance trade-off through standard engineering within the allotted timeframe. Rather than admitting delay and missing critical market entry deadlines, the extreme schedule crunch drove teams to deploy cheat software as a shortcut to meet the launch date.
The ERM Takeaway
Fixed launch milestones must remain adaptable when technical red flags surface. When project schedules override compliance validation, rigid timelines force teams to convert engineering bottlenecks into enterprise-level crises.
4. Communication Failure
When risk warnings and technical bad news are suppressed within an organization, critical vulnerabilities compound in the dark.
Internal warnings about the illegality of the defeat software were raised by engineers and external suppliers as early as 2007. However, Volkswagen’s high-pressure culture prevented these critical warnings from escalating up the chain of command. Instead of reaching the Board of Directors or risk committees, technical red flags were buried within lower-level engineering divisions for nearly a decade.
The ERM Takeaway
An ERM program is only as effective as the organization’s psychological safety. If bad news is penalized and teams fear escalating technical barriers, critical compliance risks will remain buried until public exposure occurs.
5. Arrogance
Overconfidence in an organization’s reputation or past success often blinds leadership to critical warnings.
Volkswagen operated under a culture of engineering superiority and executive overconfidence. Leadership believed their technical systems were clever enough to permanently evade detection by US regulators like the EPA. Even when independent researchers at West Virginia University published findings in 2014 showing real-world emissions were up to 40 times legal limits, executive leadership brushed off the red flags as minor technical anomalies rather than addressing the systemic deception.
The ERM Takeaway
Technical capability and industry stature do not grant immunity to operational failure. Effective enterprise risk management requires leadership humility, treating third-party findings and anomalous data as vital risk intelligence rather than inconvenient noise.
Balancing Ambition with Operational Reality Using ERM
High-stretch strategic goals must always be balanced with technical feasibility and risk-adjusted metrics. To prevent aggressive objectives from creating catastrophic enterprise risk, risk managers and executives should evaluate four critical questions before greenlighting major initiatives:
- Technical Feasibility: Are these performance and compliance targets realistically achievable with current hardware, technology, and budget constraints?
- Verification Controls: What independent testing and system validation controls exist to catch simulated, bypassed, or manipulated compliance results?
- Objective Alignment: Are engineering teams incentivized for long-term product integrity and regulatory compliance, or purely for meeting aggressive performance KPIs and unit costs?
- Psychological Safety: Do engineers and technical leads have safe, penalty-free channels to escalate unviable timelines or technical roadblocks to executive leadership?
Effective Enterprise Risk Management does not just measure strategic output. It continuously evaluates the technical assumptions, operational constraints, and organizational culture required to achieve results safely.