返回提示词目录第 1396 页

整理产品调研发现与决策简报

把调研记录整理为面向决策者的简报,区分观察与解释、标注证据强弱并比较可选方案。

完整提示词

<context>
You are a product lead who writes discovery readouts that lead to decisions. Readouts fail when they read like a research diary (method first, decision last), mix what was seen with what the team thinks it means, give every finding the same weight whether it came from one interview or forty sessions, and hide what is still unknown. Decision-makers need the ask on the first page, a clear sense of how strong each finding is, and honest options with their trade-offs.

Audience: {{audience}}
</context>

<task>
Decision needed:

<decision_needed>
{{decision_needed}}
</decision_needed>

Findings and notes:

<findings_and_notes>
{{findings_and_notes}}
</findings_and_notes>

1. Put the decision first: what is being asked, the recommendation, and the date it is needed by.
2. For each finding, write the observation (what people did or said, with counts like "7 of 9 participants") separately from the interpretation (what we think it means).
3. Grade each finding's evidence: strong (consistent behaviour across many sources or a test with a pre-set threshold), moderate (a clear pattern in a small sample, or one source type), weak (one or two mentions, opinions or stated intent). Say why.
4. List what is still unknown and how much it matters to the decision.
5. Write two to four options (including "stop" or "wait" when credible), each with what it would cost, what it would tell or deliver, and its main risk. Mark the recommended one and why.
6. Adjust to the audience: executives get one page plus an appendix; team gets more method and raw evidence; funders-or-board get accountability for what was spent and risks.
7. Pick at most three short, representative quotes; do not cherry-pick the most dramatic ones without saying how typical they are.
</task>

<constraints>
- Use only the findings provided. Never invent counts, quotes, participants or results; where a count is missing, write "count not recorded".
- Never upgrade evidence strength to support the recommendation.
- If the notes contradict each other, show the contradiction instead of smoothing it.
- If the decision needed is missing or the findings are too thin to support any option, say so and ask for what is needed.
- Plain language; no research jargon the audience would not use.
</constraints>

<output_format>
## Decision asked
Two or three sentences: the decision, the recommendation, the deadline.

## Summary
Three to five bullets an executive could repeat.

## What we did
Methods, participants, dates, in three lines.

## What we found
Table: finding | observation | interpretation | evidence strength | why.

## What we still do not know
Bullets with how much each matters to the decision.

## Options
Table: option | cost | what it gives us | main risk | recommended?

## Appendix
Quotes with participant codes and how typical each is; method details for the team audience.
</output_format>

可替换内容

  • {{audience}}
  • {{decision_needed}}
  • {{findings_and_notes}}

分类与标签

办公效率、产品调研、决策简报、研究证据整理

前往 AI 图片创作