Surveys for product managers: discovery, feedback, churn, and NPS
Product managers should run four kinds of surveys at different moments: discovery surveys before building, feature-feedback surveys right after a release, churn surveys the moment someone cancels, and relationship NPS on a steady quarterly cadence. Keep them short, target the right segment, and treat survey data as a way to find people to talk to — not as a substitute for talking to them. Below is the cadence as a table, 10+ example questions by survey type, and how to act on what comes back.
Which surveys should a product manager run?
Surveys are cheap to send and easy to misread, so the discipline is matching the survey type to the decision you're making. Discovery surveys size and prioritize problems; feedback surveys check whether a release landed; churn surveys explain why people leave; NPS tracks the relationship over time. Run each at the moment it's most informative, not on a generic schedule.
| Survey | When to run | Length | Decision it informs |
|---|---|---|---|
| Discovery survey | Before building; quarterly problem-sizing | 5–8 questions | What to build and for whom |
| Feature feedback survey | Right after a release / in-product | 2–4 questions | Whether the feature works and what to fix |
| NPS (relationship) | Quarterly, rolling | 1–2 questions | Overall product health and loyalty trend |
| Churn / cancellation survey | At the moment of cancel | 2–4 questions | Why people leave and what's preventable |
| Onboarding / activation survey | After first key action or week one | 3–5 questions | Where new users get stuck |
| PMF (product-market fit) survey | Periodically with active users | 3–4 questions | How disappointed users would be without you |
Trigger in-product micro-surveys off behavior, not time. Ask about a feature right after someone uses it, ask about onboarding right after activation, and ask the churn question on the cancel screen. Context-triggered surveys get higher response rates and far more accurate answers than a generic email blast days later.
Example discovery survey questions
- How do you currently solve [problem]? (open text)
- How big a pain is [problem] for you day to day? (1 = minor, 5 = major)
- How often do you run into this? (daily / weekly / monthly / rarely)
- What have you tried, and why didn't it fully work? (open text)
- If we built something to fix this, what's the one thing it must do? (open text)
- Which of these would you find most valuable? (rank these options)
Example feature feedback survey questions
- How easy was it to do [task] with the new feature? (1–5)
- Did it do what you expected? (Yes / Mostly / No)
- What, if anything, was confusing or missing? (open text)
- How much better is this than how you did it before? (much worse … much better)
Example NPS and PMF questions
- How likely are you to recommend us to a colleague? (0–10) — plus: what's the main reason for your score? (open text)
- How would you feel if you could no longer use this product? (very disappointed / somewhat disappointed / not disappointed) — the Sean Ellis PMF question
- What type of person do you think would benefit most from this product? (open text)
- What's the main benefit you get from us? (open text)
Example churn / cancellation survey questions
- What's the main reason you're canceling? (too expensive / missing a feature / didn't use it enough / switched to another tool / problem solved / other)
- What could we have done to keep you? (open text)
- Which competitor, if any, are you moving to? (open text)
- Would you consider coming back if we fixed that? (Yes / Maybe / No)
How do you act on product survey results?
- 1Segment before you read. The same answer means different things from a power user vs. a trial that never activated — filter by plan, tenure, and usage.
- 2Use surveys to find people, then interview. A high-pain open-text answer is a lead for a 20-minute call that gives you the 'why' a survey can't.
- 3Watch for response bias: who didn't answer matters. Churned users who ignore your survey are often the most churned.
- 4Tie findings to a roadmap decision explicitly — 'we're building X because the discovery survey showed Y' — so the survey changed something.
- 5Close the loop with respondents when you ship what they asked for; it's the cheapest retention move you have.
What tool should a PM use?
For embedded, behavior-triggered micro-surveys inside your app, an in-product tool (Pendo, Sprig, and similar) is purpose-built. For standalone discovery surveys, churn forms, and NPS you send by link or email, a general survey tool is plenty — and a free one with unlimited responses lets you survey your whole base without a cap. Formkii is free with unlimited responses, supports NPS and ranking question types, and exports to CSV, which covers discovery, churn, and relationship NPS surveys. Match the tool to whether the survey lives inside the product or outside it.
Frequently asked questions
What surveys should a product manager run?
The core set is discovery surveys before building, feature-feedback surveys after a release, churn surveys at cancellation, and relationship NPS on a quarterly cadence, plus optional onboarding and product-market-fit surveys. Each answers a different question, so match the survey type to the decision you're trying to make rather than running one generic survey for everything.
When should you send an NPS survey?
Relationship NPS works best as a rolling quarterly survey to a sample of active users, so you get a steady trend line rather than a once-a-year spike. Transactional NPS, by contrast, fires right after a specific interaction. Always pair the score with an open-text 'why' question, since the reason is more actionable than the number.
How do you run a good churn survey?
Put a short survey right on the cancellation screen, while the reason is fresh and you still have the user's attention. Ask the primary reason as a single choice with a few common options, then one open-text question about what could have kept them. Keep it to two to four questions so people complete it on their way out.
Are surveys enough for product discovery?
No. Surveys are great for sizing and prioritizing problems across many people, but they can't give you the depth of a conversation. Use survey results to find the right people to interview, then run those interviews to understand the 'why' behind the patterns. The two methods together are far stronger than either alone.
What's a free survey tool for product managers?
Formkii is free with unlimited responses and includes NPS and ranking question types, which covers discovery, churn, and relationship NPS surveys you send by link or email. For micro-surveys that need to fire inside your app based on user behavior, a dedicated in-product tool is the better fit. Pick based on whether the survey lives inside or outside the product.