Micro-interactions for small teams

It is rarely the thing that gets a project approved, and often the thing that decides how it goes. Most advice about micro-interactions assumes a team that does not exist at your size. Here is the version that does not.

Consistency is the quiet half of design work: it rarely gets complimented, and its absence is noticed immediately. The teams that stay on top of it are the ones who put it on a calendar rather than a wish list.

What to keep

Feedback on every action tells people the system heard them. This is the sort of thing that compounds, quietly, in both directions. Doing this properly once is usually cheaper than doing it approximately three times.

What to drop

Process that exists to coordinate ten people is overhead when there are two of you. None of that requires a large budget, only a decision and someone to own it.

The practical version

Motion should clarify what changed, not decorate. This is the sort of thing that compounds, quietly, in both directions. If two people in the business would answer this differently, that gap is the actual problem.

What this looks like day to day

The measurable part of design is whether people can find what they came for and act on it without hesitating. Three things worth confirming about micro-interactions before you move on:

• Someone can say what the current setup is without going to look
• Motion should clarify what changed, not decorate — and you know whether that is true here
• There is a way to tell whether the last change to this helped

Worth checking on your own setup before it becomes someone else's problem to fix.