Superhero Silhouette Art by Poster Inspired
Get your 11 x 17 poster, here.
connect :: rss :: twitter :: google+ :: linkedin :: built in chicago
Heuristic Evaluation
Heuristic evaluation is a method that uses guidelines, or heuristics, to detect usability issues. Originally developed by Jakob Nielsen to inspect computer software, it has since made its way into the web world – where heuristic evaluations are used to determine a site or app’s messaging, usability and flow. And also used to identify potential issues and opportunities within the overall design.
In other words, if you want a formal, systematic way to evaluate what’s really going on (or not) with your current site or app interface, perform a heuristic evaluation.
The beauty of a heuristic evaluation is that it’s simple, low cost and useful at any stage of the product life cycle. And you don’t need an army of researchers to conduct one.
Now, back to Jakob. His heuristics, by far, are the most widely used:
1. Visibility of system status
Always let the user know what’s going on (eg – show a status bar).
2. Match between the system and the real world
Your site/app/system should speak the user’s language.
3. Give users control and freedom
Allow users to explore without worry.
4. Design with consistency
Maintain the same look and feel the throughout your site/app/system.
5. Error prevention
You should always strive to prevent errors. (…)
6. Design for recognition rather than recall
The more you can minimize the user’s memory load, the better.
7. Design for flexibility
Allow users to save frequent actions, preferences and settings.
8. Aesthetic and minimalist design
If you’re reading this post, then this should be self-explanatory.
9. Help users recognize, diagnose and recover from errors
If an error should occur, then your message needs to be clear, concise and comprehensible. Use plain language, not code.
10. Provide help and documentation
It’s better if your system can be used without, though it’s often necessary.
Some final thoughts:
Even though heuristic evaluations can be implemented at any stage of the product life cycle, it’s best to perform them early in the design process. And ideally, used to complement user testing, not replace it.
And while Jakob’s heuristics are widely used, they’re often supplemented with additional heuristics relevant to a specific project.
For more information, visit:
Fluid Project Wiki | Usability Evaluation Questions
The Quick & Dirty Heuristic Evaluation Template (PDF)
UX for the masses | A guide to carrying out usability reviews
Week One: Code Academy User Experience Design
In the vein of continuing education, meeting market demand, and indulging my inner nerd, I applied and interviewed for Code Academy’s User Experience (UX) Design class, and got in!
I wanted to learn more about UX Design for the better part of a year. Rather, I always knew. But that knowing always came with that know-but-didn’t-really-know feeling. Then a prospect mentioned it. Then I heard about Code Academy. Then I heard about their UX class. And next thing you know, I’m sitting in a room with 25-ish classmates at 1871, while our instructor, Carolyn Chandler, introduced us the course, explained the importance of sketching, and all there is to know about heuristic evaluations.
And then I freaked. What am I doing?! I already have more than enough on my plate. My schedule’s already scheduled. How will I complete the homework week in and week out?! ARGH!
**calm down, Kitty. you can handle it. the intro was self-explanatory. you’ve been sketching all your life. you reread the ppt. now do the homework.**
Okay. Our assignment for week one: complete a heuristic evaluation of one of four sites (listed on the ppt), using one of four evaluation methods (also listed on the ppt).
I think I may have chosen the most difficult site to evaluate. However (and thankfully), my choice of evaluation method will more than make up for that. I’m withholding names and URLs to protect the innocent. And I’ll delve deeper into what heuristic evaluations are all about in my next post. Promise.
Until then,
K