Stand on a balcony above a main hall on a Saturday night and you will see thousands of people moving like weather.
There is a science to it. Arrival curves, dwell times, choke points, the precise number of seconds a family will hold still before the children start pulling toward the next thing. Threshold tolerances. Bottleneck coefficients. The geometry of how bodies distribute themselves across a space when they are not directed, and the entirely different geometry of how they move when they are. We measure all of it, model it, argue about it in rooms full of people who have strong opinions about linear feet per minute and what happens to guest satisfaction when that number drops below a threshold nobody told you about until it did.
We measure it because we have to. When you invite large numbers of people into a built environment, flow is not a design preference. Flow is survival. Get it wrong and the experience collapses before it begins, not because the creative failed but because the operational reality overtook it.
But here is what took me years to actually understand, and I mean understand at the level where it changes how you work, not just how you talk: moving people efficiently is not the job. Moving people beautifully is the job. Those two things can coexist, but they require entirely different questions, and most organizations stop at the first one because the first one is easier to measure.
The shift happened gradually on my teams, and I cannot point to a single meeting where it crystallized. But somewhere along the way we stopped asking how do we move them faster and started asking what should they feel while they move. That one change, from a throughput question to an experience question, rewired everything downstream. It changed what we noticed. It changed what we built. It changed what we considered a problem worth solving.
Because the queue is not the obstacle to the experience. The queue is part of the experience. The ten minutes before the doors open. The slow approach toward the main reveal. The hallway between the thing guests came for and the thing they did not know they needed. The threshold moment where outside becomes inside and the world they left behind starts to fall away. Every one of those in-between spaces is either designed or abandoned, and most organizations abandon them because they are not the thing. They are the space before the thing.
But anticipation is not the absence of experience. Anticipation is an emotion, one of the most powerful ones available to an experience designer, and it is almost entirely underused in our industry. The moment before the reveal, if it is built correctly, does more emotional work than the reveal itself. The slow build of sound as someone moves through a corridor, the light that shifts almost imperceptibly as they get closer to the entrance, the glimpse of what is ahead visible just long enough through a doorframe to pull them forward rather than stop them in their tracks. These are small decisions. Each one is individually cheap. Each one is individually forgettable. Together they create the sensation of inevitability, the feeling that the experience began the moment the guest arrived and never stopped, that there was no seam between the ordinary and the extraordinary, that they were always already inside it.
We started designing the wait the way we designed the show. Same intentionality. Same attention to pacing. Same questions about what someone should feel at this specific moment and what the next thirty seconds should do to them emotionally. The wait became scored. The transitions became choreographed. The in-between spaces became part of the story rather than pauses in it.
Throughput went up. Complaint volume went down. But the number I actually cared about was the one that moved in a way I did not fully anticipate: guests started describing the arrival as part of the magic. Not the price of admission. Not the thing they endured before the thing began. Part of it. The beginning of it. Something they wanted to tell people about.
That is the signal that the design worked.
Now here is the leadership lesson underneath all of this, because there always is one.
Every experience has constraints. Every project has a bottleneck, a moment where the math does not work perfectly, where the physical reality of the space or the timeline or the budget creates a problem that cannot be entirely solved, only managed. Most organizations treat the bottleneck as a failure condition. Something to apologize for. Something to work around or minimize or hide behind enough production value that guests stop noticing it.
The productions that feel effortless are never the ones with the fewest constraints. They are the ones where someone looked directly at the constraint and asked a different question. Not how do we fix this. Not how do we hide this. But what could this become?
That question is a leadership posture before it is a design strategy. It requires the ability to see a limitation without being defined by it. To hold the problem and the possibility simultaneously. To resist the organizational gravity that pulls every team toward the path of least resistance, which is almost always the path of least imagination.
The bottleneck is a stage. The queue is a canvas. The threshold is an opening scene. Every constraint in a guest experience is a moment that has not been designed yet, sitting inside a space that most people have decided is not worth designing. The competitive advantage lives exactly there, in the spaces everyone else has given up on.
We do not manage crowds. We choreograph moments.
The difference between those two things is not a production philosophy. It is a leadership philosophy. It is the decision, made deliberately and held consistently, to take responsibility for the full guest experience, not just the highlight reel of it. To refuse the distinction between the important moments and the transitional ones. To believe that every second a person spends inside something you built is a second you are accountable for, and to build accordingly.
That standard is harder to hold than it sounds. It requires the willingness to spend real time and real attention on the parts of the experience that will never be photographed, never be quoted in a review, never show up in the metrics your organization tracks most closely. It requires the conviction that the invisible work matters, even when you cannot prove it in a spreadsheet.
But guests feel it. They feel it in the way an experience that is choreographed all the way through feels fundamentally different from one that is only choreographed in the moments someone decided were important. They cannot always name what they are feeling. They describe it as magic, as seamless, as the sense that everything was thought of. What they are actually describing is the presence of intentionality in places where they did not expect to find it.
That is what we are building toward. Every time. In every space. Including the ones between the spaces.
Especially those.