Bad Practice In User Interface Design - Misuse Of The Drop-Down Menu
You see it everywhere; in the operating system your computer is running and in the websites you visit. There is no escaping poor interface design.
I've been meaning to write an article on this subject for some time now, squarely centred on website interface design. However, reading this list of The 5 Sins of Vista and subsequently the ensuing tirade of abuse hurled at the author by numerous Digg commentators - merely for expressing a distaste for certain tasks being made more complex than they should be - I decided to cast an eye over both OS and website interface design.
Rather than cram everything into one mammoth article, I've decided to split things across an as yet undetermined number of parts. Part 1 will focus on the drop-down menu and its use, or misuse, in website interface design.
Blurring the Lines
Quite unsurprisingly the boundaries between website interface design and OS interface design have become blurred in recent times; in particular, with regards to navigation.
It is not surprising to be honest. More people are spending more time at their computers than ever before, and most of the time people are at their computers they are browsing the Internet.
People are familiar with what would be considered common
OS interface elements and as such web designers have come to incorporate some of these elements into their website designs. The rub is that familiarity
does not equate to the best tool for the job
. More specifically, what works in an OS interface is not always appropriate for use in a website.
Action versus Destination
The biggest offender, in my view, is misuse of the drop-down menu
. Lifted straight out of a desktop application, the drop-down menu that runs across the top of the program interface and provides access to a multitude of tools and options, has been adopted for use in the navigation of countless websites.

For some reason that continues to escape me, drop-down menu website navigation is a particular favourite of blue chips. The global websites of Sony, Dell and Nokia all rely heavily on the drop-down menu for navigation.
The big problem is that the drop-down menu was never intended for navigation. As such there are a number reasons that make the drop-down menu a poor mechanism for navigation.
Firstly, the content of a drop-down is hidden from the user. Any designer with even the slightest comprehension of good practice will know that navigation should never be invisible. A web designers' job is to make it as easy as possible for the user to find what they are looking for and hiding the navigation immediately throws up unnecessary barriers.
Aside from hiding destinations from the user, a user has to know that a button has a menu hidden behind it in the first instance. You are unable to see what lurks within unless you position your mouse over the button and wait for the menu to appear. This takes time and effort and while we may consider this insignificant, we should all know by now how little it takes to put a user off. We are also assuming, of course, that the menu will appear because the user has Javascript enabled and meets any other criteria for the usually scripted menu to function correctly. For me, the technical prerequisites alone are reason enough to avoid the use of drop-down menus in website navigation.
So what about drop-down menus in software applications? They are used in virtually any modern application you can care to mention, so why are they such a bad thing in website navigation?
Let's take a moment and think about what drop-down menus in software applications are actually used for; you access the File
menu to save a document, to open a document, or to print a document. The Edit
menu to undo, to copy, or to paste, and so on... These are not destinations. These are actions. Drop-down menus in applications are used to provide access to functions that allow a user to perform a particular action. Essentially, a drop-down menu is a means to do something
- not a means to get somewhere
.
Drop-down menus were never designed as a navigation tool, yet somewhere along the line someone thought to mimic drop-down behaviour and bend it for use in website navigation.
A Better Way

There are of course better mechanisms for facilitating website navigation. Mechanisms that avoid invisible navigation. One only need look at the Finder column view in Mac OS X for an example of visible folder navigation.
Online, we only have to look to Internet giants such as BBC News, Amazon and eBay for examples of websites that, in spite of their cavernous archive of web pages, do not have a single drop-down navigation menu in sight.

