What an event looks like
Tuesday, 4:30 PM. Conference room on the second floor.
A reference scenario — a typical integration event for a 24-person team. Here's how the whole thing flows.
4:30 PM. Conference tables go against the wall. Six play zones appear instead, purple light pulses, and the instructor says: 'welcome — we're going to try to divide you, but it ends well.' First nervous laughs.
5:00 PM. Four teams of six, a brief explanation, headsets on. First mission: Cyberscape. Two minutes of silence. Then someone shouts 'I have the code!', someone else 'not that way, back, back!'. People from accounting and people from DevOps are now on a first-name basis.
5:45 PM. Rotation. Teams swap games. Top spots on the leaderboard change every 10 minutes. The CEO loses to the intern team and can't believe it. It's the first time this year they're heard laughing this loud.
6:45 PM. Finale. The top two teams hit the deciding scenario — Alien Infection. Five minutes of pure adrenaline. Everyone gathers around the stations, commentating live like it's MMA.
7:15 PM. Debrief. Short conversation: what happened, who surprised, how the teams communicated. Pizza, beer, last photos. By 8 PM part of the team heads to a bar together — on their own. Nobody planned that.
What's left after the event
- participants
- 24
- total time
- 2.5h
- people left out
- 0
- teams competing at once
- 4
participants
total time
people left out
teams competing at once
A reference scenario based on a typical integration event flow. The actual event is tailored to your team size, time and company vibe.