Interaction Design Prototype
10 weeks · 0 milestones
High-fidelity interactive prototype addressing a problem identified through real user research. Triad: concept/ideation artifact (design rationale document: how each key interaction decision — navigation structure, primary actions, information hierarchy, affordances — traces back to a specific research finding or insight; this is a research-grounded design argument, not a visual style rationale), technical execution artifact (high-fidelity interactive prototype — minimum 10 linked screens or states demonstrating the core user journey — with documented minimum 3 iteration rounds), documentation/critique artifact (iteration record: for each round, what the starting state was, what usability test finding or design critique prompted the change, and what changed — with before/after screenshots or Figma version history). Proof Accessibility Rule applies: Figma (free tier), Penpot (open source and free), and Adobe XD (free starter plan) are all valid free-tier prototyping tools. Studio critique: UX practitioner with design research experience reviews interaction design decisions and challenges the research-to-design traceability — 'this looks good' is not a valid critique response for a UX MSc standard. Proof: design rationale document, prototype link, iteration documentation, critique notes. Verifier: UX practitioner (minimum 3 years), product designer with UX research background, or design research academic.
Milestone map
Milestone map
3 milestones
Select a specific interaction problem from your research or a real product context — a task flow failing for users, an unclear interface state, or a new feature requiring interaction design from scratch. Produce a design brief (minimum 400 words) covering: the interaction problem, the specific users affected, testable success criteria, and technical or business constraints.
Proof required
Submit your interaction design brief (minimum 400 words) with problem statement, user description, success criteria, and constraints.
What gets checked
- Problem is specific enough to scope the design work — not 'improve the homepage'
- Success criteria are testable — not 'users will feel better about it'
- Brief describes an interaction problem, not a visual design problem