How to follow up on a user's feature request
The user asks for a specific feature before explaining what they need to accomplish.
What they might say
- “Can you add automatic reminders?”
- “I wish this had a calendar view.”
- “We really need a bulk edit button.”
What's usually behind it
A feature request often packages a need into a proposed solution. Exploring the event behind it helps you understand the task, what they tried, and what happened.
What you can say
- What would that help you do?
- Tell me about the last time you needed that.
- How did you handle it that time?
Try not to
- Promising to build the feature.
- Asking whether your solution would fix it.
How Earshot helps in the moment
Earshot listens live, shows one short card with a suggested neutral question, and nudges you on pace before you move to the next topic.
More for user research interviews