What Is Interaction Design?
Learn how interaction design shapes actions, responses, states, paths, feedback, recovery, and accessibility across a product or service.

Interaction design is the practice of shaping how a person acts with a product or service and how that product responds.
It covers actions, controls, states, feedback, timing, movement, errors, recovery, and paths across screens and channels. The goal is a clear, useful interaction, not motion for its own sake.
Put It in Plain Words
A person may act with a key, tap, click, swipe, field, or voice.
The site or app should make each act clear.
It should reply soon, so the person knows the act was seen.
A new state should be clear on screen and to tools that read the page out loud.
If work takes time, the page may need a wait sign or a short note.
If an act fails, the person needs a cause they can use and a way back.
A key that cannot be used should not be the sole clue that one more step is due.
Keys, touch, a mouse, speech, and screen tools may each need a test.
Motion can show a shift, but it should not be the sole sign.
A path may cross mail, phone, a site, and a step done by staff.
The plan should cover those joins, not stop at one screen.
Shared rules help the same acts work in the same way.
A new rule needs proof, states, notes, and an owner.
A test model can show how an act may work before the full build.
The built form still needs tests and checks.
Site data can show where an act took place, but it may not show why.
Think of a Save key. It should have one clear name. When it is used, it may need to lock for a short time. A wait sign can show that the work is in hand. A note can then say that the work was saved.
If the save fails, keep the work on the page. Tell the user what went wrong in plain words. Give them a safe way to try once more. Do not send them back to a blank form.
Think of a menu. A key can open it. The next key can move through it. The escape key can close it. Focus should go to a place that makes sense. The same path should work with no mouse.
Think of a file that is too large. Say so near the file field. State the size that can be used. Keep the rest of the form. Put the focus on the fault so it is easy to find.
A state is a point in time. A field can be blank, in use, wrong, right, or locked. A job can be new, in hand, done, or failed. Name each state before the team draws the screen.
A rule says what the site should do. If the cart is bare, the Pay key should not just fade out. The page should say what must be put in the cart and give a way to do it.
A path should have a way in and a way out. A person may need to stop, go back, save, or ask for help. Those acts are part of the work, not odd cases that can wait.
Use real words and real data in the test. A long name, a slow link, or a failed card can change the full path. Blank gray boxes hide these needs.
Test the work on a small screen and with zoom. A row may turn to a stack. A note may push a key down. The order should still match the task.
Ask a person to do the task with no hint. Watch for false starts and long stops. Ask what they thought the next act would do. Then fix the rule, words, or cue that led them off track.
The work is not done when the frames look neat. It is done when the built path acts as planned, the key states are clear, and the team has checked the main risks.
A Quick Check Before You Use It
Name the user goal, available action, and expected response.
Map default, focus, hover, active, loading, success, and error states.
Provide clear feedback and a safe recovery path.
Test input modes, assistive technology, motion, and timing.
Verify the built interaction with real users and real content.
How Does Interaction Design Work?
Start with a user need and the context in which the action happens. Map the path, controls, rules, states, feedback, delays, errors, and exits. Reuse a tested pattern where it fits.
Prototype the risky parts, then test comprehension and task completion. Designers and developers should review the implemented behavior together because a static frame cannot show the full interaction.
Why Is It Important?
Interaction design connects what a person intends with what a system does. Clear responses and recovery can reduce uncertainty and prevent harmful or irreversible mistakes.
It also creates consistency across a product. People should not have to learn a new rule each time they save, cancel, submit, search, or go back.
Where Is It Used?
Websites, apps, software, kiosks, and devices.
Forms, checkout, onboarding, search, and account flows.
Menus, dialogs, tables, controls, and notifications.
Voice, chat, gesture, keyboard, and assistive interfaces.
Online and offline service journeys.
A Plain Interaction Design Example
A person presses Save. The control shows a busy state, repeat presses are prevented, the result is confirmed, and a failure keeps the entered work with a clear retry path.
The interaction includes more than the button style. It includes the rule, system response, timing, message, focus, state, and recovery.
What an Interaction Specification Needs
User, goal, context, entry, and exit.
Actions, controls, rules, paths, and dependencies.
States, feedback, timing, motion, and data changes.
Errors, undo, cancellation, recovery, and support.
Access criteria, test evidence, implementation notes, and owner.
How to Design an Interaction
Research the current task, context, barriers, and language.
Map the path and every meaningful state or decision.
Reuse suitable patterns and prototype uncertain behavior.
Test access, comprehension, timing, errors, and recovery.
Review the build and maintain the pattern with evidence.
Interaction Design vs. User Experience Design
Interaction design focuses on actions and responses. User experience design covers the wider experience, including research, structure, content, interface, service, and outcomes.
Interaction design is part of UX, but a polished interaction cannot repair a product that solves the wrong problem or excludes important users.
Common Mistakes
Designing only the default and success states.
Using motion or color as the only sign of change.
Leaving keyboard, touch, speech, or screen-reader behavior until the end.
Treating a static mockup as a complete interaction specification.
Adding a novel pattern when a tested common pattern already fits.
Frequently Asked Questions
Is interaction design the same as UI design?
No. UI design covers the visible interface. Interaction design focuses on how actions, responses, states, feedback, and recovery behave over time.
Does interaction design require coding?
Not always, but technical collaboration is essential. The implemented behavior, platform limits, data, performance, and accessibility all affect the interaction.
Can interaction design be tested?
Yes. Use realistic prototypes or builds to test tasks, comprehension, input modes, feedback, errors, and recovery with relevant users.
Use UX Design Services for the wider practice and How a Design System Works for reusable interaction patterns.
Need a product experience with clear actions, complete states, accessible feedback, safe recovery, and behavior that survives implementation?
Book a free Brand and Tech Assessment to map the current problem, evidence, constraints, and practical next step.
Sources
- GOV.UK Digital Outcomes: Interaction design and user research capabilities. https://www.gov.uk/guidance/digital-outcomes-team-capabilities
- GOV.UK Design System: Components and tested usage guidance. https://design-system.service.gov.uk/components/








