# 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.

- Type: practice
- Domain: Experience & interface
- Level: Foundational
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/interaction-design/>)

## What 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.

## Why 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.

## When 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.

## How it works

1. Start with the user goal and describe the smallest successful task from entry to completion.
2. Map actions, states, transitions, feedback, constraints, and exits—not just screens.
3. Choose controls whose appearance suggests behavior, then provide immediate, perceivable feedback.
4. Prototype keyboard use, screen-reader announcements, latency, empty data, and failure.
5. Test whether people can predict outcomes, notice changes, and recover; refine the model rather than decorating confusion.

## A 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.

## Where 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

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/interaction-design/#visualization-interaction-design>)

## Sources

1. [Human Interface Guidelines](<https://developer.apple.com/design/human-interface-guidelines>) — Apple · Institutional guideline
2. [10 Usability Heuristics for User Interface Design](<https://www.nngroup.com/articles/ten-usability-heuristics/>) — Nielsen Norman Group · Professional guideline

## Related topics

- [Direct Manipulation](<https://wiki.soroush.uk/topic/direct-manipulation/>)
- [Error Prevention](<https://wiki.soroush.uk/topic/error-prevention/>)
- [Motion Design](<https://wiki.soroush.uk/topic/motion-design/>)
