Most organizations are taught to “find the constraint.”
And that advice—grounded in the work of Eliyahu Goldratt—is powerful.
But it is often misapplied.
Not because it’s wrong.
But because it assumes something that is frequently not true:
That the system is stable enough for a meaningful constraint to exist.
When a Constraint Can’t Be Seen
A clear constraint depends on:
A stable flow of work
A shared understanding of what is important
A system where priorities are coherent
When these conditions are present, constraints are visible and actionable.
When they are not:
Constraints don’t disappear—they become symptoms of instability
Everything looks constrained.
Nothing consistently is.
A Different Starting Point
Instead of asking:
“What is the constraint?”
Ask:
“What conditions should be present for effective flow—and which are missing?”
This shifts the focus:
From diagnosing bottlenecks
To identifying missing capabilities and conditions
A Real Pattern: Misalignment as a Missing Capability
In one organization:
There were no Quickest Valuable Releases (QVRs)
No alignment across products
Shared services were overloaded
The visible symptoms:
Multitasking
Long delays
Work piling up everywhere
It would be easy to say:
“Shared services is the constraint”
But that was not the issue.
What was missing was:
The capability to align demand
Without that:
Everything was started
Nothing finished
Constraints appeared everywhere
Seeing Symptoms as Signals
The observable issues were real:
Overloaded teams
Poor estimation
Too much work in process
But these were not independent problems.
They were:
Symptoms of missing system conditions
This is where many organizations get stuck:
They try to fix symptoms directly
Instead of asking what capability or condition is absent.
A Key Insight (Aligned with Goldratt)
Goldratt noted:
“Often reducing batch size is all it takes to bring a system back into control.”
This is critical.
Because it shows:
You don’t always need to find the constraint
You can restore stability by improving a key condition
This aligns with inherent simplicity:
A small number of factors drive system behavior
But those factors are not always constraints
Sometimes they are missing capabilities
Primary and Enabling Improvements
In practice, improvement happens on multiple levels—but with different intent.
Primary Improvements
Restore essential system conditions
→ e.g., aligning demand through QVRs
Enabling Improvements
Improve local flow and make the system visible
→ e.g., shared or borrowed team members
Masking Improvements (the danger)
Improve locally while hiding the underlying issue
The key question:
Does this improvement make the system more understandable—or less?
When You Can’t Change What’s Being Worked On
In many organizations, constraints are not just technical—they are organizational and role-based.
You may not be able to change:
What is being requested
How priorities are set
In these cases:
Improvement becomes a way to reveal the cost of current decisions
By improving:
Flow visibility
Work completion
Dependency clarity
You make systemic issues visible.
This often becomes the lever for broader change.
From Building to Improving
A subtle but critical shift:
Don’t ask: “What are we building?”
Ask: “What are we trying to improve?”
This changes everything:
Focus shifts to objectives
Trade-offs become explicit
Prioritization becomes meaningful
The Improvement Cycle
Improvement is not linear.
It is a cycle:
Identify missing conditions
Improve them (primary)
Reduce friction and reveal structure (enabling)
Increase understanding
Repeat
Over time:
The system becomes stable enough that a true constraint emerges
Final Thought
This is not a rejection of Theory of Constraints.
It is a deeper application of it.
Finding the constraint is a tactic.
Improving the conditions that allow a constraint to emerge is a strategy.
See follow up post After the Pilot: What Should We look for?
If you like my work, you will find AmpGPT of interest. It is ChatGPT, specially trained in Amplio, to interact with you to help you learn. Amplio is not a framework but is built on a solid foundation of system, cognitive, and learning dynamics. It can assist you regardless of the approach you are taking. You can learn more about it here.