A Story of Unintended Consequences

Unintended Consequences: How to Prevent Good Changes from Backfiring

Many years ago, I came across an interesting story about a plant manager who was fed up with extremely high turnover at a factory on the U.S.-Mexico border.

“I’ve had enough!” he proclaimed against his staff’s advice. “We’ll just raise wages to be the highest in the area.”

The neighboring plant executives were none too pleased—this manager had significantly moved the needle on the prevailing wage rate and snatched some of their valued employees.

Yet three months later, the turnover more than doubled.

“How could this be?” thought the plant manager.

One day, a worker stopped him in the aisle to shake his hand and thank him: “Because of you, I do not have to work here for 6 months before returning to my hometown. I only had to be here for 3 months. I will be leaving tomorrow.”

The plant manager had failed to consider that cash was the key motivator for many migrant workers who were mostly transitory. The extra (unexpected) pay allowed workers to reach their savings goals sooner—and leave faster.

A well-intentioned change made the problem worse.

This is the danger of unintended consequences, and it happens far more often than most leaders realize. This guide will help you identify, prevent, and mitigate unintended consequences before your next improvement initiative backfires.

What Are Unintended Consequences?

Unintended consequences (sometimes called “unanticipated results” or “unforeseen issues”) are outcomes of a purposeful action that were not intended or foreseen when the decision was made.

The concept has been around since the late 1690s, when English philosopher John Locke wrote about how a law restricting interest rates might affect borrowers by discouraging lending.

In 1936, American sociologist Robert K. Merton of Harvard University popularized this concept in his review titled “The Unanticipated Consequences of Purposive Social Action,” where he identified five sources of unanticipated consequences, including ignorance and error.

Why This Matters for Process Improvement

Every improvement initiative—whether implementing Lean, deploying new technology, or restructuring a team—carries the risk of unintended consequences. The irony is that the more significant the change, the higher the likelihood of unforeseen outcomes.

Understanding this risk doesn’t mean avoiding change. It means anticipating and planning for side effects before they derail your improvement efforts.

The Three Types of Unintended Consequences

Not all unintended consequences are negative. Merton’s research identified three common categories:

Type 1: Unexpected Drawbacks

Definition: An unforeseen negative outcome that occurs in addition to the desired effect of the change.

Real-World Example:

In 1990, the Australian state of Victoria mandated that all bicyclists wear safety helmets. The overall number of head injuries did reduce significantly—the intended outcome was achieved.

But there was also an unintended reduction in the overall number of bicyclists:

Young riders thought helmets were “not cool”
Experienced riders were fed up with steep fines (and possible jail time)
Many gave up riding altogether

The policy achieved its safety goal but undermined the broader public health benefits of cycling.

Business Examples of Unexpected Drawbacks:

Cost-cutting measures that reduce quality and drive away customers
Automation that improves efficiency but creates new bottlenecks elsewhere
Standardization that improves consistency but stifles innovation
Remote work policies that improve flexibility but weaken team cohesion

Type 2: Unexpected Benefits

Definition: A positive, unplanned outcome that occurs alongside the intended benefit.

Real-World Example:

A warehouse operator installed new lighting with advanced motion-sensing controls to reduce energy costs. The motion-detecting sensors kept lights off when no forklifts were present in certain aisles.

The unexpected benefit: Forklift operators began working more confidently and faster. They could make turns or move quickly knowing there were no other forklifts or workers in the vicinity—the darkness signaled a clear path. Safety improved along with efficiency.

Business Examples of Unexpected Benefits:

Process documentation created for compliance reveals improvement opportunities
Cross-training programs for coverage purposes increase employee engagement
Customer feedback systems for service improvement generate product innovation ideas
Remote work tools deployed for pandemic response improve collaboration permanently

Type 3: Perverse Results (Making It Worse)

Definition: When trying to solve a problem, we make it worse—the opposite of the intended effect occurs.

This is exactly what happened to our plant manager. His solution (higher wages) directly accelerated the problem (turnover) he was trying to solve.

Business Examples of Perverse Results:

Incentive programs that reward individual performance but destroy teamwork
Quality inspections that slow production more than they reduce defects
Approval processes designed to prevent errors that create so much friction people circumvent them entirely
Customer satisfaction surveys that become so frequent they annoy customers

Why Unintended Consequences Happen

Understanding the root causes helps you prevent them:

Root Cause	Description	Example
Ignorance	Lack of knowledge about the system or stakeholders affected	Not understanding migrant workers’ savings goals
Error	Incorrect analysis or flawed assumptions	Assuming all employees are motivated by the same factors
Narrow Focus	Optimizing one metric while ignoring others	Reducing costs without considering quality impact
Short-Term Thinking	Focusing on immediate results, missing delayed effects	Quick fixes that create technical debt
Complexity Blindness	Underestimating system interconnections	Changing one process step without considering downstream effects
Overconfidence	Certainty that the solution will work as planned	Skipping pilot testing because “we know this will work”

How to Prevent Unintended Consequences

The good news: unintended consequences can be anticipated and mitigated with the right approach.

Strategy 1: Think Through Potential Impacts Before Acting

Use a structured checklist asking key questions about the project’s intent and activities:

Pre-Implementation Checklist:

Who will be affected by this change (directly and indirectly)?
How might each stakeholder group respond—positively and negatively?
What behaviors might this change encourage or discourage?
What could go wrong? What’s the worst-case scenario?
If this solution works perfectly, could it create new problems?
What assumptions are we making? How confident are we in them?
Have we seen similar changes fail elsewhere? Why?

Strategy 2: Expand Input to Include Multiple Perspectives

Seek input from stakeholders and subject matter experts (SMEs) who have different perspectives or expertise:

Frontline workers who will execute the new process
Customers (internal or external) who will experience the change
Adjacent teams whose processes connect to yours
Skeptics who can poke holes in your assumptions
People who’ve tried similar changes elsewhere

The plant manager in our story might have avoided his mistake by simply asking workers why they left—before implementing his solution.

Strategy 3: Use Structured Risk Assessment Tools

Don’t rely on informal brainstorming alone. Use structured tools to systematically identify and evaluate risks:

FMEA (Failure Modes & Effects Analysis)

FMEA is a structured approach to identifying potential failure modes, their causes, and their effects—before they occur.

For each potential failure mode, you assess:

Severity: How bad would it be if this happened?
Occurrence: How likely is it to happen?
Detection: How likely are we to catch it before it causes harm?

These scores combine into a Risk Priority Number (RPN) that helps prioritize which risks need mitigation.

Other Useful Tools:

Pre-Mortem Analysis: Imagine the project has failed—then work backward to identify what went wrong
Stakeholder Impact Analysis: Map how each stakeholder group will be affected
Second-Order Thinking: Ask “And then what?” for each expected outcome
Red Team Exercise: Assign someone to find flaws in the plan

Strategy 4: Pilot Before Full Implementation

Test changes on a small scale before rolling out broadly:

Select a representative pilot group
Define success criteria and monitoring metrics
Establish a timeline that allows effects to materialize
Gather feedback from all affected parties
Adjust based on learnings before scaling

Pilots reveal unintended consequences while the blast radius is still small.

Strategy 5: Monitor for Unintended Effects Post-Implementation

Even with thorough planning, some consequences only emerge over time. Build monitoring into your control plan:

Track metrics beyond your primary KPI
Solicit ongoing feedback from affected parties
Conduct post-implementation reviews at 30, 60, and 90 days
Create channels for people to report unexpected issues
Be willing to adjust or reverse course if needed

The Rest of the Story

What happened to our plant manager?

Eventually, he came to his senses. He went back to the original hourly wage model, then worked with his team on the underlying problem: attracting and retaining workers who wanted to remain in the area.

They improved overall compensation by strengthening benefits:

Subsidizing the cafeteria
Adding nursery daycare vouchers
Creating a better dental and vision health plan
Other incentives that rewarded long-term commitment

This solution addressed the root cause (workers needed comprehensive support, not just cash) rather than making assumptions about what motivated employees.

Unintended Consequences Across Industries

Healthcare

Risk: Reducing appointment times to see more patients → rushed care, misdiagnoses
Risk: Electronic health records for efficiency → increased documentation burden on clinicians
Prevention: Pilot changes, measure patient outcomes alongside efficiency metrics

Manufacturing

Risk: Reducing inventory to cut costs → stockouts and production delays
Risk: Automating quality inspection → operators become less vigilant about quality
Prevention: FMEA analysis, cross-functional review of proposed changes

Financial Services

Risk: Automating loan decisions for speed → bias in algorithms affects certain customer groups
Risk: Reducing branch locations → alienates customers who prefer in-person service
Prevention: Stakeholder impact analysis, diverse review teams

Key Takeaways

When we act to bring about change, our actions could result in pleasantly positive or perversely negative consequences. But we can mitigate—or at least be cognizant of—unplanned results by:

Thinking through potential side effects before implementing changes
Gathering diverse perspectives from those who will be affected
Using structured tools like FMEA to systematically identify risks
Piloting changes before full-scale rollout
Monitoring broadly after implementation—not just your primary metric

The goal isn’t to avoid change—it’s to implement change with eyes wide open to what might go wrong.

Build Your Risk Assessment Skills

Option 1: Learn FMEA
Master the tools for identifying and preventing failures with our Demystifying FMEA course at OpExecs Academy.

Option 2: Evaluate and Prioritize Risks
Learn structured approaches to risk assessment with our Evaluate, Prioritize and Abate Risks course—essential for any project leader.

Option 3: Get Expert Support
Planning a major change initiative? Schedule a meeting with our team to discuss how OpExecs can help you anticipate and prevent unintended consequences.