Fable
The writers' room and the theater backstage
After a new theater was built, the operations team began preparing for the premiere. The scriptwriting team was responsible for writing the script: when characters enter, when they speak, when they deliver monologues, and which branch to take when the audience reacts differently. The backstage team was responsible for theater operations: raising and lowering the curtain, switching lights, dispatching props, and calling actors to standby.
At the first meeting, the producer wrote two things on the same line of the same procurement list, under the heading "performance system." He compared quotes from three vendors; one quoted low because its back-office automation system was strong, but its script tools were nearly unusable; another had an excellent script editing experience but very primitive back-office scheduling. The producer sorted by total price and chose the first.
A week before the premiere, the dress rehearsal collapsed. According to the newly revised script, the actor needed to make a rapid emotional turn—one line was still an argument, and the next had to switch to a monologue. The playwright team's tools fully supported this jump, but the backstage lighting system could not react in time; switching from argument lighting to a monologue spotlight took four seconds. During those four seconds of blankness, the actor stood on stage waiting for the light, and the murmurs in the audience drowned out the lines.
During the retrospective, the lighting technician said something very honest: the script you write can switch emotions ten times in a second, but my spotlight motor takes at least three seconds to get into position. The two systems have different speed limits, and comparing them on the same line made the cheaper one treat the slower system as the overall cost anchor.
The producer changed the process. From now on, all performance projects will be evaluated in two separate rounds for script tools and backend systems. The first round compares only the script tool's diagram expression capability, branch editing, and multi-version management—regardless of the backend. The second round compares only the backend system's concurrent scheduling, latency, and fault tolerance—regardless of the script. Each round ranks its own top three, and only then are they cross-matched.
During matching, an unexpectedly good combination emerged: a script tool focused on nonlinear narrative editing paired with a backend system from an industrial automation background with solid stability and latency control. The two had never appeared on the same quote before, and only surfaced when evaluated separately.
Later, the theater's operations manual included an iron rule: procurement decisions for creative tools and runtime infrastructure must not be merged. Merging them lets the shortcomings of one system suppress the strengths of the other, and what you end up buying is a compromise, not the best combination.