Word on the street is that the benefit of User Centred Design is hard to prove… I’m a fan of UCD as a process and I think that it is difficult to measure where process has been central to outcome, but today that’s a tangent. Part of the argument that is made is that a good designer can do almost as much by applying their design experience and expertise as what can be achieved through a UCD approach. In many cases, I heartily agree. Sometimes the process is more about the client than it is about the end users.
A project I’ve been working on recently is a case in point. This project is a pretty big deal – a lot of time and effort and, of course, money, have been ploughed into it already and there is plenty more to follow. Stakeholders have already been working on this project for ages when I get the call to come in and do my thing.
From a quick look at the proposed designs it is clear that there are some fairly significant issues that need to be resolved – both at the proposition level and at a more tactical, executional level. I don’t need research to tell me that and, because of my experience, I have a pretty good idea of what we need to do to fix this.
There is no WAY that I am going to be able to persuade all of the stakeholders who have invested so much in their current approach that they need to make the changes I’m suggesting… after all – I’m just one voice. One subjective, lonely voice… with my opinion alone, I have a long, lonely and difficult path ahead to try to get my clients to make the right decisions. Chances are, I’ll not be successful.
Cue user research. By conducting a quick round of user research I develop astounding powers of persuasion, because it is no longer my subjective, individual opinion that I am asking people to trust. Through the access I have to data accumulated in the course of research, I am able to validate my opinion with something much more substantial – the voices of the end users, the stories of my interactions with those end users, anecdotes, examples, tangible stuff.
Is this just a waste of project resource? Should I spend more time on trying to be more persuasive and less time on research? I think not.
In my experience, by talking to and observing your end users, by looking for patterns and themes, there is always something interesting to learn – almost always something that is directly applicable to your project, and if not, then certainly something that will help you develop in your ability to understand and design good user experience. If you’re interested in social interactions online, then staying in touch with how people are talking about, thinking about, using different tools is something that you should regularly be doing. Take this opportunity to throw in a few questions related to ongoing areas of interest.
At the end of the day – our job is to try to make sure that good decisions are made about the user experience of projects we are working on. If it were up to us alone, perhaps we wouldn’t need research. For as long as persuasion (of our clients, stakeholders etc) is a critical part of our role, research is an incredibly useful tool.
It’s been more than a year now since I first wrote about Ambient Intimacy, and in that year it seems a whole lot has gone on. Twitter continues to be the predominant micro-blogging(?) platform although Google now owns Jaiku. Presence continues to be compelling, yet there hasn’t been the growth in ‘life streaming’ that perhaps we were expecting to occur. Everyone loved FaceBook, and now many of us love to hate it. And we’re all still talking about Portable Social Networks and better tools for managing our social networks across platforms, but we’re not really seeing very much of this in action yet.
On a personal level, I’m sure that many of us have had some pretty significant personal changes in the past year. For myself, the two highlights have been moving from working with a consultancy to going freelance, and starting a family.
All of these changes in the past year have gotten me to thinking about something that I’m going to call Ambient Exposure. Exposure in terms of disclosing information of course, but also exposure in the way that a trader might think of it – a vulnerability, a risk associated with taking a position that could, potentially, result in loss or harm.
There are two key attributes of social tools social tools such as Twitter, Jaiku, Facebook and others that means that Ambient Intimacy leads to Ambient Exposure being the content you are sharing and the contacts with whom you are sharing it.
Ambient Intimacy occurs as you share your presence information and other personal information with people in your contact list – that is simple enough, and on the surface the exposure is obvious. However, for very many of us, we have taken little care in managing and really understanding exactly *who* is on our contact list. As your friends or followers list becomes progressively larger, we are less able to remember exactly who is listening – employers? colleagues? people we want to impress professionally? clients we’re currently working for? people we’d like to work for later? (just to focus on the professional aspect – there are a million potential personal minefields).
Essentially, we may not *want* to have the same level of intimacy with some people as we do with others … but do our social tools support this in helping us either be more thoughtful about who we add to our networks and who we don’t (and allowing ‘not adding’ in a way that is polite), or in allowing us to maintain awareness of who we are talking to (what kinds of people) and to isolate groups of people for various types of communication.
My Twitter account, for example, is completely public and there are lots of people ‘listening’ to what I twitter who I don’t know. There are so many of them that I can’t remember who is there or not. As this list has gotten longer I find myself Twittering more cautiously and self consciously. I don’t want to be twittering about procrastinating on a project when the client for whom I am working is ‘listening’. My FaceBook friends list, on the other hand, is more private and has a much smaller collection of people who I actually know. I feel much more comfortable sharing personal information in this space now – so even as the rest of the world seems to be moving away from FaceBook, I actually enjoy it more than ever because my exposure is reduced and my ability to be authentic is increased. (Which raises a whole other question about what is authenticity in this space, and how much authenticity is required for proper ‘intimacy’ to be sustained. A whole other blog post, that is…).
In the same way that we are not necessarily good at or able to forecast the impact of choosing to add someone to our contact list, we are similarly perhaps not good at anticipating the impact of sharing particular types of information with others.
For some reason, I felt incredibly reticent about sharing in a social space anything about what felt like the incredibly personal experience of being pregnant and having a baby. I’m quite open about it in my relatively protected FaceBook environment, but in my highly exposed and less personal Twitter and blogging spaces I’ve been a lot more restrained.
Similarly I was intrigued to observe the almost brutal honesty of Tara Hunt‘s Twitter messages in the aftermath of her relationship breakup. As someone who is highly proficient in the social space, one could only assume that Tara had given some thought to the potential consequences of such honest tweeting. I believe that at some point around this time Tara did actually change her Twitter account from public to private, possibly as a reaction to others’ response to this openness. Nonetheless, Tara knowingly continues to take what I think is a very brave stance, only hours ago tweeting, on a totally unrelated topic – ‘Better yet, if I stumble, I do it openly and spectacularly on Twitter and YOU learn too! :)’
Tara and I and probably you take these risks or precautions in the social space because we are literate in this space. There has been a lot written about young people and the risks of openness, but the rest of us need education and potentially protection from this exposure. The benefits of ambient intimacy far outweigh the potential risks of exposure in my opinion, but awareness of this exposure is important. Education is probably the best way to help people manage exposure via content, but one of the key challenges for designers in social spaces is to design tools that support awareness and management of this exposure through unruly contact lists.
Academic researchers are … exploring the parallels between online social networks and tribal societies. In the collective patter of profile-surfing, messaging and “friending,” they see the resurgence of ancient patterns of oral communication.
I’ve been doing a lot of my shopping online recently and it has gotten me thinking about the opportunities for designing ecommerce systems that we often don’t bother spending time on. We just plug in ‘off the shelf’ solutions and this means that all too often we’re not thinking about ways that we can design the shopping experience so that it better supports the way that people actually want to shop online.
It seems from many online shopping experiences that there is an assumption that the online shopping experience has just a few simple steps:
locate the product you want to purchase
select that product (put it in the basket)
pay for the product and arrange delivery
Although, for some people some of the time, the process is this simple, very often there are much more complex pathways that people take when shopping – both online and offline. Unfortunately, very often the design of online systems doesn’t support this additional complexity. Very often just a few small changes would make a great difference.
Here are just a few examples I’ve come across lately.
Scenario: I’m in the market, but I’m not quite ready to buy.
Design requirement: Save shopping basket
There are many reasons why people don’t quite complete a transaction, but one that I find is really very common is this one… I’m just not quite ready to buy yet. It could be that it’s a large transaction and I need to be completely certain that I want to buy it, it could be that I’m comparing your product or price or service with your competitors, but quite often I’ll do the first and second stages of the shopping process – locating products and putting them in the trolley – but not be quite ready to give you my payment details.
It is amazing how many e-commerce systems ‘forget’ all the shopping I’ve done – some apparently deliberately, with time out error messages to boot. This means that, when I come back with my credit card out and ready to shop, I have to start all over again – finding the products and putting them back into the basket. Depending on the size of your product range and the state of your information architecture, this can sometimes be a particularly daunting task – daunting enough to perhaps result in abandonment.
Where is the value to anyone in ‘forgetting’ what’s in my basket? Who benefits from this? Certainly not your customer who has to go to extra effort when they return to make their purchase, and not the business either, who will almost certainly be losing revenue as a result of this design decision.
Amazon (predictably) are a great example of how not to forget what’s gone in the basket – their ‘buy later’ functionality means that I can even choose to not buy something that is in the basket and *still* not have it deleted or forgotten. Amazon is an excellent example of how to manage this ‘remembering’ – but many small ecommerce sites have similar functionality – you don’t have to be Amazon to be able to do this.
It will take a little more technical effort and design work to manage this ‘saving’ of the basket but it should definitely be the default for all e-commerce systems.
Scenario: I’m in the market, but I’m not quite motivated to buy.
Design requirement: Follow up and provide incentive
I also call this one ‘The Almost Impulse Buy’ – again, the customer goes almost all the way through the purchasing process but pulls out just as it comes time to commit with their wallet. There are a lot of reasons why people don’t quite go through with the purchase, but three surprisingly common ones are:
they simply forget! – surprisingly, buying your products is not the only and most important thing that your customer is dealing with. Other more important stuff comes up, they get distracted – and they quite simply forget that they were ever just about to hand over some of their hard earned cash to you. They move on and don’t make it back.
they need just a little more reason to buy – it could be that they don’t really *need* your product, or that they don’t really need to buy it from you, or that they feel as though they should do a little more research or wait a little time before buying – there is not quite enough motivation for them to complete the purchase at that time.
something you’re doing sucks – it could be that something is broken, a question is not answered, or something about your product or service just doesn’t quite match your customers needs… this is unresolved and, as a result, so is this transaction.
Each of these ‘problems’ has a very similar solution – get in touch! Drop me an email, tell me you’ve noticed that I didn’t quite complete my purchase, ask me if something was wrong, give me an alternative method to purchase (a return email, a phone number) or a way to tell you what was wrong, give me an incentive to complete the purchase now.
Recently I almost purchased a hamper online at Fortnum & Mason – about 24hours after I *didn’t* complete the transaction I received an email from them letting me know that they’d noticed, asking me if there was a problem and telling me that if I *did* complete the purchase they’d put me in a draw to win an enormous hamper for free. Nice work.
Other smaller sites have sent me emails that seem to me to be human generated – one even had a little note telling me that something I had almost purchased was now available as a special deal. Perhaps they’re hand done, perhaps they’re automated, the end result is a little warm fuzzy for the customer – you noticed that they didn’t go through with the purchase and you care enough to find out why and to try to win their business. For the small amount of effort that this would require, it wouldn’t take very many conversions to make this time and money well spent.
Scenario: I’m just researching but information I need is buried in your purchasing process
Design requirement: Make desired information more easily accessible to your customers outside of the purchasing process.
Sometimes abandonment isn’t actually abandonment… sometimes it’s just research that can’t be done any other way. Understanding delivery charges and timeframes is an example you’ve probably come across before – you can’t find out about what delivery options are available without going through the process of purchasing, even though you’re not at all committed to that purchase. I once had a client who had a geographically restricted service, but the only way you could find out if that service was available to you was to commence the purchase transaction where step three was ‘put in your postcode to find out if we can provide service in your location’. These things sound pretty dumb and obvious, but you run into them all the time. Meanwhile, back at corporate HQ, people are wondering why shopping baskets are being abandoned at step three…
As well as making it easier for your customers, providing this information outside of the transactional process also helps you get more accurate numbers on the effectiveness of your design – those customers who are just going through the motions to get the information shouldn’t be counted as abandonments at all – in many cases, this results in undue resources being spent on redesigning step three, when, in fact, the real problems that cause committed customers to drop out are somewhere else entirely.
So – just a few of my favourite ways that you could potentially make some small changes and reap almost immediate benefits for your e-commerce business. I’d be interested to hear of any other basket/checkout related bugbears you have and how they should be addressed by user experience designers.