design_for_people_-_john_d_lee
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
design_for_people_-_john_d_lee [2025/07/12 15:13] admin |
design_for_people_-_john_d_lee [2025/08/15 23:22] (current) admin |
||
|---|---|---|---|
| Line 10: | Line 10: | ||
| - | ## Process of Human Factors Engineering (Human Centered Design) | + | ## 3 Phases of Human Factors Engineering (Human Centered Design) |
| Iterative on three major phases: understand users, create a prototype, and evaluate the prototype. | Iterative on three major phases: understand users, create a prototype, and evaluate the prototype. | ||
| Line 20: | Line 20: | ||
| - | ## Understand | + | ## Phase 1. Understand |
| ### Task Analysis | ### Task Analysis | ||
| - | Task analysis is a broad term that encompasses many other techniques such as use cases, user stories, and user journeys. All of these techniques focus on understanding | + | The goal of task analysis is to understand: |
| - | * Why - users’ goals and motivations | + | * **Why** - users’ goals and motivations |
| - | * What - the tasks and subtasks to achieve these goals | + | * **What** - the tasks and subtasks to achieve these goals (Workload, mental & physical demands, multitasking, human error.) |
| - | * When - the ordering and timing of these tasks | + | * **When** - the ordering and timing of these tasks (functions performed by human or by machines) |
| - | * Where - and the location and situation | + | * **Where** - and the location and situation (Environment and context, eg. cold outdoors, wheelchair accessible, potential hazards) |
| + | Task analysis is a broad term that encompasses many other techniques such as use cases, user stories, personae and scenarios. | ||
| - | ## Create | + | ### Personae and Scenarios (user journeys) |
| + | |||
| + | Personae are helpful for building the right scope of design target. One the one hand it prevents the natural tendency of the design team to assume users are like themselves (scope too narrow). One the other hand it is also helpful for avoiding an “elastic user” whose characteristics shift as various features are developed. Designing for an elastic user may create a product that fails to satisfy any real user. (scope too broad) | ||
| + | |||
| + | Scenarios (user journeys) also help define what's most important for user. When creating a scenario, tasks are examined, and only those that directly serve users’ goals are retained. Two types of scenarios are most important --- daily use scenarios and necessary use scenarios. eg. Entering the car, entering the car during a snowstorm. | ||
| + | |||
| + | Personae and scenarios analysis is an early stage version of task analysis. It gives us confidence that the conceptual design can meet target users' needs before going into detail. | ||
| + | |||
| + | ### Use cases | ||
| + | Use cases analysis is more detailed. It can be described in a more formal way in a flow diagram, helping move from conceptual design to a software or hardware prototype. | ||
| + | |||
| + | |||
| + | ### Further readings | ||
| + | |||
| + | [[https://dschool.stanford.edu/tools/the-gift-giving-project|Standord wallet exercise]] This exercise provides a brief exposure to design thinking. The goal is to practice designing and recognizing a user’s need and then translating that need into a prototype product that is then evaluated | ||
| + | |||
| + | |||
| + | |||
| + | ## Phase 2. Create | ||
| ### Task design | ### Task design | ||
| - | Change what operators do than on change the devices they use. A workstation for an assembly line worker might be redesigned to eliminate manual lifting. Or a robot might be designed to lift the component. | + | Change what operators do than change the devices they use. A workstation for an assembly line worker might be redesigned to eliminate manual lifting. Or a robot might be designed to lift the component. |
| ### Equipment design | ### Equipment design | ||
| Line 43: | Line 62: | ||
| Changes the physical environment where the tasks are carried out. This can include improved lighting, temperature control, and reduced noise. | Changes the physical environment where the tasks are carried out. This can include improved lighting, temperature control, and reduced noise. | ||
| - | Designs of task, equipment and environment are usually considered together as the picture below. Cognition consideration are where we derives theories, principles and guidelines. | + | Designs of task, equipment and environment are usually considered together as the picture below. Cognition consideration are where we derives theories, principles and guidelines. Commonly seen cognition considerations are: [[time_delay|Response Time & Delay]] |
| {{::design_of_task_equipment_and_environment.png?360|}} | {{::design_of_task_equipment_and_environment.png?360|}} | ||
| Line 59: | Line 78: | ||
| - | ## Evaluate | + | ## Phase 3. Evaluate |
| ### Heuristic evaluation | ### Heuristic evaluation | ||
| - | Heuristic Evaluation is done internally, with 3 individuals inspect the design and identify if there is anything violating design principles, safety requirement, etc. | + | Heuristic Evaluation is done internally, with 3 individuals inspect the design and identify if there is anything violating design principles, safety requirement, etc. |
| + | |||
| + | #### Check with 10 Design principles | ||
| + | Use design principles to give quick input on whether the design are consistent with human capabilities. | ||
| + | |||
| + | - Create useful innovation: Address a need, solve a problem | ||
| + | - Attend to details: Small changes to the design can have a big effect on people. | ||
| + | - Simplify: Remove irrelevant information, but do not mask essential indicators and feedback | ||
| + | - Honest and understandable: Functions should be reflected in forms that make their states visible, changes predictable, and interactions intuitive | ||
| + | - Provide flexibility: People should be able to **adjust, navigate, undo and redo, adopt shortcuts** | ||
| + | - Consistency: The same label or action should mean the same thing in different situations — don’t deviate from well-defined conventions | ||
| + | - Anticipate needs: Provide options rather than require people to recall them. Choose **thoughtful defaults** because people often adopt initial settings | ||
| + | - Minimize memory demands: Interactions with technology should not disrupt the flow of activities unless necessary | ||
| + | - 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://ui-patterns.com/patterns|UI Design Patterns]] | ||
| + | |||
| + | |||
| + | #### 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.1752304410.txt.gz · Last modified: 2025/07/12 15:13 by admin