Note: We created two separate designs for user testing, one which took a more user-friendly approach and another which focused exclusively on efficiency. After the first round of testing (which consisted of three music directors and an "elf" from the radio station) we dropped the design which focused on efficiency and merged the best design concepts from both into a single design. Because we ran each user in the first round on both designs (we counterbalanced so that an equal number of users started with either design) there was a significant learning and preference bias (the tasks remained the same across the two designs, therefore users were more comfortable by the time they tried the second design). This may have been an influence on the users' unanimous preference for the second design they were presented with. Nonetheless, we found it a useful exercise to use multiple designs in our first round of testing, since many details from both made it into the final design.

Prototype Photos


v1.0 of user-friendly implementation

The user has drag/dropped two files from the desktop onto the interface and the files have begun uploading to the system.


v1.0 of user-friendly implementation

The user has clicked on one of the uploading albums and sees the detailed album view with cover-art. Each field on this page is editable (the field highlights on a mouse hover and turns into a text-box on click).


v1.0 of high-efficiency implementation

The main screen that shows up on loading. The "+" button at the bottom manually brings up the list of uploading albums and previously uploaded.


v1.0 of high-efficiency implementation

An album (starmarker.zip) has completed uploading and is ready to be approved (and filed) into the playback system.


v1.0 of reporting interface (both aforementioned v1.0 implementations use the same reporting interface)

Currently with no filtering selected, all albums are being shown.


One of the user testing sessions at the WMBR studio.


Some of the interface widgets and task cards used.


v2.0 of our merged implementation

Notice the pause button by each upload progress bar, the clear approve/delete buttons for the album (and the removal of the trash bin icon previously in the top right corner), and the re-wording on the upper left tabs for clarity. Changes not seen include a screen hover on dragging files over the interface (an entire gray-out screen blankets the screen and says "upload"), a highlight on hovering over any editable fields (including the tracks, which then allow editing of artists on individual tracks), and other minor changes. Other forthcoming changes include being able to delete single tracks (also using a hover over track affordance) and a clear visual cue that uploading albums can be clicked on to see specific album information.


A view of the testing session on Monday March 18th.


v2.0 of reporting interface

Notice the Piazza-like tagging for genre filtering (allowing flexible genre additions as well as multi-selection filtering), release date range filter, and additional playback count columns (for easy sorting between commonly used date ranges). Note that there were several transparencies made for both versions of the reporting interface to reflect changes in filtering and when clicking on one of the playback count headers (which sorts by play count in descending order).

Back to the top

Briefing

What follows is the briefing presenting to participants in the paper prototype tests:

KaJaMi Participant Briefing

Thank you for taking the time to help us test the prototype of our system.

You will be acting as the “user”, our goal is not to test you, but to test our system and find flaws or inconsistencies that will improve the final implementation.

One person from our group will act as a “computer” who will control the experiment and provide tasks that we would like you to perform using the interface.

The other group members will act as “observers”, and will be taking notes on the experiment.

We will be asking you to perform tasks that relate to your current music director duties, but using our interface instead of what you are normally used to. At a high level these tasks will include importing digital music, previewing music and getting CMJ reporting data. We ask that you do not ask interface related questions during the test itself (as this will better help us find faults in our interface) but we can answer anything after the test is complete.

Thanks and have fun!

Back to the top

Scenario Tasks

Scenario

Task

Imagine you are a music director, Lana, and you wish to upload some albums to the digital library via the KaJaM! interface

Open KaJaM! and log into the system

You have downloaded 2 albums onto your computer: Starmarker.zip and KaJaM.zip and wish to import them to the library

Import Starmarker.zip and KaJaM.zip into the digital library

While KaJaM.zip is importing, you wish to preview one of the tracks

Preview (play) a track in the KaJaM album

The track from the KaJaM album sounds familiar, and you quickly realize you have already imported the album and don't need it again

Delete the currently importing KaJaM album

The Starmarker.zip file finishes importing, and you wish to make sure all the track details are correct

Inspect track details*

You find incorrect and incomplete track details you want to fix

Edit track details to reflect the correct information**

You wish to approve the album to officially file it in the digital library

Approve the album

Before you leave, you wish to complete College Media Journal reporting for the month

Take a look at the reporting data in the digital library

