Hello, this template will give you a good opportunity to plan, conduct and analyse the testing results. I tried to make it as easy to understand as possible, but if you will have any concerns, please, contact me via telegram. Thank you.
Test goals
As an example «To measure the baseline of understandability of Course Passing flow».
…
Test goals
Name
KPI
Notes
Name
KPI
Notes
1
As an example «To measure the baseline of understandability of Course Passing flow».
How we would understand that the goal is achieved «We receive enough (not less than 30) representative answers clearly shows participants perception (CSat-like)»
There are no rows in this table
Hypothesis
Journey step
Area
Hypothesis
KPI
Validation method
Status
Journey step
Area
Hypothesis
KPI
Validation method
Status
1
When it will appear?
User Experience
…
Unclear
There are no rows in this table
Methodology
The main goal of the study was to …. To do that, we will conduct a series of exploration think-aloud interviews where we will address scripted questions and prove our hypothesis.
We suggest not to spend more 5–7 sessions because they will cover 80% of problems, which face 80% of users. However we’ll conduct 10 interviews because of the RITE method.
Think aloud sessions
Think aloud sessions are more structured than interviews and less likely to go off road. However, we have prepared scenarios for the tasks with clarification questions to help users perform the needed actions.
Before the session, it’s crucial for the user to understand what’s going on. We need to calm them down with small talk and provide clarification that we test the service, not the user, there are no right or wrong answers and all the feedback would be helpful to make an experience more obvious and friendly.
The next step is to show an example, what we expect during the interview. The interviewer can provide and example of task execution by speaking his thoughts aloud.
During the session the interviewer should encourage people to speak their minds and ask clarification questions, meanwhile interviewer shouldn’t show any sign of clue for the user if he/she is doing right or wrong.
Note! The interview should be built on trust and conversation, not interrogation, so the strict following of the interview script is highly unrecommended. Use the flow instead.
for problems that occurred >3 times
The idea of RITE testing is very similar to general usability testing: it also uses the same script, the sessions are also conducted with thought aloud, however after each session, the design team would make adjustments to the designs, solving every problem noted during the session. In this case new respondent wouldn’t need to face them again and new flow problems could be discovered. However, there are some limitations, like huge flow problems shouldn’t be fixed between sessions, but only those problems, that can be rushed in a matter of hours and those problems, which doesn’t need additional validation.
Respondents
Respondents description goes here…
Respondents list
When
Name
CSat
Notes
Link
When
Name
CSat
Notes
Link
1
There are no rows in this table
Scenarios
Scenarios actual for moderated studies (like interview) and for unmoderated user tests.
Start
Greetings, how are you…
My name is …
Thank you very much for…
Right now we’re in the middle of …, and here we will need your help.
Today we’re going to test, not you, but our design to find some gaps to adjust our solution to make it align with your perception of how things should work.
During our session I’ll ask you to perform some tasks and a loud your thoughts in the process, for example…
If you’re ready I would like to start recording.
Scenario 1: Landing (Example)
Let’s start. In your professional growth plan your resource manager marked {Theme} as a major point of improvement and suggested to find some course to fill this gap. Let’s not waste any minute and do that!