Open with whack-a-mole reality.

Picture this: You’ve just spent six months and significant resources eliminating your production bottleneck. The celebration is short-lived. Within weeks, customer service is overwhelmed, creating a new constraint that’s throttling your entire operation. You fix that, and suddenly your sales team can’t generate enough qualified leads. Welcome to the whack-a-mole reality of constraint migration—the universe’s way of reminding us that optimization is never “done.”

I first encountered this phenomenon at a manufacturing company where we’d brilliantly solved our assembly line bottleneck. We were so proud. Production capacity increased by 40%. Then our warehouse couldn’t handle the volume. Fixed that. Then our shipping department became the constraint. Fixed that. Then our invoicing system couldn’t keep up. It felt like playing an endless game where winning one round just started another, harder round.

That’s when I realized: Constraint migration isn’t a problem to solve—it’s a reality to manage. In fact, it’s proof your transformation is working. Every time a constraint moves, it means you’ve successfully improved one part of your system. The challenge isn’t preventing constraint migration; it’s anticipating it, preparing for it, and using it to drive continuous improvement.

Predictive Constraint Management

The secret to managing constraint migration is shifting from reactive to predictive mode. Most companies chase constraints after they appear. Smart companies see them coming and prepare. Here’s how I learned to predict where constraints would migrate before they became critical.

At a consumer goods company, we developed what I called the “Constraint Migration Map.” Before addressing our primary packaging bottleneck, we asked: “If we solve this, where will the constraint move?” We identified three likely destinations:

• Raw material supply (if production increased 40%)
• Quality control (if throughput exceeded inspection capacity)
• Distribution center capacity (if daily shipments increased)

We then prepared for each scenario while addressing the primary constraint. When packaging capacity improved by 45%, the constraint did migrate to quality control—but we were ready. We’d already cross-trained additional inspectors, implemented inline quality checks, and established overflow protocols. What could have been a crisis became a smooth transition.

The Theory of Constraints tells us that every system must have a constraint that limits its output. But it doesn’t tell us that constraints have personalities and patterns. Through dozens of transformations, I’ve identified predictable migration patterns that help you stay ahead of the game.

Systematic Approach to Constraint Evolution

Managing constraint migration requires a systematic approach that goes beyond traditional bottleneck analysis. Here’s the framework I’ve refined through years of chasing constraints:

Phase 1: Constraint Mapping

Before touching any constraint, map your entire value stream and identify:

• Current constraint location and impact
• Upstream dependencies that could become constraints
• Downstream processes that assume current flow rates
• Support functions sized for current capacity
• External constraints (suppliers, customers, regulations)

At a food manufacturer, our constraint map revealed 14 potential migration points. This wasn’t discouraging—it was empowering. We knew exactly where to look when constraints moved.

Phase 2: Capacity Analysis

For each potential constraint location, calculate:

• Current capacity utilization
• Capacity at projected post-improvement flow rates
• Investment required to prevent constraint migration
• Time required to expand capacity
• Alternative approaches to manage increased flow

This analysis reveals your “constraint cliff”—the point where each process becomes the new bottleneck. At an electronics manufacturer, we discovered their customer service would become constrained at exactly 127% of current production. We hired and trained new service reps while improving manufacturing, preventing the migration crisis.

Phase 3: Migration Triggers

Identify what will trigger constraint migration:

• Volume increases beyond threshold levels
• Mix changes that stress different resources
• Seasonal patterns that shift constraints
• External changes (supplier issues, demand spikes)
• Technology or process changes

Understanding triggers lets you implement early warning systems. At a distribution company, we installed simple visual indicators showing when any process approached 85% capacity—our signal to prepare for potential constraint migration.

Phase 4: Preemptive Strengthening

This is where predictive management becomes powerful. Instead of waiting for constraints to migrate, we strengthen likely destination points before addressing the primary constraint. It’s like reinforcing the next section of dam before releasing more water.

Key strategies for preemptive strengthening:

• Build flexible capacity in likely constraint areas
• Cross-train personnel across multiple processes
• Establish overflow protocols and partnerships
• Create modular systems that can scale quickly
• Develop constraint-breaking technologies in advance

