It's the little things

The Shane Company has a great example of a slick usability trick in their print-out ring sizer, for you to see which size ring you need, they have pictures of coins and a ruler on the printout so you can ensure that the printout wasn't scaled to an inaccurate size:

Very simple, but very nice.

The printout has many other simple but elegant tricks on it to ensure that the user doesn't get anything wrong, such as:

Guides so that you cut out the ring sizer at the exact tip:

 

Printing the numbers in the center so that they're not mercy to your scissor skills:

 

And if you have a ring that fits perfectly, you can just compare that ring to the circles on the page to see what the perfect size is... it's always nice to provide two different ways to perform a task if you have two different entrypoints through which you might need to get to the answer:

Comments

• Anonymous
  January 01, 2003
  SW - It's not built in, that's a very geek-specific piece of functionality. With OWA 2003, you can do a raw HTTP request with Translate: f on the GET request directly to the /path/to/the/message.eml, and that'll get you the full MIME headers... but obviously that's not a simple operation =) My question to you is... what do you do after you look at the headers? E.g. why do you want that information, how does it help you make a decision, what are the possible paths of that decision, etc?

• Anonymous
  January 28, 2008
  I recently found a printable sizing guide on crocs.com that shared some similarities.

• Anonymous
  January 29, 2008
  The comment has been removed

• Anonymous
  January 30, 2008
  The comment has been removed