Collaborative games BABOK technique 10.10 is a structured, facilitated activity in which stakeholders play by agreed rules to build a shared understanding of a problem or solution [1, 2, 3]. BABOK describes it with three elements (game purpose, process, outcome) and names Product Box, Affinity Map and Fishbowl as examples [2]. For the CBAP exam (120 questions, 210 minutes [4]), learn when a game beats an interview or workshop, the facilitator role and the main risk: false group confidence [5].
Collaborative games BABOK definition
Collaborative games are elicitation activities, played like a game, that help participants with different views build a joint model of a problem or solution [3, 5]. The players move sticky notes, draw, sort cards or role-play, and a neutral facilitator keeps the rules [3, 5]. The point is not fun for its own sake. The game structure lowers inhibition and gets quieter people to contribute, so hidden assumptions surface faster than in a normal meeting [3, 5].
The technique sits in Chapter 10 of the Business Analysis Body of Knowledge (BABOK) Guide v3, between 10.9 Business Rules Analysis and 10.11 Concept Modelling [1]. The full text is behind IIBA membership, so this article paraphrases it and points to study summaries that quote it.
Why collaborative games matter for the CBAP exam
The Certified Business Analysis Professional (CBAP) exam has 120 case-study and scenario-based multiple-choice questions in 210 minutes [4]. It rarely asks you to recite a game's rules. It asks you to pick the right technique for a scenario: stakeholders who will not speak up, a group that cannot agree on priorities, or a team stuck on the same ideas. Collaborative games are a likely answer in those cases. They are a weak answer when you need precise, verifiable facts about the current state.
The three BABOK elements: purpose, process, outcome
BABOK 10.10 has three elements: .1 Game Purpose, .2 Process and .3 Outcome [2].
| Element | What it covers | Exam angle |
|---|---|---|
| .1 Game Purpose | Each game has a defined objective, such as building shared understanding among people with different perspectives [3] | The purpose comes first; a game without a clear objective is a limitation, not a strength |
| .2 Process | Rules, a time box, a neutral facilitator and visual or tactile activities; many games run in three steps: opening, exploration, closing [3, 5] | Know the facilitator's job and the order of the steps |
| .3 Outcome | The group reviews results and decides on actions or decisions based on what it learned [3, 5] | The output feeds later analysis; it is not a signed-off requirement |
The opening, exploration and closing pattern also appears in Gamestorming, a widely used facilitation book. Its authors describe opening as the step that reveals possibilities, and closing as the step that helps people "converge and select, rank options" [6]. In their model, the outcome of one game becomes the input to the next [6].
Steps of a typical game
- Opening. The facilitator explains the rules and goal; players learn the game and generate ideas [5].
- Exploration. Players connect ideas, test assumptions and experiment [5].
- Closing. Players assess the ideas and pick the most useful ones [5].
- Review. Facilitator and players agree on actions or decisions [3, 5].
Product Box, Affinity Map and Fishbowl: the games BABOK names
BABOK's example table names three games: Product Box, Affinity Map and Fishbowl [2]. Practitioners add many more, such as Speed Boat, Buy a Feature, Empathy Map and Draw Toast [5, 10].
| Game | How it works | Best for |
|---|---|---|
| Product Box | Players design the box a product would be sold in: name, tagline, key features on the front, details on the back | Finding the features and value that matter most to users |
| Affinity Map | Players write ideas on cards, then cluster similar ones and name each group | Making sense of many ideas or findings; spotting themes |
| Fishbowl | A small inner group discusses a topic while an outer circle listens and notes key points; people may swap in | Exploring different viewpoints in depth; letting observers hear a debate before they join |
Expect the exam to describe a game rather than name it. "Stakeholders design packaging" points to Product Box. "Group similar ideas into themes" points to Affinity Map. "Inner circle speaks, outer circle observes" points to Fishbowl.
The facilitator role in collaborative games
The facilitator is a neutral party who explains and enforces the rules, keeps the game moving and makes sure every participant has a role [3, 5]. Neutral matters: if the business analyst owns the solution, a game run by that analyst can steer the group toward a pre-set answer.
Good facilitation also means watching energy. One agile coach advises changing pace when people disengage and letting discussions take unexpected turns, because those turns can be the most valuable [13]. The same coach notes that a game gives colleagues "an acceptable setting" to challenge each other [13].
Strengths and limitations
BABOK lists strengths and limitations along these lines; a practitioner summary repeats the same list [1, 5].
| Strengths | Limitations |
|---|---|
| Reveals hidden assumptions and differences of opinion [3, 5] | Some games feel silly and make reserved people uncomfortable [5] |
| Encourages creative thinking [3, 5] | Long games feel unproductive when objectives are unclear [5] |
| Pulls quieter participants into an active role [3, 5] | The group reaches the conclusion together, which can create false confidence [5] |
| Can expose business needs that are not being met [5] | Needs a skilled, neutral facilitator and prepared materials [3, 5] |
The false-confidence point is a common exam trap. Agreement in the room is not evidence. Confirm game output with other techniques before treating it as a requirement.
Where collaborative games are used across knowledge areas
Collaborative games are mainly an Elicitation and Collaboration technique. IIBA's official task card for 4.5 Manage Stakeholder Collaboration, whose purpose is to help stakeholders "work towards a common goal", lists Collaborative Games first among its frequently used techniques [7]. The technique also appears in the full technique list for 4.2 Conduct Elicitation, though the 4.2 card's short list does not include it [8]. Our map of all 50 BABOK techniques by knowledge area notes that Collaborative Games rarely leaves this chapter.
| Knowledge area / task | How a game helps |
|---|---|
| 4.2 Conduct Elicitation | Draw out needs and ideas, often inside a workshop |
| 4.5 Manage Stakeholder Collaboration | Rebuild engagement and shared goals |
| Strategy Analysis (informal) | Games such as Product Box or Speed Boat explore future-state value; our Business Model Canvas guide suggests games to fill and prioritise each block |
| Requirements Life Cycle Management (informal) | Buy a Feature style games help groups prioritise |
The last two rows are practice, not BABOK task lists. For the elicitation tasks themselves, see our guide to Elicitation and Collaboration.
Collaborative games in real practice
In practice, collaborative games trace back to Luke Hohmann's Innovation Games, published by Addison-Wesley in 2006 to help teams uncover customers' "true, hidden needs and desires" [9]. His set includes Product Box, Buy a Feature, Speed Boat, Prune the Product Tree and Remember the Future, framed as a form of primary market research [10]. Agile teams later adopted the same games for backlog work and retrospectives.
The research is positive but narrow:
| Study | Sample | Main findings |
|---|---|---|
| Collaborative games in agile requirements engineering, 2018 [11] | Two Scrum projects in one large food-processing company; about 8 attendees per session (3 customers, product owner, Scrum Master, 3 developers) | All games averaged 3.5 to 4.2 out of 5; every game raised customers' willingness to attend meetings; creativity scored weakest; Prune the Product Tree felt somewhat juvenile |
| Game-based Sprint retrospectives, 2022 [12] | Six Scrum teams, six games | Games helped with dull, unstructured retros, excessive complaints and unequal participation; meetings became more productive to some degree; a smaller group saw no benefit |
The 2018 authors link the weak creativity scores to well-understood internal needs and a non-innovative system [11]. That fits BABOK's own logic: games pay off most when the problem is unclear, not when the answer is already known.
Experts disagree on collaborative games with executives
Practitioners agree that games can surface hidden needs, but not on whether to call them games or use them with senior people.
1. The label does not matter; the goal does. Hohmann says skeptics exist, but "The label you put on the technique doesn't matter" [14]. His team ran budget games with the city of San Jose [14]. A software consultancy founder reports playing Remember the Future with a client's president, COO, CTO and head of business development, and calls the sessions "a huge success" [15].
2. Rename it for senior audiences. An agile coach warns that senior management "can be sceptical if games look too trivial" and suggests calling it an activity or workshop instead [13]. A practitioner who ran Innovation Games with clients in the Middle East says her hardest sell was her own local colleagues, who worried the format could hurt their credibility; clients engaged within minutes [16].
3. Games waste time; keep them out of real meetings. In a project management forum thread, one practitioner calls games "a wasted of time in my opinion", while a product owner at a telecom prefers to keep team building separate from retrospectives [17]. A retired mentor in the same thread counters that games and materials such as Lego keep retros fresh [17].
4. Evidence is promising but thin. Both studies come from small action-research settings with self-reported ratings [11, 12]. Supporters cite higher engagement; skeptics can point out that creativity did not improve in a routine project [11].
The disagreement is mostly about framing and audience, not about whether structured, visual group work helps.
Common misconceptions about collaborative games
- "Games are icebreakers." An icebreaker warms people up. A BABOK collaborative game has a purpose, rules and an outcome that feeds analysis [2, 3]. One practitioner does use them as icebreakers [5], but that is a side use.
- "Group agreement means the requirement is confirmed." BABOK flags false confidence as a limitation [5]. Verify with other techniques.
- "Any team member can facilitate while also pushing their idea." The facilitator should be neutral [3, 5].
- "Games are the same as brainstorming." Brainstorming (10.5) generates many ideas without judgment. A game adds rules, roles and a structured close, and often both diverges and converges.
- "Games only suit start-ups." Reports range from food processing and municipal budgets to C-suite kick-offs [11, 14, 15].
Practice Questions
Question 1. A business analyst runs a session where stakeholders design the packaging for a new self-service portal, choosing a name, a tagline and three headline features. What technique is the analyst using, and what is the main output?
- A. Prototyping; a clickable mock-up
- B. Collaborative games; a shared view of the most valued features
- C. Focus group; a ranked list of opinions
- D. Brainstorming; an unfiltered list of ideas
Answer: B. This is Product Box, one of BABOK's named collaborative games. The output is shared understanding of what users value most, not a design artifact.
Question 2. After an energetic game, every participant agrees on the top three needs. The sponsor wants to baseline them as requirements immediately. What should the business analyst do first?
- A. Baseline them, because the group reached consensus
- B. Repeat the game with the same group to confirm the result
- C. Confirm the results with other techniques and stakeholders before baselining
- D. Ask the facilitator to sign off the needs
Answer: C. BABOK warns that a group-reached conclusion can create false confidence. Confirm elicitation results before treating them as requirements.
Question 3. Two departments have stopped attending elicitation sessions and blame each other for delays. The business analyst wants to rebuild a common goal. Which task and technique pairing fits best?
- A. 4.5 Manage Stakeholder Collaboration with Collaborative Games
- B. 4.3 Confirm Elicitation Results with Document Analysis
- C. 3.1 Plan Business Analysis Approach with Estimation
- D. 5.1 Trace Requirements with Collaborative Games
Answer: A. The official 4.5 task card names Collaborative Games as a frequently used technique for getting stakeholders to work towards a common goal [7]. Who those stakeholders are and how to engage them is covered in stakeholders and personas.
Conclusion: the gap between BABOK collaborative games and real practice
BABOK treats collaborative games as a neutral, purpose-driven elicitation technique; practitioners use them more narrowly and argue mainly about framing.
| Area | Standard | Reality | Delta |
|---|---|---|---|
| Name | "Collaborative games" | Often renamed "activity" or "workshop" for senior audiences [13] | Reduced to a workshop format |
| Use | Elicitation and stakeholder collaboration [7, 8] | Heavy use in agile retrospectives and backlog prioritisation [11, 12] | Added by practitioners |
| Purpose | Shared understanding of a problem or solution [3] | Engagement and attendance gains are the most consistent finding [11] | No gap |
| Creativity | Listed as a strength [5] | Weakest-scoring area in a routine internal project [11] | Under-used |
| Audience | Any stakeholder group | Mixed views on executives; some C-suite sessions succeed [13, 15, 16] | No gap |
For the exam, learn the three elements, the three named games, the neutral facilitator and the false-confidence limitation. At work, define the purpose before the game, pick a name your audience will accept, and confirm the output with other techniques.
Practise CBAP scenarios on our CBAP practice exam.
Last verified: October 2026
FAQ
What are collaborative games in BABOK?
Collaborative games (BABOK 10.10) are facilitated activities with rules that help stakeholders build a shared understanding of a problem or solution. Participants work visually, for example with sticky notes or drawings. A neutral facilitator runs the game, and the group ends by agreeing on actions.
What are the three elements of collaborative games?
Game purpose, process and outcome. The purpose defines what the game should achieve, the process covers rules, facilitation and the opening, exploration and closing steps, and the outcome is the set of decisions or actions the group takes away.
Which collaborative games does BABOK name?
BABOK names Product Box, Affinity Map and Fishbowl as examples. Product Box finds the most valued features, Affinity Map groups ideas into themes, and Fishbowl lets an inner group discuss while others observe. Many other games, such as Speed Boat and Buy a Feature, come from Innovation Games.
What is the main limitation of collaborative games on the CBAP exam?
The most tested limitation is false confidence: because the group reaches a conclusion together, it may feel more certain than the evidence supports. Other limitations are that games can seem silly, can make reserved people uncomfortable and can waste time without clear objectives.
Do collaborative games work with executives?
Practitioners disagree. Some report successful sessions with a client's president, COO and CTO, while others advise calling the session a workshop because senior people may see games as trivial. The purpose and a strong facilitator matter more than the label.
Sources
- BABOK Guide v3, 10.10 Collaborative Games (IIBA KnowledgeHub)
- BABOK v3: A Summary (CBAP study summary, PDF)
- BA Techniques: Collaborative Games (training blog)
- CBAP certification (IIBA)
- Collaborative Games in Business Analysis (practitioner blog, 2021)
- Early-release chapter from Gamestorming 2.0 (2025)
- Task card: Manage Stakeholder Collaboration (IIBA, PDF)
- Task card: Conduct Elicitation (IIBA, PDF)
- Innovation Games: Creating Breakthrough Products Through Collaborative Play (book listing)
- Innovation game (encyclopedia entry)
- Adopting Collaborative Games into Agile Requirements Engineering (ENASE 2018, PDF)
- Game-based Sprint retrospectives: multiple action research (2022)
- Using a Team Game for Richer Retrospectives (2020)
- Serious games and Innovation Games at PlayCamp (2015)
- Client-only Use of Innovation Games (2010)
- Innovation Games to Feed the Fuzzy Front End (2009)
- How do you handle Sprint Retrospective meetings in Scrum? (forum thread, 2018)