Data entry and usability

For the past few days I’ve been doing temp work as a customer relations assistant dealing with letters from annoyed train company customers (Some of them are whiny but others I can well understand why they are pissed off).

The software I used is a CRM system (Remedy Action Request System 4.0) and basically my past 3 days has been spent bashing my head against the desk because of the usability issues that made my work more difficult than it needed to be.

The group I was in only started on Tuesday and so we were given the easy task (for ‘easy’ read boring and repetative and that any trained monkey could do). We were dealing with all complaints from a specific incident where the signals completely screwed up and lots of trains were cancelled and the ones that weren’t went to their destinations slower than a stoned sloth on sedatives.

This was basically what I had to do:

  1. In the CRM open the topmost scanned document in the list and check that it is for a specific date
  2. Use Search Customer form to check database for record matching customer. If found use this customer, else make a new one in the New Customer form (using an external address lookup program to autocomplete the address fields if necessary).
  3. Add a note for the customer file about sending compensation and standard letter.
  4. Link the case to the specific signal failure incident (search in the incident screen)
  5. Go to the Create Letter page and send a standard letter. Click the create button to open up a Microsoft Word document with the customer details pre-filled and the standard header and footer. Copy and paste the standard appolagetic reply for the incident from another open Word document, filling out some places with details from the scanned document. Save and print document.
  6. Open the Compensation page and add vouchers for click print vouchers.
  7. Close the case

Usability problems encountered so far with the system (not limited to the CRM software)

N.B. This list is nowhere near complete, I was only using a small amount of the systems full functionality. I’m sure there are more things that suck about it.

I really suspect that the people who setup this system or wrote this software have never done data-entry in their lives and never actually had to use it beyond checking that it didn’t break.

Note to people designing this type of software, it is not meant to be clickable and friendly for newbies. It is meant to be used in a high-volume kind of way that means optimise for speed. Newbies may be puzzled at the lack of a search button to click but after they’ve been using it a few hours they will thank you for being able to hit the enter key rather than having to take their hands away from the keyboard in order to use the mouse.

Now my assignment with this company has finished because I was ‘surplus to requirements’ due to the backlog having been cleared or so the agency told me, so I go in to get my timesheet signed and I find that the rest of my group (i.e. people also hired to clear their backlog) are still there and being trained on new stuff. It might have been because my stats showed that I got through the least cases but that was probably because when I found a case that wasn’t part of the backlog I filled in the customer details anyway to save one of the more experienced people wasting their time on such a trivial task.


Comments