Interaction design (IxD) is the craft of how people and systems meet: what happens when someone taps, types, waits, or gets stuck, and how we make that understandable, fair, and resilient. It’s not the same as “only visuals”; it’s the behavior layer that sits between strategy and engineering.
01
Behind most products the stack is messy, and with AI in the loop, even more so. IxD is how we sequence information, set expectations, and expose the right detail at the right moment, so experts aren’t overwhelmed and newcomers aren’t lost.
02
A product is a path over time: onboarding, recovery from errors, handoffs between tools. Interaction designers map those paths, prototype them, and test whether they hold up for real work.
03
When software infers, recommends, or automates, people need to see what happened, what they can change, and what comes next. That’s interaction and content design working together: patterns like progressive disclosure and graceful failure are part of the job.
04
Design systems aren’t decoration kits. They encode how decisions get made once so teams don’t reinvent patterns, freeing energy for harder product problems.
Common take
“Design is making it pretty.”
Closer to the work
A huge slice of the job is problem framing, tradeoffs, and alignment: turning ambiguity into something buildable, then iterating with research and engineering.
Common take
“UX is wireframes.”
Closer to the work
Wireframes are one output. The work includes research synthesis, journey mapping, prototyping, usability, and crit, often owning the story of why a direction is right.
Common take
“The designer hands off to dev and walks away.”
Closer to the work
The best outcomes come from tight loops with engineering and partners in research and data, especially when the product is AI- or data-heavy, where the experience has to line up with how the system actually behaves.