Interaction Design
Interaction design shapes how people act with a product over time, connecting goals, controls, feedback, system state, and recovery into a coherent experience.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/interaction-design/
01What it means
Interaction design defines interface behavior: what people can do, how a product responds, how state changes become visible, and how a task unfolds across moments. It covers flows and controls, plus timing, feedback, constraints, accessibility, and expectations created by familiar patterns.[1][2]
- 01User goalDesired progress in a specific context
- 02Perceived optionsObjects, controls, signifiers, and constraints
- 03User actionInput through an available interaction method
- 04System responseState change, processing, or refusal
- 05FeedbackWhat happened, current status, and next possibilities
- 06Recovery or continuationUndo, correct, retry, or advance
The new state changes what the person perceives and does next
Interaction design extends beyond screen layout to timing, input methods, system rules, accessibility, errors, and how behavior remains understandable over time.
02Why it matters
Good interaction design reduces uncertainty between intention and result. People can predict what a control will do, recognize whether the system received an action, and recover without losing work. This improves completion, trust, accessibility, and perceived performance even when the service is unchanged.
03When to use it
Use interaction design whenever a product asks someone to choose, enter information, manipulate content, move between states, or wait. Give extra attention to frequent tasks, irreversible actions, unfamiliar workflows, and interactions that cross devices or network boundaries.
04How it works
- Start with the user goal and describe the smallest successful task from entry to completion.
- Map actions, states, transitions, feedback, constraints, and exits—not just screens.
- Choose controls whose appearance suggests behavior, then provide immediate, perceivable feedback.
- Prototype keyboard use, screen-reader announcements, latency, empty data, and failure.
- Test whether people can predict outcomes, notice changes, and recover; refine the model rather than decorating confusion.
05A practical example
A team designing shared-document invitations maps sending, acceptance, editing, conflict, and revocation. The button confirms recipient and permission before sending, announces success without moving focus, and leaves a visible access record where the owner can later change or revoke permission.
06Where it breaks
Interaction design cannot compensate for unclear policy, unreliable services, or missing research. Familiar patterns vary by platform and audience, and a delightful transition can still exclude people if it traps focus, depends on gesture alone, or ignores reduced-motion preferences.
Common mistakes
- Designing isolated screens without defining transitions and state
- Using animation as feedback while omitting text or semantic status
- Assuming a familiar icon means the same thing to every audience
07Sources
- Human Interface GuidelinesApple · Institutional guidelineHuman Interface Guidelines
- 10 Usability Heuristics for User Interface DesignNielsen Norman Group · Professional guideline10 Usability Heuristics for User Interface Design