Showing posts with label design. Show all posts
Showing posts with label design. Show all posts

Tuesday, 29 March 2011

The Experience of Others

You're sitting in a restaurant having a great time, in fact it's a wonderful evening.  You have a good round table with a bunch of friends, the food is fantastic, the service is excellent, the wine is flowing.  The next day you get an email from the restaurant owner asking to rate your visit and you give it 5 stars.  It was fantastic.

Mrs Restaurant Owner is very happy because her customer was deeply satisfied with the experience.  She also runs a good business so she made some money that night.  Overall, it was a success for everyone involved.  Fantastic guest experience, good business, everyone is happy.  Wonderful. Beautiful. Perfect.

Ah. Experience.  That's a troublesome thing you see because it's actually quite difficult to establish what precisely was it about the experience that was good.  Was it the conversation?  Was it the company?  Both of these things?  Or the food? Or the seating configuration?  In fact, it's all of these and much more.  Experience is an emergent phenomenon.  It's emerges from a set of relationships, objects and timing in a specific moment for a specific individual to feel, well, something.

Product managers of a website have the same challenge as a restaurant owner.  They need to create an emergent set of experiences that support the business objectives.  Those emergent experiences could be for example, ease of use, joy, engagement, desire, advocacy (telling others), typing in credit card numbers, or creating a profile.


A Product Manager is an experience engineer.


Creating something which is emergent is not easy.  It's bloody difficult.  If everybody could do what Apple have done with their products in the last 10 years they would have done, but they didn't.  If something is difficult to do, it's difficult for others to copy.  And creating emergent systems that create wonderful experiences is extremely difficult. It's part art and part science.

In this world of emergence first you need to understand the systems from which your experience will come from.  The restaurant owner looks at all the details, from hiring of chefs, their kitchen organisation, the staffing rotas, the buying of ingredients, the menu design and hundreds of other small details and tries to create repeatable patterns of success that result in emergent experiences that restaurant goers rave about.  It's difficult in a restaurant and it's difficult on a website.

This web of interrelated influences that creates the emergent behaviour is a 4D world.  It's like the web itself, connected nodes of influence that act like the synapses in our brain, triggers firing behaviour from one sphere to the next. The fourth dimension is of course time, because each customer interacts with your company several times in several ways in different states of mind at different locations.

A creative product manager will first try to understand the web of influences, understand the triggers and amplify the ones that work, as well as trying new things that could be new influences and triggers.  All the time, measuring the impact as best she can.

Here's the thing though, experience can never be fully measured.  It's indescribable, intangible.

I can try and explain to you how I felt thinking this through on my walk up Shaftesbury Avenue this morning, Run DMC pumping through my headphones, excited because I'd pulled together some thinking that I'd been dwelling on for weeks, rucksack on my back, thinking of my next ski touring trip.  I could try.  No-one can ever really feel that except me, at that time, in that place with my history, future and present before me.

You can measure many aspects of experience, many dimensions.  Snapshots. Like the restaurant rating from the delighted customer.  You cannot really feel the experience of others, but you need to do your damn best to try.

As a product manager you are dealing with millions of those experiences.  And furthermore, you are building an interface that your customer will experience using a team of other people.

Building great experiences for others, through others.  A tough, but rewarding challenge.

Thursday, 10 February 2011

How not to ask for a phone number

A real life lesson in simple usability improvements that can improve conversion rates.

My wife and I love the movies, so to celebrate Valentine's Day this weekend we'll be going to our local cinema to see "The Kings Speech".  I've heard it's very good.

I booked online with at the cineworld.co.uk site (@cineworld) and only just managed to book thanks to a rather horrible usability hurdle.  Here follows what I wrote to them using the contact pages after the experience.

Dear Cineworld

"...I wanted to share with you a usability problem I had with the payment pages.  If my experience is anything to go by it will be seriously hampering your conversion rates and if you fix it should improve your bottom line immediately...


It's to do with the validation of the mobile phone number.


I initially put in my number as follows;
077XXXXXXXX


The error message told me to add the country code. So I did;
+4477XXXXXXXX


The error message told me to only use digits.  So I did;
004477XXXXXXXX


Then the was another error message.  Can't remember exactly what it said.  To get through the validation process I needed to actually type;
4477XXXXXXXX


4 attempts!
From someone who works building websites for a living and has done so for the last 11 years!


It's quite possibly the worst validation experience I've ever  had.


Suggestions;
1. If you want to capture the data in that format tell them so in the form up front 
2. Alternatively have a drop down of country codes to select from with UK as default.  Then ask people to enter their number as normal in the field and get your programmers to remove the first zero and any spaces.


In essence - you're making it way too complicated.


Hope you find this useful..."

What's happened here?

I've seen this happen many times.

The developer says, "In order to send SMS confirmation messages, my system needs clean and correct numbers.  I need the country code, then the mobile number in the following format; [XXYYYYYYYYYY] (where X is the country code, no zeroes, no symbols and Y is the number, no spaces, no zero up front)".

The developer does not say, "How do people usually type in their mobile numbers?  How can I help them enter it in a way that is obvious for them and still helps me get the data in the format I need"

Don't blame the developer though.  The producer / product manager should be on top of this during the design process and the interaction designer should instruct the developer.

Cineworld, to be fair have built a pretty intuitive website and it's very easy to find and select a movie to book.

Funnily enough, Cineworld did populate the form with a suggestion format in the field.  I didn't see it, the light grey was so light it didn't register.  Then, when I got it wrong, I didn't have obvious instructions on what the format should have been.


The only way top really test this is to watch real people using it.  People with nothing to do with the design process. Learn from idiots like me, tweak the form, then measure the results.  How many more visitors converted into bookings did I make as a result of that change? Sounds obvious.

Be your own customer.