The first thing I’ve ever written to be sold directly to people (as opposed to writing for a magazine or website) is now available:
This is my first Adaptive Path report. It’s a “Best Practices Brief” on the importance of clear labeling and terminology in site design. (Though, of course, it can be expanded to pretty much any design realm.)
Here’s my little illustration which introduces the report:
It was in the process of writing this report that I started to become obsessed with this notion of managing expectations. Words on websites are *all about* appropriately setting expectations, since they are pretty much all that a user has to go on to know what to click to find stuff that will satisfy their needs.
The thing is, as any one who has tried to write thoughtfully and carefully knows, words are hard. They’re often ambiguous. Or dull. Or they make sense on their own, but not when grouped with other ones. This report addresses the common nomenclature pitfalls we’ve seen again and again at Adaptive Path (typically in our client work, but also just being active Web users).
This report is likely not of direct interest to readers of peterme — statements like “Make your labels explicit” and “Clever labels can obscure destinations” are just preaching to the choir here. In my experience, bad labels come not from the web design team, but from their “clients” throughout the organization. Clients who are very attached to certain words, usually for some perceived branding goodness. I’m hoping that his report can be passed around to a web teams’ colleagues in an effort to make clear why you shouldn’t, for example, label training as “Education Services.”