This template structures what a facilitator should say and do throughout a testing session of a digital product or interactive prototype with a user.

Disclaimer. Legal and operational aspects of research (consent forms, GDPR requirements) aren’t covered here. This template is best suited for “UX teams of one,” when a non-researcher (designer, product manager, etc.) has to conduct good enough testing.

Facilitator’s data

Goal (what you ultimately want to achieve):

To check whether…
To learn how… in reality.

Research questions (currently unknown information that you want to get):

Do users understand that…?
How convenient/understandable/clear is… for users?
What is the user’s mental model for…?
How well does… tackle the user’s problem/need…?

<aside> 👉 Replace all the green <text in the brackets> with information relevant to your case.

</aside>

Prototype:

<Link to the prototype>
<Video recording of you passing the scenario> Prototyping tools and prototype versions often change, and a recording can serve as a good reference for the team even if the prototype for some reason becomes unavailable.

<aside> ⚠️ If user login is required, make sure you’ve prepared test credentials, or a user will feel comfortable using real credentials (compare banking vs. online education apps).

</aside>

1. Intro

<aside> ⚠️ Memorize and learn how to pronounce the user’s name. For example, “Juliet(a)” sounds differently in Mexico and France. Check this: pronouncenames.com.

</aside>