Thursday 10th September, 2015
2:15pm to 3:00pm
We were going to change a fundamentally important part of our products, a form where people can buy and sell financial derivatives. It is the most important piece of functionality that we have, and a change for the worse could be problematic for clients and the company.
It was going to take at least one month to schedule one to one interviews and usability testing of any proposed interface.
We couldn’t use server logs for time on task because of the way that the interface was used.
What we needed was something that could give us some indication of how any proposed changes might impact usage; something which could help us decide between initial competing solutions.
So I reached into the past and went back to GOMS (Goals, Operators, Methods and Selectors - sometimes known as Keystroke Level Modelling). As well as providing a way to measure the impact of our changes, it gave us another tool for analysing how a person uses our interfaces, and a way to generate more ideas.
Sign in to add slides, notes or videos to this session