
run a user test of our trail guide with visitors, collect data against the criteria and constraints, and decide on one final fix.
Phase 5: Prove It
Do Now. Your visitors today have never seen your guide. What is one thing you must NOT do while they use it, so the test is fair?
During a user test, what should the design team do?
Trail designers, today the guide faces real users. Our “visitors” are students from another class, staff or family members who have not seen the guide. They walk through your stops while you collect data.
What we measure. 1. Time: seconds spent at each stop. 2. Understanding: after each stop, the visitor answers one question, such as “What made these layers?” 3. Accessibility: could they read or hear it easily? 4. Impact: did anyone step off the path, drop litter or crowd a spot? Each measure matches a criterion or constraint.
Worked example 1: reading the data. Sample data from Jamal’s team: Stop 1 averaged 150 seconds and 5 of 6 visitors answered correctly. Stop 2 averaged 240 seconds and only 2 of 6 were correct. Stop 2 is too slow AND unclear. That is the failure point.
Worked example 2: one fix, then retest. The team cut Stop 2 to one map and two sentences, with the full story in the audio. They retested with two new visitors, who each took about 150 seconds and answered correctly. Small sample, but a clear improvement. These are sample numbers.
Watch for effects on the park. A stop that makes people crowd a narrow ledge could trample plants. That counts as a failed constraint even if visitors learn a lot.
Record one row per visitor per stop.
| Visitor | Stop | Time (s) | Answered correctly? (Y/N) | Easy to read or hear? (1–3) | Any impact on the space? |
|---|---|---|---|---|---|
| 1 | 1 | ||||
| 1 | 2 | ||||
| 1 | 3 | ||||
| 2 | 1 | ||||
| 2 | 2 | ||||
| 2 | 3 |
Plan and justify the final fix.
Describe your one final fix. Use your test data to explain why it should help, and how it affects visitors, park staff and the park itself.
Data collected, fix chosen. Next lesson is Opening Day: you present the guide to the park’s education staff.
Exit ticket: what surprised you most about how visitors used your guide?
How confident are you that you can I can test a design against its criteria and constraints and use the data to improve it.
Materials: finished prototypes, stopwatches or phone timers, data sheets, one question card per stop, 4–6 visitors from another class or staff.
Setup: arrange stops along a hallway “trail” if you can. Each visitor sees two or three teams’ guides. Leave 12 minutes at the end for a quick fix and retest.
Listen for: teams coaching visitors; ignoring data that looks bad; changing many things at once.
Support / stretch: give a pre-labeled data sheet. Stretch: make a bar graph of average time per stop with a line at 180 seconds.