Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Testing outcomes

  1. Understand if the topic page leads to the outcomes/call to action in the content strategy
    1. Decides to study (at Victoria) a subject in this topic and moves over to relevant degree page
    2. Decides this topic is not a good fit and move to another topic
    3. Contact us using the details provided.
  2. Understand if the programme page leads to the outcomes/call to action in the content strategy
    1. Applies to enrol.
    2. Contacts us for help with course planning
    3. Registers for an open day/Student Recruitment event
  3. Identify where users have issues with the designs (so we can improve before building)
  4. Identify any unmet user needs (for team consideration)

Notes for facilitators

  • We are doing "user testing", meaning that (after the greeting and introduction) they drive the computer and we guide, prompt and most importantly, observe.
  • As natural as possible, given the circumstances and tasks
  • Go with the flow, redirecting at the end if key areas (tabs, blocks, functions, etc) were not covered.
  • Paul to facilitate and Jo to observe and take notes.
  • Will request permission to record screen and voice.

Participants

  • Seven to ten, with most being new to us and possibly 1-2 from our previous batch of school students.
  • $30 Prezzie card per participant
  • Will meet at each school site

Equipment and set up

  • Paul's own laptop or the Victoria one with the following:
    • Hotgloo opened on the groupings, adjusted for the sceen size
    • Screen recording software
      Voice recording software
  • Printed copies of ethics form: Participant Information Sheet.
  • Printed copy of test script.


Introduction

The introduction is very important.  

  1. Put the student at ease and explain the purpose

Key messages:

  • This part of our website is build for school students, so we have to test it on people like you.
  • We're interested in observing you play with our new web page designs and listening to your feedback.
  • We're not testing you or your computer or website skills! Every answer you give us is helpful and RIGHT! 
  • Please don't hold back, as we need to hear all your thoughts, no matter how critical.
  • Your participation is highly valued - you're helping make a difference - thank you.

2. Explain privacy - but in a low-key non-scary way

  1. The testing is confidential

"You won't be identified in any notes - at the most we'll use your first name."

 

2. We'll use screen recording software. 

"We'll use software that records the screen in case we need to go back over anything after the session. You won't notice that it's running. It will record your voice, but not a photo of you."

 

3. Please sign the ethics form.

 

Conversation guide

1. Welcome, build rapport and set the scene 

Talk about them as a person - their interests, leading to their study interests now. Leading to tertiary study - plans for next year?

Use of the web as a source of information for future decisions

Any knowledge of VUW website

Explain user testing, what wire frames are (and are not), and the importance to articulate their thoughts and impressions (questions, likes, hesitations, etc)

Explain the level of feedback we would like (Could show them how the first page of the wire frames has been translated to a live web page, if it helps).

We have only written up one topic or subject area so far and that it Architecture, so for the purposes of this exercise we need you to pretend that you are considering studying architecture and would like to learn more about this.

2. Topics

Let's start with the high level view of what you can study at Victoria. Have a look for information about studying architecture at Victoria.

Student will either browse, use search interests or site search. If not browse ask why they searched and why the one they chose.

Ask them to describe what they see, can do and why they are taking the actions they are

Should get to Architecture topic page. If not, assist.

If lost for words prompt with question like, "What does this page tell you?" or "Tell me what you are thinking"

About tab

Do they use tool tips? Do they try clicking on different things?

Watch for how early they jump to subjects (and is it from tab control or links) and even to degrees (in which case bring them back to topics once they finish their roaming).

"What content seems the most interesting, confusing, boring, etc?" Careers? Stories?

What did you learn on that page?" "How do you feel about that page?"

Do they get to the contact details block (here or on any tab)?

Subjects tab

Do they try to use anchor links (not working)?

Is the "What you might study" section useful to you? Why? What else would you want to know?

 

3. Degrees

At some point the user will get to the degree page. If not, prompt and ultimately assist.

 

 

Close out

  • Pressie card
  • Copy of GUS 
  •  Tell them how to find out about open days


 



 

  • No labels