Concept Specification and Low-Fidelity Prototyping
University of Washington
2025-02-03
Learning Goals
Announcements
Ideating from data
Feasibility Analysis
Low-fidelity prototyping
Learning Goals
Announcements
Ideating from data
Feasibility Analysis
Low-fidelity prototyping
understand | create | deliver |
---|---|---|
Develop empathy –> define | ideate | prototype –> test |
understand | create | deliver |
---|---|---|
Develop empathy –> define | ideate | prototype –> test |
[A user] needs [adjective] [need] in order to accomplish [goal]
Example:
Prospective students need up-to-date and trustworthy information about accessibility and student culture to decide on a college.
Example: Multilingual DHH people use captions just like anyone else
Example: Multilingual DHH people need captions in at least two languages to follow a conversation
Example: Multilingual DHH people need to control features of captions so that captions match their expertise and preferencs when watching multilingual content
Write down 1-2 user needs that capture multiple aspects of identity based on your interviews
Does your solution idea
Pick two identity-based design dimensions
Come up with three ways they might interact
Pick one interface design dimension
Think about how that design dimension might interact with that goal or risk
Learning Goals
Announcements
Ideating from data
Feasibility Analysis
Low-fidelity prototyping
Is the idea viable within the constraints of the class
Can be built within 4 weeks
Built –> publically deployed
“What will it cost?”
We have close to $0. Let us know if you need something though and we’ll discuss
“Will it be possible to maintain and support long-term?” (not a requirement)
“How does the team’s availability match the needs?”
For each aspect of feasibility: What will you need? What challenges do you forsee?
Learning Goals
Announcements
Ideating from data
Feasibility Analysis
Low-fidelity prototyping
We will work on this next Monday
Turn design ideas into testable and tangible artifacts for collecting and analyzing the user demands at the early stage.
Be wary of “overdesigning” –> more difficult to critique
Wizard-of-Oz Prototyping
Social Appropriateness
“Will it be allowed and accepted?”