The image has two people in it.
You have to look to find them.
The magenta and cyan light trails have taken over almost the entire frame. Sweeping arcs, violent zigzag lines, overlapping spirals - light moving in six directions simultaneously without a shared timing structure. The two human figures are silhouettes, visible only as dark shapes inside the interference. You can see the outline of arms, the posture of someone trying to do something. But the light has taken over the frame.
This is what concurrent change looks like from the outside.
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.
The light in this image does not have that structure. The magenta and the cyan are not in conversation with each other. They do not share a timing structure. They are two independent light sources passing through the same space without coordination.
The result is not two patterns in the same frame. 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 the image: 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 colors and what they mean
Magenta and cyan.
These are not arbitrary choices in the image. In the color system developed across this body of work, brain/change overlaps appear at the warmer end, and tech/change intersections appear at the cooler end. Magenta and cyan represent the two most common concurrent-change pairing in large organisations: the technology implementation and the change management programme running simultaneously.
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 exactly this image.
The people inside the interference cannot tell which light source to respond to. Both claim urgency. Both generate action requests. The timing structures do not align. The result is the zigzag purple pattern in the image: the trace of what it looks like to move in response to two uncoordinated signals at the same time.
The two figures in the image are not absent. They are still there - still in the frame, still inside the organisation. 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 light to the image. The silhouettes get harder to see.
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.