3.1. Best Practices for Moderating

● Begin with rapport: Clarify goals and reassure users it's the prototype—not them—that's being tested.

It's important to start the testing session by establishing a comfortable environment for the participants. This means clearly explaining the objectives of the test and emphasizing that the only thing under review is the prototype, not the users themselves. This approach helps to alleviate any nerves or pressure the users may feel, allowing for more open and honest feedback.

Imagine you’re trying out for a play. If the director reassures you that they’re just looking at how the scenes play out, rather than judging your performance, you would likely feel more relaxed and perform better. Similarly, testing a prototype works best when users aren’t worried about being judged.

● Encourage think-aloud: Ask “What are you thinking?” if they’re silent.

Encouraging participants to vocalize their thoughts while they interact with the prototype provides insight into their decision-making processes. By prompting users to express what's on their mind, researchers can gather valuable data regarding user reactions, confusion, and overall interactions with the prototype. This practice can highlight areas in the design that may not be intuitive or engaging.

Think of a teacher encouraging students to explain their problem-solving steps in math class. When a student says, 'I chose to add these numbers first because...', the teacher can see their thought process more clearly and help them where needed.

● Stay neutral: Don’t offer help that biases results—guide only if they’re truly stuck.

As a moderator, it's crucial to maintain neutrality to avoid influencing the participants’ responses. If a user struggles with a task, the moderator should offer minimal assistance only when it's necessary. This approach ensures that the data collected reflects the user's genuine interaction with the prototype, providing true insight into usability issues.

Consider a sports coach observing players during practice. If they jump in to correct a player’s technique too quickly, they might alter how the player approaches the game. Instead, waiting to see how the player handles the situation independently can provide better feedback on areas needing improvement.

● Prompt gently: If they pause, say: “Tell me what’s happening in your mind right now.”

When participants hesitate or pause during the session, gently prompting them can help bring their thoughts to the surface. This technique allows the moderator to understand how users interpret tasks and identify moments of confusion, which can be critical in improving the prototype.

Think of a friend who’s presenting a project. If they stumble, a supportive comment like, 'What were you thinking there?' helps them regain their confidence and share their thought process, enriching the discussion.

● Avoid closed questions: Use prompts like “Why did you do that?” or “What do you expect next?”

Closed questions often lead to simple 'yes' or 'no' answers that don’t provide much information. Instead, open-ended prompts encourage participants to elaborate on their thoughts and experiences, thus yielding richer insights into user behavior and expectations.

Imagine asking someone about their favorite movie. Instead of simply asking, 'Did you enjoy it?' which might get a 'yes' or 'no', asking 'What did you enjoy most about the movie?' invites a much more thorough and insightful response.

--