I was reading this post from Jensen Harris on how difficult it is get users to criticise user interfaces. He calls it "Usability Stockholm Syndrome". Meanwhile, from his body language I could tell one of my co-workers was obviously not that happy with a document I had written on recovering if one of our systems has an error. However, I found it really hard to get him to tell me what could be improved about it. He kept saying "No it's fine." Or "It's adequate." I had to really emphasise I want to improve both my document and my writing abilities to get some useful feedback.
This reminded me of reading a great book on writing software manuals - the User Manual Manual by Michael Bremer, who also wrote Untechnical Writing. In it he looks a trying to document a user interface. Unfortunately accomplishing the simplest task requires paragraphs of difficult prose, operating 200 different GUI controls. He says it's often much better to fix the user interface so performing the task is easy, then writing the documentation will just be an easy to understand paragraph.
There are other similarities between writing and developing user interfaces:
- The end users don't always know how to improve them, but they know when they find them difficult to read or use
- Important elements have to come to hand quickly, more obscure details can be left until later or put somewhere more obscure
- Eat your own dogfood is necessary for quality but not sufficient
- Hallway usability tests work for both
Post a Comment