How far away is what you're asking for?

Two lines of copy. “Start your first project — it takes about two minutes.” And: “Build the thing you’ve been meaning to make for years.” Both could live on the same landing page. But swap where they sit — put the two-minute line across the hero and the years-of-meaning line on the button you actually click — and something goes subtly wrong, even before you can say what. One of those sentences is standing too close to you. The other is standing too far away.

The reason has a name that mostly stayed inside the journals: construal-level theory. Worked out over two decades by Yaacov Trope and Nira Liberman, its core claim is that your mind represents the very same thing at different levels of abstraction depending on how far away it feels — and “far” arrives in several flavors at once: distant in time, distant in space, distant socially, or just hypothetical rather than certain. What’s near gets rendered in concrete, ground-level terms: the specific steps, the how, whether it’s actually doable right now. What’s far gets rendered abstractly: the point of it, the why, whether it’s even worth wanting. A trip a year out is “a real break, finally.” The identical trip tomorrow morning is “wait, where’s the charger.”

That has a hard edge for anyone who writes an interface, because every element on a screen sits at some psychological distance from the person reading it — and the language that lands changes with the distance. There’s a well-studied wrinkle here worth the name: persuasion tends to go up when the framing matches the distance. Concrete, feasibility-flavored words for the things that are near; abstract, desirability-flavored words for the things that are far. Researchers call it construal fit, and the mismatch is where copy quietly misfires.

Read your own product against that. The primary button is near — the action is about to happen, right under the cursor. Word it concretely, for feasibility: what it does, how long it takes, how little stands in the way. “Create your first note.” “Import in one click.” A near action dressed in far language — “Begin your journey” — asks the brain to go abstract about a thing it is one second from doing concretely, and the small friction of that is real. Meanwhile the vision, the reason the product exists at all, is far. That’s where abstract, desirability language belongs. Rendered as near-term feasibility instead — “configure your workspace preferences” — a distant promise gets buried under plumbing, and the point never surfaces.

Now the turn, because “match the words to the distance” is only half of it. Distance isn’t fixed. You can move it. A far, abstract goal can be dragged near by making it imminent and concrete — “your first real result is ninety seconds away” — which is often exactly the shove a hesitant user needs. And a near, dreary chore can be lifted by tying it back to the far why. So the sharper move isn’t just describing the distance an action happens to have; it’s deciding what distance you want it to feel like, and then writing to that. The mistake was never using concrete language, or using abstract language. The mistake is the mismatch between the felt distance and the words you chose for it.

One honest caveat, because the wedge is only worth anything if the science is stated straight: construal fit is well studied, but the effects are modest and lean on context. Matching the frame is a small tailwind, not a lever that moves a funnel on its own. It’s the kind of edge that compounds across a hundred strings, not the kind you’ll see in a single A/B test on your headline.

So before you write the next line of copy, ask the small question that decides everything about how it should sound: how far away is the thing I’m asking for? Then write like it’s exactly that far — or move it, on purpose, to where you need it.