Loads of web experiences out there attempt to make things easier by using services to source data and populate fields with information on the users behalf. In principle this is a great idea - ask the user to provide one or two bits of information and then return multiple populated fields back, sounds great! In reality even simple #PAF look-ups often take an age to return addresses or there are silly little mistakes in the #UX which mean that users still have to sift through a huge drop down to find the information that relates to them. Worse still the wait for the information to return takes forever and then sometimes only a couple of additional fields are populated leaving the user asking - 'was it worth it!'
These problems are still common and with some #UX planning these can be avoided. I think E-business professionals need to start or more often identify user thresholds for these sort of things and take a lead in driving the system / operational planning as well as optimising the front-end experiences.
The key here is to maintain user momentum, if something acts as a stumbling block or takes time and means the user is likely to start up another online activity you have increased your chances of losing them significantly.
Reference: #UX = User Experience
Hi, I'm Rory Yates. As an active member of the digital world this blog is a way of bringing together different strands of my digital life. It is also a chance to let people know about some of the real world things I get up to as well. These are my views only.
Showing posts with label User Experience. Show all posts
Showing posts with label User Experience. Show all posts
Wednesday, 20 October 2010
Subscribe to:
Posts (Atom)