The current trend is to create devices that do it all, but specialize in a certain area at the same time.  For instance, the Blackberry is a PDA that also makes calls/takes photos, a cellphone makes calls but will also act as a clock/watch.  The iPod is an MP3 device but it will play your movies and you can also do some gaming.  These devices do well at their main function, but tend to skimp over the other stuff.  Cell phones make calls but suffer from a poor interface.  iPods play MP3s but I’ve never seen anyone use them to play games.  Instead of focusing on adding a bunch of pointless accessories, why not make hidden features?

High end watches can be sold for an absurd amount of money.  The watch performs one function, and so the rest of what it “does” is up to the owner.  The connection to the brand, the prestige, the story that the consumer tells themself, etc.  These are the hidden features.

Hidden features aren’t spelled out in the manual.  Not every user is affected by them.  The iPhone has a bunch of hidden features, all the way from the way it looks sitting on your hip, to the way it makes you feel like a futuristic businessman when you’re touching icons and watching the cool animations.  The rush you get from pushing the accelerator on a BMW, that’s a hidden feature.

For devices that do one thing really well, and do a mediocre job on the other stuff, hidden features might be a good thing to look into.

1. the manual is a scrapbook of interesting stick figures and parts that must have been left out from your package
2. the manual is actually 5 or 6 manuals that all contain different information and distinguishing them isn’t possible at a quick glance
3. the manual contains completely useless information about the product
4. the most common: shoved into a drawer for “later” use
5. a combo of two or more of the above

I’ve explained before that I am everybody’s favorite technology guy when it comes to my friends and family. My dad had asked me for help with setting up his car to receive the bluetooth signal from his Razr. We sat there for a while, flipping through the manual, trying to find any shred of evidence about the bluetooth settings. We tried almost every menu in the car’s interface. We found buttons that would search for bluetooth devices, but none that would actually find the devices, or try to pair them at least.

I finally asked if there were extra manuals included with the car, and my dad pulled out a stack of them, one of them displaying a picture of a London phone booth. The instructions in the pamphlet led us through the process perfectly.

So I started thinking. Is it more important to have a solid UI or a helpful manual? Should we not hold it against the UI if we have to peek inside the manual? I came to a conclusion.

It’s not up to the designer to decide whether or not the UI is any good. The UI should have been at least somewhat easy to use and in the event that it hadn’t been, the purpose of the additional pamphlet should have been crystal clear. For instance, “Bluetooth Set Up” should have been written on the cover in very large letters instead of the very ambiguous phone booth photo ( a photo which could imply many different things). Easy as that. BMW still could have maintained a sense of style if they wanted to use a stock photo of a phone booth, as long as the purpose of the document was easy to identify.

Food for thought: the iPhone has been praised for its stellar UI, but its manual is the first hit when you google the word “manual.”