"Users do not read instructions."
This is part of what I call the paradox of content. There exists the desire to fix usability issues with an application by adding more instructions. When that doesn’t help, even more instructions are added. All the time, the user is not even reading them.
The way to fix usability issues is by fixing the real issue with application design, flow, etc. and by not adding more content.
This idea obviously can also be applied to content, information architecture, and web site design.
Actually, I would like to call it a methodology. The Paradox of Content Methodology.
Or maybe I can create a movement. The Paradox of Content Movement.





Posted by: Maggie on Wednesday, May 7, 2008
Great post! I totally agree. Although I sometimes wonder what Nielsen was smoking when he comes up with his famous "statistics" I do have to agree that lengthy instructions are usually pointless unless you have a dedicated (read: forced) user who *has* to use your tool to accomplish something. Especially when instructions are big red blocks of text.