Start with one ordinary task that is harder than it needs to be. Observe the difficulty, make a modest model and see whether another person can use it. A clear record of the test is more useful than a polished object whose purpose remains uncertain.
Evidence checked October 17, 2026 (America/Denver). Version 1.0. Original-source desk review; no practical testing.
What this guide helps you do
A learning route for low-consequence objects, labels and arrangements. A mock-up does not establish structural performance, product safety or accessibility-code compliance. Use the appropriate qualified review before changing a building, support, powered device or other consequential system.
Describe a task someone actually does
Choose a task such as finding a supply, recognizing a label or putting small items away. Ask the person to describe the present difficulty, then watch with permission. Write down what happened rather than assuming what they felt or why they hesitated. A short description should identify the person, setting, task and obstacle without prescribing a new object yet. Source: Design Council Framework for Innovation.
Turn the observation into a brief
State the improvement in terms you can check: a visitor can identify the right compartment, or the user can return an item without moving several others. Record constraints such as available space, cleaning, cost and materials. Keep a second option and the current arrangement in view so that making something new does not become the only possible answer.
Ask who might be left out
Invite perspectives beyond your own habits. Consider whether information can be recognized, instructions understood, controls reached and effort kept reasonable. NC State’s 1997 principles provide useful questions, while the page also says its center is inactive. Use the reference to broaden a trial; it does not certify that a design works for everyone. Source: NC State Principles of Universal Design.
Make a model that answers one question
A paper label, cardboard divider or rearranged set of loose objects may be enough for a first trial. Explain what the model represents and what it cannot demonstrate. MIT D-Lab’s account of participatory design is a reminder to choose how people take part and to allow for the time or support that participation requires. Source: MIT D-Lab participatory-design approach.
Observe use without supplying the answer
Give the person the task, then let them try it before explaining your intentions. Note where they pause, misread, reach elsewhere or ask for help. Ask what they expected and what they would change. Record the model version, conditions and a concrete result. A single successful trial is a useful observation with limited scope.
Revise and preserve the reason
Change one important feature and repeat the same task when practical. Keep the earlier sketch and result so the reason for the change remains visible. Decide whether to keep, adapt or stop the idea. The Design Council presents iteration as part of design; returning to the problem statement can be a productive result of a test. Source: Design Council Framework for Innovation.
A record you can use
| Record | What to write down |
|---|---|
| Task and setting | Who is trying to do what, where and under what conditions? |
| Observed difficulty | What happened? Separate the observation from your interpretation. |
| Success and limits | One checkable improvement; space, effort, cost and material constraints. |
| Model version | Sketch, dimensions or label text; what this model can and cannot show. |
| Trial result | Task given, person’s actions, help needed and their own comments. |
| Next version | Keep, change or stop; reason and the next question. |
Learning route
- Observe: Record one task and its difficulty.
- Frame: Choose a checkable improvement.
- Try: Make a modest model and watch use.
- Revise: Keep the evidence for the change.
Checklist
- The brief names the task and user before naming a product.
- Observations and assumptions are recorded separately.
- The current arrangement and another option were considered.
- Different users can comment without being asked to approve the design.
- The prototype’s limits are clear.
- The next change has an observed reason.
Resources and their limitations
Design Council Framework for Innovation
Design Council Framework for Innovation — Design Council
Use. Use the framework to separate understanding the problem, choosing a challenge, exploring options and testing a small version. Return to earlier questions when observation changes the brief.
Access and cost. Public webpage freely readable; tools, materials, courses, travel and services may cost extra.
Review and limits. A general design framework from a UK design charity, not a product certification or guarantee of a successful result. Only the webpage was reviewed; no workshop attended and no third-party diagram reproduced.
NC State Principles of Universal Design
NC State Principles of Universal Design — NC State University College of Design
Use. Use the seven principles as questions during observation and a modest usability trial. Include people whose needs differ from the designer’s.
Access and cost. Public webpage freely readable; tools, materials, courses, travel and services may cost extra.
Review and limits. The page identifies Version 2.0 dated April 1, 1997 and says the Center is inactive. This is a reference, not a currently available assistance service, accessibility-code checklist or compliance determination. No poster or detailed building design reviewed.
MIT D-Lab participatory-design approach
MIT D-Lab participatory-design approach — MIT D-Lab
Use. Read the distinction between designing for, with and by people. Ask whether a participatory approach fits the decision and what time or participation costs it entails.
Access and cost. About page freely readable. MIT courses, fieldwork and partnerships have separate eligibility and costs; no place or service booked.
Review and limits. An institutional account of its own approach, not independent proof of project outcomes or a universal low-cost recipe. Classes and partnerships have separate access conditions. The embedded video was not played.
Historical starting point
The Spring 1969 review of Introduction to Engineering Design lists problem definition, alternatives, representation and checking among design-learning topics. This guide carries those questions into an ordinary usability trial. The historical water-system example, costs and technical drawings are not current instructions. Locator: Whole Earth Catalog — Spring 1969, PDF page 42, printed page 40.
Related guides
- Community arts and creative practice — browse the Public Library
- Prototyping and invention — browse the Public Library
- Diagnosis and repair decisions
Last substantive desk review: October 17, 2026. Sources retain their own dates and geographic limits. Local services and individual products require a fresh check at the time of use. For a correction, retain the page title, source and passage in question.
