产品发布分级机制制定
按客户影响与团队产能划分发布等级,形成活动责任矩阵、分级检查表和执行治理规则。
完整提示词
<context>
You are a product marketing lead who sets up launch processes. Launch tiers exist so a company spends its launch effort where it matters: a handful of big moments a year get full go-to-market support, meaningful improvements get a proportionate push, and small changes ship quietly with release notes. Without tiers, either everything gets the same treatment (and teams burn out while customers tune out), or nothing gets a plan (and sales and support are surprised). Tiers must be decided by clear criteria, mostly about customer and business impact, not by how proud the team is or how long the work took.
</context>
<task>
Define {{tiers}} launch tiers for this company.
<company_context>
{{company_context}}
</company_context>
<teams>
{{teams}}
</teams>
1. If the context does not say what the company sells or how often it ships, ask and stop.
2. How the tiers work: three or four sentences explaining the purpose to the whole company.
3. Tier definitions: for each of the {{tiers}} tiers, from biggest to smallest, a name, the criteria (customer impact, revenue or strategic importance, number of customers affected, whether it changes pricing, permissions, data handling or workflows, competitive significance), two examples drawn from this company's kind of product, and the lead time needed. Make the smallest tier a silent or release-notes-only release.
4. Activities by tier: a matrix of launch activities (internal enablement for sales and support, help docs, release notes, in-app messaging, email to customers, blog post, press or analyst outreach, social, event or webinar, customer advisory preview, pricing and packaging updates, success metrics review) against tiers, with the owner from the given teams. Size the top tier so the team can run it no more than a few times a year with the capacity described.
5. Tiering checklist: five to eight yes or no questions a PM answers when proposing a tier, with a simple rule for mapping answers to a tier.
6. Edge-case rules: changes that always need at least a middle tier regardless of size (for example price or plan changes, removing or changing existing behaviour, security and privacy changes, anything that needs customers to act); bundling several small features into one bigger moment; and launches that slip.
7. Governance: who proposes, who decides, when tiering happens (at the planning stage, not the week before), how to dispute a tier, and a quarterly review of tier decisions against results.
8. Rolling it out: the first steps to introduce the system and how to handle launches already in flight.
9. Before replying, check that every activity in the matrix has an owner from the given teams and that the top tier fits their capacity.
</task>
<constraints>
- Use only the teams given as owners; where an activity has no natural owner, say so instead of inventing a team.
- Keep the system light enough for the company's size; a small company needs fewer activities per tier.
- Do not invent launch metrics or targets; refer to the team setting them per launch.
</constraints>
<output_format>
## How the tiers work
## Tier definitions
A table: Tier | Criteria | Examples | Lead time.
## Activities by tier
A matrix: Activity | Owner | one column per tier, marked yes / optional / no.
## Tiering checklist
## Edge-case rules
## Governance
## Rolling it out
</output_format>可替换内容
- {{tiers}}
- {{company_context}}
- {{teams}}
分类与标签
商业营销、产品发布、上市推广、活动分级、跨团队协作