What it is
An imaginative interview activity that helps people express frustrations and desired possibilities. The participant invents a superhero for a familiar area of life; the researcher explores what each imagined power reveals. The focus is the person’s experience, rather than a team’s ideal product.
When to use it
Primarily during Immerse, within exploratory interviews. Use with people who have relevant experience and are comfortable with the metaphor. A separate team variation can support Ideate.
Why (value)
An imaginative prompt can make it easier to discuss needs that are difficult to articulate directly. Treat the response as an opening for inquiry rather than a feature request.
How to run it
- Choose an area of life the participant knows, without prescribing a product or solution.
- Explain that they can imagine a superhero whose powers overcome frustrations in that area. Invite impossible powers as well as ordinary ones.
- Let the participant describe, write or draw their ideas. Drawing is optional; clarify the premise if needed and stop the exercise if it is uncomfortable or confusing.
- For each power, ask what it would help with and invite a concrete example from their experience. Use neutral follow-ups rather than suggesting answers.
- Record their explanation separately from your interpretation of the underlying need.
- Afterward, compare interpretations with other research and explore possible responses. An imagined power does not establish a requirement or validate a feature.
Inputs and outputs
- Inputs: A focused research question, a participant with relevant experience, and optional paper or a shared canvas.
- Outputs: Participant accounts and imagined powers, with traceable interpretations of possible needs. Record possible solution directions separately as hypotheses.
Time and effort
Low preparation. Allow flexible time within an interview and pilot the prompt. The original article does not prescribe a fixed session length.
Evidence and limitations
Participant explanations provide direct-user, qualitative, attitudinal evidence about what that person reports. Interpretations of needs remain analysis; proposed solutions remain hypotheses. The exercise does not establish observed behavior, prevalence, priority or solution effectiveness. Corroborate consequential findings through appropriate additional research. See Evidence and limitations.
Tips and pitfalls
- Do not require a costume, origin story, weakness or nemesis; those can distract from the participant’s experience.
- Do not force drawing or judge artistic ability.
- Preserve surprising answers and the person’s language without assuming your interpretation is correct.
Variations
Team ideation — Ideate: A team may use the superhero metaphor to explore possibilities. Label those outputs team-generated inference, not participant evidence or validated user needs. Do not present this variation as Buley’s original interview protocol.
Related methods
Need help planning research or facilitating this method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
This summary follows Leah Buley’s generative interview idea. The facilitation and recording guidance is a practical adaptation, not a verbatim reproduction or a validated standardized protocol.
- Leah Buley, Adaptive Path, “Design a Superhero”, March 29, 2010. Original archived byline, date and article inspected.
- “UX Superpowers,” Effervescent Librarian, May 8, 2014, a contemporary reference identifying Buley at Adaptive Path.
Explore related methods
- Interviews — Talk with users one on one to understand their goals, context, and reasoning in their own words.
- Contextual inquiry — Observe people doing real work in their own environment while they explain what they are doing and why.
- Brainstorming — Generate a large volume of ideas quickly by deferring judgment.
