Week 17 Guide: High-Fidelity Prototyping
24-week programme, Project 2 Phase. Builds on the Week 6 and Week 10 lo-fi prototyping skills.
The Real Problem This Solves
Lo-fi prototypes test whether an idea works in principle. High-fidelity prototypes test whether it works in practice: real materials, real proportions, real interactions. For Project 2, with two users and competing constraints, you need a prototype honest enough that both stakeholders can genuinely try it.
Key Ideas You Need First
1. Raise fidelity where it changes the test
You do not need everything finished. Raise fidelity only on the parts a user will judge or interact with. Fake the rest.
2. Use closer materials and true proportions
Swap paper for the real material where the feel matters. Build at true size so proportions are honest.
3. Prototype for two stakeholders
Make it usable by both of your Project 2 users, so the reset or switch between them can be tested for real.
Step-By-Step Walkthrough
- Decide what must be high fidelity for an honest test, and what can stay rough.
- Build with closer materials at true size. Focus effort on the interaction both users touch.
- Make it work for both stakeholders, including the switch or reset between them.
- Try it yourself first, then note what it is built to test.
- Document it well for testing next week and for your portfolio.
Demonstrated Example
Concept: the split roll-up mat for two desk-sharers.
High fidelity where it counts: real felt, true desk width, a working stiff centre line and two elastic fastenings, so both users can do a real partial reset. Low fidelity elsewhere: pocket labels are handwritten, colour not final.
Built to test: can each user reset their half in under a minute without disturbing the other, and do tools stay put.
Why this is strong: fidelity is raised exactly where the test needs it, at true size, and usable by both stakeholders.
Submission Checklist
| Upload item | Pass standard |
|---|---|
| High-fidelity prototype | Closer materials and true proportions on the parts that matter. |
| Built-to-test note | Names what a user will judge, for both stakeholders. |
Assessment And Pass Criteria
- Fidelity is raised where it changes the test, not everywhere.
- The prototype is usable by both stakeholders.
- It is documented clearly for testing.
Common Mistakes
- Polishing everything. Raise fidelity only where it matters.
- Wrong scale. Build at true size so proportions are honest.
- Only one user can use it. Project 2 needs both to test the switch.
Extension Challenge
Prototype the single riskiest interaction twice with different materials and compare how each feels in use.