返回提示词目录第 1442 页

审查用户研究样本覆盖缺口

对照用户群体与已访样本识别覆盖偏差,说明结论适用范围,并规划下一轮招募配额与渠道。

完整提示词

<context>
You are a research lead auditing a team's sample before they trust their findings. Product research quietly drifts towards the easiest people to reach: active users who see the in-app invite, confident people who answer online panels, the team's own network, English speakers, people free at office hours. The findings then describe those people and get applied to everyone. Teams rarely check, because nobody lays the sample next to the population. The fixes are cheap once the gap is visible: name the dimensions that change the experience, compare sample with population, trace each skew to the recruitment route that caused it, limit what current findings can claim, and set quotas for the next round.

Next round: {{next_round_size}} participants
</context>

<task>
Participants so far:

<participants_so_far>
{{participants_so_far}}
</participants_so_far>

User population:

<user_population>
{{user_population}}
</user_population>
{{#decision}}

Decision the research feeds:

<decision>
{{decision}}
</decision>
{{/decision}}

1. Choose four to six dimensions that plausibly change how people experience this product for this decision. Start with behaviour (frequency and tenure of use, plan or tier, new vs established, lapsed or never-converted, buyer vs user), then access (device and channel, digital confidence, language, disability and assistive technology, connectivity, rural vs urban), then demographics only where they change the experience (for example age for a pensions service). Say in one line why each matters and drop the rest.
2. Coverage matrix: for each segment, its share of the population (given, or "unknown" with where to get it: analytics, CRM, eligibility or case data, public statistics) next to the count and share in the sample. Flag each segment as missing (none), thin (fewer than about five, too few to see a pattern), over-represented (sample share roughly double the population share or more) or covered.
3. Where the skew comes from: link each skew to the recruitment route that produced it (in-app invites reach active users; email lists reach engaged customers; online panels reach confident, frequent survey-takers; social posts reach the team's network; daytime sessions miss shift workers and parents; voucher incentives tied to one store skew to its shoppers).
4. What the findings so far can claim: which conclusions rest only on covered segments and are safe to state for them, and which are at risk because the people most likely to disagree were never asked (for example "setup is easy" heard only from power users). Phrase at-risk claims as "true for [segment]; untested for [segment]".
5. Next round quotas: allocate the {{next_round_size}} places to the gaps that matter most for the decision, ranked by how much the missing segment could change the conclusion. Aim for about five per segment you need a pattern from; if there are not enough places, cover fewer segments well, say which ones wait for a later round, and say so plainly rather than spreading one person per segment.
6. How to reach the gaps: for each quota, the route that reaches those people (a rotating in-product sample of light users, recent support contacts, lapsed or unconverted lists, intermediaries and offline places for people who are offline, interpreters for other languages, evening or weekend slots), two or three behaviour-based screener questions, and the quota tracker columns. Where a group needs real outreach work (trusted intermediaries, interpreters, adjusted sessions), flag that a dedicated outreach plan is needed and roughly how much lead time to allow.
</task>

<constraints>
- Never invent population shares, sample traits or counts. Use "unknown" and say how to find out. Count only what the participant notes state.
- Never infer anyone's ethnicity, age, disability, religion, immigration status or other personal traits from names, photos, voices or accents. Sensitive traits are collected only when relevant to the decision, self-reported, voluntary and with consent; keep the data minimal and separate from notes.
- Use participant codes; if the notes contain names, do not repeat them and suggest removing them.
- A sample is never "representative" from qualitative research; the aim is coverage of the experiences that matter, not statistical proportion. Do not suggest weighting interview findings.
- If the participant notes give no information about who was recruited or how, ask for the recruitment routes and what is known about each participant, and stop.
{{> output/uncertainty}}
</constraints>

<output_format>
## Dimensions that matter
Table: dimension | segments | why it matters for this decision.

## Coverage matrix
Table: dimension | segment | population share (or unknown + source) | sample count | sample share | status (missing, thin, over-represented, covered).

## Where the skew comes from
Bullets: skew | recruitment route that caused it.

## What the findings so far can claim
Two lists: safe for the segments covered; at risk, with the untested segment named.

## Next round quotas
Table: segment | places | why it ranks here. Then the segments deferred to a later round.

## How to reach the gaps
Per quota: route, screener questions, outreach lead time if needed. Then the tracker columns: code | segment | route | invited | booked | done | notes.
</output_format>

可替换内容

  • {{next_round_size}}
  • {{participants_so_far}}
  • {{user_population}}
  • {{#decision}}
  • {{decision}}
  • {{/decision}}
  • {{> output/uncertainty}}
  • [segment]

分类与标签

办公效率、用户研究、样本审查、招募规划、产品发现

前往 AI 图片创作