User Tools
Site Tools
design:usage_scenario
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
design:usage_scenario [2021.11.10 11:07] Fil Salustri [Usage scenario generation process] |
design:usage_scenario [2021.11.10 11:10] Fil Salustri [Usage scenario generation process] |
||
|---|---|---|---|
| Line 130: | Line 130: | ||
| * In a team meeting, merge all the US diagrams into a single, generic baseline diagram that represents how the product you're designing would be used by a generic user. Think of this US as a //visual instruction manual// that you might ship with your product. | * In a team meeting, merge all the US diagrams into a single, generic baseline diagram that represents how the product you're designing would be used by a generic user. Think of this US as a //visual instruction manual// that you might ship with your product. | ||
| - **Develop a full diagram** | - **Develop a full diagram** | ||
| - | * Using an app like https:// | + | * Using an app like https:// |
| - | * Make sure all the USs have a consistent appearance and structure to make them easier to understand to " | + | * Make sure the US has a consistent appearance and structure to make them easier to understand to people outside your team. |
| - **Add annotations and descriptive text** | - **Add annotations and descriptive text** | ||
| * Make sure the actions are clear enough that a reader unacquainted with your project can still make sense of it. | * Make sure the actions are clear enough that a reader unacquainted with your project can still make sense of it. | ||
| Line 137: | Line 137: | ||
| - **Add interaction errors and product failures** | - **Add interaction errors and product failures** | ||
| * The number of failures and errors you add will depend on the size and complexity of the diagram. | * The number of failures and errors you add will depend on the size and complexity of the diagram. | ||
| - | * Remember that the goal is to demonstrate you can make good decisions about product failures, not include every conceivable failure/ | + | * Remember that the goal is to demonstrate you can make good decisions about product failures, |
| * Examples of product failures: an elevator' | * Examples of product failures: an elevator' | ||
| * Examples of interaction errors: a user being unable to tell if they have successfully instructed an elevator car what floor to go to; a wine glass slipping out of a user's hand. | * Examples of interaction errors: a user being unable to tell if they have successfully instructed an elevator car what floor to go to; a wine glass slipping out of a user's hand. | ||
| * Focus on the failures and errors that will most seriously affect the performance of your concept. | * Focus on the failures and errors that will most seriously affect the performance of your concept. | ||
| - **Final review by the team** | - **Final review by the team** | ||
| - | * Every team member should review | + | * Every team member should review |
| <WRAP tip> | <WRAP tip> | ||
design/usage_scenario.txt · Last modified: 2021.11.10 11:10 by Fil Salustri
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
