Did this feature work as expected? Product Survey Question
Quickly identify feature bugs and usability issues with a simple yes/no question that helps you prioritize fixes and improve user experience.
Question type
Yes/No binary choice
Primary metric
CSAT (Customer Satisfaction Score)
Answer scale variations
| Style | Options |
|---|---|
| Typical choice | No Yes |
| More emphatic | Definitely not Yes, definitely |
| Expectation-based | Did not work as expected Worked as expected |
| Functionality-focused | Not working properly Working properly |
| Outcome-based | Failed to work Worked perfectly |
Follow-Up Questions
Understanding why users answered yes or no helps you prioritize fixes and improvements. These follow-up questions dig into the specific issues or successes behind their rating.
This open-ended question captures the exact friction points users experienced, giving you concrete details to share with your development team.
Categorizing where confusion occurred helps you identify patterns across users and prioritize which areas need clearer design or documentation.
This question turns criticism into actionable improvement ideas by asking users to describe their ideal experience.
When to Use This Question
SaaS Products: Ask immediately after a user completes their first interaction with a new feature via in-app modal or slide-in notification, because catching friction in real-time lets you fix issues before they compound into frustration and feature abandonment.
Mobile Apps: Trigger within 24 hours of users completing a key workflow (like finishing a transaction or creating content) through push notification linking to in-app survey, because this timing captures fresh impressions while the experience is vivid without interrupting the moment of task completion.
E-commerce: Deploy 2-3 days after delivery when customers have actually used the product via email with prominent survey link, because this window catches genuine usability issues before the return window closes while memories remain specific and actionable.
Web Apps: Present after 3-5 feature uses to repeat users through contextual banner at top of feature interface, because multiple interactions reveal patterns beyond first impressions and show whether the feature delivers consistent value over time.
Digital Products: Ask within 48 hours of a user engaging with premium or newly unlocked functionality via in-product toast notification or email, because this captures the critical moment when users evaluate whether advanced features justify their investment or upgrade decision.
Related Questions
- Did you find what you were looking for using the search?
- Was this article helpful?
- Was the checkout process easy?
- Did you accomplish what you came here to do?
- Was this information useful?
- Did this solve your problem?
- Was this page helpful?
- Was the setup process clear?
- Did this answer your question?
- Was this tutorial easy to follow?
- Did this feature meet your expectations?
- Was the import successful?
- Did you get what you needed?
- Was this documentation clear?
- Did this workflow make sense?
- Did this tool do what you expected?
- Did we meet your expectations?
- Did our product meet your expectations?
- Did our service meet your expectations?
- Was your issue resolved to your satisfaction?
- Did we resolve your issue on first contact?
- Was the support agent polite and respectful?