Neo Insight's e-newsletter on Usability topics and techniques.
We invite you to subscribe to our monthly e-newsletter.
We apply our model of customer experience to describe and to predict many things. Working top-down, it explains how a management vision connects to - and drives - technical development. Working bottom-up, it explains why functionality and characteristics need to be in place.
In a recent usability review of a geomatics web interface, we were reminded of the intimate connection between the layers of our model, and the impact of low-level design details on the ultimate success or failure of an application. Let's look at what we found, and illustrate how just a few of the details of the organization and interaction conspired to feed up the layers and damage the overall experience and the long-term relationship with customers.
In our experience, every website has the goal of developing a long-term customer relationship. This might take the form of, for example, repeat sales; or perhaps annual upgrades to software; or repeat visits which allow the site to sell more advertising; or simply where the primary value to the user only comes from long-term use. For a government geomatics application, a long-term relationship is necessary to meet a performance-oriented goal such as "improved land-use decision-making". That's the kind of practical, measurable outcome we like to get our teeth into, as it has direct implications for usability and the customer experience.
Geomatics applications can be highly interactive and tightly integrated. They often need to support well-defined user goals and tasks. In the mapping interface we tested, users have to learn a few key concepts. They have to learn what layers are, what they contain, how their contents are represented and how they can be grouped into contexts. Users also have to learn how to make layers visible on a map, and what it means for a layer to be visible and active, and how these two concepts relate.
Just one usability test was enough to show how usability issues at the detailed design level feed up through the layers to impact conceptual understanding and the decisions made with the mapping data - the business goal of the application.
During the course of that particular test, the user did what everyone does - he built a partial mental model of what was going on. People don't develop full models; they only need enough to 1) explain their experiences so far (what they remember of them anyway), and 2) help them predict what will happen if they carry out certain actions (the main purpose of the model).
Problems we saw included:
In this test, the user arrived at two erroneous conclusions before (and only with encouragement) he achieved his goal. In a real-life situation, most users would believe they had already achieved their goal - albeit with some difficulty - and would have drawn the wrong conclusions: they would have made worse land-use decisions.
Three morals of this story
Our experience with hundreds of usability tests and heuristic evaluations like this one allows us to extract the insights, to separate the systemic architectural issues from the individual details of interaction, and to design solutions that support your customers' experience and develop your long-term relationship with customers and users. Call us to evaluate or design your Customer Experience - 613 271-3001.
For our Thursday March 8th workshop Designing usable web-based applications, sign up before February 23rd for the early registration discount of $100. Web applications are becoming as powerful as the ones on our desktop. Join this workshop to explore the challenges of designing web applications, and come away with tips, techniques and current best practices for providing high-value services that enable your users to fulfill their goals effectively and efficiently.
We'll also run either workshop at your location for 5 or more people: call us: (613) 271-3001.
A new year is a time to reflect, to step back and look at the big picture. A couple of statistics in The Economist that caught our eye recently illustrate how mobility is transforming the world:
Compare with Canada:
The markets close to home are less about adding capability and raw subscribers, they're more about adding service value. Much of the growth in North American mobile revenues is coming from email, web access, and other value-added services. Margaret Reardon at CNET reports that:
Just a reminder of the big things going on around us! 2007 could be the year the world goes mobile. And this scale of mobility will have a big impact on design. Going mobile brings a host of new customer experiences, device-specific design constraints, and new business models. Call on us (on our mobile devices!) to help put your mobile customer experience differentiators in place now! Happy 2007!
So, there we were, perusing the usability woes of the latest generation of Smartphones when Apple announces its long-awaited foray into the market - the iPhone. Steve Jobs' announcement of the iPhone at MacWorld 2007 focused on the multi-touch interaction ("it works like magic" - shouldn't there be a ™ there?), the "Software breakthrough", and aspects of the industrial design. But let's take a look at the challenges - and the opportunities - for Apple with regard to usability of the iPhone.
First, a little scene-setting. Computers are so cheap that they are being incorporated into every device we can imagine. This has some implications, especially for the user experience. Alan Cooper, in his excellent book "The inmates are running the asylum" puts forward some "riddles for the information age". These take the form "What do you get when you cross a computer with an airplane?", "What do you get when you cross a computer with a camera?", etc. The answer is always "a computer". Devices like alarm clocks and toasters that once were simple suddenly become too complex for many people to use properly.
The way we buy products - often feature-based - and the way product developers justify their existence by adding features, leads us all down the path of "creeping featurism". It takes a strong product manager or organization to prevent feature-creep, to produce a product or service with real value, charisma and simplicity. As a design-led company, Apple have shown that they can do this again and again, from the very first Graphical User Interface (well, the second - they took most of the ideas from Xerox Parc) to the iPod.
So what do you get when you cross a telephone with a computer? Some recent statistics from the UK reported in Mobile Marketing Magazine for December 27, 2006 don't paint a pretty picture of the new generation of smartphones:
Given that the cost of dealing with these problems is approximately US$70 per device, the "No Fault Found" cost to the UK industry must be around US$105M per annum, with perhaps a staggering US$4.5 Billion annual cost to the global industry! But what are the root causes behind these astonishing figures?
Usability is a key issue. A further UK study by WDSGlobal uncovered a number of reasons for these returns, relating to usability and the customer experience of Smartphones generally.
Doug Overton of WDSGLobal gives more details on the UK "no fault found" statistics in a 7m30sec video interview. We would summarize by saying: these problems were caused by complexity. To take our lead from Alan Cooper:
COMPUTER + TELEPHONE = COMPUTER
Users can't understand Smartphone capabilities before they buy them. Retail staff cannot keep up with understanding every new product that they have to sell. Smartphones are not ready-configured for the end user. And users cannot find the functions they need amongst the many functions they don't need. But users are becoming less willing to put up with this situation. Their experiences with trial products, free downloads and Beta versions on the Internet is leading them to expect things to work right out of the box - what we call "instant usability". Smartphones fail this test, and users are returning them in large numbers. As WDSGlobal conclude: "the manufacturers are not learning lessons."
So this is the challenge - and the opportunity - for Apple. Making a complex device simple again, delightful, "magic", even.
Unfortunately, Steve Jobs' speech didn't give us a warm feeling. It was about "3 devices in one"; it was about having the full Mac operating system on a small device; it was about the coolness of the physical design. The Multi-Touch interface would only seem to tackle the surface (literally and metaphorically) of the user interface complexity problem. We designed proximity detectors in Nortel telephones 8 years back. A full operating system makes a lot of OS management demands on the user. The applications that Steve talked about are inherently complex. Better icons won't help. Something more radical is needed.
But we know Apple has great designers (we know some of them). We hope they show the world how it can be done. We shall see.
We specialize in the Customer Experience. We like working with good people to augment and to complement our skills. Contact us if you feel you would like to work with us on Discovering, Designing and Delivering great Customer Experiences. We would offer one-off contracts, leading to longer-term contracts and maybe becoming a permanent part of our team. We are especially interested in people who can:
Advantages you might have would include bilingualism, graphic design, or implementation skills.
If you're interested in joining us, email us with your résumé.
The collection of new technologies and techniques referred to as "Web 2.0" is changing people's expectations and behaviour on the Web. Web 2.0 is impacting all areas of our interaction from the details of using AJAX widgets, to collective decision-making and organization, privacy and especially social networking.
This one-day, interactive workshop, organized by CapCHI, is geared towards a broad audience including government employees, product managers, business strategists, CTOs, CIOs, communication experts, technology experts and human-computer interaction specialists of any ilk, but especially those who are web designers.
In the first half of the day Peter Merholz and Maggie Fox address the topic of Web 2.0 as a social media. They will cover the business rational for Web 2.0 development and provide motivation for development in this area. Many cases studies will be reviewed.
In the second half of the day Neo Insight's Mike Atyeo will address more detailed issues of designing and testing Web 2.0 applications, particularly highly interactive AJAX applications. The important issue of accessibility will be addressed by Derek Featherstone, an expert in this particular field.
See details of the Web 2.0 workshop on the CapCHI website, plus further information, and links to podcast interviews with some of the speakers in the HotLab's January 2007 Hot Topics newsletter. Or go directly to Jeff Park's podcast interview with Mike Atyeo on AJAX and Usability :-)
"If ease of use was the only valid criterion, people would stick to tricycles and never try bicycles "
See more of Doug's history, pioneering, ideas and images at the Bootstrap Institute.
If you have any comments on The Insighter, or ideas on usability topics you'd like to hear about, send us an email with your comments.
We invite everyone to subscribe to the Insighter, our monthly e-newsletter.
If you wish to unsubscribe, just send us an unsubscribe email.