Versions Compared

Old Version 15

changes.mady.by.user Martha Vasquez

Saved on

compared with

New Version 16

changes.mady.by.user Martha Vasquez

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel7

...

After that, we’re going to introduce ourselves with 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

Asking the legal questions and let the note taker start the recording session after the tester has given consent. (3 Minutes)

Question

Reason

Background

Action/

Notes

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.

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.

Please tell us a few details about you.

Warm-up questions:

What is your name and age?

What is

Could you please tell us about the tasks of your job and your job title?

Please explain to us how a decision process would look like in your job.

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.

Questions we want to ask (DRAFT)

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 as soon as you opened the link, so we can observe your interactions with the website/product.

Please take your time and scan the website first.”

Question and requests

Task

Reason

Background

Action/

Notes

Onboarding page:

  1. Exposure test: What was your first impression of the

website

  1. page?

  2. Exposure test: Can you describe the goal of the website?

Please explain

  1. Could you please start the simulation?

Explain the simulation, building blocks and use cases in your own words

what a use case is

and

building blocks areCould you please

start the

simulation?

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:

  1. How did you feel about the pacing and content/text of the tutorial?

  2. Was there anything in the tutorial that surprised you or that you didn't expect?

  3. How confident do you feel in your ability to use the simulation after completing the tutorial?

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:

  1. How do you feel about the user interface of the simulation?

How clear is the displayed information for you

  1. What does the simulation do?

  2. Can you describe the roles and tasks in the simulation?

  3. → Ask this questions after the first few interactions: What tasks have you completed so far?

  4. How do you feel about the hints?

  5. How do you feel about the DIAL menu? Do you find this helpful? If yes/no, please explain why.

  6. How do you feel about the contextual change? Do you understand which perspective you are currently viewing?

  7. How do you feel about the progress bar?

  8. How would you describe your understanding of how the building blocks are used?

Test main functionalities:

TBD by Artun Gürkan and Martha Vasquez

Ask this question in between:

  • Can you walk me through your thought process as you completed the tasks?

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:

  1. What are the most memorable

challenges have you encountered in the simulationFurther

  1. tasks and features of this simulation for you?

  2. What would make your experience on the simulation better?

  • Can you walk me through your thought process as you completed the tasks?

    1. Follow-up Tutorial question: After experiencing the simulation -

    can you think of any changes you would make of the tutorial?Please explain what are the next steps you would take

    1. did you feel well introduced to it by the website and tutorial?

    2. Would this simulation support you make a decision regarding GovStack?

      1. If not, what feature/information was missing?

    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