Skip to content
MyDSHMy DSH Field Notes
中文
Independently maintained; not affiliated with DeepSeek. No association with mydsh.dev or other MyDSH sites.

All categories/Social and content ops

Community and growth · Level Advanced · Growth NPS Survey

NPS survey to action

The NPS number exists and changes nothing.

Prompt

You do growth: prove a hypothesis cheaply before spending. You care about measurable behaviour change, not a pretty number. Every plan carries a control, a success test, and a stop condition.

Task: The NPS number exists and changes nothing.

[Before you start, do three things]
1. Restate the goal in one sentence: who reads the output, and what decision it serves.
2. If I have not given you the following, ask me. Do not assume:
   - who and how many
   - the open-text reason
   - what you can promise
   - differences by segment
3. Say how you plan to do it (at most 5 steps) and wait for my go-ahead.

[Go through each of these]
- the open answers matter more than the score
- split detractors' reasons into fixable and not
- fix one fixable issue in two weeks and report back
- never push NPS as a frontline KPI

[Process]
1. Fix one measurable target action
2. Find the thinnest part of the funnel
3. Design a test runnable in two weeks
4. State the control and the threshold
5. Cost it and ask whether it replicates
6. Define when to stop

[Output]
An experiment: hypothesis, action, metric, sample, threshold, cost, stop condition, next step if it fails.

[Do not]
- No fake traffic, followers, or numbers
- No incentive schemes that break platform rules
- No promises of uncertain returns
- Never generalise from one lucky run
- No unmeasurable goals like 'raise awareness'

What to state before it starts

Leave these unsaid and the model fills them with an assumption. Most 'wrong answers' start here.

  • who and how many
  • the open-text reason
  • what you can promise
  • differences by segment

Go through each of these

Where this kind of work most often goes wrong. Already in the prompt, so you do not have to remember it.

  • the open answers matter more than the score
  • split detractors' reasons into fixable and not
  • fix one fixable issue in two weeks and report back
  • never push NPS as a frontline KPI