Difference between revisions of "UX Overview"
From GWAVA Technologies Training
(→Designing for Accessiblity) |
(→Examples) |
||
| (17 intermediate revisions by one user not shown) | |||
| Line 1: | Line 1: | ||
| − | The User Experience is more than just what it looks like but how it works. | + | The User Experience (UX) is more than just what it looks like but how it works. |
| − | + | We handle large amounts of customer data and losing the data can have severe business consequences for them and for us. | |
| − | + | ==Examples== | |
| − | + | If you think UX isn't important: | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | *[https://twitter.com/CivilBeat/status/953127542050795520 This is the screen that set off the ballistic missile alert on Saturday] see also [https://news.ycombinator.com/item?id=16157798] | |
| − | + | *[https://medium.com/tragic-design/how-bad-ux-killed-jenny-ef915419879e How Bad UX Killed Jenny] | |
| + | *[http://www.asktog.com/columns/027InterfacesThatKill.html When Interfaces Kill: What Really Happened to John Denver] | ||
| + | *[https://blog.codinghorror.com/the-opposite-of-fitts-law/ The Opposite of Fitts' Law] | ||
| + | *[http://epmonthly.com/article/not-heroes-wear-capes-one-las-vegas-ed-saved-hundreds-lives-worst-mass-shooting-u-s-history/ How One Las Vegas ED Saved Hundreds of Lives After the Worst Mass Shooting in U.S. History] | ||
| + | *[https://en.wikipedia.org/wiki/Therac-25 Therac-25 software failure that killed people] | ||
| + | *[http://www.cse.psu.edu/~gxt29/bug/softwarebug.html A list of software failures] | ||
| − | [http:// | + | [http://www.ganssle.com/tem/tem345.html#article2 A Fire Code for Software?] There isn't a fire code for software yet, but there will be eventually. |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ==Estimation== | |
| − | + | [http://thecontentwrangler.com/2017/09/15/how-to-estimate-the-impact-of-business-decisions-on-content-teams/# How To Estimate The Impact of Business Decisions] | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ==UX Mapping Methods== | |
| − | + | There are four kinds of [https://www.nngroup.com/articles/ux-mapping-cheat-sheet/?utm_source=Alertbox&utm_campaign=96e9850de9-UX_Mapping_Brutalism_Antidesign_2017_11_06&utm_medium=email&utm_term=0_7f29a2b335-96e9850de9-40376129 User Experience mapping techniques]: | |
| − | * | + | |
| − | * | + | * [https://www.nngroup.com/articles/empathy-mapping/ Empathy mapping] |
| − | * | + | * Customer journey mapping |
| − | * | + | * Experience mapping |
| + | * Service blueprinting | ||
| + | |||
| + | ==Journey Maps== | ||
| + | The [[Journey Maps]] process helps us clarify who wants the feature, what they are trying to do, why they are trying to do it. | ||
| + | |||
| + | ==Design== | ||
| + | |||
| + | [https://www.nngroup.com/articles/first-impressions-human-automaticity/ First Impressions Matter: How Designers Can Support Humans’ Automatic Cognitive Processing ] | ||
| − | + | [https://developers.google.com/web/tools/chrome-user-experience-report/ Chrome User Experience Report] A useful resource for user experience in the real world. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | [https://accessibility.blog.gov.uk/2016/09/02/dos-and-donts-on-designing-for-accessibility/ Dos and don'ts on designing for accessibility] 6 posters to make designing for accessibility easy. | |
| − | + | ||
| − | + | [http://www.ganssle.com/tem/tem345.html#article2 A Fire Code for Software?] Is it safe? | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ==Checklists== | |
| − | + | Much of what we do is complex, done rarely or both. Something that helps is a checklist Some people are taking a long time to learn how powerful they are. | |
| − | * | + | *[https://www.newyorker.com/magazine/2007/12/10/the-checklist The Checklist (New Yorker 2007)] |
| − | + | *[http://toyotadriverseat.com/community/tssc-childrens-hospitals.htm TPS for the Children 2017] | |
| − | * | + | Notice these are both dealing with the exact same problem a decade apart. Let's try to do better. |
| − | + | ||
| − | + | ==Writing Requirements== | |
| − | * | + | From [http://www.ganssle.com/tem/tem343.html The Embedded Muse 343] |
| − | * | + | Writing good requirements is vital, and should include the following characteristics: |
| − | * | + | *Atomic: it describes just one thing. |
| − | * | + | *Complete: it has everything you need to implement the requirement. |
| − | * | + | *Concise: It should be simple and clear to anyone reading it, what is to be accomplished. |
| + | *Consistent: Use the same terminology throughout the specification. | ||
| + | *Correct: It should be appropriate to the system not just a cut&paste from somewhere else. | ||
| + | *Implementation free: Define what should be done, not how. | ||
| + | *Necessary: Why is it important? | ||
| + | *Traceable: How will it be tracked so development, QA and support will know where the feature came from. | ||
| + | *Unambiguous: Is it clear enough that there is only one way it can be interpreted (this is very hard). | ||
| + | *Verifiable: What does success look like? | ||
| + | *Viable: Will it actually improve the system? | ||
Latest revision as of 17:28, 19 March 2018
The User Experience (UX) is more than just what it looks like but how it works.
We handle large amounts of customer data and losing the data can have severe business consequences for them and for us.
Contents |
[edit] Examples
If you think UX isn't important:
- This is the screen that set off the ballistic missile alert on Saturday see also [1]
- How Bad UX Killed Jenny
- When Interfaces Kill: What Really Happened to John Denver
- The Opposite of Fitts' Law
- How One Las Vegas ED Saved Hundreds of Lives After the Worst Mass Shooting in U.S. History
- Therac-25 software failure that killed people
- A list of software failures
A Fire Code for Software? There isn't a fire code for software yet, but there will be eventually.
[edit] Estimation
How To Estimate The Impact of Business Decisions
[edit] UX Mapping Methods
There are four kinds of User Experience mapping techniques:
- Empathy mapping
- Customer journey mapping
- Experience mapping
- Service blueprinting
[edit] Journey Maps
The Journey Maps process helps us clarify who wants the feature, what they are trying to do, why they are trying to do it.
[edit] Design
First Impressions Matter: How Designers Can Support Humans’ Automatic Cognitive Processing
Chrome User Experience Report A useful resource for user experience in the real world.
Dos and don'ts on designing for accessibility 6 posters to make designing for accessibility easy.
A Fire Code for Software? Is it safe?
[edit] Checklists
Much of what we do is complex, done rarely or both. Something that helps is a checklist Some people are taking a long time to learn how powerful they are.
Notice these are both dealing with the exact same problem a decade apart. Let's try to do better.
[edit] Writing Requirements
From The Embedded Muse 343 Writing good requirements is vital, and should include the following characteristics:
- Atomic: it describes just one thing.
- Complete: it has everything you need to implement the requirement.
- Concise: It should be simple and clear to anyone reading it, what is to be accomplished.
- Consistent: Use the same terminology throughout the specification.
- Correct: It should be appropriate to the system not just a cut&paste from somewhere else.
- Implementation free: Define what should be done, not how.
- Necessary: Why is it important?
- Traceable: How will it be tracked so development, QA and support will know where the feature came from.
- Unambiguous: Is it clear enough that there is only one way it can be interpreted (this is very hard).
- Verifiable: What does success look like?
- Viable: Will it actually improve the system?