When these websites do utilise drop-down menus, it is in the appropriate manner. eBay, for example, uses a drop-down menu within the My eBay
management area for performing actions. It even has it sat under an Action
heading.
It is no coincidence that these websites top user polls for ease-of-use. Nor is it in any doubt that they would have achieved the success they have if it weren't for that ease-of-use. For me, these websites are the pin-ups of good website interaction design. Perhaps if the wider community of web designers held these websites as icons to aspire to rather than the likes of Sony or Nokia, and dare I say it, looked at interaction design with more than a cursory glance, then perhaps the web can be a better place for all of us.
Comments are closed for this journal entry.
Kitsimons...
![]()
...is the online home of Simon Kitson, a web designer with a healthy enthusiasm for standards-compliant, accessible design and a penchant for blogging about nothing in particular.
Notes
- Nice Nike Football ad from Madonna's better half.
- Top marks for the realigned BBC News website, bringing it more in line with the lovely new, jQuery driven, BBC homepage.
Beautiful full-screen image browsing served up by the snazzy PicLens plug-in. Impressive, though practicality is debatable.- Yahoo shifts to search the
semantic web
. Potentially huge, and very welcome news for usstandards nuts
.
The Coke Zero Game. Latest masterpiece from the infuriatingly talented North Kingdom.
It's sites like the Red Bull Flight Lab that remind you what Flash is for. Brilliant application and an awful lot of fun.- Rejoice! The new Indiana Jones trailer has finally made an appearance. Can't wait.
- Help the Email Standards Project get Google's attention in the hope they will finally improve Gmail's awful rendering of HTML email.
- Awesome panoramic view of the Airbus A380 cockpit interior. This is the super-future.
- Excellent article from accessibility supremo Roger Johansson on how inappropriate, or overuse, of HTML features meant to aid accessibility can actually have the opposite effect.









Nathan Logan
23 January, 2007
Thanks for the article – I think you made some good points.
It’s interesting that you mention Amazon (and report that it “top[s] user polls for ease-of-use”) because the .com version actually makes use of a huge drop-down menu (but also presents an incomplete vertical navigation).
The real point I wanted to bring up, though, is that I think your distinction between destination and action is artificial. Take File->Save As for example. I actually get a new window with which I can interact. File->Print Preview even gets rid of the document behind. Tools->Options takes me to another window entirely, where I may or may not be making changes relative to this document. Not everything there is an Edit->Undo or Window->Maximize. And I think users get that.
If I were to guess (and that’s all we’re doing here without studies or stronger arguments), I would say that users understand the drop-down paradigm – that a top-level item may have sub-sections – and if it does, a drop-down is acceptable. And the fact of the matter is that as they are used more, they will become more usable (since users will know what they are and how to use them). This is particularly the case with oft-used sites like ESPN, Amazon.com, and even Google (click on “more>>”) embracing them.
They aren’t always the best solution – no argument there. But there are times when users benefit from them. Let me leave you with an example. When I go to ESPN, I can go directly to College Football, rather than hit the College page first and go from there – and in fact, I can get to full rankings with 1-click from the homepage, rather than the 3 it would otherwise take.
Steve Tucker
23 January, 2007
Great article, Simon. I think you’ve really hit the nail on the head by pointing out that dropdown menus should be used only for actions rather than navigation. Oddly Adobe’s website supports a prominant navigation dropdown on it’s homepage. I for one would imagine they’d be experts in the field of usability.
Oh, and you’ve also successfully made me feel stupid for supporting a dropdown menu on my own site for so long:
“Any designer with even the slightest comprehension of good practice will know that navigation should never be invisible”
Ahem.
kitsimons
23 January, 2007
Thanks Nathan. Good points.
Accessing options in an application’s drop-down menus will nearly always open up a dialog box or take you to another screen. However, this is a side-effect of the user wishing to perform an action – their goal is not to open a dialog box after all.
I suppose a better example is that you wouldn’t browse through pages in a Word document by using the application’s drop-down menus. Navigation between pages in a document is accomplished through buttons in the UI, or by using the scrollbar.
I agree with you about drop-downs being useful to a certain extent as well, but I think the key is that this process requires a degree of proficiency. You and I may have this, but the vast majority of web users out there don’t. It also requires a level of familiarity – not being familiar with the ESPN website myself, I would have to dig around to find what I’m looking for. There are methods of navigation that would allow me to do that in one click, but without hiding it behind a drop-down menu.
@Steve – that wasn’t my intention. Honest :-)
I’ve made many a faux pas in the past. I’m sure I continue to do so in one way or another…
Live and learn, eh?
Steve Tucker
24 January, 2007
Aye, live and learn! :)