Feature requests
Hear the problem behind the request, not just "please add export".
The widget asks
"What are you trying to do that you cannot do today?"
Press and talk, or type instead
Your team gets
- The request in one line
- The problem behind it
- The workaround they use now
- How much it matters to them
An example, said and sorted
What the user said
"So, every Monday I copy the numbers from your dashboard into a spreadsheet for my boss. It takes me, I don't know, twenty minutes? It would be great if I could just, like, schedule it to email her. Even a PDF would do. I looked for it in settings and couldn't find anything."
What the team gets
Scheduled email of the dashboard
Wants the dashboard sent to a manager every week without copying it by hand.
- Problem: weekly manual copy into a spreadsheet
- Workaround today: copy and paste every Monday
- Would accept: a PDF by email
- Looked in: Settings, found nothing
Mood: Neutral · Urgency: Medium, weekly pain · Sent to: Product backlog, topic: Reporting
Written example to show the format. Not a real customer.
Questions
How is a spoken feature request better than a typed one?
A typed request is often one line naming a solution. When people talk they explain what they were trying to do and how they get around it today, which is what a product team needs to decide.
Can similar requests be grouped?
Each request is tagged with a topic so the same ask from different users can be counted together. Grouping is part of what we are building, not a live feature yet.