Team Engagement Activities That Run Every Month

Team engagement activities last when they repeat on a schedule and give the team something to build on. A monthly bomb session does both: the team plays one mission a month, climbs from the easiest section toward the hardest, and a different teammate hosts each time, so there is always a next step and a new person leading.

Why one-off team engagement activities fade by the next month

One-off team engagement activities fade by the next month because nothing connects them to what comes after. A great afternoon leaves a good feeling but no habit, no goal and nothing to look forward to. By the following month the team is back to its usual rhythm, and the event is a photo in a chat thread.

The pattern is familiar to anyone who has organized a team day. Energy is high on the day. The feedback form says people enjoyed it. A month later, ask what changed and the honest answer is very little. The event was self-contained, so its effect was too.

Part of the problem is novelty. A one-off event is built to be different from normal work, and that difference is what makes it fun. It also makes it hard to repeat. Organizers feel they need a bigger or newer event each time, which costs more effort and money, so the gap between events grows.

Another part is ownership. A one-off event is usually planned by one person, often a manager or an office coordinator. Everyone else attends. Attending is pleasant but passive, and passive experiences fade quickly.

An activity that lasts needs three things a one-off event lacks: a reason to come back, a sense of getting better over time, and a share of the running for people other than the organizer. A small monthly session can have all three, as long as it is designed as a series rather than an event repeated.

A monthly engagement session around the mission ladder

A monthly engagement session around the mission ladder works like this: the team plays one mission each month, starting in Section 1 and moving through to Section 4 over the year. The mission list is the ladder. Each rung adds modules, introduces a new kind of puzzle or tightens the timer, so the team always has a next challenge waiting.

Bomb Appétit has twenty missions in four sections of five. Section 1 teaches the three starter modules. Section 2 adds new module types and longer bombs. Section 3 brings in needy modules, which never stay solved and keep interrupting the work. Section 4 has the biggest and hardest bombs, including one with fourteen modules in a larger case. The full list is on the missions page.

A monthly session takes thirty to forty-five minutes. The host picks up the month's mission, the team splits into bombs of two to five players, and each bomb attempts the mission two or three times with a different Defuser each attempt. The session ends with ten minutes of conversation about what changed since last month.

Why a ladder rather than a random mission each month? Because the ladder gives the team a story. Month one is learning what the wires look like. Month six is a bomb with five modules and Experts who split the pages without being told. Month ten is the first needy module and the chaos it brings. That arc is visible to the team, and it makes the next session feel like a continuation rather than a repeat.

The ladder also gives the team a decision each month. If the bomb went off every time, stay on the same rung. If it was defused with time to spare, step up. How to make that call, and what each step adds, is set out in which mission a team should attempt next.

How does a team see its own progress between engagement sessions?

A team sees its own progress between engagement sessions in two places: the results of each run and the per-mission leaderboards, which rank signed-in players by their best verified defusal. A simple shared note of the mission played, whether it was defused and the time left adds the team's own view on top.

The leaderboards are the built-in record. Each mission has its own board, and a player is listed once, by their best defusal: the most time left on the clock, then the fewest strikes. Only signed-in players are ranked, and signing in uses GitHub. Guests can still play everything; their runs just do not appear on a board. Because there is no single overall ranking, a team cannot compare one mission's result with another's on the board itself. The reasons are explained in one board per mission and why there is no overall ranking.

For a signed-in player, the board shows a percentile, such as "Top 12%", and pins their own row below the table when they are further down. The Experts in a run are named beside the Defuser, and the board can be filtered to show solo runs or runs with Experts. That makes the leaderboard a reasonable place for a team to look up its best run on a mission it has played.

The game does not keep a team total or a score across months, so the team's longer story lives in its own notes. A shared document with one line per month is enough: the date, the mission, how many attempts, the best result and one sentence on what the team did differently. After six months, that page tells the team more about its progress than any single number could.

Reading those notes at the start of each session is a small ritual worth keeping. "Last month we lost two bombs to the button, this month we said the color before every press" connects the sessions and gives the host an easy opening line.

Who runs the engagement session when the manager is away?

The engagement session is run by a rotating host, not the manager, so it carries on whether or not the manager is around. Each month a different teammate hosts: they pick up the planned mission, set up the bombs, keep time and lead the closing conversation. The manager is in the rotation like everyone else.

Rotating the host solves several problems at once. The session no longer depends on one person's calendar. Hosting becomes a small, visible responsibility that people can take on without it being a big deal. And the manager gets to play as an ordinary Expert, which changes the dynamic in a useful way.

The host's job fits on a short checklist:

1. A week before, post the date and the month's mission in the team channel.
2. On the day, split the team into bombs of two to five and name each bomb's first Defuser.
3. Ask each Defuser to open Play, pick the mission and, for remote players, create a room and share its code.
4. Keep time for two or three attempts per bomb, rotating the Defuser each attempt.
5. Lead ten minutes of conversation and add the month's line to the team's notes.

A team larger than five needs more than one bomb running at once. For teams of ten, fifteen or more, the plan in large group team building activities with parallel bombs covers how to split people and keep several rooms in step.

What if nobody volunteers to host? Set the hosting order at the start of the year, alongside the calendar. People are far more likely to take a turn that was agreed in January than to volunteer on the day. Swaps are fine, as long as the person swapping finds their own cover.

The engagement mistake: measuring attendance instead of turns

The engagement mistake is measuring attendance instead of turns. Counting who showed up tells you who was present, not who took part. A colleague can attend every session as a silent Expert and never once hold the bomb or host. Counting turns at the Defuser's seat and turns as host tells you whether engagement is spreading across the team.

Attendance is easy to count, which is why it is the default. It also rewards the wrong thing. A session with full attendance where the same three people defuse every time looks like a success on paper. In practice, most of the team is watching, and over a few months they stop coming.

Turns are a better measure because they track the experiences that matter. Defusing puts a person in the most visible seat, describing what they see under pressure. Hosting puts them in charge of the session. Both build confidence in ways that sitting in an Expert seat does not, although the Expert seat is a fine place to start.

Tracking turns is simple. Add two columns to the team's notes: who defused this month and who hosted. After a quarter, anyone who has not yet defused is invited to go first next time. Nobody is forced into the seat, but nobody is left out by accident either.

There is a second benefit. When the team looks back at the end of the year, the record shows not just how far up the ladder they climbed, but how many different people helped them get there. That is a more honest picture of engagement than a percentage of seats filled.

Twelve-month engagement calendar for a team

The twelve-month engagement calendar below walks a team from Section 1 to Section 4 with one mission a month. It suits a team of eight playing as two bombs of four. The hosts are invented names showing a rotation in which the manager, Malik, hosts in month three rather than month one.

The calendar skips some missions on purpose. Full boil and Back of house in Section 3 add more needy modules, and No substitutions, Double shift and the final mission in Section 4 are much harder. A team that finishes month twelve with time to spare can carry on into those the following year.

Treat the calendar as a default, not a contract. If a month's mission goes badly, repeat it next month instead of stepping up. If the team breezes through Section 2, skip ahead. A fifteen-minute version of a session, for months when the team can spare only a short slot, is set out in quick team building activities in a fifteen-minute bomb.