You notice the reporting data is displaying _the Blue Dot _genre, but you want to look at "Electronica/RPM"

Filter the reporting data to show only "Electronica/RPM"

Now all reporting data is on "Electronica/RPM" only, but it is not sorted by play count in the last month

Sort the reporting data by play count in the last month, in descending order

Everything looks good, but you still want to make adjustments to the reports based on physical CD play count before submitting them

Export the reporting data to Excel file format for further editing

Now that you are all done, you wish to go home

Done!

*The album contains tracks with pre-tagged information, but some are incorrect or incomplete:

Track #

Track Name

Artist

Album

Label

Release Date

Genre

1

While I'm Dead

Starmarker

Unknown

Polyvinyl

 

 

2

Sand Beauty

Starmarker

Unknown

Polyvinyl



3

Silvre Lining

Starmarker

Unknown

Polyvinyl



**The facilitator assumes Lana Googles the album information, so facilitator provides all the correct information to the user on a separate sheet of paper:

Track #

Track Name

Artist

Album

Label

Release Date

Genre

1

While I'm Dead

Starmarker

Killer Kilometer

Polyvinyl

20/02/2013

Electronica/RPM

2

Sand Beauty

Starmarker

Killer Kilometer

Polyvinyl

20/02/2013 

Electronica/RPM

3

Silver Lining

Starmarker

Killer Kilometer

Polyvinyl

20/02/2013 

Electronica/RPM

Back to the top

Observations

Importing tasks

Legend (relevant for prototype iteration 1 only, note that reporting interfaces were identical in both designs for this iteration):

(U) - This point specifically references the user-friendly design

(E) - This point specifically references the high-efficiency design

Prototype Iteration 1

User

Import Files into the Library

Preview Song Tracks

Delete Importing Album

Inspect and Edit Album/Track Details

Approve Album

Music Director #1

  • User found the drag and drop interface to be intuitive and easily learnable, but isn't familiar with the fact that file start importing as soon as the mouse button is released. Instead, user searched for an "OK" button to start importing officially. This is a tradeoff we made to achieve more efficiency, but sacrifices some safety because the user may inadvertently drop the wrong file on the interface.
  • User recognized the play button beside the track right away (learnability)
  • User's single click on the play button starts playing the track right away (efficiency)
  • If user clicked on play accidentally, a pause button appears in place of the play button to stop track (safety)
  • (U) had some trouble locating the trash can because it was placed far away from the user's line of vision (learnability)
  • (E) quickly found the "X" delete button beside the uploading album (safety)
  • Both interfaces lack affordances in terms of what is editable and what isn't, user had to experiment by single clicking on the fields (learnability)
  • User noted the directly editable fields are very convenient (efficiency)
  • User noted a mistake in adding the genre can be easily fixed by clicking the "x" beside the genre tag (safety)
  • User was confused about how to "approve" the album on both interfaces because he did not associate approval with the "checkmark" button (learnability)
  • Again, a tradeoff was made between efficiency and safety: single click on the "checkmark" button will approve the album immediately (efficiency)
  • User prefers a confirmation message (safety)

User

Import Files into the Library

Preview Song Tracks

Delete Importing Album

Inspect and Edit Album/Track Details

Approve Album

