Jam Universal

A global outcry for worldwide usability and whatever makes you stand-up and say WTF!

Archive for July, 2006

PDA Heaven – Hell on Earth

Posted by Peter Cavallo on July 30, 2006

 TEST DATA! Give me test data! I’m heard screaming in my cubicle.

Ok, what we have here is our first mobile application to review. Which is an application that keeps track of stock items and transfers of stock and Bin locations (Bins are containers that hold stock).

This is a connected application, which means it needs to work in close proximity to the local network. I am told the application is used by warehouse workers who are computer iliterate! Ok, so this has to be very intuitive, almost to the piont where it thinks for you.

So, I connect the application to the local network here and away we go.

Hang on. I’m using a PDA bought from Harvey Norman will they be using the same type??! Guess what! “NOPE!” says the product manager. “They will be using a device with a mini keyboard and barcode reader”. “oh”, I say feeling the next question bubbling up inside. “Do….we……have……one?” “Um no” he says looking down to the ground in shame. “But we are discussing with a company about supplying one……soon”.

OK, let’s go onto something else while I wait for this new device to come through.

Ahh. I’ll contact the Customer and talk to some of the users of the first version of this application. (The one they didn’t tell me about until it was finished and sent to the customer! argh!) Right I need to contact the guy who talks to the customer. Write and email, yes good plan, explain the whole thing in detail and then I can get moving with putting some user profiles together.

…..waiting

Posted in Usability | Leave a Comment »

First day of many – PDA heaven

Posted by Peter Cavallo on July 11, 2006

Well, I’ve got the PDA and after only a few attempts got a working version of the application too. I love gadgets so doing a usability study on the User Interface of a PDA was going to be fun, fun, fun. OK, (rubbing his hands together) let’s get going.

The first thing I do is create a document outlining what I’m going to be doing and hand it to the project manager.

  1. Purpose: This document outlines the process of conducting a usability test and UI review of [mobile application name] and the requirements for this process to be completed.
  2. Outline: To check [mobile application name] & [mobile application name] for usability issues with a view to obtaining information to create a Style Guide for mobile application and user profiles for future development.

Process Inputs

Installation
Install working versions onto a PDA. These versions need to be fully functional and have test data available.

Application Instruction
Time spent with a developer who knows the process flow of tasks that can be performed on each application. reading the Mobile documentation URS.

User Profiles
Create a user profile

  1. Information on who will use this device and the environment they work in. This information can be gained from current customers or targeted customers.
  2. Physical environment use of the device – whether sitting or standing or walking.
  3. User Experience – (of PDA device)
    1. Novice User
    2. Expert User
  4. Job Types – What will be the most frequent use of the application?

Task Analysis
Write tasks for both Novice and Expert Users to be performed using both applications. A developer will be needed on a periodic basis to help design the tasks.

Usability Test
Usability testing involves the systematic observation of representative users as they perform realistic tasks ultilizing the system. This methodology can reveal the extent to which an application meets the users needs, and the extent to which it can be readily learned and/or used.

Typical measures that are utilized include the incidence of various usability problems (derived from observation of performance or user comments), the time required to accomplish specific tasks or subtasks, the nature and incidence of various user errors or failures to accomplish tasks, and subjective ratings of user satisfaction along various design dimensions.

  • Observation test
  • User Questionnaire
  • Customer feedback from current application (if avialable)

Outputs

Report
Once all test data has been collected and collated a report will be created outlining key usability issues and recommendations from the user observation tests.

Presentation

An overview presentation can be provide outlining the key issues and allow discussion on recommendations for the application.

Work Orders

The key usability issues should be processed into work orders for the development team. All this must be completed before the application is released and or shown to customers.

Mobile Style Guide

This document will outline the style and standards for all Mobile products.

Posted in Usability | Leave a Comment »