Identification and Preparation Methods

Through trial and expensive error, I’ve developed specific methods for identifying and preparing for constraint migration:

The Load Test Method

We simulate post-improvement flow rates through downstream processes before implementing improvements. At a pharmaceutical company, we ran mock schedules showing what would happen if tablet production increased 50%. The simulation revealed that packaging would fail catastrophically at 40% increase. We upgraded packaging capability first, then improved tablet production.

The Weak Link Analysis

Every process has a weakest link that’s not yet the constraint. We identify these by asking:

• What process is closest to capacity?
• What resource has the least flexibility?
• What area has the highest variability?
• Where do small disruptions cause biggest impacts?
• What depends on single points of failure?

These weak links are prime candidates for constraint migration. Strengthen them proactively.

The Migration History Pattern

Constraints often follow patterns based on your industry and business model. In manufacturing, the typical pattern is: Production → Quality → Packaging → Shipping → Order Processing → Customer Service → Sales → Product Development → Back to Production

In software companies: Development → Testing → Deployment → Infrastructure → Customer Support → Sales → Product Management → Back to Development

Understanding your industry’s pattern helps predict where constraints will migrate next.

The Economic Order Analysis

Sometimes constraint migration isn’t about capacity—it’s about economics. As you improve throughput, the economics of different processes change. What was acceptable at lower volumes becomes prohibitively expensive at higher volumes.

We calculate the “economic constraint point” for each process—the volume where unit costs make that process economically unviable. At a logistics company, we discovered that our current routing system would become economically constrained at 150% of current volume due to inefficient algorithms. We implemented new routing technology before hitting that threshold.

Constraint Migration Patterns

After managing dozens of constraint migrations, I’ve identified consistent patterns that help predict and prepare for transitions:

Pattern 1: The Cascade Effect

When you dramatically improve a major constraint, multiple downstream processes often become constrained simultaneously. It’s not whack-a-mole—it’s whack-all-the-moles-at-once.

At a chemical plant, solving our reactor bottleneck increased output by 60%. Suddenly, storage, quality testing, packaging, and shipping all became constrained simultaneously. We’d prepared for single-point migration, not cascade migration. Now we always prepare for cascade scenarios when improvements exceed 30%.

Pattern 2: The Pendulum Swing

Constraints often migrate between operations and support functions. Fix operations, and support becomes constrained. Strengthen support, and operations becomes the bottleneck again.

A software company exemplified this pattern:

• Development was constrained → Fixed it
• QA became constrained → Automated testing
• Development constrained again → Improved processes
• DevOps became constrained → Built CI/CD pipeline
• Development constrained again → Hired more developers

Recognizing the pendulum pattern helps you prepare both sides for alternating improvements.

Pattern 3: The Hidden Constraint Emergence

Sometimes solving a visible constraint reveals hidden constraints that were masked by the primary bottleneck. These are particularly dangerous because they’re unexpected.

At a retail chain, our distribution center constraint masked a critical IT system limitation. When DC throughput improved, the ordering system crashed under increased transaction volume. Always ask: “What hidden constraints might emerge when we improve flow?”

Pattern 4: The External Migration

Constraints don’t respect company boundaries. Improve internal operations enough, and constraints migrate to suppliers or customers. A manufacturer improved production by 80%, only to discover their key supplier couldn’t provide raw materials fast enough. Now we map external constraints as carefully as internal ones.

Pattern 5: The Skill Constraint Shift

As physical constraints are resolved, human skill constraints often emerge. An aerospace company eliminated equipment bottlenecks only to discover they didn’t have enough skilled technicians to operate at higher capacity. Technical constraints often migrate to human constraints.

Migration Planning Tools

Over the years, I’ve developed specific tools that help organizations plan for constraint migration:

The Constraint Migration Matrix

This tool maps current constraints against potential migration points, showing:

• Probability of migration (High/Medium/Low)
• Impact if constraint migrates there (Critical/Significant/Moderate)
• Current preparation level (Ready/Partial/Unprepared)
• Investment required to prepare
• Time required to prepare

The matrix creates a heat map showing where to focus preparation efforts. At a logistics company, the matrix revealed that customer service was high probability, critical impact, and unprepared. We immediately began hiring and training.

The Capacity Ladder

This visual tool shows the capacity of each process step like rungs on a ladder. The constraint is the lowest rung. As you raise that rung, you can see which will become lowest next. Simple but powerful for creating organizational understanding.

The Migration Trigger Dashboard

We create real-time dashboards showing:

• Current capacity utilization by process
• Trend lines approaching constraint thresholds
• Early warning indicators
• Projected constraint migration timing
• Preparation status for each potential constraint

When any metric enters the “yellow zone” (approaching 85% capacity), we trigger preparation protocols.

The Constraint Migration Playbook

For each potential constraint location, we document:

• Signs that constraint is migrating here
• Immediate actions to take
• Resources required to manage constraint
• Success metrics
• Lessons from previous migrations

When constraints migrate, teams aren’t scrambling to figure out what to do. They execute pre-planned responses.

Success Stories in Migration Management

Let me share three detailed examples of successful constraint migration management:

Story 1: The Prepared Manufacturer

A medical device manufacturer anticipated constraint migration perfectly. Their assembly line was the clear bottleneck, limiting production to 1,000 units daily. Before improving assembly, they:

• Analyzed where constraints would migrate at different production levels
• Identified sterilization as the next constraint at 1,400 units/day
• Installed additional sterilization capacity while improving assembly
• Trained quality inspectors for increased volume
• Negotiated expanded supplier agreements

When assembly improvements yielded 1,500 units/day capacity, sterilization was ready. The constraint did migrate there, but it wasn’t disruptive. They continued this pattern through four constraint migrations over 18 months, ultimately increasing throughput from 1,000 to 2,800 units/day without any crisis moments.

Story 2: The Agile Software Company

A SaaS company took a different approach—they built flexibility to handle constraint migration rather than trying to predict it precisely. They:

• Created cross-functional teams that could shift focus quickly
• Implemented modular architecture allowing easy scaling
• Built excess capacity in cloud infrastructure
• Established partnerships for overflow support
• Created rapid hiring and onboarding processes

As constraints migrated from development to QA to customer support to infrastructure, they shifted resources dynamically. Their “constraint response time” averaged 3 days—the time from constraint identification to effective response.

Story 3: The Predictive Retailer

A retail chain used advanced analytics to predict constraint migration. They:

• Built models predicting where constraints would migrate based on historical patterns
• Created “constraint weather forecasts” showing migration probability
• Implemented automatic capacity adjustments based on predictions
• Established “constraint insurance”—backup capacity in predicted migration points
• Measured prediction accuracy and continuously improved models

Their prediction accuracy reached 78%, allowing them to prepare for most constraint migrations before they occurred. When their e-commerce platform improvements increased online orders by 200%, the predicted constraints (payment processing, customer service, and last-mile delivery) were already reinforced.

The Continuous Evolution Mindset

The most important shift in managing constraint migration is mental: Stop seeing it as a problem and start seeing it as a sign of success. Every constraint migration means you’ve improved something. It’s evidence of progress, not failure.

TOC practitioners sometimes refer to these in the negative as working through layers of resistance to a change. But I prefer the positive frame: working through layers of improvement opportunity. Each migrated constraint is a new chance to enhance your system.

Organizations that excel at constraint migration management share certain characteristics:

• Anticipation Over Reaction: They spend more time preparing for future constraints than fighting current ones. At minimum, they’re always one constraint ahead in their thinking.
• System Thinking: They see constraints as system properties, not local problems. Improving one area always considers system-wide impacts.
• Continuous Learning: Each constraint migration teaches them about their system. They document patterns, refine predictions, and get better at management over time.
• Flexible Resources: They maintain resources that can be redeployed as constraints migrate—cross-trained people, modular systems, adaptable processes.
• Migration Metrics: They measure not just constraint performance but migration management effectiveness—prediction accuracy, response time, preparation effectiveness.

