The feature in focus always looks bigger than it is

Ask a user what would make your product perfect and they’ll tell you, with real conviction, about the one thing that’s missing. In that moment they aren’t lying and they aren’t confused. They’re doing what every brain does when it turns its full attention on a single thing: swelling it. Whatever you look at, while you’re looking at it, feels like it matters more than it will the moment you look away.

Kahneman called this the focusing illusion, and he compressed it into a line worth taping above a roadmap: nothing in life is as important as you think it is while you are thinking about it. The study that named it was almost comic. People believe Californians are happier than people in the Midwest, and Californians believe it about themselves — because the question makes the mind jump straight to the weather, which really is nicer, and skip the traffic, the rent, and the hundred ordinary things that fill an actual day. Attention is a spotlight, and the spotlight lies about proportion. Whatever it lands on grows.

It’s worth separating this from a neighbor it’s easy to confuse it with. The availability trap is about memory — the bug you can most vividly recall feels like your most common one. The focusing illusion is about attention — the factor you’re currently thinking about feels like your most important one, whether or not you can recall a single other instance of it. One is loud because it’s easy to remember. This one is loud simply because it’s lit.

⁂

For a builder it runs in two directions, and both are traps. The user filing a request is inside it: while they compose the words, that gap is the entire product, and their forecast — if you just add this, I’ll finally love it — routinely overshoots how much it will actually move their day-to-day satisfaction. Then you ship it, and the lift is smaller and shorter than anyone predicted, because once the thing exists it stops being the thing in focus and sinks back into the background of a normal day. The illusion hands the user off to plain old habituation, and the delight they promised themselves evaporates on schedule.

The same lie catches you from the other side of the table. Stare at one number every morning and it starts to feel like the business. The bug open in front of you feels like the biggest problem you have — not because it is, but because it’s the one currently under the light. A roadmap built by whoever is loudest this week is a roadmap built out of other people’s spotlights.

⁂

So the move isn’t to distrust users; it’s to distrust the size they report, not the existence of the need. Take the signal, discount the magnitude. Weight what people do over what they say matters in the moment they’re saying it. When you do ship a wished-for feature, don’t just log the request as closed — watch whether overall retention or satisfaction actually moves, or whether the glow fades as focus drifts to the next gap. And count, don’t listen: the focusing illusion is deafening for the one person in front of you and near-silent across a cohort, so the honest measure of importance is how many people independently walk into the same wall, not how vividly any one of them describes it.

The caveat that keeps this from turning into an excuse: the feature they’re asking for is often real and worth building. The illusion isn’t a claim that the need is fake. It’s a claim about weight — the predicted impact on the whole feeling is inflated by the act of attending to it. Believe the direction of the request. Just don’t believe the forecast.