10 Heuristics For User Interface Design - Article by Jakob Nielsen
10 Heuristics For User Interface Design - Article by Jakob Nielsen
10 Heuristics For User Interface Design - Article by Jakob Nielsen
NielsenNormanGrouphasjobopeningsforUXSpecialists(bothentryleveland
experiencedcandidateswanted).DeadlineMarch17.
Summary:JakobNielsen's10generalprinciplesforinteractiondesign.Theyare
called"heuristics"becausetheyarebroadrulesofthumbandnotspecificusability
guidelines.
Visibilityofsystemstatus
Thesystemshouldalwayskeepusersinformedaboutwhatisgoingon,throughappropriatefeedback
withinreasonabletime.
Matchbetweensystemandtherealworld
Thesystemshouldspeaktheusers'language,withwords,phrasesandconceptsfamiliartotheuser,
ratherthansystemorientedterms.Followrealworldconventions,makinginformationappearinanatural
andlogicalorder.
Usercontrolandfreedom
Usersoftenchoosesystemfunctionsbymistakeandwillneedaclearlymarked"emergencyexit"toleave
theunwantedstatewithouthavingtogothroughanextendeddialogue.Supportundoandredo.
Consistencyandstandards
Usersshouldnothavetowonderwhetherdifferentwords,situations,oractionsmeanthesamething.
Followplatformconventions.
Errorprevention
Evenbetterthangooderrormessagesisacarefuldesignwhichpreventsaproblemfromoccurringinthe
firstplace.Eithereliminateerrorproneconditionsorcheckforthemandpresentuserswithaconfirmation
optionbeforetheycommittotheaction.
(Readfullarticleonpreventingusererrors.)
Recognitionratherthanrecall
Minimizetheuser'smemoryloadbymakingobjects,actions,andoptionsvisible.Theusershouldnothave
torememberinformationfromonepartofthedialoguetoanother.Instructionsforuseofthesystemshould
bevisibleoreasilyretrievablewheneverappropriate.
(Readfullarticleonrecognitionvs.recallinUX.)
Flexibilityandefficiencyofuse
Acceleratorsunseenbythenoviceusermayoftenspeeduptheinteractionfortheexpertusersuch
thatthesystemcancatertobothinexperiencedandexperiencedusers.Allowuserstotailorfrequent
actions.
Aestheticandminimalistdesign
Dialoguesshouldnotcontaininformationwhichisirrelevantorrarelyneeded.Everyextraunitof
informationinadialoguecompeteswiththerelevantunitsofinformationanddiminishestheirrelative
visibility.
Helpusersrecognize,diagnose,andrecoverfromerrors
Errormessagesshouldbeexpressedinplainlanguage(nocodes),preciselyindicatetheproblem,and
constructivelysuggestasolution.
Helpanddocumentation
Eventhoughitisbetterifthesystemcanbeusedwithoutdocumentation,itmaybenecessarytoprovide
helpanddocumentation.Anysuchinformationshouldbeeasytosearch,focusedontheuser'stask,list
concretestepstobecarriedout,andnotbetoolarge.
IoriginallydevelopedtheheuristicsforheuristicevaluationincollaborationwithRolfMolichin
1990[MolichandNielsen1990NielsenandMolich1990].Isincerefinedtheheuristicsbased
onafactoranalysisof249usabilityproblems[Nielsen1994a]toderiveasetofheuristicswith
maximumexplanatorypower,resultinginthisrevisedsetofheuristics[Nielsen1994b].
SeeAlso:
Bruce"Tog"Tognazzini'slistofbasicprinciplesforinterfacedesign.Thelistisslightlytoolongforheuristic
evaluationbutservesasausefulchecklist.
Examplesofthe10heuristicsinWebapplications.
The10usabilityheuristicsappliedtoeverydaylife(justforfun).
Fullsetof2,397usabilityguidelines(acrossmultiplereports).
References