Back to Details

product-launch

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Product launch

产品发布

Build a launch around a specific audience, credible claim, working conversion path, and learning loop.
围绕明确的受众、可信的主张、有效的转化路径和学习闭环来构建发布方案。

Choose a mode

选择模式

  • Strategy: positioning, audience access, channel choices, timeline, and risks.
  • Implementation: build only the required site, waitlist, tracking, or launch assets.
  • Audit/dry run: test readiness, claims, links, conversion, instrumentation, and operations.
  • Postmortem: explain results, update positioning, and define follow-up experiments.
Scale the artifact to the launch. A small beta does not need a multiweek war room or a large GTM document.
  • 策略： 定位、受众触达、渠道选择、时间线和风险。
  • 实施： 仅构建所需的网站、waitlist、追踪配置或发布素材。
  • 审计/演练： 测试准备就绪程度、主张、链接、转化、埋点和运营情况。
  • 复盘： 解释结果、更新定位并定义后续实验。
根据发布规模调整交付物。小型 beta 不需要持续数周的作战室或大型 GTM 文档。

Workflow

工作流

  1. Inspect product briefs, site/repository, analytics, waitlist, audience evidence, assets, platform accounts, and prior launches before asking questions.
  2. Establish stage, audience, problem, proof, target action, launch date/window, owner, budget, constraints, existing reach, and decision metrics. Ask only for missing inputs that change the plan.
  3. Research current alternatives, audience language, communities, channel rules, and relevant calendars from primary or first-party sources where possible. Date platform-sensitive findings. Do not claim knowledge of opaque ranking algorithms.
  4. Write plain-language positioning: for whom, what changes, mechanism, why now, and why credible. Remove unsupported claims.
  5. Choose a launch type and few channels based on audience access and product fit. For each, state format, owner, timing rationale, response plan, policy constraints, conversion path, and metric.
  6. Inventory the smallest asset set needed. Treat landing pages, demos, screenshots, support docs, share artifacts, tracking links, and product changes as dependencies only when the chosen plan requires them.
  7. Test the conversion path end to end. If demand capture is required, follow the safe waitlist guidance.
  8. Instrument source attribution, activation, conversion, follow-up, and failure states. Define what decision each metric supports and distinguish directional attribution from causal proof.
  9. Run a dry launch: links, forms, email delivery, mobile, accessibility, analytics, support, rollback, incident ownership, and platform-policy checks.
  10. Operate the launch, then review at an appropriate early window and after enough time for the target behavior to mature.
  1. 在提问之前，检查产品简报、网站/代码仓库、分析数据、waitlist、受众证据、素材、平台账户和以往发布。
  2. 确定发布阶段、受众、问题、证据、目标动作、发布日期/时间窗口、负责人、预算、限制、现有触达范围和决策指标。只询问那些缺失后会改变计划的信息。
  3. 尽可能从一手来源或第一方来源研究当前替代方案、受众用语、社群、渠道规则和相关日程。对受平台政策影响且敏感的信息标注日期。不得声称了解不透明的排名算法。
  4. 用通俗易懂的语言写明定位：面向谁、带来什么改变、作用机制、为何此时以及为何可信。删除缺乏支持的主张。
  5. 根据受众触达能力和产品契合度选择发布类型和少量渠道。对每个渠道说明内容形式、负责人、时机理由、响应计划、政策限制、转化路径和指标。
  6. 盘点所需的最小素材集。仅在选定方案确有需要时，才将落地页、演示、截图、支持文档、分享素材、跟踪链接和产品变更视为依赖项。
  7. 端到端测试转化路径。如果需要收集用户需求，请遵循 waitlist 安全指南。
  8. 对来源归因、激活、转化、后续行为和失败状态进行埋点。明确每项指标支持什么决策，并区分方向性归因与因果证明。
  9. 进行发布预演：检查链接、表单、邮件送达、移动端、无障碍、分析工具、支持、回滚、事件处置负责人和平台政策。
  10. 执行发布，然后在合适的早期时间点进行复盘，并在目标行为有足够时间成熟后再次复盘。

Load conditional references

加载条件性引用

  • Read launch strategy for positioning, channel selection, asset planning, operations, and postmortems.
  • Read waitlist implementation only when implementing or auditing signup capture.
References do not determine interaction or output; this file is authoritative.
  • 阅读 发布策略，了解定位、渠道选择、素材规划、运营和复盘。
  • 仅在实施或审计注册信息收集时阅读 waitlist 实施。
引用文件不决定交互或输出；本文件为准。

Output contract

输出约定

Return only mode-relevant sections:
  • launch context and evidence/assumption ledger;
  • positioning and target action;
  • channel plan and asset dependencies;
  • implementation changes and conversion-path notes;
  • measurement and attribution plan;
  • dry-run findings, operations, rollback, and owners;
  • follow-up schedule or postmortem with decisions.
仅返回与所选模式相关的部分：
  • 发布背景与证据/假设台账；
  • 定位与目标动作；
  • 渠道计划与素材依赖项；
  • 实施变更与转化路径说明；
  • 衡量与归因方案；
  • 演练发现、运营、回滚和负责人；
  • 后续时间安排或包含决策的复盘。

Verify

验证

  • Audience and channel choices are supported by evidence or labeled assumptions.
  • Material claims have proof and current platform rules are sourced/date-stamped.
  • Every public link and primary conversion path works in the deployed environment.
  • Signup, confirmation, attribution, activation, and failure events are observed.
  • Privacy, consent, security, accessibility, and suppression/retention requirements are addressed.
  • Owners, incident path, rollback, and follow-up decisions are explicit.
  • 受众和渠道选择有证据支持，或已明确标注为假设。
  • 实质性主张有证据支持，且当前平台规则注明了来源/日期。
  • 每个公开链接和主要转化路径都能在已部署环境中正常工作。
  • 已观测到注册、确认、归因、激活和失败事件。
  • 已处理隐私、用户同意、安全、无障碍以及联系抑制/数据保留要求。
  • 明确指定负责人、事件响应路径、回滚方案和后续决策。