“If we removed this feature tomorrow, what would you miss?”
From getuserfeedback.com · Editorial
Why it works
Ask users what they like and everything scores well; everything is fine. The removal frame breaks that politeness — imagining the absence forces them to simulate the gap, and only genuine dependence survives the test. What they say they'd miss maps almost exactly onto what they actually use under pressure, which is rarely the feature you spent the most building. This is the cheapest way to find your load-bearing surface before you accidentally cut it, and to discover which celebrated feature nobody would even notice was gone.
When to ask
Among active users who've had time to build habits, when you need to know what's load-bearing before a redesign, deprecation, or roadmap cut.
Good follow-ups
- What's the one thing you'd be most lost without?
- What would you do the next morning instead?
- Which part, honestly, would you not even notice was gone?
Watch out for
Reading a long 'I'd miss everything' as strength. Undifferentiated loss aversion is noise; the signal is specificity and intensity. Push for the one thing they'd be most lost without and what they'd do the next morning instead — that workaround reveals the true value, or the lack of it.
Where to ask
- In-product surveygreat
Best as a low-stakes prompt to active users — the loss frame makes them name what they'd actually fight to keep, which a satisfaction question never does.
- User interviewworkable
Works live and you can probe the 'why', but a scheduled call self-selects for your most invested users, who'd miss everything.
Pairs well with
Stage: Engagement · May 2026