Experiential Design · Systems Design · Community Building
A friend of mine had told a guy she was talking to that a game night existed; it didn't, not yet. She needed it to exist by the time their date happened, so I made it exist for her: about ten people from my dorm, sophomore year, Jackbox and a few card games, no snacks.
The very first game night; ten people, some Jackbox, no snacks.
That's genuinely how it started. A favor, and a bit of a cover story.
I think what's stayed with me is that I didn't set out to build anything; I just didn't want my friend to get caught in a small lie. Everything that came after, the rules, the themes, the twelve nights, grew out of one night that was never supposed to need a sequel.
I ran the first few on instinct, just games set out on a table, and it worked for a while, until people started getting bored or didn't know what to play; no flow, nothing pulling the night together. That's what told me the format needed a real schedule, not just a room full of options.
By game night nine or ten, I could feel the weight of it, so I wrote a formal rule set: RSVP thresholds, dropout cutoffs, late penalties. It wasn't about being strict for its own sake; it was what let me keep doing this without it quietly costing me everything else.
Actual Gartic Phone game played while waiting for people to arrive on time.
I started building a distinct mechanic for each theme instead of reusing the same format, spacing game types across a night so nobody sat through twenty minutes of one they didn't care for. The murder mystery ran on a hint economy: win a round, earn a clue, and Perfect Match, the Valentine's night, was built around a bracket where your way in was bringing someone the group hadn't met.
The clearest sign I had wasn't a survey; it was growth I never orchestrated. Ten people became fifty at the Valentine's night; strangers came back with their own friends in tow. The event had a reputation before I ever told anyone about it myself.
Every night ran on its own core mechanic, and each one was really solving the same small problem in a different shape: how do you get people who don't know each other to actually talk.
"Strangers meeting strangers" was never one problem, it was several; the room was never just one type of person, and a mechanic that worked for one of them could easily fall flat, or feel like pressure, for another.
The itinerary itself was a design decision. Once I moved away from setting games out and letting people wander, I built each night as a real sequence, mixing game types on purpose so different kinds of people got their moment. No single night leaned on one type for too long.
The sequence itself followed an arc, not a flat list.
The mechanic for a given night depended on more than the theme; it depended on what the room actually felt like once people were in it. Same underlying goal, getting strangers talking, but a completely different mechanic depending on whether the room was going to sit still or move around.
For the murder mystery night, I built a hint-based economy. Two teams were investigating who "killed" me, with what, and where; every game they won unlocked a clue toward the answer. The games themselves, trivia, drafting, password, were almost secondary; the real design work was in pacing the hints so no team solved it too early or too late.
Perfect Match required people to bring a plus-one the group hadn't met, a small constraint that gave everyone a built-in, low-stakes reason to talk to someone new. It's the mechanic I'm proudest of, and the one I wish I'd leaned on more.
One more layer: each plus-one submitted a fact about themselves nobody else knew, giving people something specific to open with instead of small talk, and making the guest feel like an actual guest.
Hosted at a friend's place instead of my usual space, this night used a live tally board updated every thirty minutes; points from pong, flip cup, and small games built up visibly through the night instead of all landing at once at the end.
Most nights started the same way: a theme and a rough set of games months out, based on instinct. About a week out, once RSVPs locked in, I'd go back and cater the game selection to that specific group.
None of it worked if people didn't know it was happening, or worse, half-knew and showed up unsure. For every night I built the same small funnel: a group chat, a flyer, and a Google Form collecting RSVPs, dietary notes, and plus-one info. Reminders came next, more than felt necessary at first, until I learned repeating one closer to the date cut last-minute questions to almost nothing.
The invite didn't stop at a time and a place. Every theme also came with a dress code, and instead of writing a vague line about it, I attached a Pinterest board to the invite, a curated set of reference images matching that night's theme, so nobody had to guess what "garden party" or "Y2K" meant to me specifically.
It mattered more than I expected going in. People actually leaned into it; they'd show up dressed for the world of the night, not just for a hangout, and that visual buy-in did a lot of quiet work toward the goal underneath everything else: making people feel fully immersed the second they walked in, before a single game had even started.
The Google Form did more than collect RSVPs. On a lot of nights I'd also ask people whether they'd rather stay with people they already knew or get placed with people they hadn't met, since forcing everyone into stranger-teams would've kept some people from coming at all.
From there it became a personality balance problem. Stacking all my loudest friends onto one team never worked; it crowded out quieter players. So I split strong personalities across teams on purpose, then filled the rest with people I thought would actually get along.
One of the closest friendships in my friend group now started because I put two strangers on the same team, on purpose.
Most nights ran out of my dorm's basement, which was a big, pretty characterless space. Left alone, it didn't feel like it was built for ten to fifty people to gather in; it just felt big. Part of the job was making it feel confined enough to hold a group without feeling cramped, roping off the actual play area instead of letting the room's real size set the tone before anyone even started playing.
With too many people to have every chair face the board directly, I angled the tables instead, keeping each one enough personal space and leaving sightline "windows" between them so everyone could see without straining, wherever they sat. I also sat louder and taller people toward the back and shorter, quieter people up front, so nobody was stuck behind someone blocking their view.
Most nights ran on teams of around eight, and letting all eight play every single game at once turned into noise: too many people answering the same trivia question, nobody actually leading. So for a lot of the games, teams picked two or three representatives per round instead. That let me build actual pacing into a night instead of watching every round dissolve into cross-talk.
It also solved a problem I hadn't planned for: people who didn't want to play a specific game could just sub out for that round instead of sitting out the whole night. Over twelve nights I got better at rotating who represented the team, so everyone actually got a turn somewhere in the night.
Something I hadn't planned for at all: I always asked people to bring a snack, so food ended up more potluck than catered, spread out somewhere in the room. That meant people were getting up mid-game to go grab something, which broke the room's attention exactly when I needed it held.
The fix was an actual built-in intermission, not just tolerating people wandering off whenever they felt like it. Once the night had a real break, people stopped drifting during games, and the break itself turned into one of the more energizing parts of the night: time carved out to cut away from the games and just talk to someone new. Socializing and eating both worked better once they had their own dedicated moment.
Underneath all of it was the same backend: Google Sheets for scoring, Forms for check-ins and puzzle unlocks, Slides and Canva for the presentations people actually saw, Illustrator for the flyers. Nobody in the room ever saw the spreadsheets; they just felt a night that seemed to run itself. That gap, between how much structure was actually there and how little of it showed, is probably the part I'm most proud of.
People in my honors college who moved into my dorm two years after I did had already heard about game night. It got there through word of mouth, through people who came once and brought someone the next time.
