You have likely heard the terms UI and UX thrown around in every pitch deck and product roadmap meeting you have attended. There is a third term that often gets bundled into those acronyms but actually stands on its own as a distinct discipline. That term is Interaction Design, commonly abbreviated as IxD.
Interaction Design is exactly what it sounds like. It is the design of the interaction between users and products. It is the conversation that happens between a human and a machine.
Most founders mistakenly believe that if a product looks good (UI) and solves a general problem (UX), the job is done. However, if the specific mechanics of how a user inputs data and how the system responds are clunky or confusing, the product fails.
IxD is not about static images. It is about movement, reaction, and flow. It is the difference between a button that just sits there and a button that depresses, changes color, and confirms an action when clicked.
The Anatomy of Interaction Design
#To understand IxD, we have to look at it through a more rigid framework than just general design feelings. Academics and practitioners in the field, specifically Gillian Crampton Smith and later Kevin Silver, broke this down into five specific dimensions. Understanding these dimensions helps you move from guessing to engineering a better experience.
The first dimension is Words. Words are the interactions. This includes button labels, menu items, and dialogue boxes. They should be meaningful and simple. In a startup context, vague copy causes friction. If a user has to guess what a button does, the interaction has failed.
The second dimension is Visual Representations. This covers the graphical elements users interact with. It includes typography, icons, and images. These are affordances. They give clues on how the user should interact with the interface. Does that graphic look clickable? If it looks clickable but is not, you have created a broken interaction.
The third dimension is Physical Objects or Space. Through what medium is the user interacting with your product? Are they on a crowded subway using a thumb on a smartphone? Are they sitting in a quiet office using a mouse and keyboard? The physical constraints dictate the design. A complex dashboard that works on a 27 inch monitor will be unusable as a mobile interaction.
The fourth dimension is Time. This is where IxD separates itself from visual design. Time refers to media that changes with time, such as animations, videos, and sounds. It also refers to the amount of time a user spends on the interaction. This dimension helps users understand whether their action was registered. If a user clicks save and nothing happens for three seconds, they will click it again. That is a failure of the fourth dimension.
The fifth dimension is Behavior. This is the culmination of the previous four. It describes the action and reaction. How do users perform actions on the site? How do they operate the product? This includes the emotions and reactions the user has toward the product.
IxD vs. UI and UX
#It is helpful to draw clear lines between these disciplines so you know who to hire or what problems you are actually solving.
User Interface (UI) design is focused on the look. It is the color palette, the font choice, and the layout. It is similar to the paint and trim on a house.
User Experience (UX) design is the broader umbrella. It encompasses the entire journey a user has with your company, from customer support to the product itself. It is the feeling of living in the house.
Interaction Design (IxD) is focused on the moment of contact. It is the mechanism of the doorknob. Does it turn easily? Does it indicate whether you should push or pull? It is the specific mechanics of the actionable parts of the product.
In a startup, you often have one person wearing all three hats. That is acceptable and often necessary. However, that person needs to know when they are switching modes. You can have a beautiful UI that has terrible IxD. This usually results in a product that looks great in screenshots but feels broken when you actually try to use it.
The Role of Feedback Loops
#One of the primary responsibilities of IxD is managing feedback loops. When a user interacts with a system, the system must communicate back.
Think about the physical world. If you drop a pen, you hear it hit the floor and see it roll. You get instant confirmation of gravity and the object’s state.
In the digital world, nothing exists until we design it. If a user fills out a form and hits submit, the screen must change. A spinner must appear. A success message must flash. This is the system acknowledging the user.
Founders often ignore this in the MVP phase. They focus on the database record being created successfully. But if the user does not know the record was created, they feel anxiety. They assume the product is broken.
Questions to consider regarding feedback:
- Does every action have a reaction?
- Is the system status always visible?
- Are error messages helpful or just technical codes?
Cognitive Load and Simplicity
#Interaction Design is ultimately about managing cognitive load. Every time a user has to stop and think about how to use an element, you spend a fraction of their limited attention span.
If you use a standard magnifying glass icon for search, the cognitive load is zero. The user has seen that interaction a thousand times on other sites. If you decide to get creative and use a picture of a ferret to represent search, the user pauses. They are confused. They have to learn a new interaction language just for your app.
Startups often try to reinvent the wheel to appear innovative. In IxD, being boring is usually better. Standard patterns work because they are predictable. Predictability reduces the mental effort required to use your tool.
When you are reviewing your product, look for friction. Look for moments where you have to explain how to use a feature. If you have to explain it, the interaction design is likely flawed. The interface should explain itself through context and cues.
Scenarios for Application
#Consider a SaaS dashboard. You want the user to delete a project. A poor interaction design allows the user to click delete and the project vanishes instantly. This seems efficient, but it is dangerous. It invites error.
A good interaction design introduces friction intentionally. The user clicks delete. A modal window appears (Dimension 2). It asks for confirmation in clear text (Dimension 1). It might require the user to type the name of the project to confirm (Dimension 5). This interaction prevents mistakes.
Consider a mobile app for field technicians. The physical context (Dimension 3) involves bright sunlight and dirty hands. Small buttons with low contrast will fail. The interaction design must adapt to large touch targets and high contrast visuals to be functional in that environment.
We cannot predict every way a user will try to break our product. This is where the scientific stance comes in. You must observe usage.
Where do users rage click? Where do they drop off? These are symptoms of poor interaction design. It means the conversation between human and machine has broken down.
You do not need to be a designer to improve IxD. You just need to be observant. Watch someone use your product without helping them. Watch where they hesitate. That hesitation is your roadmap for what needs to be fixed.
Focus on the verbs. Clicking, scrolling, swiping, typing. Make those actions feel substantial and responsive. If you get the interactions right, the user stops thinking about the interface and starts thinking about the value you provide.

