This week we came across this tweet:

There is some lively debate about the actual existence of the pagefold on websites (see http://www.thereisnopagefold.com/).  The main arguments as far as I can tell, is that the pagefold does not apply to the web because, unlike the physical world where a newspaper fold applies to all readers, online users can view pages in a variety of screen resolutions which alter the placement of the fold and there is a scroll bar on most websites to find more content.

My take is a little more pragmatic;

When we observe users in labs, time and time again we see some people not using the scroll bar.  While good designs help to avoid this, it does happen.  As such we recommend to our clients that they present key information (not all content) above the page fold in common screen resolution formats (eg. 1024 by 768).

Whilst I agree that we should think about websites outside of the newspaper paradigm I do believe that talking about the fold encourages website owners to think about the placement of key information on the page to make it easier for users to undertake key activities.

What do you think?

There are some serious coffee drinkers in the UsabilityOne office, and a number of us are fairly fussy about our coffees too. So when our new coffee machine arrived we were keen to fiddle with the settings and configure it just the way we like it.

Several weeks later, we still haven’t worked out how to do that. We do know how to change the language on the menu though.

When designing an interface, design for the most likely and frequent activities your users will undertake.

Mapping applications are a great way to present your contact information, particularly when your company has multiple stores or locations. However, if executed poorly they can actually add to the difficulty of you customers finding your stores. The following are some important design considerations when presenting information with a map.

Take care when starting on a map at the country level as the only way to find locations. Maps like the one below typically rely on visitors zooming and panning controls of that particular mapping application, something not all users are familiar with. Forcing visitors to use the map to drill-down from a country to suburb level can also be time consuming and error prone. When testing the example below, participants who were experienced with using online maps took an average of 19 mouse movements to locate the South Melbourne store.

Users like to be given options so they can choose a means of interaction that suits them best. Some users prefer drilling down using a map, others do not. Displaying alternatives to the map, such as a postcode search or state selection, allows users to choose the option that best meets their needs.

Below is a good example where users are given flexible choices in locating their nearest store. They can enter their postcode for an exact match, drill-down by state or interact with the map. The state selector still gives users an overview of locations, but eliminates extensive zooming on the map from the country level.

As with all features of your site; design your mapping feature so that the user can use it as they wish. Offering multiple ways to interact with the feature means users will be able to find one that best suits them.

The process was slower than I had expected it to be, but the real crunch came at the point of making a payment; my credit card signature needed to be assessed by the self-serve assistant.  It was apparent after a moment or two of scratching my head and looking about like a idiot, that it was I (rather than the system) that was required to notify an assistant that they were required to complete this transaction.  As the assistant was busy attending other customers I had to wait, for what seemed a long time, for my turn.  This seemed completely counter-productive.

I have used my credit card in a number of other comparative self-serve systems recently including car park and public transport ticketing machines.  In these instances signature validation was not required.  Of course, Woollies level of security with signature assessment is a notch above these systems, however, this experience for a first time user will undoubtably put many off from self-serving again.

When you consider how vital credit cards are for self-serve transitional purchasing, surely some revision is required to aid consumer adoption of the service?  I would encourage Woollies to consider one of the following: