What it is
An improvisational brainstorm based on interaction and movement with the body.
Reasons to use it
To remind participants that interactions are human and physical, to teach stakeholders empathy for users, and to get away from our computers.
Small: 1-2 hours
How to do it
Gather three to six members of the project team who are ready to think on their feet. If possible, identify a few users who can play along.
Bring the project team to the user’s environment. If that’s not practical, model the user’s environment in a conference room.
Assign each member of the project team to a role, interface, or “touchpoint” that you have identified in a journey map. If users are present, ask them to pretend to accomplish their goals as usual. Otherwise, assign a persona to each member of the product team who isn’t serving as a touchpoint. If you anticipate discomfort, assign roles in advance and start with a basic script.
Use props to role play how users accomplish their goals. “Speak the interface” to one another. For example, one of the touchpoints might say “Submit all of your required forms,” and the user might respond “Arg! I don’t know what forms are required!”
Review the exercise as a team and document the opportunities/challenges that this exercise suggests.
Applied in government research:
- No PRA implications. Even when users are present, the PRA explicitly exempts direct observation and non-standardized conversation, 5 CFR 1320.3(h)3.
- If you are not working with government employees, you will need to observe standard precautions for archiving personally identifiable information.
An explanation of bodystorming on Wicked Problems Worth Solving. Austin Center for Design.