Designing without manual,
A couple of weeks back, I was talking to my cousin who is a doctor in US who happily declared that she had finally bought a iPhone. My cousin is very intelligent and a great doctor but she is not one who can be called tech savy and would be a perfect example of a late adapter.
She was very happpy about the ease of use of the iPhone and wished it had USER MANUAL. The first thing that astounded me, was the discovery that there were people who actually read a manual :-) Most of my device user manuals are stored in unopened packets for a couple of years till my wife throws it out.
The second thing that came to my mind was the manuals are needed for products which are extremely complicated to use (like the VCR or the universal remote control). My design philosophy has been that if you need to develop a manual, you have not designed it right.
A good product is one in which the configuration is simple and well laid out. I have always found it maddening when the configuraion is not in place where it is supposed to be and hidden under obsure headings. For example, a Samsung touch phone whose ring tones was hidden somewhere under media files and not under phone settings.
Just as a product manager loves to add functionality, the engineer loves to add usless configuration for the same unless functionality. On the other hand user wants a device which works but has no interest to on functionality and configuration.
Also the devices in todays date are powerful enough to figure a lot of configuration details on their own. For example, does a user care if the password for wifi is WEP, WPA-TKIP, WPA-AES, WPA2-TKIP, WPA2-AES, 802.1x .... All that the user knows is that there is a password.
Coming back to my cousin's problem of not having a manual was she could not become a power user without it. The joy of discovering the features on iPhone, the 'a-ha' moments in finding its simplicity and then bragging about it to your friends is priceless.
She was very happpy about the ease of use of the iPhone and wished it had USER MANUAL. The first thing that astounded me, was the discovery that there were people who actually read a manual :-) Most of my device user manuals are stored in unopened packets for a couple of years till my wife throws it out.
The second thing that came to my mind was the manuals are needed for products which are extremely complicated to use (like the VCR or the universal remote control). My design philosophy has been that if you need to develop a manual, you have not designed it right.
A good product is one in which the configuration is simple and well laid out. I have always found it maddening when the configuraion is not in place where it is supposed to be and hidden under obsure headings. For example, a Samsung touch phone whose ring tones was hidden somewhere under media files and not under phone settings.
Just as a product manager loves to add functionality, the engineer loves to add usless configuration for the same unless functionality. On the other hand user wants a device which works but has no interest to on functionality and configuration.
Also the devices in todays date are powerful enough to figure a lot of configuration details on their own. For example, does a user care if the password for wifi is WEP, WPA-TKIP, WPA-AES, WPA2-TKIP, WPA2-AES, 802.1x .... All that the user knows is that there is a password.
Coming back to my cousin's problem of not having a manual was she could not become a power user without it. The joy of discovering the features on iPhone, the 'a-ha' moments in finding its simplicity and then bragging about it to your friends is priceless.
Comments