Zone A crew
Owns spatial/interface cues the other can't see — must describe, not hint vaguely.
VIRTUAL ESCAPE · TWO ZONES · COLLABORATION
Two rooms.One way out.Both of you.
Like an escape room in a futuristic facility — except success depends on what each side shares, not how fast one side thinks alone.
- Format
- Virtual / hybrid teams
- Duration
- ~90 min + debrief
- Players
- 8–40
- Skill
- Cross-team collaboration
Quick answer
Joint Task Force is Tryitowl's cross-team coordination simulation: two groups in separate virtual rooms must share interlocking clues to escape a locked facility — neither side progresses without the other's information.
Collaboration isn't a buzzword. It's a relay with no runner.
2
physically separated zones — neither sees the full puzzle
100%
of clues needed to escape are split across both sides
0
paths out if either side tries to solo the last mile
Clues found in Zone A only unlock what Zone B can reach — and the reverse. Unless they build the chain together, neither team leaves.
Joint Task Force is about collaboration under real separation. Teams navigate a virtual, escape-room-style facility. The group is divided across two areas with different perspectives and partial information.
Along the way they must pass signals, artefacts, and logic that only make sense when combined. Hoard information, skip a hand-off, or assume the other side 'already knows' — and the clock wins.
The debrief lands on interdependence at work: where your org behaves like two rooms that forgot they're sharing one outcome.
How the session runs
Structured phases keep energy and learning tight — from brief through play to debrief.
Act 1
Lock-in & split
Brief sets the mission: escape the facility before time expires. The cohort discovers they're not in one room — they're in two linked zones with different interfaces and no shared whiteboard.
Setup
Act 2
Parallel puzzles
Each zone tackles what it can see. Early wins feel local — then both sides hit walls that need the other half of the pattern, code, or narrative.
Friction
Act 3
Interlocking clues
Discoveries in Zone A become the key to a lock in Zone B, and vice versa. The design forces explicit transfer: describe, verify, commit — not nod and hope.
Hand-offs
Act 4
Synchronised exit
Final sequence requires both zones to act in sequence within the same window. Finish together or reset the loop. Then facilitator-led debrief on silence, trust, and shared ownership.
Release
Collaboration forks (examples)
- Option: Establish a compact naming protocol and trade screenshots.
- Option: Assume alignment — lose minutes re-proving what was already true.
Consequence: Timer bleeds; frustration spikes.
How teams typically split
Zone B crew
Owns complementary fragments; success is listening as hard as solving.
Floating timekeeper (optional)
Rotates who verbalises the shared timeline so neither side optimises locally.
Risk: If nobody owns synthesis, drift wins.
What facilitators watch
Qualitative signals more than scores — the simulation makes them visible in play.
Clue-chain completeness
Linked vs orphaned
Verified hand-offs
Named vs assumed
Synchronisation
Joint actions on time
Psychological safety under pressure
Facilitator rubric
Facilitator debrief
- Where did we behave like two rooms with one badge swipe?
- Which clue did we almost hoard — and what did that cost the other side?
- What is our real-world Zone A / Zone B — and who bridges them?
- Name one hand-off you'll make explicit next week (who, what, when).
- What would 'escaping together' look like on your hardest programme right now?
Also in the experience
- Facilitator-led debrief tied to platform data
- Digital delivery, configurable cohort sizes
- Futuristic escape-room frame — virtual delivery; debrief ties to matrix and programme work.
Frequently asked questions
What is the Joint Task Force simulation?▼
A virtual escape-room-style collaboration simulation. Teams are split across two zones with different information and must communicate precisely to solve shared puzzles. Success depends on coordination, not individual speed.
How does Joint Task Force develop cross-team coordination?▼
It makes information hoarding and vague handoffs costly immediately. Facilitators debrief listening quality, clarity of updates, and how hierarchy helps or blocks parallel problem-solving.
Can Joint Task Force run for remote and hybrid teams?▼
Yes — it is designed for virtual delivery with breakout rooms and shared timers. In-person variants exist for offsites that need a high-energy collaboration diagnostic.
How long is a Joint Task Force session?▼
Typically ninety minutes including briefing, two-zone play, and debrief. Shorter conference formats are available with a lighter behavioural unpack.
Let's talk about your team
Book a facilitated session — we'll match group size, format, and outcomes to the right simulation.