I admit to being a bit of a design snob. I initially judge blogs on the way that they look or their terrible photos rather than the quality of their writing. And I often want to avoid restaurants whose websites have irritated me in one way or another. Of course, once I look further into some of those blogs I find writing I love, and once I actually go to some of those restaurants I find I enjoy them. But first impressions mean a lot.
A couple of days ago, a friend was asking me for a restaurant recommendation. Easy task, I thought. I had some restaurants in mind and just needed to check and see if they were open and send her the websites. What should have been a 5-minute email turned into a half-hour nightmare as I slogged through websites that are more intent on impressing me with movies, music, and other annoyances than on giving me direct information.
Hear this, restaurants: We are not looking to your sites for entertainment. We want to get our information, get out, and get back to watching Eli Stone. Noise of clinking glasses or a dull roar or fancy music does not make us want to go to your restaurant more, it just tips off our employers that we are making dinner plans instead of filing our TPS reports. We don't want to sit through 30 second flash movies of how happy we'll be if we go to your restaurant. We just want the facts: When are you open, what's for dinner, and how much does it cost. And I want to do that in as few clicks as possible.
Oh, and also? We are in the Bay Area -- arguably the technology capital of the world. How difficult is it to learn to code up a simple HTML page? Why are you still making us click through to PDF's of your menus or (horrors) Word documents? It's all about time for me, and opening up the pdf takes up my precious seconds.