Teamwork
Designed for Engineers to spark real collaboration and high-energy learning.
Session constraints and alignment parameters selected by facilitator: [30 minutes, Online, Bored, Physical movement, Low pressure].
The 2am Debug Dilemma
Tell the group: It’s 2am and the production server is down. The on-call engineer needs help, but the team is scattered across time zones. Ask: What’s the very first message you send to get everyone aligned and moving fast? Everyone privately drafts a sentence, then shares anonymously via chat. Compare the answers and reveal the most effective approaches.
Tap to view the full activity.
Why this works
Jumping straight into a high-stakes, familiar scenario builds intrigue and urgency. Having participants privately write their response before sharing lowers risk and lets everyone see different ways teams communicate under pressure.
Code Review Myth Hunt
Read aloud three statements about teamwork in code reviews: (1) ‘Only senior engineers should leave comments’, (2) ‘If nobody finds a bug, the code must be safe’, (3) ‘Automated tools catch everything important’. Each participant votes true or false for each statement using a poll. Reveal the actual answers and discuss the most surprising misconceptions.
Tap to view the full activity.
Why this works
By exposing common myths, engineers get a chance to see where their beliefs align or differ, and the surprise makes the true answer memorable.
Silent Standup Snapshot
Everyone imagines their last team standup. Without sharing aloud, participants write down a private score (1-5) for ‘How much did I actually help my teammates yesterday?’ After, share average scores anonymously in a poll. Facilitator reveals the group’s actual average and asks: What small action could boost the score next time?
Tap to view the full activity.
Why this works
Starting with private reflection makes participation low-risk. Sharing the anonymous group average opens honest discussion about real teamwork habits.
Bug Triage Lightning Vote
Present this scenario: Two critical bugs appear right before a major release. One affects user data privacy, the other stops users from logging in. Divide the room into two factions. Each team debates for two minutes, then votes with rapid emoji reactions for which bug to fix first. Facilitator reveals common industry priorities and why teams sometimes disagree.
Tap to view the full activity.
Why this works
A fast-moving, competitive vote brings energy into the session and shows how real teams wrestle with urgent decisions under pressure.
Architect’s Trade-Off Table
Show this dilemma: You're designing a new feature. Management wants it fast, users want it stable, and engineering wants technical integrity. Ask everyone to choose privately: speed, stability, or integrity. Then pair up and compare choices—why did they pick what they did? Facilitator brings out real-world consequences of each decision.
Tap to view the full activity.
Why this works
Giving participants a realistic trade-off anchors teamwork in actual product design moments, and pairing up makes it safe to share reasoning.
Refactoring Reflection Relay
Facilitator asks: Think about a recent code refactor you worked on. Write down one unexpected teamwork lesson you learned—could be about communication, shared ownership, or disagreement. Then, in breakout pairs, share your lesson and listen to your partner’s. Each person posts their favorite takeaway in the group chat.
Tap to view the full activity.
Why this works
Reflecting on personal experience transforms abstract teamwork into something participants own, and sharing in pairs gives comfort and space.
Sign up to unlock 3 more activities
Get the full pack, facilitation flow, and more ready-to-run ideas.