In a brilliant contrarian blog post, titled provocatively “Should you lose the n00bs?”, Seth Godin asks how simply should applications be designed, and what kind of prerequisites a programmer should expect from its users. For years, the standard approach was to design any application with an ignorant user in mind (which German speaking programmers not so affectionately call the DAU approach, for “dümmster annehmbarer User” = “stupidest user possible”). Godins objects:
“The problem with this approach is that you can never be simple enough. And of course, the bigger problem: Once you dumb it down so every single person gets it, you bake out the magic and the mystery and the elegance. (…) At the symphony, should there be big applause signs so that people don’t clap at the wrong time?”
The great idea behind this short post is that it disconnects intuitiveness from usability:
- Intuitiveness refers to how easy it is for new users to catch on – and this depends upon prior knowledge. Connecting tables in Access is intuitive, if you know how a relational database works. Using Google Reader is intuitive if you know what an RSS feed is.
- Usability refers to principles of efficiency and predictability in using a tool. A link on a website should stand out of non-linked text, preferrably underlined. The “File” menu should be the first in any windows application. A user should be able to correct errors with Undo. Usability applies to every kind of user, regardless of his knowledge about the application.
Instead of making applications idiot-proof, Godin suggest to either accept confusion and encourage questions, or to respectfully shut newbies out:
“Why not consider making it easy for the confused to ask for help? And treat them with respect when they do. If you don’t create a little confusion, it’s unlikely you’ve built something remarkable.
And to go one step further: sometimes it’s okay to lose the n00bs. Not in an arrogant way (except for some brands) but in a way that says, ‘this might just not be for you…’”