The Stage Manager's Prompt Book: On Directing Traffic Through Planned Choreography
In the dim wings of a theatre, during a live performance, absolute chaos is a single misstep away. Actors, crew, and set pieces must flow in a precise, unbroken sequence. The guardian against this chaos is not the director, who envisioned the play, but the stage manager and their sacred text: the prompt book. This volume contains every line, every light cue, every set change, and every actor’s entrance and exit, mapped to the second. It is the single source of truth for the show’s choreography. In managing the pathways of a website—our URLs, redirects, and internal links—we are not urban planners or gardeners. We are stage managers, and our site is the performance.
The prompt book’s first lesson is that every movement must be intentional and documented. An actor cannot simply ‘find their way’ to the center stage; they follow a marked path in the dark. Similarly, a URL should not be an accident. Its creation, like an actor’s entrance, should be written into the book. When a page is retired or merged, we don’t just pull the set piece offstage and leave the actor stranded. We write a new cue: a 301 redirect. This is the backstage crew, silently and instantly guiding the audience’s attention (and the search engine’s crawler) from the old mark to the new one, preserving the narrative flow without a jarring ‘404’ blackout.
Cue Lights, Not Confusion
Consider internal linking as the lighting grid. A follow-spot illuminates the lead actor during a soliloquy, telling the audience exactly where to look. A well-placed contextual link does the same, focusing authority and attention on a key page. But stage lighting is also atmospheric; general washes set the scene. Our site-wide navigation and footer links serve this purpose, establishing the consistent ‘world’ of the site. The prompt book balances these two types of illumination, ensuring no crucial moment is left in the dark and no light is so harsh it ruins the mood.
The canonical tag finds its parallel in the understudy system. Sometimes, an actor plays two minor roles that are, for all narrative purposes, the same character in different costumes. To avoid audience confusion, the prompt book notes this duality, but the program lists one principal actor. The canonical tag is that program note. It tells the indexing world, “For the purpose of this story, treat this duplicate performance over here as the main one.” It prevents the crowd from applauding for the wrong name.
Finally, the prompt book is a living document for a run of performances, not just opening night. After each show, notes are taken. An entrance that was too slow, a prop that was misplaced—these are adjusted. Our site structure requires the same vigilant maintenance. Analytics are our nightly notes. We see where visitors hesitate (a broken link, a confusing path), where the traffic jam occurs (poor information architecture), and we adjust the choreography for the next ‘performance.’ We are not building a static monument; we are managing a dynamic, ongoing production where every click is an audience member following the cues we’ve so carefully written.
The goal, both on stage and on the server, is an experience that feels effortless, intentional, and coherent. The audience should never see the stage manager frantically pushing an actor into place, just as a user should never encounter a dead end or a confusing maze of duplicate pages. By borrowing the stage manager’s discipline of the prompt book, we learn to direct traffic not as engineers of roads, but as choreographers of meaning, where every link is a cue, every redirect is a smooth scene change, and the entire site moves with the purposeful grace of a well-rehearsed play.
Notes & further reading
A few pages I came back to while writing this: