GC Musings: The Dry Run Effect
Now that The Muppet Movie Game is postponed indefinitely, those of us interested in Game planning will have to go elsewhere to get our fix of behind-the-scenes discussion.
This is the first in an ongoing, irregular series of articles I'm going to write about my own GC experiences. I encourage other GCs to contribute their thoughts as well, either in comments here or on their own blogs.
THE DRY RUN EFFECT
By Curtis Chen, Team Snout
Last Sunday, DeeAnn and I ran the Portland DASH, a one-day walking puzzle hunt in downtown PDX. "DASH" stands for "Different Area—Same Hunt," and we had worked with people in seven other cities to organize this event. For us, it was a much smaller event than we're used to, and we saw some interesting differences.
When Team Snout has run full-weekend, driving Games, we always see a huge "spread" between the fastest teams and the slowest teams. Some people are puzzle fiends; others like to take their time and forgo hints for hours. We do our best to support both styles of play, but in some of our later events, we spent a lot of effort trying to manage the spread and cause teams to finish within a two-hour window. (That may sound like a long time, but the natural spread is eight to ten hours. That's no good when your end party location is only open for six hours on Sunday.)
In 2006, we did a "dry run" (full-scale, on-location playtest) of the Hogwarts Game with three teams, two weeks before the actual event. We had an observer riding along with each team, so we got very detailed data about how they were solving throughout the event. (One team also inconvenienced a couple of young lovers, but that's another story...)
The most interesting thing we observed on the Hogwarts dry run was the complete lack of a typical spread, despite our preparation of several "bonus clues" to keep faster teams occupied. The three dry run teams never let themselves get more than three clues apart at any time. According to our observers, whenever one team saw another team pulling out of a location, the remaining team would suddenly become more motivated to take a hint and speed up their solving of that clue. Nobody likes being left behind.
I've started calling this "the dry run effect," and we recently saw it in action during the Portland DASH.
So Crazy It Just Might Work
During most of the Portland DASH, DeeAnn and I were the only GC staff available. (Another long story.) This meant we had to cover all the tasks: handing out clues at each location, answering the telephone help line, monitoring clue sites, and taking care of any other little crises that came up. We knew we wouldn't be able to handle doing hints by phone if more than two teams called at once, so we decided to give pre-printed hint envelopes with each clue.
Every single one of our teams finished ahead of schedule: we started around 10:15 AM, and the first team hit EndGame around 2:30 PM. Our scheduled hard cutoff time was 4:30 PM, but even the slowest team arrived an hour before that. I'm pretty sure being able to take hints at any time, without having to call GC and admit you were stumped, caused more teams to take hints earlier and more often. But there was another important factor--we ran the event as a relay.
This is, to my knowledge, something that no other GC has done in this type of event. (If you know of someone who has, please tell me; I'd love to compare notes.) Our goal was to make clue distribution possible for a two-person GC to handle. This is how it worked:
- GC waited at each location for the first team to arrive.
- When the first team showed up, GC handed all the sealed clues to that team.
- The team opened one copy of the clue and started solving it.
- When the next team showed up, the first team handed all the remaining, sealed clues to them.
- This process repeated for every subsequent team. If a team ever finished solving their clue before the next team showed up to "hold the bag," they contacted GC for further instructions. (We were usually able to return to the location and hold the remaining clues until the next team arrived.)
But remember the spread I was talking about? We had seven teams in the Portland DASH, and we never saw them spread across more than three clue locations--the same as in the Hogwarts dry run. I haven't done all the number crunching and statistical modeling, but the following is my intuition about what's going on.
Three in 3
When Team Snout discusses "the spread," we talk about three sub-groups of all the teams that are playing: We have (1) the fast teams, (2) the middle of the pack, and (2) the slow teams. (Please note that none of those terms is intended as pejorative; we recognize that people play at different speeds, and we do not force anyone to conform to a specific timeline. We want everyone to have fun.)
This spreading-out happens in many circumstances, even down to the team level. Think about it: When a Game team arrives at a location, there's always the one guy who jumps out of the van and runs flat-out to get the clue, then the rest of the team who tumble out after it's parked, and finally the driver, who has to lock up. (If it's Sunday morning, there may also be one or two nappers who stay behind.)
With twenty-plus teams, the atomic units become clusters of teams instead of individual team members. But with a smaller number of teams--say, three in the Hogwarts dry run, or seven in the Portland DASH--I believe players recognize each other more easily, and they're more aware of where they are in the pack. If a team thinks they're falling behind, they may think about taking a hint sooner.
Nobody likes being left behind. With only seven teams, you'll know when you've encountered most of them. With twenty teams, there are some you're never going to see, and unless told otherwise by GC, you can always hold out hope that some of them are still behind you; therefore you have less motivation to speed up your solving.
This is just an observation. I don't think this is a problem that requires fixing, but if confirmed, it will be useful for other GCs to know. Your dry runs will not show the same spread as your full event, and if your event is small, you won't see much of a spread at all. This will affect your timeline and staffing requirements. Plan accordingly!