Your Constraint Migration Action Plan

Ready to get ahead of constraint migration in your organization? Here’s your action plan:

Week 1: Current State Assessment

• Map your complete value stream
• Identify current constraints and utilization levels
• Calculate capacity at each process step
• Document historical constraint patterns
• Assess preparation for likely migrations

Week 2: Migration Prediction

• Build your Constraint Migration Matrix
• Identify top 3 likely migration destinations
• Calculate when migration will occur at current improvement rates
• Assess impact of migration at each point
• Create early warning indicators

Week 3: Preparation Planning

• Develop migration playbooks for likely constraints
• Design flexibility into potential constraint areas
• Identify quick-win preparation opportunities
• Build migration trigger dashboard
• Assign owners for migration preparedness

Week 4: Implementation Launch

• Execute highest-priority preparations
• Implement early warning systems
• Train teams on migration management
• Establish regular migration reviews
• Begin tracking migration metrics

Ongoing: Continuous Evolution

• Review predictions vs. actual migrations monthly
• Refine prediction models based on experience
• Share migration learnings across organization
• Build migration management capability
• Celebrate successful migrations as progress

The Competitive Advantage of Migration Mastery

Organizations that master constraint migration management gain significant competitive advantages:

• Speed: While competitors react to new constraints, you’re already prepared. This speed difference compounds over time.
• Efficiency: Proactive preparation is always cheaper than reactive scrambling. You invest purposefully rather than desperately.
• Predictability: When you can predict and prepare for migrations, your improvement trajectory becomes more predictable and plannable.
• Confidence: Teams that know migrations are managed gain confidence to pursue aggressive improvements.
• Learning Velocity: Each well-managed migration teaches you more about your system, accelerating future improvements.

The Migration Reality

Here’s the truth about constraint migration: It’s not going away. As long as you’re improving, constraints will migrate. The question isn’t whether you’ll face constraint migration—it’s whether you’ll manage it proactively or reactively.

The organizations I’ve seen fail at transformation aren’t those that faced constraint migration—everyone faces that. They’re those that were surprised by it, unprepared for it, or defeated by it. They treated each migration as a setback rather than a sign of progress.

The winners? They’re the ones who understood that constraint migration is just optimization in action. They prepared for it, managed it, and used it to drive continuous improvement. They turned the whack-a-mole game into a systematic capability for getting better.

Every constraint you improve will create a new constraint somewhere else. That’s not a bug in the system—that’s the system working exactly as it should. Your job isn’t to prevent migration but to manage it so well that it becomes a competitive advantage.

Once a constraint has been successfully elevated or eliminated, a new constraint will inevitably emerge, and the process must be repeated to identify and address this new bottleneck. This is the reality of optimization. Embrace it. Prepare for it. Master it.

Because in the end, the organizations that manage constraint migration best are those that improve fastest. And in today’s market, the fastest improver wins.

Welcome to the endless game of constraint migration. May you play it well.

Todd Hagopian has transformed businesses at Berkshire Hathaway, Illinois Tool Works, Whirlpool Corporation, and JBT Marel, selling over $3 billion of products to Walmart, Costco, Lowes, Home Depot, Kroger, Pepsi, Coca Cola and many more. As Founder of the Stagnation Intelligence Agency and former Leadership Council member at the National Small Business Association, he is the authority on Stagnation Syndrome and corporate transformation. Hagopian doubled his own manufacturing business acquisition value in just 3 years before selling, while generating $2B in shareholder value across his corporate roles. He has written more than 1,000 pages (coming soon to toddhagopian.com) of books, white papers, implementation guides, and masterclasses on Corporate Stagnation Transformation, earning recognition from Manufacturing Insights Magazine and Literary Titan. Featured on Fox Business, Forbes.com, AON, Washington Post, NPR and many other outlets, his transformative strategies reach over 100,000 social media followers and generate 15,000,000+ annual impressions. As an award-winning speaker, he delivered the results of a Deloitte study at the international auto show, and other conferences. Hagopian also holds an MBA from Michigan State University with a dual-major in Marketing and Finance.