Mission journal / Purpose and handoffs
Put a shared purpose in play
A useful mission gives people something to accomplish together and a reason to notice how they collaborate. Keep the task small enough that the process has room to breathe.
Start with the working relationship
Before selecting an activity, finish this sentence: “We want to practise working together when…” Perhaps information crosses between departments, a new colleague asks for help, or two people interpret the same request differently. That sentence makes the mission more useful than a generic invitation to have fun.
Do not frame the session as a cure for low morale. If people are facing understaffing, unfair treatment or unresolved conflict, acknowledge those conditions and address them directly. A light exercise can support a conversation, but it cannot repair a broken agreement about work.
Write a brief with a purpose, a finish line, a time limit and boundaries. State what participants will make and what will not be assessed. Explain that observation, quiet writing and opting out are legitimate choices. Share the brief in advance rather than using surprise as a way to secure participation.
Mission / A clearer first day
Build a one-page welcome guide
The practical brief
Create a one-page guide that helps an imaginary new teammate complete one ordinary task. Choose something low-risk, such as finding a meeting agenda or knowing where to ask a process question.
Allow three minutes for individual notes. Each person lists information a newcomer might lack. Gather the notes without immediately evaluating them, then group similar questions. Choose the most important task and draft instructions in plain language. Avoid actual passwords, customer details or private internal links in any version that might leave the team.
Use the next few minutes for a reader test. Someone who did not write a section explains what they would do first, where they would go next and what still feels ambiguous. The writers listen before defending their wording. Revise the guide using that feedback, then stop at the agreed time even if the layout remains imperfect.
The outcome is not a polished onboarding resource. It is a visible example of assumptions becoming explicit. If the team wants to use the guide later, assign a separate accuracy check and an owner. Do not let a playful prototype quietly become official policy.
Facilitator notes and debrief prompts
Offer reader, editor, question-collector and observer roles without assigning them by personality. Ask: “What did we assume everyone knew?” and “Which question improved the guide?” End by naming one handoff that would benefit from the same reader test.
Try a context relay, not a speed relay
For a second mission, ask one group to write a fictional request for another group to interpret. The receiving group lists what it understands, what it would need to clarify and the next safe action. It should not guess missing information just to finish quickly.
Return the questions to the first group and allow one revision. Compare the two versions for clarity rather than cleverness. This format practises useful clarification and shows why a short message can create more work downstream. Keep scenarios fictional so the discussion does not become an indirect complaint about a colleague.
Let participation take different shapes
For remote teams, make the document the main workspace rather than treating a room's whiteboard as the source of truth. Read instructions aloud, provide the same instructions in text and invite comments before the call. Camera use should not be the price of being counted.
For mixed schedules, leave a contribution window and name a facilitator who will summarise the input. Do not reward whoever happened to be online first. If some colleagues prefer observing, invite them to comment on the instructions or handoffs afterwards; equally, let them decline that role.
Close with one usable change
Reserve the final five minutes for reflection. Invite everyone to write one helpful condition, one point of friction and one adjustment worth trying. Sharing aloud remains optional. Discuss the process rather than who was most enthusiastic.
Choose one improvement for ordinary work, such as adding a “what happens next” line to requests. Agree who will test it and when the team will review it. The mission has done enough if it makes one collaboration habit easier to see and easier to change.
Explore a problem-solving mission