ishenwei/nexus
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Auto-sync: 2026-04-21 17:12

Browse Source
This commit is contained in:
weishen
2026-04-21 17:12:45 +08:00
parent 914c8f6925
commit 0fe7ba237f
1888 changed files with 220 additions and 68174 deletions
Download Patch File Download Diff File Expand all files Collapse all files

42
wiki/concepts/Go-to-Market-Brief.md
View File

@@ -1,42 +0,0 @@
---
title: "Go-to-Market Brief"
type: concept
tags: [product-management, launch, gtm]
sources: [product-manager.md]
last_updated: 2026-04-20
---
## Definition
GTM Brief 是发布前编写的跨职能协调文档，定义目标受众、价值主张、发布清单、成功标准和回滚预案。
## Structure
1. **What We're Launching**：一段话描述产品、解决的问题、为什么现在重要
2. **Target Audience**：细分市场、大小、为什么他们关心、通过什么渠道触达
3. **Core Value Proposition**：单行公式 + 按受众分组的 messaging
4. **Launch Checklist**：Engineering、Product、Marketing、Sales/CS 分项清单
5. **Success Criteria**：按时间框架的指标、目标、负责人
6. **Rollback & Contingency**：回滚触发条件、负责人、沟通计划
## Launch Tiers
| Tier | Description |
|------|-------------|
| 1 (Major) | 重大发布，公司范围可见 |
| 2 (Standard) | 标准发布 |
| 3 (Silent) | 静默发布，无需营销支持 |
## Success Criteria Timeline
- Launch day：错误率 < 0.5%
- 7 days：功能激活率 ≥ 20%
- 30 days：功能用户 vs 对照组留存 +8pp
- 60 days：相关主题支持票据 −30%
- 90 days：功能用户 NPS +5 points
## Key Principle
- 确认 Support 和 CS 在 GA 前接受培训——不是发布当天
- 翻转 flag 前写好回滚 runbook
- GA 后 48 小时内发送发布总结给全公司
## Connection
- [[Product Manager Agent]] ← coordinates ← [[Go-to-Market Brief]]
- [[Launch Phase]] ← executes ← [[Go-to-Market Brief]]
- [[Sprint Health Snapshot]] ← monitors ← [[Go-to-Market Brief]]