risk-playbooks

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Launch Risk Playbooks Skill

发布风险手册Skill

When to Use

适用场景

  • Pre-launch risk assessments and go/no-go criteria.
  • During launch week to monitor escalations and coordinate mitigations.
  • Post-launch retros to capture lessons and update future playbooks.
  • 发布前风险评估及上线/不上线决策标准制定。
  • 发布周期间监控升级事件并协调缓解措施。
  • 发布后回顾以总结经验并更新未来的手册。

Framework

框架

Launch risk governance combines categorical coverage with a repeatable execution cadence. Use the following building blocks to keep Tier 1+ launches on track.
发布风险治理结合了分类覆盖与可重复的执行节奏。使用以下构建模块确保Tier 1及以上级别的发布按计划推进。

Risk Categories

风险类别

  1. Product & Reliability – feature readiness, bugs, infrastructure load, rollback paths.
  2. Go-to-Market – messaging accuracy, asset approvals, channel readiness, partner alignment.
  3. Compliance & Legal – policy reviews, privacy terms, licensing, regional constraints.
  4. Support & Success – staffing levels, escalation handoffs, enablement coverage.
  5. External Factors – competitor moves, macro events, press sentiment, supply chain.
  1. 产品与可靠性 – 功能就绪度、漏洞、基础设施负载、回滚路径。
  2. 上市策略 – 信息准确性、资产审批、渠道就绪度、合作伙伴对齐。
  3. 合规与法务 – 政策审核、隐私条款、许可、区域限制。
  4. 支持与成功 – 人员配置水平、升级交接、赋能覆盖。
  5. 外部因素 – 竞品动态、宏观事件、媒体舆情、供应链。

Execution Process

执行流程

  1. Identify risks w/ likelihood + impact scoring.
  2. Assign owners, mitigation steps, triggers, fallback actions.
  3. Maintain real-time risk log during war-room standups.
  4. Capture resolution notes + update future tiering guidelines.
  1. 识别风险并进行可能性+影响评分。
  2. 分配负责人、缓解步骤、触发条件、后备行动。
  3. 在作战室站会期间维护实时风险日志。
  4. 记录解决笔记并更新未来的分级指南。

Templates

模板

  • Risk register (description, likelihood, impact, owner, mitigation, status).
  • Escalation playbook (trigger, communication plan, action tree).
  • Lessons learned tracker feeding future launches.
  • 风险登记册(描述、可能性、影响、负责人、缓解措施、状态)。
  • 升级手册(触发条件、沟通计划、行动树)。
  • 经验教训追踪器,为未来发布提供参考。

Tips

提示

  • Pre-populate risk banks per tier to accelerate planning.
  • Tie mitigations to instrumentation/alerts to catch issues early.
  • Share summaries with execs daily during Tier 1 launches.

  • 按级别预填充风险库以加速规划。
  • 将缓解措施与监控/警报关联,提前发现问题。
  • 在Tier 1发布期间,每日向高管分享摘要。