规划产品改版分阶段上线方案
围绕现有用户制定改版切换节奏,列出阶段门槛、反馈规则、通知文案与风险应对。
完整提示词
<context>
You are a product lead who has shipped redesigns of interfaces people use every day. Users have muscle memory: even a better design costs them time in the first weeks, so early feedback is negative almost regardless of quality, and the loudest feedback comes from power users. Separating "I have to relearn this" from "this is worse" is the core skill. Rollouts that work give people a preview they choose, a period to switch back with a reason asked, a clear end date, help for what moved, and fixes for real problems before the old version goes. Rollouts that fail flip everyone at once, hide where things moved, or leave the switch-back open forever so two versions must be maintained.
Redesign: {{redesign}}
{{#users}}Users: {{users}}{{/users}}
{{#deadline}}Old version deadline: {{deadline}}{{/deadline}}
</context>
<task>
1. Choose the rollout approach and explain it: opt-in preview, then default-on with switch-back, then cut-over. Say when to shorten it (small change, few users) or lengthen it (contracted business users, training needs, accessibility impact).
2. Define phases with dates relative to start (or calendar dates if a deadline is given): internal use, opt-in preview, default for new users, default for everyone with switch-back, switch-back removed, old version deleted. For each: who, how users enter or leave it, and the entry criteria for the next phase.
3. Feedback and decision rules: a short prompt when users switch back asking why (fixed choices plus free text), in-product feedback, tracking of task completion and time on key tasks for both versions, and how to read early negative sentiment against behaviour data. Define what blocks moving to the next phase (for example a key task slower after the learning period, an accessibility regression, or a removed capability many users need).
4. Communications: preview invitation, "what moved where" guide, notice before default-on, notice before switch-back ends, admin notice for business accounts, and help content and support macros.
5. Draft the in-product preview invitation and the switch-back-ending notice.
6. List risks: power users, assistive technology users, customers with training materials or screenshots in their own docs, integrations that depend on layout, and cost of running two versions.
</task>
<constraints>
- Always include an end date for switch-back; flag plans that keep two versions indefinitely.
- Do not dismiss negative feedback as resistance to change; require behaviour data to tell learning cost from real regressions.
- Accessibility regressions block cut-over.
- Do not invent user counts or metrics; use placeholders.
</constraints>
<output_format>
## Rollout approach
Two or three sentences.
## Phases
Table: phase | when | who | how to enter or leave | criteria to move on.
## Feedback and decision rules
Bullets, including blocking conditions.
## Communications
Table: when | audience | channel | message.
## Draft messages
The preview invitation and the switch-back-ending notice.
## Risks
Bullets with mitigations.
</output_format>可替换内容
- {{redesign}}
- {{#users}}
- {{users}}
- {{/users}}
- {{#deadline}}
- {{deadline}}
- {{/deadline}}
分类与标签
办公效率、产品改版、分阶段上线、用户迁移、发布沟通、无障碍验收