I’ve been saying this for a while — as a medium gets faster, it gets more emotional. We feel faster than we think.
June 17, 2009
March 25, 2009
January 14, 2009
People Do NOT Want to Register
Jared M. Spool writes about how removing compulsory registration from a website translated into a $300,000,000 increase in sales. (Via UI and us). The intentions behind the registration were good: make things easier for repeat customers by remembering their information. This would reward the most loyal customers, and for first-time customers registration would only be a small one-time step. But in practice, the registration was universally hated.
We were wrong about the first-time shoppers. They did mind registering. They resented having to register when they encountered the page. As one shopper told us, “I’m not here to enter into a relationship. I just want to buy something.”
…Without even knowing what was involved in registration, all the users that clicked on the button did so with a sense of despair. Many vocalized how the retailer only wanted their information to pester them with marketing messages they didn’t want. Some imagined other nefarious purposes of the obvious attempt to invade privacy. (In reality, the site asked nothing during registration that it didn’t need to complete the purchase: name, shipping address, billing address, and payment information.)
Repeat customers weren’t any happier. Except for a very few who remembered their login information, most stumbled on the form. They couldn’t remember the email address or password they used. Remembering which email address they registered with was problematic – many had multiple email addresses or had changed them over the years.
When a shopper couldn’t remember the email address and password, they’d attempt at guessing what it could be multiple times. These guesses rarely succeeded. Some would eventually ask the site to send the password to their email address, which is a problem if you can’t remember which email address you initially registered with.
(Later, we did an analysis of the retailer’s database, only to discover 45% of all customers had multiple registrations in the system, some as many as 10. We also analyzed how many people requested passwords, to find out it reached about 160,000 per day. 75% of these people never tried to complete the purchase once requested.)
The form, intended to make shopping easier … just prevented sales – a lot of sales.
The $300,000,000 Fix
The designers fixed the problem simply. They took away the Register button. In its place, they put a Continue button with a simple message: “You do not need to create an account to make purchases on our site. Simply click Continue to proceed to checkout. To make your future purchases even faster, you can create an account during checkout.”
The results: The number of customers purchasing went up by 45%. The extra purchases resulted in an extra $15 million the first month. For the first year, the site saw an additional $300,000,000.
Personally, I am in complete sympathy with the test’s participants. I don’t want to have to register to do something. In fact, I’ve re-registered for ADC a few times, because I lost my login information. (I really wish I could reclaim my first ADC membership from highschool, now tied to a defunct AOL address, because the member # is one digit shorter!)
Security Implications
Unfortunately, people have good reason to be wary of registration — it puts their credit card information at risk. And we’ve all been burned by spam and junk-mail from someone who abused registration information.
The Future is Here
Modern web browsers all have some kind of auto-fill that can remember and enter shipping/billing information. This technology obsoletes the benefits of registration in the story.
There’s more that could be done to be smarter about registration. For example, not exposing it in any way unless a person has made several orders.
Of course, the smartest thing is to avoid registration, because your users hate it. Services like BugMeNot prove this.
January 4, 2009
How To Beat Web Apps
The way Apple stays ahead of the web app trend is by creating native Cocoa experiences that can’t be duplicated in web apps — both on the Mac and iPhone.
Lemur CATTA and the Author’s Burden
― Vincent Gable on March 25, 2009
Mike Lee had an interesting idea for improving comments on blogs. Before someone can post a comment, they have to pass a reading comprehension test, to show they read the article they are commenting on. He called his implementation Lemur CATTA
It’s a good idea, especially for certain communities. But the implementation rubbed me wrong from day one. My problem was that the questions were automatically generated.
I feel like it’s the author’s burden to make their work as accessible to readers as they can. If they are placing a barrier in front of commenters, they should do everything they can to make sure the barrier is effective at blocking the bad, but easily permeable to the good. I don’t feel Auto-generated questions are compatible with that responsibility.
There’s a callousness to auto-generated questions. The author is essentially saying, “Yeah, I took many hours to write this post, and I’m going to inconvenience every reader who wants to reply, but damned if I take a few minutes to write these questions myself”. And that just rubs me the wrong way.
To be fair, writing reading comprehension questions is harder then it seems — at least when I’ve tried it. Maybe a computer is more effective at generating quizzes then a prose writer. (But I doubt it’s more effective then a prose writer with practice.) And auto-generation has all kinds of benefits. It can be applied to comments, and real-time discussions, for example. But sometimes the human touch is more comforting. It gives an assurance that the author cares about what you have to say, and worked through any problems you might be having with the comment system.
More info on Lemur CATTA at lemurcatta.org.