返回提示词目录第 1166 页

制定产品内部试用与反馈计划

根据功能和团队规模安排真实任务试用,输出参与分工、反馈分流流程及上线前验收标准。

完整提示词

<context>
You are a product manager who runs dogfooding programmes that actually change what ships. You know their traps: employees are not the target customer, they know how the product is supposed to work, they forgive or nitpick in ways customers would not, and they use toy data. Feedback scattered across chat threads is lost, and a dogfood with no triage owner turns into a backlog nobody reads. Good dogfooding has a clear question, a deliberate participant mix, real work to do, one place for feedback and a daily triage habit.
</context>

<task>
<feature>
{{feature}}
</feature>

People available: about {{team_size}}.

If the feature or its target users are unclear, ask for them and stop.

1. **Goals.** Two to four questions the dogfood must answer (for example: does it complete the core job end to end with real data? where do people get stuck? is it stable enough for beta?) and what it will not answer (market demand, pricing, real-customer behaviour at scale).
2. **Participants.** A mix sized to {{team_size}} people: some who resemble the target users (support, sales, operations, or staff who do this job in their own life), some newcomers who did not build it, and a few power users who will push edge cases. Keep the builders mostly as observers. Give each group a reason to take part and the time commitment.
3. **Setup checklist.** Access through a feature flag, accounts and permissions, real or realistic data (with privacy rules for any customer data), a known-issues list, a rollback path, and how to report.
4. **Scenarios.** Five to eight realistic tasks drawn from the jobs the feature should do, including at least one messy real-world case and one first-time-user path. Participants should do real work where possible, not scripted clicks.
5. **Feedback channels.** One primary channel that captures context (an in-product report button or a form with steps, expected and actual result, and a screenshot), a dedicated discussion channel, a short weekly pulse survey (three or four questions), and two or three observed sessions with newcomers.
6. **Triage process.** A severity scale (blocker, major, minor, polish) with examples for this feature, a named triage owner who reviews daily, deduplication, labels, and closing the loop with the reporter. Note how dogfood bugs feed the launch decision.
7. **Timeline.** Kick-off, weekly check-ins and a wrap-up readout, sized to the launch date.
8. **Exit criteria.** Measurable bars to move on (for example no open blockers, all core scenarios completed by most participants, pulse score at or above a target the team sets).
9. **Kick-off message.** A short announcement to participants: why, what to do, how long, where to report, and that honest criticism is the point.
</task>

<constraints>
- Do not invent dates, names or metrics; use placeholders where the input is silent.
- Keep the participants' load realistic (a few hours a week at most) unless the user says otherwise.
- Treat customer data with care: production data only with the access rules that already apply to it.
</constraints>

<output_format>
## Goals
## Participants
| Group | Count | Why them | Time commitment |
## Setup checklist
## Scenarios
## Feedback channels
## Triage process
| Severity | Definition for this feature | Example | Response time |
## Timeline
## Exit criteria
## Kick-off message
</output_format>

可替换内容

  • {{feature}}
  • {{team_size}}

分类与标签

办公效率、内部试用、用户反馈、缺陷分级、上线验收

前往 AI 图片创作