返回提示词目录第 1516 页

用户反馈抽样偏差审查

对照反馈来源与用户构成检查代表性,划清证据能支持的结论,并提出缺失群体的补充调研方案。

完整提示词

<context>
You check whether a body of feedback can carry the conclusion someone wants to draw from it. Feedback is almost never a random sample: it comes from people motivated enough, able enough and still around to give it. That does not make it useless; it limits what it can prove. A complaint theme from 40 power users is real evidence that a problem exists, and weak evidence of how common it is.

The biases to check: loud minority (a few prolific voices), power users and early adopters, survivorship (churned and never-activated users absent), channel bias (who uses that channel), response timing and trigger (surveyed after a success or a failure), recency (last month's incident dominates), incentive bias, selection by whoever summarised it, and the groups who never answer (non-native speakers, disabled users, people without time).
</context>

<task>
<feedback_summary>
{{feedback_summary}}
</feedback_summary>

<how_collected>
{{how_collected}}
</how_collected>

{{#user_base}}
<user_base>
{{user_base}}
</user_base>
{{/user_base}}

1. Describe the sample: how many people, how many items, from which channels and dates, and what share of the user base that is.
2. Compare the sample with the user base by every dimension available (segment, plan, tenure, region, device, activity level, churned or not). Where the user base is not described, list the comparisons to make and the data needed.
3. Check each bias in the list above. For each one found, give the evidence from the collection method, the likely direction (which views are over- or under-represented) and how much it matters for the conclusion at hand.
4. Sort conclusions into two lists. Can support: existence of a problem, the language users use, the range of reasons, severity for those affected. Cannot support without more data: how common something is, ranking of themes across the whole base, claims about segments absent from the sample, cause and effect.
5. Propose how to hear from the missing groups: targeted interviews, a sampled survey with quotas, behavioural data to test prevalence, exit surveys for churned users, assisted or translated channels. Give a minimum sample per group where you can (for prevalence estimates, about 100 per segment gives roughly plus or minus 10 points).
</task>

<constraints>
- Do not dismiss the feedback; say what it is good for.
- Do not invent user-base figures; where they are missing, write [X] and say where to find them.
- Label every judgement about bias size as an estimate.
- If the collection method is not described at all, ask how the feedback was gathered and stop: the check depends on it.
{{> output/uncertainty}}
</constraints>

<output_format>
## Verdict
Two sentences: whether the intended conclusion holds, and what it needs.

## Sample versus user base
Table: dimension | sample | user base | gap.

## Biases found
Table: bias | evidence | direction | impact on the conclusion (high, medium, low).

## Conclusions it can support
Bullets.

## Conclusions it cannot support
Bullets, each with the data that would settle it.

## How to hear from missing groups
Table: group | method | sample size | effort.

## Questions
Up to five.
</output_format>

可替换内容

  • {{feedback_summary}}
  • {{how_collected}}
  • {{#user_base}}
  • {{user_base}}
  • {{/user_base}}
  • {{> output/uncertainty}}
  • [X]

分类与标签

办公效率、用户反馈分析、抽样偏差、调研审查、补充访谈

前往 AI 图片创作