To keep things friendly and approachable, applications often ask a new user to supply their first name. In designing the sign up procedure for Cozi Central, I applied my favorite trick for asking for first names: provide an example of what kind of name you want.
To ask a user their first name, you'd think you could just create a text box labeled "First name:". The problem is that many people don't want to use their first name. A user might prefer to go by a nickname, for example. However, at sign up time, the user has no idea how your product is going to use the name they enter, so they may hesitate to enter a nickname instead of their real first name. Your application may end up addressing the user by a name they dislike.
You could just ask the user for "Name:", and figure that they can enter whatever they want. Now you've got a new problem: tons and tons of people will enter their full name, or their last name, or something else. Your program might then address them cheerfully but stiffly: "Good morning, John Anthony Smith!"
To elicit a first name but leave the door open for something else, ask the user for "Name:", but provide an example that shows a first name:
This seems to work quite well in practice. (I give credit for this trick to software designer and all-around nice guy David Sloo.)
Caution: There's a limit to how far you can push this idea, as Cozi learned this past week. Since our sign up page used an example for Name, we went ahead and put examples next to most of the fields, including the email address fields. The sample email addresses were at cozi.com, so that we could avoid collisions with a real domain name. Bad idea: many users thought we were giving them a new email address, so they entered their own name @cozi.com instead of entering their existing email address. We promptly cut the email address examples from the sign up page. By now, most people should know what an email address looks like.
I think "example.com" is a good domain to use for email addresses, although users could easily make the same mistake - assuming that you're asking for an "example.com" email address.
Posted by: Matt Hamilton | October 01, 2006 at 09:07 PM
There is an RFC about example domain names, email addresses and so on. I can't recall the number but example.com is a reserved domain name by IANA for this purpose.
Posted by: Ross | October 02, 2006 at 12:47 AM
Thank you for bringing this very important issue up. There is a large segment of the population for whom the first name/last name distinction doesn't really work. A great many of us prefer to go by our middle names (the H. Albert Smith's). A subtle hint like this lets us know that we can use our middle names without some authority figure (police officer, bank teller, customs official, &c.) totally freaking out because document A says Harold A., while document B says H. Albert.
It has been my experience that when I need to collect someone's full name, including fields for first name, middle name (not simply middle initial), last name, and preferred name (pre-filled with first last), works well, at least when it comes to traditional American names.
Posted by: Chris | October 02, 2006 at 06:27 AM
It's always a good thing to give an example. For this purpose, one better has to provide a link or a button labeled "see an example"and then one get something more clear, explaining that the user can write his real name or a nickname and his e-mail address is required.
Of course the user can miss the example, but an user can do a lot of unexpected things.
Posted by: lucmars | October 02, 2006 at 12:23 PM
Useless info: This example-name use is how UK soldiers came to be known as "Tommies", the enlistment paperwork in WWI told them to enter their names, "for example Thomas Atkins" (although various sources claim this usage goes back to at least the Napoleonic era).
Posted by: Arbitrary feedback poster | October 19, 2006 at 02:39 AM