Wednesday, 21 January 2009

Block 3, Blog 1 - Applying Quantative Usability Methods

The Cashless System at the Ricoh Arena


Above: Cashless card on tray. This is where the card is placed during a transaction.
Below: Video, what happens during a transaction, how long it takes and the current feedback.



Attribute: Feedback

Measuring Concept: Receive requested feedback

Measuring Method: Time taken for feedback to appear and user to read and understand feedback

Now Level: System changes colour when it is safe to remove card from tray, no other feedback such as balance is given.

Worst Case: Balance appears after transaction, but takes too long to appear and too long to read.

Planned Level: Balance appears after transaction, is easily visible and doesn't take long to appear.

Best Case: Balance appears while using card, not just after a transaction. Display shows price before use, price of product purchased, and the remaining balance. The display would update quickly, and be easy to read, and clear after card is removed.


Metrics(Measuring Method)

  • Time taken for feedback to appear
  • Time taken for user to read feedback
  • Time taken for user to understand feedback
  • Time the whole transaction takes
  • Number of problems occurred*
  • Time for problems to be resolved
  • Number of unresolved problems
  • Number of user complaints
  • Average queue time**

*Some problems could include things such as the card not being accepted, the balance not displaying, taking too long to display or not displaying at the right time, and cards not displaying the correct balance.

**This isn't completely relevant to the feedback attrivute, but since the queue time ties in with the main aim of the system it would be helpful to note whether the added feedback is cutting down or adding to queues.

No comments: