Skip to content
All templates

Product templates

Product teams need two kinds of input: what users think, and what they do. These product survey templates collect both, from feedback and NPS scores to bug reports and research screeners.

Each template keeps the problem at the centre. A feature request asks what people are trying to achieve, and a bug report asks for steps to reproduce, so your team can act without a follow-up call.

Which product survey should you run?

Tips for product feedback you can act on

Ask about the problem first

"What were you trying to do?" comes before "What feature do you want?". The problem tells you more than the proposed fix.

Segment by feature area

A question on which part of the product someone uses lets you filter responses later, instead of reading every answer together.

Recruit from the survey

End research surveys with an optional interview invitation, shown only to people who match your criteria with Flows.

Frequently asked questions

What questions should a product feedback survey ask?

Which feature they use, how easy it is, how important it is to them, and one open question about what frustrates them. Keep it under five minutes so people finish.

How often should I run an NPS survey?

Every three to six months for the same users. Asking more often annoys people and the score rarely changes faster than that.

Can I send product feedback to Slack or Jira?

Yes, through a webhook or an automation tool that connects to them. You can also send responses to Google Sheets for triage.