| Table of Contents | ||||
|---|---|---|---|---|
|
...
First Email:
Dear [Participant],
We we are thrilled to invite you to participate in our upcoming user test!
(Name) forwarded us your contact information. Your feedback is valuable to us and can help us improve our product. The test will take about 45 minutes and you can choose a time slot on the dates:
...
With your consent, this session will be recorded. We Wewant to assure you that your privacy is important to us, so we will only use the recording internally and store it for a short amount of time. Your personal information will not be shared with anyone outside the meeting.
...
Gofore UX-Team
Location/Time
...
13.04. - 14.04. from 9AM to 12AM
→ 2 Test Users from Gofore on Thursday, 06.04. and Tuesday, 12.04.
...
Agenda
Define what you will test
Set up Test Session
Prep the user and let them consent
Testing the Onboarding site, tutorial and Simulation
Write up notes
Action list
...
Script
Test Plan
User Testing Intro
Consent
Warm-up Questions
Prototype
Onboarding Page
Experiencing onboarding page
Questions
Task
Tutorial
Experiencing Tutorial Page
Depending on the user’s actions questions will be asked (During the tutorial and Simulation)
Simulation (Revisited)
Experiencing first page
Questions
Task
Interview regarding the whole experience (Including onboarding, simulation and tutorial)
| Info |
|---|
It is important to know that the script is flexible. The script will be used as a guideline. |
1. User Testing Intro
To get the test started, we should thank them for taking the time and helping us with our research.
After that, we’re going to introduce ourselves with our name, company and job title. (2-3 Minutes)
Hi, _____________. My name is ___________, and I’m going to be walking you through this session today.
Before we begin, I have some information for you, and I’m going to read it to make sure that I cover everything.
You probably already have a good idea of why we asked you here, but let me go over it again briefly. We’re asking people to try using a Website that we’re working on so we can see whether it works as intended. The session should take about 45 minutes.
The first thing I want to make clear is that we’re testing the site, not you. You can’t do anything wrong. We’d like you to explore the product freely and share your thoughts with us, so please speak out loud during the session.
Legal Considerations and Consent Form
(especially for recording)
Questions we want to ask (DRAFT)
Possible scenario etc possible scriptAsking the legal questions and let the note taker start the recording session after the tester has given consent. (3 Minutes)
Question | Background | Notes |
|---|---|---|
1- Do you have any questions about the recording process or what will happen to the recording afterwards? → If not, I would start recording the session. | Starting question before the recording starts. We should ask for consent on camera. | Start the recording session, if the answer is YES. |
2- Do you have any objections about us recording this session, including your voice and face or my colleague taking notes on the side? | If the answer is No, continue with asking questions about the personal data. |
Warm-up Questions
Question | Background | Notes |
|---|---|---|
Please tell us a few details about you. Warm-up questions: What is your name and age? Could you please tell us about the tasks of your job and your job title? Civil Servant tester question: Can you briefly describe your role and responsibilities within the public sector? | Gather personal information and check if the tester fits the screener details | continue with a short onboarding text and post the link in the Teams chat. Explain what will happen next on the session. |
Prototype
Questions we want to ask during the session
User clicks on link and we ask him to share the screen with us. Explain the user should take the time to read through the onboarding page - this should take about 5-10 minutes .
| Warning |
|---|
If the user asks you how to do a task, please do not tell him/her but rather ask “How do you think the task should be done?” or “What would you expect it to do?” |
“Thank you! Let’s get started with the session, please share your screen with us, so we can observe your interactions with the website/product. (Wait for them to open the page)
(First Request) Please keep in mind that this is a clickable prototype. But currently please do not click any button. You can scroll if you want to. Please think out loud while doing that and explain what you are seeing what is your first impression of the page.
(Wait a bit for them to explain) (Ask questions about onboarding page depending on what they explained)
Can you describe the goal of the website?
In your own words, please describe what the “Building Blocks” are
Do you have an understanding of what the “Simulation” is?
(Improvise)
(End of onboarding)
Please take your time and scan the website first.”
---
Question and requests | Task | Background | Notes |
|---|---|---|---|
Onboarding page:
| Explain the simulation, building blocks and use cases in your own words and start the it. | Does the onboarding page explain the simulation accordingly? What kind of information would we need to add to explain the simulation better? Is the page self explanatory? | Wait a few minutes/moments before asking questions |
After the tutorial is completed:
| Explore the tutorial. | We want to check if the user knows what to do on their own, otherwise the tutorial is not a good onboarding option. | Tutorial starts - Wait until the user clicks through the whole tutorial. Just intervene if asked. |
Simulation Task: → After you’ve experienced the simulation, please explain the building blocks in general in your own words → please explain one “specific build” block
| Test main functionalities: TBD by Artun Gürkan and Martha Vasquez Screen background: GovStack approach and Building Blocks. Ask this question in between:
| How “good” do the UI Elements feel? Did the information get transported as we planned? Does the perspective/context change work? Does the progress bar work - if not, maybe it can be removed from the layout. | Ask these questions after the user used the simulation for a few actions. How useful are the overlays? This part should take about 10-15 Minutes |
End Questions:
| Ask the user to close the prototype and stop the screen sharing, so we can ask them a couple of more questions. |
After the test - stop the recording and say
“Thank you very much for your participation, your feedback really helps us improve our product.”
After(To-do-List)
create a task list and go through them 1 by 1
if there are a lot of highlights on that list, we know which feature to redesign
evaluate your own performance
Create a to-do list with action items
improvements and why → refer to the task and question of the session
explain the problem in a “How might we” - question
add possible suggestions
should/could be improved section
create follow up Jira Tasks