Moderated and unmoderated tests are an essential part of UX work, but the biggest difficulty for those who perform it on a daily basis is creating clear and efficient roadmaps. A bad script leads to superficial results, while a well-constructed script generates deep insights and immediate action. This guide focuses on how to create, adapt and use scripts for moderated and unmoderated tests in a practical and recurring way, even in small teams.
The proposal is to show a simple way to create itineraries, define tasks, avoid biases and transform feedback into concrete improvements. Focus and routine: how to fit tests into the workflow without becoming a giant project.
Why the script and the heart of the test
The roadmap is what guarantees consistency, comparability and focus. Without him, the session becomes a loose conversation, full of vague opinions. With it, the researcher can observe behavior, detect friction and compare results between users. A good script does not constrain, but guides.
Script is not a list of random questions. It needs to be linked to clear objectives. If the objective is to evaluate onboarding, all tasks must lead the user to this flow. If the goal is to validate understanding of value, questions should explore initial perception.
Differences between moderated and unmoderated script
In moderated tests, the researcher can adapt questions, deepen answers, and ask for clarifications. The script acts as a guide. In unmoderated tests, the script needs to be self-explanatory, because the user executes it alone. This requires clear instructions, well-described tasks and objective questions.
Main differences:
- Moderate: flexible script, allows for in-depth study.
- Not moderated: closed script, focus on clarity.
Basic structure of a functional script
An effective roadmap might follow this structure:
- Introduction and context.
- Warm-up questions.
- Main tasks.
- Perception questions.
- Closing and final feedback.
This framework works for almost any test and can be adapted to suit the purpose.
Introduction: creating comfort
The introduction serves to reduce anxiety and align expectations. A short opening script might include:
- Presentation of the researcher.
- Explanation of the objective of the test.
- Reinforcement that there is no right answer.
Example of opening speech:
"Today we're going to test some flows. It's not you who's being evaluated, it's the product. Feel free to comment on anything you're thinking."
Warm-up questions
Initial questions help to understand the user's context. They also create rhythm before tasks.
Examples:
- How often do you use applications of this type?
- What do you expect from this type of product?
- What are the biggest difficulties in your daily life?
These questions help to calibrate subsequent analysis.
Defining main tasks
Tasks must be realistic and linked to the objective. Avoid artificial tasks that the user would not do in real life. Instead of "click the X button", use "try to do Y".
Examples:
- "You want to make an appointment. How would you do it?"
- "Imagine you want to buy this product. What's the next step?"
Focus and observe natural behavior.
Perception questions
After each task, ask questions that explore perception:
- What was easy?
- What was confusing?
- What did you expect to find?
These questions reveal invisible friction during the task.
Closing
At the end, ask about general impression:
- How was the experience?
- What would change?
- Would you use this product?
This moment usually generates important qualitative insights.
Roadmap for moderated tests: complete example
Objective: evaluate onboarding of a finance app.
Structure:
- Introduction: explain the test.
- Warm-up: "Do you control expenses today?"
- Task 1: "Sign up for the app".
- Task 2: "Add an expense".
- Questions: "What was confusing?"
- Closing: "Would you use it?"
This itinerary is simple, but it covers the entire initial journey.
Roadmap for unmoderated tests: complete example
Objective: evaluate app landing page.
Structure:
- Clear instructions at the beginning.
- Task: "Find what the app does".
- Objective question: "What is the main promise?"
- Task: "Click on the registration button".
- Question: "Would you trust your data here?"
In unmoderated questions, avoid too open-ended questions.
How to avoid biases in the script
Scripts can induce responses. To avoid:
- Do not use words that suggest the answer.
- Do not praise or criticize during the test.
- Avoid questions that start with “did you like it?”.
Neutral questions generate more honest answers.
How many tasks to include
A lean script is better than a long script. In general:
- 3 to 5 main tasks.
- 5 to 10 questions in total.
Excessive tasks tire the user and reduce the quality of responses.
How to adapt scripts for small teams
Small teams need agility. Good practices:
- Use ready-made templates.
- Reuse base questions.
- Adjust only specific tasks.
Therefore, the script can be created in less than 1 hour.
Roadmaps and prototypes
Prototypes allow you to test before developing. The script must consider limitations of the prototype and avoid tasks that depend on non-simulated functionalities. Explain this to the user to avoid confusion.
Scripts and recurring tests
When the team tests frequently, the script must be standardized. This allows you to compare results over time. Create a base of fixed questions and only change specific tasks.
Checklist for effective scripts
- Clear objective.
- Realistic tasks.
- Neutral questions.
- Total time of up to 30 minutes.
- Closing with open feedback.
This checklist avoids confusing itineraries.
How to analyze script results
After the test, group answers by topic. Identify:
- Recurrent problems.
- Unique relevant comments.
- Areas of greatest friction.
Transform these points into an improvement backlog.
How to communicate results to the team
Results must be clear and objective. A simple format:
- Problem identified.
- Evidence of the test.
- Impact on the user.
- Suggestion for improvement.
This format facilitates decision making.
Common mistakes in everyday itineraries
- Asking too many questions.
- Escape from the initial objective.
- Do not record results.
- Not acting on insights.
Avoiding these mistakes turns tests into real improvements.
Conclusion
Well-crafted scripts are the secret to effective moderated and unmoderated testing. They ensure focus, consistency and real learning. In small teams, a lean script is enough to generate powerful insights. The important thing is to maintain discipline, test frequently and transform results into concrete improvements.
##FAQs
1) How many people should I test?
Five users usually reveal the most problems.
2) Does the script need to be long?
No. The simpler the better.
3) Can I reuse scripts?
Yes, as long as you adapt the tasks to the context.
4) Does unmoderated testing work for prototypes?
Yes, if the instructions are clear.
5) How to avoid bias?
Use neutral questions and do not influence the user.