christophermears

Using KANO techniques and user interviews I was responsible for gathering requirements for the new Ford content management system. This involved creating personas, and deriving scenarios from those personas in order to begin creating the user journeys.

These user journeys were then used as a basis for a card sorting excercise in which the information architecture for the system could be loosely defined.

Following the persona creation and scenario building processes I constructed a site map to demonstrate the information/navigation heirachy for the Salomon brand center in which they organise their various brand materials.

Organising the contents in this fashion presented a clear indiction of a potential information architecture for the system.

For the new Vodafone image library it was important to identify areas in which user flow through the system could be improved upon.

One way in which this could be accomplished was through the use of a user flow diagram to visualise how a user would find an image in the library.

The conclusions from this indicate that the following improvements could be made to improve the flow:

• Relevant, related images are shown on the image page itself.
• More image information was displayed on the search results to give the user a better idea what they were looking at.
• It is possible to search from any page.

The Vodafone "Creative Review" project was a mechanism Vodafone could use to get feedback from their various global markets on the creative that was being produced in that month.

Figure 1 represents a high-level conceptual model of what a review entails to an end user, whilst figure 2 is a slightly more detailed look at the interactions both the user and the client (Vodafone) will have with the system at each stage in the review process.

As part of the new automatic templating system built for Network Rail, there was a requirement to create posters for the nearest toilet. This created a challenging UI problem.

The functions of the control needed to be:

• Ability to create either one or two directions along with the type of toilet
• Ability to specify how far the/each toilet was
• Ability to specify which direction the toilet is in
• Ability to specify the type of toilet

In the initial design, the user was able to chose the direction of the arrow by simply clicking on it multiple times. However I decided a preferable and more intuitive way to do this would be to have a rotate clockwise, and rotate anti clockwise button for each arrow. This way the maximum number of clicks they would have to do to reach their desired arrow would be reduced by half as they weren't being forced to rotate in one direction.

Due to the reasonably limited number of different toilet types (men/women/disabled/baby change) a simple next/previous pattern was used.