design_for_people_-_john_d_lee
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| design_for_people_-_john_d_lee [2025/08/15 23:05] – admin | design_for_people_-_john_d_lee [2025/08/15 23:22] (current) – admin | ||
|---|---|---|---|
| Line 84: | Line 84: | ||
| Heuristic Evaluation is done internally, with 3 individuals inspect the design and identify if there is anything violating design principles, safety requirement, | Heuristic Evaluation is done internally, with 3 individuals inspect the design and identify if there is anything violating design principles, safety requirement, | ||
| - | 10 Design principles | + | #### Check with 10 Design principles |
| - | 1. Create useful innovation: Address a need, solve a problem | + | Use design principles to give quick input on whether the design are consistent with human capabilities. |
| - | 2. Attend to details: Small changes to the design can have a big effect on people. | + | |
| - | 3. Simplify: Remove irrelevant information, | + | |
| - | 4. Honest and understandable: | + | - Attend to details: Small changes to the design can have a big effect on people. |
| - | 5. Provide flexibility: | + | - Simplify: Remove irrelevant information, |
| - | 6. Consistency: | + | - Honest and understandable: |
| - | 7. Anticipate needs: Provide options rather than require people to recall them. Choose **thoughtful defaults** because people often adopt initial settings | + | - Provide flexibility: |
| - | 8. Minimize memory demands: Interactions with technology should not disrupt the flow of activities unless | + | - Consistency: |
| - | necessary | + | - Anticipate needs: Provide options rather than require people to recall them. Choose **thoughtful defaults** because people often adopt initial settings |
| - | 9. Consider adaptation: Adopt a systems perspective to identify otherwise unanticipated outcomes, particularly as people adapt to the changes in the system | + | - Minimize memory demands: Interactions with technology should not disrupt the flow of activities unless necessary |
| - | 10. Fit the task to the person rather than the person to the task | + | - Consider adaptation: Adopt a systems perspective to identify otherwise unanticipated outcomes, particularly as people adapt to the changes in the system |
| + | - Fit the task to the person rather than the person to the task | ||
| + | |||
| + | #### Check design patterns | ||
| + | |||
| + | Use conventional design pattern if possible. | ||
| + | [[https:// | ||
| + | |||
| + | |||
| + | #### Conduct cognitive walkthrough | ||
| - | Then you can do cognitive walkthrough as well: | ||
| * Is it likely that the person will perform the right action? | * Is it likely that the person will perform the right action? | ||
| * Does the person understand what task needs to be performed? | * Does the person understand what task needs to be performed? | ||
design_for_people_-_john_d_lee.1755270308.txt.gz · Last modified: (external edit)
