Talk2UserMost feedback is either collected at the wrong time, in the wrong place, or asks the wrong questions. The result? Silence, noise, or answers that lead you astray. Here's how to do it better.
The Core Idea
Ask at the right moment, in the right place, with the right question. One well-timed question beats a 20-field survey.
When to Ask
Timing is everything. Ask too early and they don't know enough. Ask too late and they've forgotten.
After a key moment
Just completed onboarding? Finished their first project? Hit an error? These are golden moments — the experience is fresh and they have something to say.
After they've had time to explore
Don't ask for feedback on day one. Wait until they've used the product enough to have an opinion. For most products, that's 3-7 days or after 2-3 sessions.
When they reach out first
Support tickets, chat messages, and emails are feedback opportunities. They already have something on their mind — dig deeper.
Where to Ask
In-app (contextual)
A small prompt after a specific action. "How was setting up your first project?" gets better answers than a generic survey email.
Email (for deeper feedback)
Good for users who've been around a while. Keep it short: one question, personal tone, easy to reply. "Hit reply and let me know" works better than survey links.
Support conversations
After solving their problem, ask: "Is there anything else you wish worked differently?" They're already engaged and grateful.
What to Ask
The best questions are short, specific, and focused on behavior — not opinions.
"What were you trying to do when you got stuck?"
Gets you to the real problem, not a vague complaint.
"What almost made you leave?"
Surfaces friction you might not see in analytics.
"What's the one thing you wish this did differently?"
Forces prioritization. You'll see patterns fast.
"How would you describe this to a friend?"
Tells you if your positioning matches how users think about you.
What Not to Do
- •Don't interrupt critical workflows — never pop up during checkout or in the middle of a task.
- •Don't ask too many questions — one question gets 10x the response rate of a 5-question survey.
- •Don't ask leading questions — "Don't you love feature X?" will get you nothing useful.
- •Don't ask hypotheticals — "Would you use X?" is worthless. Ask what they actually do.
Key Takeaway
The best feedback comes from users in the middle of a problem, not after they've forgotten. Ask one question, at the right moment, in the place where they already are.