As I stopped to get my morning coffee, the woman behind the counter was going on about this newsletter she receives about her daughter’s preschool and how hard it was to decipher. She still wasn’t sure if her daughter actually had preschool that day or not. Her frustration was obvious, and reminded me of the ever-present challenge of usability in our lives. Nobody likes having a toaster you can’t figure out, roadsigns that are hard to understand or websites that are impossible to navigate. Product developers have an important task on their hands: to ensure consumers find the product useful. We consider ourselves product developers as well because websites can be more than brochure-ware; they are e-commerce engines, communications tools, educational resources and more. On the web, usability is a make or break element. If users can’t understand how to use a website or can’t find what they’re looking for, they’ll be gone - probably forever. It is an avoidable obstacle, however, if given some thoughtful planning and consideration. There are numerous schools of thought out there on usability best practices, but a good place to start is to evaluate the current state of your site from a general usability perspective. Conducting a quick heuristics evaluation can shed a lot of light on glaring problems and obstacles. Below are seven questions to ask about your website in the context of your market, goals and target audience, based on heuristics standards set by Jakob Nielsen, 1. Does the website inform users about what’s going on during their engagement and give feedback in a timely and appropriate manner?, 2. Does the website use language and terminology that the user is familiar with and follow real-world logic and convention?, 3. Does the website provide adequate exit options, allowing users to correct mistakes and providing clear error messages?, 4. Does the website use consistent language, navigation and action standards across the entire site?, 5. Is the website structured to prevent or check for user error with tools like confirmation steps, etc?, 6. Does the website provide clear direction about where the user is in a process or in the site, eliminating the need for the user to have to remember where they came from or how they got there?, 7. Is the website content relevant to the section and the audience?