Music Director #2

  • User really likes being able to type in the URL instead of downloading then dropping the file (efficiency)
  • (U) Had a hard time finding how to open the album information, tried to click on "Recently Uploaded" tab (learnability)
  • For a long time, user had trouble finding the trash can (learnability)
  • Tried clicking on the trash can but surprised to find it deletes without asking her to confirm (safety)
  • User figured out how to edit fields rather fast, but not sure how to "save" the entry (tried clicking inside the textbox when she really just wanted to exit the textbox (safety)
  • Tried clicking on "checkmark" icon, which could cause further problems as that will approve the entire album and make the edit screen disappear altogether (safety)
  • User used the comments section before approving, found it to be a really good idea

User

Import Files into the Library

Preview Song Tracks

Delete Importing Album

Inspect and Edit Album/Track Details

Approve Album

Music Director #3

  • Did not understand the "drag and drop" instructions (learnability)
  • User had trouble uploading the files due to lack of clarity in instructions and also did not understand the “Today’s Upload” tab, tried clicking on other tabs (learnability)
  • User struggled with learnability insomuch that efficiency and safety were not concerns
  • User found the play button very quickly and had no other issues (learnability)
  • (E) User liked having all the information in one place (play button, album information etc.) for all albums
  • (U) User saw the trashcan and assumed that it works the same way as the Windows Recycle Bin (learnability)
  • User can drop multiple files into a trash can, is there a way to quickly delete multiple albums? (efficiency)
  • User likes a place where you can open the trash can to look at deleted albums (safety)
  • User looked for a save button to confirm edits to the field (safety)
  • User likes the add genre feature to allow for sub-genres and easy deletion of wrongly labeled genres (safety)
  • No issues with approval

User

Import Files into the Library

Preview Song Tracks

Delete Importing Album

Inspect and Edit Album/Track Details

Approve Album

"Elf"

  • Our interface did not make it explicit that users are to drop zip files directly (learnability)
  • User noted that he will want to drop multiple files at a time (efficiency)
  • User tried to unzip all files first then drag and drop the content directly onto the KaJaM interface (efficiency)
  • User also noted that there doesn't seem to be a way to cancel a file dropped accidentally (safety)
  • User was confused that the right side of the screen was completely blank, and instead clicked on "recently uploaded" tab to look for the tracks within currently uploading album (learnability)
  • Quickly found the play button to preview each track User tried to unzip all files first then drag and drop the content directly onto the KaJaM interface (efficiency)
  • User wants a feature that allows for stopping the import but not delete it 
  • Had trouble deleting all 3 separate tracks quickly, just deleting one at a time (efficiency)
  • Don't need confirmation message, especially if it acts like a recycle bin like on Windows (safety)
  • User suggested offering more affordances for single click because he is a "double-click" guy (learnability and efficiency)
  • What if there are different artists in each album (compilations are very frequent), want the ability to change the artist name for each track versus for the album (efficiency versus customizability)
  • Various artists for the entire album, but separate artist name for each song
  • No issues with learnability, efficiency or safety but want to see what he has approved during the current session (want to see what other people have uploaded recently)

Prototype Iteration 2

User

Import Files into the Library

Preview Song Tracks

Delete Importing Album

Inspect and Edit Album/Track Details

Approve Album

Student User #1


The drag and drop interface was intuitive and easy (learnability,efficiency).


Confused about how to pull up album details once the albums are uploading, lacks visual affordance for clicking on the uploading albums (learnability).


The now modified delete upload button was extremely obvious and easy to find (learnability).


Confused about where different fields go in the album information panel (e.g. she thought the "Unknown" was producer name and not album name, and she thought "Date Unknown" was today's date instead of album release date) and require more visual affordances for what each field denotes (learnability).

Consistently looking for a help button on the interface ("Is there help available for that?") (learnability).


Intuitive and easy for this user (learnability).

Student User #2


Readily dragged and dropped files to the interface (learnability,efficiency), but dragged the second file to the smaller space (once the right-pane came in). User remarked that it was not clear whether he was to drag and drop the zip files or the contents, or whether both zip files could be dragged together.


User may not have known how to get into track details to view the song tracks. User remarked about the lack of affordances on the upload rows. (learnability)


User had no issues deleting the file, but paused the upload before deleting the upload. User remarked that it wasn't obvious that the .zip file corresponded to an album. (learnability,safety) User inquired about whether it was possible to delete on a per-track level, although it wasn't a task. (efficiency)


User remarked that they didn’t know if one of the items was the band or album name (but knew that “Unknown” was the other name), but acknowledged the affordance of the highlight (learnability). The user also remarked about the intuitive nature of the date picker. (learnability)


CRITICAL INCIDENT: User was slightly confused about upload vs. approve and wasn’t sure if leaving would approve (learnability,safety), user also remarked that it may not be the case that users want the approved album to disappear. (efficiency)

Student User #3


No significant issues.


Double-clicked on the row and paused a moment to search for the play icons.


No significant issues.


No significant issues.


No significant issues.

Back to the top

Reporting Tasks

Prototype Iteration 1

User

Switch to Reporting Mode

Filter View by Genre

Sort View by Play Count

Export Reporting Data to Excel File

Music Director #1

  • User found switching modes via the tabbed interface to be easy and intuitive (learnability)
  • Single click on another tab switched the mode immediately (efficiency), and user noted he can easily switch back if he accidentally clicked on another tab (safety)
  • User struggled with understanding the "filter" button and what it means - he thought it brings up another "filter" window (learnability)
  • Dislikes how 2 user clicks are required every time a genre needs to be filtered (efficiency)
  • Requires user to confirm genre choice by explicitly clicking on "Filter", but user did not like this (safety)
  • User did not know how to sort the rows (no affordances offered to suggest that clicking on the header row sorts it) (learnability)
  • User noted that having an arrow displayed beside the header would really help to indicate the sort function (learnability)
  • Single click on the head column sorts the table in descending order, second click sorts the table in ascending order. User thought this was convenient (learnability)
  • User found the export button very quickly and no troubles with this task (learnability)
  • User liked that the file started downloading right away without prompting him to confirm (efficiency versus safety)

Music Director #2

  • No issues with switching to reporting mode
  • Interface is a bit too busy and overwhelming (learnability and safety, but may help efficiency)
  • User noted that the reporting data does not filter by date range (e.g. everything in the last 6 months)
  • User finished sorting rather quickly as she knows to click on the header row from knowledge in the head
  • No issues with exporting to excel file

Music Director #3

  • No issues finding the reporting mode
  • Struggled in understanding what date range the reporting data covered (learnability and safety)
  • User had trouble sorting by play count, did not realize that the header row can allow sorting (learnability)
  • Eventually tried to export to Excel for further manipulation
  • No issues with exporting

"Elf"

  • No problem finding the "Reporting" tab
  • Made a comment implying the filter button was redundant ("You have to click filter now?") (efficiency)
  • No issues with filtering but user wants to report multiple genres (e.g. not jazz or world, but only want electronica and rock)
  • No issues with sort because the user is knowledgeable with Excel
  • However, user does not see what the play counts are for? Is this one week or two weeks? (learnability)
    • Want to filter play count in each column by date
  • No issues with export, user thought the button was very clear

Prototype Iteration 2

User

Switch to Reporting Mode

Filter View by Genre

Sort View by Play Count

Export Reporting Data to Excel File

Student User #1


Easily found the reporting tab (learnability).


Removing the piazza-like tag for blue dot was immediately intuitive (learnability, efficiency), at which point adding the electronica genre was also easy.


Immediately decided to click on the correct column header, as she noticed the arrow cue and affordance in the column header (learnability).


The button for exporting to excel was obvious (learnability).

Student User #2


No significant issues.


Readily identified the "x" button to switch the genres. User remarked on the salience of the genre selectors. (learnability)


No significant issues.


No significant issues.

Student User #3


No significant issues.


No significant issues.


No significant issues.


No significant issues.

Back to the top

Prototype Iterations

Design

First Iteration

Second Iteration

Importing

The efficient design featured a text box and button, while the "friendly" design featured neither.

A text box added to the "friendly" design to provide affordances for pasting or typing URLs

Managing Imports

The efficient design had a more visible "stop" button, next to the progress bar, while the "friendly" design placed its "delete" button far from the user's focus

The "friendly" design added a 'pause upload' button near the progress bar and changed the "No (do not approve)" button to a visible, red "Delete Upload" button

Organization

The efficient design used a button to switch between upload and reporting modes and featured recent uploads on the same "upload" page, while the "friendly" design separated current from recent uploads, and used tabs for navigation

The "friendly" design reworded its tabs to be more clear as to their purpose

Navigation

The efficient design assumed that scroll-bars would be used normally to scroll through recent uploads, while the "friendly" design used a button to scroll through the details while keeping the approve buttons static.

A scroll-bar replaced the "scroll-button" for scrolling through details in the "friendly" design.

Reporting

The interface featured a single-genre drop-down box which required clicking on a "filter" button to filter. The release dates included and date ranges of playback counting were unclear.

Genre was converted to a Piazza-like tagging design much like that of the "friendly" design and removed the requirement to click on a "filter" button; release date ranges were made explicit and columns were added to clarify over which date ranges counts were collected

Miscellaneous Features

N/A

Added a hover-based mechanism to view per-track artists for compilation albums; tooltips were added to clarify what each text field represented in the editor pane

Back to the top

  • No labels

1 Comment

  1. Prototype: You definitely put a good amount of time/thought into prototype creation--well done!
    User testing observations: I like that you clearly tested on people in your intended user class.
    Overall: Great job!