Forced Analogy

Purpose

Forced Analogy pushes teams to compare their challenge to something completely unrelated — a restaurant kitchen, a beehive, a rock band — and extract transferable principles. By deliberately breaking familiar mental models, the technique generates novel solutions that rational analysis alone would never surface.

At a glance

• Group size: 3–12
• Duration: 20 minutes
• Difficulty: Intermediate
• Facilitation style: Creative, guided discussion
• Setting: In-person or virtual

How to run

1. State the challenge (2 min). Write the problem or design question on the board.
2. Introduce the analogy domain (2 min). Choose or randomly assign an unrelated domain (e.g., “a hospital emergency room”, “a jazz band”). The more distant from the actual domain, the better.
3. Explore the analogy (8 min). Ask: “How does [analogy domain] handle a challenge like ours? What roles exist? What processes? What makes it succeed or fail?” Capture observations on sticky notes.
4. Transfer principles (5 min). For each observation, ask: “What would this look like in our context?” Translate analogy insights into concrete ideas.
5. Select the best (3 min). Vote or discuss which transferred ideas are most promising.

Materials needed

• Sticky notes and markers
• A list of possible analogy domains (prepared in advance)
• Whiteboard divided into two columns: Analogy World | Our World

Pitfalls & common mistakes

• Choosing an analogy too close to the domain. “How would another software company handle this?” won’t yield novel insight.
• Staying too literal. The power is in abstracted principles, not surface similarities.
• Dismissing ‘silly’ analogies. The most absurd comparisons often produce the most original ideas.

Inclusion & accessibility

• Offer multiple analogy domains to choose from — not everyone connects with the same references.
• Explain the analogy domain briefly for participants unfamiliar with it.
• Allow both visual and verbal expression of analogy connections.

Variations

• Random object: Use a physical random object (grabbed from a bag) as the analogy source.
• Nature analogy: Restrict to biological systems — ecosystems, organisms, natural phenomena.
• Historical analogy: Compare to a historical event or era.

When NOT to use this

• When the team needs to optimize an existing solution rather than rethink fundamentals.
• When time pressure demands quick convergence rather than divergent exploration.

Source & further reading

• Gordon, W. J. J. (1961). *Synectics: The Development of Creative Capacity.* Harper & Row.
• Gray, D., Brown, S., & Macanufo, J. (2010). *Gamestorming.* O’Reilly Media.