Mission journal / Questions and experiments
Let different minds unlock it
The best problem-solving challenge is not necessarily the hardest puzzle. Choose one that makes listening, testing and revising possible without putting anyone's competence on trial.
Make the thinking visible
A group can reach a correct answer without collaborating well. One confident person may solve the task while everyone else watches. Design for a visible process instead: individual thinking, a shared explanation of assumptions, a small test and a chance to revise.
Use a problem with several reasonable approaches. Avoid riddles that depend on a cultural reference, unfamiliar vocabulary or a trick answer. If expertise is relevant, make it available to everyone through a short reference sheet. An activity should not reward hidden prior knowledge unless learning that knowledge is the stated purpose.
Explain the constraints before starting and leave them visible. Separate genuine requirements from preferences. Teams often benefit from asking, “Do we know this is necessary, or have we assumed it?” Praise useful clarification rather than treating questions as interruptions.
Mission / Build, test, revise
Design a paper stand
A small prototype with room to learn
Using a few sheets of paper and a short length of tape, make a tabletop stand for a lightweight card. Agree the card's size, the available materials and the test before anyone begins.
Begin with four minutes of individual sketching. Each person can draw, describe or write an idea. Then invite contributions without criticism. Compare approaches using the same criteria: stability, material use and ease of construction. The group chooses an initial design; it does not need to combine every suggestion into one complicated object.
Build a rough version and test it on the same stable surface. Record what happened in plain language. “The base folded when the card leaned forward” is more useful than “It failed.” Ask the group to change one feature, predict the effect and test again. This keeps revision connected to evidence rather than the confidence of the proposer.
Never use heavy objects, sharp tools or elevated testing surfaces. This is not a strength contest. A digital alternative is to sketch two stand concepts and annotate likely failure points, or to redesign a fictional information handoff using the same test-and-revise sequence. Let participants choose a route that works for their access needs.
Facilitator notes and debrief prompts
Give equal attention to builders, sketchers, questioners and recorders. Ask: “What did our first test teach us?” “Which assumption changed?” and “What helped us discuss a weak idea without criticising its author?” Avoid naming a best engineer.
Try an evidence-sorting mission
For a no-materials alternative, prepare a fictional service problem with six short observations. For example, a meeting often starts late, the joining link appears in two places, and several people report uncertainty about the agenda. Keep the observations neutral and do not copy identifiable workplace complaints.
Ask the group to separate observations, interpretations and unanswered questions. An observation might be “The link changed twice.” An interpretation might be “Nobody cares about punctuality.” The difference matters because the second statement assigns a motive without evidence.
Have the group choose one question it could answer cheaply, then propose a low-risk experiment. Perhaps one clearly marked meeting link would reduce confusion. The purpose is not to solve the fictional organisation; it is to practise resisting a premature explanation.
Protect space for less immediate answers
Silent thinking is not a warm-up to the real work; it is part of the work. Give people enough time to read and respond. In mixed-language groups, offer the brief early and avoid rewarding fast verbal responses. Written input, paired discussion and asynchronous review can reveal ideas that a rapid brainstorm misses.
If someone spots an answer immediately, ask them to document their reasoning while others explore. Do not require them to pretend ignorance, but do not let the session become a demonstration by one person. A facilitator can invite alternative approaches without forcing anyone to defend an idea publicly.
Debrief the decision, not the person
Finish by asking what evidence influenced the group's decision and what remained uncertain. Invite a private written reflection as well as open discussion. Agree on one ordinary work habit to test, such as writing assumptions at the top of a project brief.
Do not treat the activity as a diagnostic test of creativity, leadership or intelligence. It offers a limited view of a group in one setting. The useful outcome is a better conversation about how work gets done, followed by a modest change the team can actually sustain.
Add optional, friendly competition