forked from openpracticelibrary/openpracticelibrary
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request openpracticelibrary#457 from openpracticelibrary/c…
…ms/heuristic-evaluation Create Practices “heuristic-evaluation”
- Loading branch information
Showing
1 changed file
with
23 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
--- | ||
title: Heuristic Evaluation | ||
subtitle: Provide expert review of UX designs | ||
date: 2018-10-30T16:18:22.725Z | ||
authors: | ||
- rdebeasi | ||
area: delivery-measure-and-learn | ||
people: '2' | ||
time: 30 minutes | ||
difficulty: moderate | ||
participants: | ||
- UX designers | ||
- or team members interested in UX | ||
--- | ||
## What is it? | ||
Heuristic evaluation is a method for reviewing designs based on ten basic principles. The term was [coined by Jakob Neilsen](https://www.nngroup.com/articles/ten-usability-heuristics/) back in 1995, but the principles are still just as relevant today. | ||
|
||
## Why use it? | ||
- Provide expert review of designs, which can be a great companion to feedback from usability testing. | ||
- It can be difficult to provide useful design critiques. These heuristics help reviewers provide concrete, actionable feedback. | ||
|
||
## Further Information | ||
- [Ten usability heuristics](https://www.nngroup.com/articles/ten-usability-heuristics/) |