Use case · Discovery
Find out whether it’s worth building, before you build it.
ProductSignal interviews the people who asked for a feature, and the people who would have to live with it. You get what they said on one page, tied to who said it.
ForProduct managersProduct designersFounders
Interview #37
04:51 · asked for bulk export
AI
You asked for a bulk export in May. Walk me through the last time you needed it.
Elena
End of the quarter. I copied forty rows into a spreadsheet by hand, then pasted them into Jira.
AI · follow-up
If the export existed, where would those rows have gone?
Elena
Straight into Jira. The spreadsheet was only ever the middle step.
Evidence
64 interviews · 5 days
It would replace the spreadsheet we rebuild every quarter.
Honestly, not a priority right now. We export twice a year.
We already solved it with a script. It works well enough.
Jira sync was never in the spec.
One discovery study, five days in. One conversation on the left, the evidence from the other 63 on the right.Every quote links back to its interview
Runs on the people who asked
ProductSignal finds the people who asked for it in the feedback you already have, and invites them, plus some who didn’t.
Bulk export · 41 requests
study opened Mon 09:30
Requests matched · Intercom, Zendesk
Mon 09:30
Invites sent · 41 who asked, 40 who didn’t
Mon 09:34
Interview started · link
Tue 14:08
Added to the topic
04:51 in
Day 2 of 5 · closes on Friday
It asks why they wanted it
The interview already knows what each person asked for, so it skips the feature and asks what they were trying to get done.
Interview #37 · Elena
02:36
Context · Intercom conversation · May
“Any chance of a bulk export? Copying rows by hand is slow.”
AI
In May you asked for a bulk export. What were you trying to get out, and where was it going?
Elena
Quarterly numbers, into Jira. The export would only be the first half.
Added to the topic · Bulk export
The questions
Three openers. The rest is listening.
You can edit them, add your own, or leave them as they are. Most teams leave them.
- Opener 01Walk me through the last time you needed this.Starts from a real moment, not an opinion about something that doesn’t exist yet.
- Opener 02What do you do today instead?Finds the workaround, and what it costs them each time.
- Opener 03What would have to be true for you to use it every week?Separates polite interest from real need. The useful answers are specific.
- Add your own opener
Ferro · bulk export
“We were a sprint away from building an export. What people needed was the Jira sync at the other end of it.”
64
interviews in five days
3 weeks
of build time cut from the spec before work started
Other use cases
Same loop, different question.
Why they left · evidence
128 interviews
Sarah K.· Team plan
“I opened it the next day and it was empty. I didn’t know what I was supposed to do next.”
Tomás R.· Starter
“My teammates never joined. I was the only one using it.”
Jonas W.· Team plan
“The price made sense once it worked. It just never got there for us.”
Every quote links to the person who said it
Churn
Why people leave, from the people who left. Interviews start the week they cancel.
See use case →Interview #41 · day 6
03:27
Priya
Have my team in it. I invited them, but there was nothing to show them yet.
AI · follow-up
What would have made the first screen worth sharing?
Added to the topic · Onboarding
Onboarding
Where new users get stuck in the first week, while they can still tell you.
See use case →