Iteration 3

With the digital prototype we took a step back in our testing process. We want to be sure that just like the paper prototype the functionalities of the digital one are all clear. This will be investigated in iteration 3. This iteration isn’t completely finished yet, so we will wait with publishing the results and the conclusion, but here is already the set-up of it.

Iteration 3

Goal

  • We want to test whether by digitalising the prototype no new issues are discovered that weren’t there in the paper prototype.
  • We will test if the reactions of the users remain the same.
  • Temporarly the  buttons with logo’s are replaced by keywords to test just the basic operations. Later on, the logo’s on the buttons will be tested on ‘clearness’.

Method

Digital Prototype in HTML5 together with the Think Aloud protocol.

Rationale

  • Digital Prototype is used because the application is developed to work as a plug-in with accompanying site and this closely resembles how the application will look like in the future.
  • The reasons to use the think aloud protocol are the same as in Iteration 1.

Who, What, Where, Time?

  • Who? 5 testpersons, 2 were family-related to a group-member, 3 of them were searched in the wild
  • What? All the test-persons will be asked to execute some basic assignments: register (T3.1) and log-in (T3.2) , give a tip via the plug-in (T3.3), remove a friend (T3.4), look at a tip and like it (T3.5), add a friend  (T3.6), give a tip via the site (new-tip tab and friends tab) (T3.7), log out (T3.8).
  • Where? 200A Foyer and Kapucijnenvoer 113, 3000 Leuven
  • Time? The duration of each test took at most 5 to 10 minutes.

Results

  • n = 3: Didn’t find at all the functionality to add a friend. They used the search-functionality to look for a new friend and not the add-friend-button (R3.1).
  • n = 2: Found the adding-functionality, but it took at least ten seconds longer than the other assignments to complete (R3.2).
  • n = 2: Mentioned that the concept of liking a tip is clear, but re-liking1 a tip wasn’t easy to find (R3.3).
  • n = 1: After registration asked and we quote: “Did it work?” (R3.4).

Conclusion

  • T3.1 It was not clear to all test persons if registering was successful or failed so we will add a notification of this (R3.4).
  • T3.2 There were no noticable problems with the login, so this is good.
  • T3.3 Everything went fine.
  • T3.4 By executing this assignment we noticed we forgot the ‘Are you sure? – pop-up’2 !
  • T3.5 Liking a tip was no issue. To make sure people do find the re-liking1 functionality we will display a short message when hoovering over the (dis)liked button (R3.3).
  • T3.6 All the testpersons encountered problems while adding a friend. The button to fullfill this functionality is not obvious enough. They all searched for this at the left side of the page and didn’t look at the right top. We will adjust this button and move it to the left top (R3.1 & R3.2).
  • T3.7 Giving a tip via the site didn’t reveal any problems.
  • T3.8 Also logging out gave us no noticable problems.

1: Re-liking: When you have (dis)liked a tip, you can change your mind and undo your opinion.

Areyousure 2: Are you sure? – pop-up: Extra confirmation screen when removing a friend, because comments on our blog suggested that this decision was too heavy without any confirmation.

Areyousure

Advertisements

Recap Iteration 2

After exploring the world of testing and iterations for the first time, a new iteration was immediately set-up and executed. Here is a brief recap of it.

Iteration 2

Goal

  • We want to test if the logo on the main screen doesn’t distract the users anymore (R1.1)
  • Is the friends-functionality added in accordance to the expectation of the users (R1.2,R1.3)?
  • R1.4 and R1.5 will not be tested in this iteration. The first result is trivial and the second will be elaborated later.
  • We added ‘settings’-functionalities, we will test them as well.

Method

We use the Wizard Paper Prototyping method together with the Think Aloud protocol.

Rationale

  • Wizard prototyping allowed us to quickly add the friends-functionality and to change the layout regarding the logo.
  • Think Aloud gave us the opportunity to test where the attention of the users was going to. We wanted to know what the test-persons thought about the functionality and not just whether the functionality was operating in the right way.

Who, What, Where, Time?

  • Who? 3 co-students, each belonging to a different group from the class User Interfaces.
  • What? All the test-persons were asked to execute some basic assignments: give a tip via the plug-in, give a tip via the friends-tab, add a friend, search for a friend, like a tip.
  • Where? The tests took place at the campus in the 200B building.
  • Time? The duration of each test was 5 to 10 minutes.

Results

Some new remarks were mentioned:

  • R2.1: All the users said that the logo’s of the buttons on the friends tab not pointed out what their functionality was.
  • R2.2: One person thought that the search-for-friends-fucntionality was not clear enough, but the two other users understood the search function completly right.
  • R2.3: Two users told us that they didn’t immediately saw what was adjustable and what not when they were on the settings-page.
  • R2.4: There were no remarks anymore on the logo of the main page.

Conclusion

  • The added functionalities (friends and settings) were necessary but the logo’s on the friends tab and the layout of the settings page need to be changed (R2.1, R2.3).
  • The new location of the logo was clearly an improvement (R2.4).
  • Because just one person pointed out that the search-functionality wasn’t clear, but the others didn’t, this aspect will remain the same in the next iteration (R2.2).

Recap Iteration 1

In this post we will give a short overview of the first iteration of the development of our application Tip-It!

Iteration 1:

Goal

Get a general idea of the impression of the users. Do they understand and find the functionalities?

Method

We use the Wizard Paper Prototyping method together with the Think Aloud protocol.

Rationale

  • Wizard prototyping is highly applicable in our case because you can test en maybe adjust your prototype immediately. Different functionalities can easily be added or removed.
  • Think Aloud allows us to look into the mind of the users and to collect their thoughts.

Who, What, Where, Time?

  • Who? 4 co-students, each belonging to a different group from the class User Interfaces. 
  • What? In the first two tests, the users had to tell what they should do with the given prototype, without any information. What did they expect to happen when they executed their actions? The other two testpersons were asked to try some basic functionalities, namely give and like a tip.
  • Where? The tests took place at the campus in the 200B building.
  • Time? The duration of each test was 5 to 10 minutes.

Results

3 of the 4 people spontaneously told us that they liked the concept of the application! Yet there were some remarks:

  • R1.1: The 4 testpersons all thought that the logo at the top of the site was a button. They also mentioned that it distracted them from the actual functionality.
  • R1.2: 2 users wondered if there was a friends-functionality en warned us for possible spam if the application was open to everybody.
  • R1.3: One user asked if the possibility to send a tip to multiple persons exists.
  • R1.4: All testpersons clicked on the site-preview while this wasn’t a link to the tipped site and thus non-clickable.
  • R1.5: Two users didn’t exactly understand what the purpose of the notifications was.

Conclusion

  • In general the users were very enthusiastic about the application.
  • But a certain friends-functionality was clearly missed and will be included in the next iteration, just as the possibility to send a tip to multiple persons (R1.2, R1.3).
  • The previews will include a link to the site they represent (R1.4).
  • The logo will be smaller and moved to another location (R1.1).
  • Notifications are not being handled in the next iteration, because this isn’t a basic functionality. Later on, we will elaborate this more (R1.5).