Desirability

Two products with the same features and no obvious friction, and only one of them gets used — that pattern is old. Put them side by side, compare them line by line, and the comparison comes out even, yet people pick one and stay. With no language for the difference, it got filed under taste for a long time.

Meetings ended accordingly: make it prettier. Nobody could say what would need to change for that to happen, so the next meeting became two mockups on a screen and everyone pointing at the one they liked. Asked why, people said it just looked better, and the decision drifted toward whoever had the most standing in the room that day.

The name arrived when user experience got broken into separate attributes. Alongside usability, which asks whether people can reach their goal easily, and usefulness, which asks whether the product solves something real, this attribute asks whether anyone wants to come back. Having a name turned the taste argument into work: teams could write down which attribute they were trying to raise, and decide up front how they'd know whether it moved.

Three things stack up to create the pull: the first impression, the response to each action, and the personality the product carries.

1. The first impression lands in under a second. Size hierarchy in the type, consistent spacing, restraint with color — all of it registers before a single word is read, which is why fixing it pays so well. Tidying the spacing on a signup screen changes how the same sentence reads, and that edit costs an afternoon rather than a sprint.
2. The response comes back on every interaction. Does the button look pressed when pressed? Does a deleted row leave in a way that makes sense? These short responses are micro-interactions. Each is a fifth of a second; encountered a hundred times a day, they become the impression of the whole product. When nothing happens for half a second and then the screen changes, the user spends that half second deciding whether to press again.
3. The personality comes out of how the product talks. "Operation failed" and "That didn't save — try once more" leave different residue from the identical failure. The short text on buttons and notices is microcopy, and it's usually the cheapest place to raise this attribute.

The stack even bends judgment. People rate better-looking screens as easier to use than they actually are. Build the same flow twice, polish only one version, and testers who used the polished one report the task as easier — with identical completion times. So a product that scores well here gets small annoyances forgiven, and one that doesn't loses people over the same annoyances.

The weight of this attribute changes with the market. It counts most where people have several products to choose from and choose individually — anything sold by letting someone try it free and spread it to their team. It counts less in internal systems a company assigns and employees have to use regardless. It isn't irrelevant there, but on those products raising usability first returns more.

Inside a product, certain screens carry more of it than others: the first screen and onboarding, before any of the user's own content exists; the empty state, where a list has nothing to show yet; and the moment right after something finishes. All three are moments where a person forms a judgment, so the impression sticks. Meanwhile, on a screen someone opens twelve times a day, anything attention-grabbing turns into an irritation fast. The welcome animation that charmed on the first visit is a wait by the twentieth.

Movement in this attribute shows up in numbers eventually. Retention — how many people keep coming back — moves first, and survey answers about recommending the product shift with it. If the share of users who've recommended it tripled in six months, something in between is worth finding. No single metric belongs to this attribute alone, though. When the attributes underneath it are broken, polishing here moves nothing at all.

"Everything works, there's just no reason to open it again."

Nothing is broken; this attribute is simply low.

"This round is about desirability, so task success rates won't show it."

Agree on a different measure before the work starts.

"Let's start with the empty state — it's the first thing a new team sees."

Pick the screen where the attribute carries the most weight, rather than spreading the work evenly across the product.

At Pagedeck a lot of teams disappeared within a week of signing up. Mia went through the records and found no evidence of anyone getting stuck: teams created a document, invited someone, and simply never returned. With nothing pointing at usability, the cause stayed unexplained for a while, and the weekly numbers kept looking the same.

Noa went back to look at what the first document actually showed. A blank page and one line of gray helper text, and nothing else — no sign of what happens after the first sentence, no sign of what kind of product this is. She put three usable document outlines into the empty state and rewrote the text around them, and the share of teams returning a week later went up. Ravi moved the same wording onto the landing page.

The most common misreading is that this attribute means a pretty interface. Visual changes come first, so the impression is easy to form, but what's being described is the wish to open something again, not the surface of a screen. Work that only adds decoration makes loading slower and text harder to read, which pushes the attribute down instead of up. Rewriting one line of text often beats adding one more animation, and it survives a redesign better too.

The second is deciding it's subjective and therefore unmeasurable. One person's reaction is, but ask many people the same question and a tendency appears. A common method hands testers a list of adjectives at the end of a usability session and asks them to pick. When eighteen of twenty-five pick "rigid," that's a signal rather than a preference. Declare the attribute unmeasurable and it stays an argument — and arguments go to whoever is loudest.