Concurrent change at scale produces a particular failure mode that does not look like resistance. It looks like cognitive blankness. People stop being able to distinguish one change program from another. The patterns merge into noise.
This is not a motivation problem. It is a working-memory problem. Human working memory holds roughly four to seven items simultaneously (Cowan, Behavioral and Brain Sciences, 2001; Miller, Psychological Review, 1956). Each concurrent change program adds load. When the load exceeds processing bandwidth, the individual programs stop being readable as separate signals.
The difference between pattern and noise
A complex juggling pattern - even a seven-ball shower - has a readable structure. The arcs have timing. The peaks and valleys repeat at predictable intervals. The balls do not interrupt each other because the siteswap notation that defines the pattern specifies exactly when each ball must leave each hand.
Two unrelated patterns running in the same space do not have that structure. They do not share a timing reference. They are two independent signals passing through the same nervous system without coordination.
The result is not two patterns at once. It is noise.
This is the structural difference between managing multiple changes and experiencing change saturation. Multiple well-sequenced changes with coordination between them produce a complex pattern that is readable, if demanding. Multiple concurrent changes with no shared timing structure produce a field of interference in which the individual people inside it cannot identify which arc belongs to which program, which signal requires action, which timeline governs which commitment.
The two most common concurrent programs
In large organisations, the most common noise-generating pair is a technology implementation and a change management programme running at the same time.
Each is coherent on its own. Each has its own champion, its own steering committee, its own communications plan, its own roadmap with milestones in specific quarters. When they run simultaneously - with separate governance, separate communications, separate vocabularies for the same events - they produce interference rather than pattern.
The people inside cannot tell which signal to respond to first. Both claim urgency. Both generate action requests. The timing structures do not align. The result is the zigzag motion of someone trying to respond to two uncoordinated signals at the same time.
The people in a saturated organisation are not absent. They are still there - still inside the work. They have been reduced to outline by the volume of interference they are navigating.
What you do not do
The common response to change saturation is to add more communication. More town halls. More newsletters. More manager briefings covering all the concurrent programs. The implicit logic is that saturation is a knowledge problem: if people understood all the programs better, they would be less overwhelmed.
This is the wrong diagnosis. The saturation is not caused by insufficient information about the individual programs. It is caused by the absence of a shared timing structure across them.
Adding more communication about each individual program adds more signal to a system that is already over its bandwidth. The people inside it become harder to reach, not easier.
The juggling equivalent
When a learner is overwhelmed by three balls, you give them two.
Not because three balls is too ambitious. Not because the learner is incapable of learning three balls. Because the nervous system is a processing system with a bandwidth limit, and the first requirement for building a new pattern is that the individual can actually see what the pattern is doing.
With two balls, the arc is readable. The timing is visible. The drop produces clear feedback about what went wrong. The pattern can be debugged because it can be seen.
With three balls and insufficient bandwidth, everything drops at once and nothing is learnable because nothing is readable.
Read next: The Club Pass Is a Contract - what shared timing structure actually looks like when it works.