Designing for the People Who Use It
Use measured body data and user research to choose product sizes, reach distances and control requirements. Consider people with limited sight, hearing or movement, and test whether the design works for its intended users.
What a learner can do afterwards
- Explain why one average body measurement does not show the range of users or prove that a product will fit them
- Name two body measurements that inform product dimensions, such as hand breadth for handle length or seated lower-leg length for seat height
- Redesign one feature of a product so it works one-handed or without sight
- Explain how observing a task and asking users about it can provide complementary evidence, including actions they did not mention
1 · Read
Your brief names the people and tasks a product is for. One average body measurement does not show the range of those users. A product may fit people on either side of the average if it allows enough space or adjustment. Use measured ranges and fit tests to choose one size, several sizes or adjustment.
Hand breadth helps set handle length. Seated lower-leg length helps choose a seat height that supports the feet. Reach helps position controls. Body measurements inform product dimensions; they are not automatically the final dimensions. Clothing, movement, clearance and the task also matter.
Match signals to the person and task. Someone may miss a sound-only alert. A changing light or suitable vibration can provide another channel. A raised symbol identifies a control by touch; it does not announce completion. Several channels can help more users, but cannot guarantee access for everyone.
One-handed use needs reachable controls that one hand can operate. Limited hand strength may call for low-force controls and a stable product. For a ticket-machine user with limited strength and sight, try reachable low-force controls, tactile markings and audio guidance. Keep readable visual information too. Test the whole task with the intended user; button size alone does not establish access.
Ask users about their needs and, with their agreement, observe the task. Grip changes or workarounds may not appear in an interview. Ask what those actions mean before deciding they show a problem. Record both reported experience and observed actions in the brief, then test proposed changes.
Use body data to choose sizes and controls. Match access features to the task. Ask users, observe with their agreement and test the design.
Original lesson, questions and flashcards written for this dataset about body measurements, accessible controls and user research.
Original reading written for this dataset about identifying controls and making event signals usable for intended users.
More to read
Separate finding a control from noticing an event
Ask the intended user which information channels they can use and what they prefer. People with limited sight or hearing do not all have the same needs.
A raised mark can help identify a control by touch. It stays in place, so it cannot announce that a task has just finished. An event needs a changing signal. A vibration may help when a person can detect it while holding or using the device; a light may help when the person can see it.
With the user's agreement, test a safe prototype during the task. Can they find the control, operate it and understand the result? Ask about their experience as well as observing their actions. Record preferences and test results before choosing changes.
2 · Watch
به انگلیسیTake it off screen
Where it sits
Learn first
Optional connections
This opens up
Where this leads
Jobs that lean on this skill. Follow one to see everything it is built on.
8 questions wait behind this lesson, each with its answer explained. Every answer feeds the sky: stars light as they are learned, and dim when it is time to come back.