United We Transform | Facilitator run sheet

Forced Connections

Small groups examine an unrelated stimulus object, catalogue its concrete attributes, and translate those qualities into fresh concepts for a specific problem. They cluster the resulting ideas, prioritize promising options with dot votes, and develop the top choices into actionable proposals.

45 minutes | 4 to 24 people

Choose this exercise

Purpose: Generate non-obvious solution concepts by intentionally mapping unrelated stimulus attributes to an existing problem statement.

Use it when: Use during ideation workshops when a group is stuck in familiar thinking, has exhausted direct brainstorms, or needs lateral concepts for a complex challenge.

Skip it when: Skip when the group is new and uncomfortable looking silly, when the problem is a straightforward logistical fix, or when immediate convergent analysis is required.

Group arrangement: Small groups of 3 to 5 participants (for 4 or 5 people, form a single group)

Timing: Source documents suggest 30 to 60 minutes; this 45-minute plan balances stimulus breakdown, divergence, sharing, and actionable development.

Materials and tools

Before participants arrive

  1. Display the core challenge or 'How Might We' question clearly on a central flip chart or screen.
  2. Arrange tables with flip chart paper, sticky notes, and markers for groups of 3 to 5.
  3. Keep stimulus items hidden in an opaque bag or box until the second step.
  4. Dedicate clear wall or board space for the whole-room clustering and voting phase.

Say this to open

Welcome. We are exploring our challenge from an unexpected angle. I will give each group a completely unrelated physical object. Your task is not to solve the problem with the item itself, but to pull out its concrete traits and force links back to our challenge. The stranger the initial connection, the better. Write down wild ideas first; we will extract practical concepts afterward.

How to run it

  1. Frame the challenge and model a connection 5 minutes

    Read the posted problem statement aloud. Give participants 2 minutes for clarifying factual questions. Model the mechanic using a pre-selected object before handing anything out: show an umbrella, list the attribute 'repels water', and say, 'What if we created an automated shield that absorbs routine inquiries before they reach our inbox?' Remind everyone to hold back criticism and stay divergent.

  2. Examine stimulus and catalogue attributes 5 minutes

    Hand one random object from the bag to each small group. Direct groups to handle their object, inspect its physical qualities, functions, materials, and motion. Instruct one person per group to record at least eight distinct attributes on their flip chart paper (such as flexible, hollow, clicks into place, reflective). Call time at 5 minutes.

  3. Force connections to the problem 15 minutes

    Direct participants to examine each attribute on their list and ask: 'If our solution had this property, what would that look like?' Everyone writes ideas individually on sticky notes, one concept per note, aiming for at least ten notes per table. If an idea sounds odd, have them write it down anyway without debate. Group members may also build verbally on each other's ideas.

  4. Post connections and share highlights 8 minutes

    Ask each table to select their three most provocative sticky notes and send one member to post them on the central board. Give groups up to 1 minute each to highlight their posted ideas from their seats. While groups finish, cluster notes with obvious overlaps into loose themes on the board.

  5. Prioritize with dot votes and develop next steps 12 minutes

    Hand 3 sticky dots to each participant. Give everyone 3 minutes to review the board and place dots on the concepts that offer the most promising starting points. Select the top 2 to 3 voted concepts. Assign one concept to each table to develop for 5 minutes: answer 'What is the practical version of this idea?' and 'What is one concrete next test?' Collect final summary sentences on the board.

Debrief questions

Finished output: A clustered board of lateral ideas, 2 to 3 prioritized concept candidates, and documented next-step development notes for each chosen concept.

Remote

Use breakout rooms of 3 to 5 people. Display the problem statement in the main room. Place a distinct high-resolution image of an everyday object (such as a stapler, bicycle bell, or pinecone) in each breakout workspace on a digital whiteboard. Groups record attributes on digital stickies, create connections, copy their top 3 stickies to a central board, and vote using digital stamps before returning to breakouts to develop actionable proposals.

Hybrid

Seat in-person participants at small tables and assign remote participants to online breakout rooms of 3 to 5. Hand physical objects to in-person tables and assign digital image cards to virtual groups. All groups post their top three stickies onto a unified digital board projected in the room and shared on screen. Run dot voting and the final development step simultaneously on the shared board.

Access and participation choices

If the session gets stuck

A group only lists surface traits like color and size, leading to shallow connections.
Prompt them on behavior and utility: ask how it operates, how it breaks, how it moves, or what sounds it makes.
Participants dismiss connections immediately as impractical or silly.
Remind the room that evaluation belongs in the final step; instruct them to capture every wild idea on paper first so the underlying principle can be extracted later.

Terms used here

Sources and adaptation

Observed in WorkshopBank, which attributes the lineage of forced connections to Don Koberg and Jim Bagnall (1972), Fritz Zwicky, and Edward de Bono's lateral thinking methods.

Retained the core mechanic of attribute extraction followed by forced problem mapping and the 5-phase structure documented in WorkshopBank. Structured the timing to a 45-minute workshop block, adjusted subgroup sizing to 3 to 5 people so all counts between 4 and 24 divide cleanly, modeled an explicit umbrella example before distributing items, and paced sharing so groups post notes first before giving brief spoken highlights.

See our editorial policy for AI use, sourcing and corrections.