DesignWIKI

Fil Salustri's Design Site

Site Tools


design:usage_scenario

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
design:usage_scenario [2021.11.10 11:07]
Fil Salustri
design:usage_scenario [2021.11.10 11:10]
Fil Salustri [Usage scenario generation process]
Line 127: Line 127:
     * Each team member develops a US diagram (with annotations are required) for their own Persona and SUC.      * Each team member develops a US diagram (with annotations are required) for their own Persona and SUC. 
     * This is best done with paper and pencil in your [[design journal]] so that you can "play around" with it to make sure you have all the necessary steps.     * This is best done with paper and pencil in your [[design journal]] so that you can "play around" with it to make sure you have all the necessary steps.
-  - **Review the US sketches in a team meeting**+  - **Review and Integrate the US sketches in a team meeting**
     * 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://www.diagrams.net/, generate an "online" version of each US. +    * Using an app like https://www.diagrams.net/, generate an "online" version of the US. 
-    * Make sure all the USs have a consistent appearance and structure to make them easier to understand to "outsiders".+    * 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/error.+      * Remember that the goal is to demonstrate you can make good decisions about product failures, //not// include every conceivable failure/error.
       * Examples of product failures: an elevator's motor burning out during operation; a wine glass becoming permanently stained from holding red wine.       * Examples of product failures: an elevator's motor burning out during operation; a wine glass becoming permanently stained from holding red wine.
       * 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 US diagram one last time to ensure accuracy, brevity, and completeness.+    * Every team member should review the US diagram individually one last time to ensure accuracy, brevity, and completeness.
  
 <WRAP tip> <WRAP tip>
design/usage_scenario.txt · Last modified: 2021.11.10 11:10 by Fil Salustri