“What's the smallest thing we could add that you'd notice?”
From getuserfeedback.com · Editorial
Why it works
Open feature requests skew big and aspirational because users assume you want vision; you get rewrites and integrations, all expensive, most speculative. Constraining the question to the *smallest noticeable* thing inverts that: it surfaces the daily papercut they've silently routed around — the missing keyboard shortcut, the export that drops a column, the confirm dialog nobody needs. These are cheap to ship and disproportionately felt because they sit on the path users already walk every day. The word 'notice' is the filter: it screens out nice-to-haves and isolates friction with real, repeated cost.
When to ask
Among active users who know the product well enough to feel its rough edges, when you want quick wins rather than roadmap-sized bets.
Good follow-ups
- How often does the lack of that actually bite you?
- What do you do right now to work around not having it?
- If you could only have that one thing this week, would you take it?
Watch out for
Letting the answer balloon into a major feature anyway ('a full mobile app'). When it does, the constraint failed — re-anchor with 'something we could ship this week that you'd feel by Friday'. Also resist dismissing a request because it sounds trivial; triviality plus daily frequency is exactly the high-leverage zone.
Where to ask
- In-product surveygreat
Best fired in-context to active users — proximity to the actual workflow keeps answers small and specific instead of a wishlist of big rewrites.
- User interviewworkable
Live you can probe what 'notice' means to them, but a call invites grand feature pitches; the smallness has to be defended out loud.
Pairs well with
Stage: Engagement · May 2026