“What feedback do you have for us?”
From getuserfeedback.com · Editorial
Why it works
Every structured question encodes an assumption about what matters; an open invitation removes that frame and lets the user set the agenda. That's its whole value — it catches the unprompted, off-roadmap, 'I didn't know I could tell you this' signal that targeted questions filter out. The cost of that openness is variance, which is exactly why it complements (rather than replaces) the sharp questions in the rest of the library.
When to ask
Keep it permanently available in-product rather than firing it at a moment. Its job is to be there when a user already has something to say.
Good follow-ups
- What made you decide to tell us about this now?
- If we could only fix one of those things, which would it be?
- Is this stopping you from getting something done, or more of a nice-to-have?
Watch out for
A blank, generic prompt invites blank, generic answers — and a flood of low-signal dumps with no structure to triage. The recovery is to pair it with one specific question, set light expectations ('what's one thing we could do better?'), and have a real path for routing what comes back, so the channel stays trustworthy.
Where to ask
- In-product surveygreat
Its native home: an always-available, low-friction field in the product so feedback lands the moment someone feels it.
- Long-form surveyworkable
Fine as a free-text closer, but a generic prompt buried at the end of a long form gets thin answers.
- User interviewworkable
Works as a warm-up or a closing 'anything else?', but in a live conversation a specific question will out-earn it every time.
Available as a ready-made survey: Feedback form
Stage: Stick · May 2026