Graphical Interfaces: Software Evaluation Through User Tests
This is the second exercise (that I am posting) of the Graphical Interfaces course (2010):
Task in short: To analyze a GUI, taking things like users, goals and visual framework into account.
Aim: To practice analysis skills.
The task was to analyze the GUI of a software for brainstorming, called Effective Mind, by Realize. Tools for making this were user tests, key path scenarios, validation scenarios and an analysis of the data elements.
The result of myself and my course mate can be found here (.pdf).
The task information is listed below:
1 a) User test. One of us performed the first test scenario, and the other observed. Then the roles are changed and the second test carried out. The test person’s task was to "think aloud", constantly describing whatever goes though her or his mind. The observer tried to record the interesting comments and where the process goes smoothly and where it halts.
My task was to find an alternative use of a snow shovel and my colleague Malin's was to find out how to market the Interaction Design Master's program.
1 b) Key paths and validation through use cases/validation scenarios and walkthrough.
1 c) List data elements and their most prominent properties.
2 General ideas of improvement. Suggestions of any features or functions that, given the user group and the set requirements, were missing.
Reflection: I remember this to be a somewhat overwhelming task due to the seemingly endless shortcomings of the software. We were surprised to find out that a program that poorly designed actually was used and paid for by companies. If this reveals more about them or us is left to be discovered but fact is that I for one felt that I could easily design something a lot more user friendly.
