methodatlas
RunsheetInnovation

Rolestorming

ComplexityLow
Time30-60 min
Participants3-12
FormatWorkshop
MaturityEstablished
01

Prerequisite

What needs to be finished first

Complete firstPersonas

At least three concrete personas, competitor profiles or fictional roles are prepared as cards with name, context and goals.

Without: Without developed roles, ideas remain clichés and the method provides no real perspective shift.
Complete firstHow Might We

A challenge formulated as How Might We is available in writing for the role to work on.

Without: Without clear challenge, role ideas drift into disconnected anecdotes and cannot be consolidated.
02

Preparation

What needs to be ready before start

Materials

Role cards with name, context, goals, pet peeves (one card per role); stickies; timer; whiteboard or board with lanes per role and shared consolidation area.

People / roles

One facilitator who orchestrates role changes; three to twelve participants who step into roles; one scribe per role (optional) or self-documentation on stickies.

Pre-read

Challenge as HMW sentence; role list (for example grandmother, competitor CEO, 12-year-old child, industry outsider); short briefings per role; example idea as warm-up.

Time needed

30-60 min

Setup

Distribute role cards (one per person or small group). Board lanes per role. Rule: speak from the role, not about the role. Exaggeration allowed.

03

Core question

The one question this method answers

Which solution ideas for the challenge emerge when the team thinks from clearly defined outside roles?

04

Flow

Marker: Phase

StepDurationActionHint
1Phase 1: Warm-up and role briefing
10 minRead challenge aloud. Hand out role cards. Each person reads their role and names three traits of the figure. Short example round with test question.If someone answers from their own perspective during example round, steer briefly. Role is not costume, but thinking frame.
2Phase 2: Solo ideation in role
10-15 minSilent phase: each person generates as many ideas as possible in their role on stickies. One idea per sticky. Target at least 8 ideas per role.Phones away. Anyone stuck in role should use concrete traits of the figure (for example "What would my grandmother find annoying about this?").
3Phase 3: Role showcase
15-20 minPer role, 2-3 min pitch of best ideas, still spoken in role. Others note follow-on ideas. Cross-pollination: pick up ideas from other roles.If a role only produces clichés, facilitator asks from role context: "What specifically annoys this person about the current solution?" Force concreteness.
4Phase 4: Translate back and cluster
10-15 minDrop role. Translate ideas into own perspective: which of them is feasible or at least testable in context? Cluster, create shortlist of 3-5 ideas.Without translation back, exercise remains play. Every idea needs a note on how it would look concretely for the real target group.
05

Artifact

What comes out at the end

Form

Board export or markdown note with challenge, role list, collected ideas per role, shortlist after translation back with concretion note and follow-up action per top idea.

Versioning / ownership

Date, challenge and participants in header. Derive shortlist as separate document or tickets. Follow-up sessions reference the role that produced an implemented idea so the lever remains transparent.

Tool alternatives
  • Miro or FigJam with lanes per role
  • Whiteboard with photo export
  • Notion page with section per role and shortlist
  • Mural with Rolestorming template

rolestorming-working-template.md

Compact working template for Rolestorming with context, input, output artifacts, and next step.

Rolestorming Working Template

Goal

Brainstorm from other roles or personas to break your own mental patterns.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Execution

Short notes along the runsheet.

Output artifacts

  • Role cards:
  • Idea pool by role:
  • Consolidated shortlist:

Assumptions and open questions

  • ...

Decision / next step

Owner, date, and success signal.

06

Example output

Concrete filled scenario, fictional example

rolestorming-beispiel.md

Concrete filled scenario, fictional example

Rolestorming - How might we guide first installers to their first aha moment in week 1? (2026-05-18)

Roles: Sabine (solo tax advisor, 52, impatient), Marcus (competitor CEO), Ben (12 years old, TikTok-native), Anonymous designer from Duolingo.

Sabine

  • Tutorial in 30 s with client example instead of demo data.
  • Skip button always visible.
  • WhatsApp support bubble after step 2.

Ben

  • Streak display from day 1.
  • Vibration as reward.
  • Mini quiz instead of slideshow.

Translation back - Shortlist

  1. Task template with real industry context on first start (from Sabine). Owner @lisa, validation via fake door by 2026-05-30.
  2. Step quiz instead of linear slideshow (from Ben, Duolingo). Owner @ben.
  3. Inline support hint after step 2 (from Sabine). Owner @anna.
07

Pitfalls

Recognize symptoms and steer against them

Trap

Role becomes cliché

Symptom

Ideas from grandmother role are only big, slow, simple instead of concrete needs.

What to do

Fill role cards with real traits (hobbies, pet peeves, goals). Facilitator asks follow-up from role context instead of allowing cliché.

Trap

Not staying in role

Symptom

Participants slip back into own view: "But realistically that would not work."

What to do

Facilitator interrupts and brings back to role: "What would Sabine say about this?" Reality check only in Phase 4.

Trap

Missing translation back

Symptom

Workshop ends with funny ideas from roles, none transferred into real concept.

What to do

Strictly keep Phase 4, at least 10 min reserved. Every shortlisted idea needs note on how it would look for real target group.

Trap

Too little diversity in roles

Symptom

All roles resemble own target group (for example only three personas from same segment).

What to do

Plan at least one industry-foreign, one child-like and one adversarial role (for example competitor, regulator). Distance creates new associations.

Trap

Status dynamic breaks through

Symptom

Senior participants do not take role work seriously and comment ironically.

What to do

Set norm before start: taking role seriously is prerequisite. If senior keeps blocking, short 1:1 or switch role. Otherwise group flips.

08

Stop criteria

Done signals checkable in under a minute

No clearly formulated HMW sentence or challenge anchor available.
No willingness in team to take roles seriously, irony dominates.
Role cards are missing or so generic that no perspective shift emerges.
Topic is purely technical without user reference, roles provide no leverage.
Fewer than three participants, role diversity not reachable.
Time budget under 30 min, solo phase and translation back both impossible.

Finished the runsheet?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.