Aug 11, 2026

The difference you feel but can't point at

Why two interfaces that look the same feel nothing alike.

Jacob Collado
Jacob Collado
Founder, Inertia

Put two versions of the same interface side by side. One feels considered, the other doesn't, and almost nobody can tell you why. Including, and I say this with affection, people who design for a living.

The difference is real. It's just smeared across a hundred decisions too small to name on their own.

Noticed versus felt

How many kinds of detail are there? Two, roughly, and they behave nothing alike.

Noticed details get pointed at in reviews. The colour, the illustration, that animation on the hero. Felt details don't survive being described out loud. A menu closing a beat faster than it opened. Optical alignment that's mathematically wrong and visually correct. One light source implied across an entire product, consistently, by someone who never mentioned it.

Nobody compliments these. They just come away thinking the thing is well made and couldn't defend the opinion if you pushed.

Nudge the play button right

Optical over mathematical. Centre a play icon by its bounding box and it looks off-centre, because the triangle's visual mass sits left of where the maths thinks it is. Nudge it right. Now the numbers are wrong and your eyes are happy.

Both are centred. The left by its bounding box, the right nudged until its weight, the dot, sits on the centre.

Asymmetric motion. Things should arrive slower than they leave. Arriving earns a moment of attention; leaving should get out of the way. Match the durations in both directions and everything feels faintly sluggish on exit, and nobody will be able to say what changed.

Text that never reflows. A number that changes width while it counts makes the whole row twitch. Tabular figures cost nothing and delete an entire category of visual noise.

Descenders. Draw a box tight around text and eventually it clips a g or a y. Looked perfect in the mockup, which used a word that happened not to have any.

Does any of this show up in feedback? Never once. All of it is why something feels resolved.

You can't see a problem that isn't there

Because they're the absence of a problem, which is a genuinely hard thing to see.

You can't perceive a layout that didn't shift, a hover that didn't flicker, an animation that never stalled. Good detail work removes small irritations nobody consciously registered anyway, so your reward for doing it well is that nothing whatsoever happens.

Try putting that on a timeline. It's why it's first thing cut.

One is nothing, forty is the gap

One of these is imperceptible. Forty of them is the entire gap between work that feels premium and work that feels approximate, and there's no midpoint where it suddenly becomes visible.

Which is also why you can't bolt it on at the end. Polish isn't a phase, it's a thousand small calls made right the first time, mostly by people who'd struggle to fully explain their reasoning if you cornered them about it.

Not mystique. Just what accumulated judgment looks like from the outside.

Caring when nobody asked

You get there by caring about things nobody asked you to care about, over and over, for years, with absolutely nothing confirming it mattered.

The only real signal is people trusting the work and not being able to articulate why. If you need credit for the details, this part of the craft is going to be miserable. If you don't, it's most of the job.