Stage Three

Stage Three

Our design group has continued developing our User Interface Design in much the same way as we did in stages 1 & 2.

The task

In stage 2, our task is to perform user testing to try to improve upon the design we developed in stage 2. My primary role was to create the Test plan. We held a group meeting during which we discussed what information we wanted to gather, and what specifically we felt needed testing. From these discussions, I documented the test plan, with the exception of the test script which Cameron wrote, since he was going to be the Moderator.  I also had the idea of creating a score card for scoring each user against each task.  By using numerical values wherever possible, I felt sure this would simplify our analysis.

An epiphany

11292638_1643681655864431_103220080_n
Our paper based prototype for
testing user customisation was
a surprise hit!

While developing the test plan, it became clear to me that we needed to test more than just the structural design. This was because our test group were children in the ages of 5-12. I felt that they needed a more hands on demonstration of the games, and the customisation of their character.  Without these elements, the testing would be dull for them and unlikely to hold their interest.  I also felt that this would give us a better idea of the interest they had in these elements than simply asking.

A tester playing a minigame on the Android functional prototype.
A tester playing a minigame on
the Android functional
prototype.

As a result of this epiphany, Scott created a paper prototype of the character customisation, while I developed a basic, though incomplete android app as a functional prototype of the games.

Test day

On the day of testing, I acted as an observer, using the prepared

Our test setup, complete with screen capture and video of the subject.
Our test setup, complete with
screen capture and video of
the subject.

scorecard to take notes and rank each of our tasks according to how hesitant, uncertain and how much deviation from the expected task the user was.  Each of these values was collected as a number from 1 to 5, allowing a simple statistical analysis.  We also collected more anecdotal evidence as notes, while taking particular note of anything the user particularly liked or disliked.

Analysis

The spreadsheet for analysing our data.
The spreadsheet for analysing our data.

This approach of creating quantifiable data meant that I was able to collate and analyse all of the quantifiable data within 45 minutes to an hour of the conclusion of testing.  I did this by creating an ugly, but functional spreadsheet.  I then added the more subjective, anecdotal conclusions from the notes that has been made on the score cards.

Want to read more?

You can read more about what I discovered through the testing process by reading my reflection or read the brief below.

[embeddoc url=”http://www.davidroweonline.com/wp-content/uploads/2015/06/UI-Design-Brief-Stage-3-Final.pdf” download=”all” viewer=”google”]