lifecycle-mapping

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Lifecycle Mapping Frameworks Skill

生命周期映射框架Skill

When to Use

适用场景

Blueprinting onboarding, expansion, renewal, or churn-prevention journeys.
Aligning automation programs with account stages, ICP tiers, or health scores.
Auditing existing programs for gaps or over-saturation.

规划新用户引导、客户拓展、续约或防流失旅程。
使自动化程序与客户账户阶段、ICP层级或健康评分对齐。
审计现有程序，查找缺口或过度饱和问题。

Framework

框架

Stage Definition – awareness, activation, adoption, expansion, advocacy (customize per business).
Signal Library – activation events, product usage milestones, score thresholds, purchase behaviors.
Touch Architecture – how many touches per stage, channel mix, personal vs automated.
SLA Matrix – entry/exit criteria, owner, response time, success metrics.
Experiment Layer – embed test slots to iterate hooks, cadences, or offers per stage.

阶段定义——认知、激活、采用、拓展、拥护（可根据业务定制）。
信号库——激活事件、产品使用里程碑、分数阈值、购买行为。
触达架构——每个阶段的触达次数、渠道组合、人工vs自动化触达。
SLA矩阵——进入/退出标准、负责人、响应时间、成功指标。
实验层——嵌入测试位，针对每个阶段迭代钩子、节奏或优惠方案。

Templates

模板

Lifecycle heat map (stage vs metric vs automation coverage).
SLA worksheet (stage, trigger, owner, time-to-response, fallback).
Journey backlog board (ideas, prioritized, building, live, measuring).
GTM Agents Campaign Planning Checklist – captures marketing director playbook @puerto/README.md#183-212.
KPI Guardrails Sheet – track reach, engagement, SQL impact, CAC payback with min/max thresholds.
Status Packet Template – weekly single-slide update mirroring GTM Agents project-manager format @puerto/TEAM-STRUCTURE.md#193-204.

生命周期热力图（阶段vs指标vs自动化覆盖范围）。
SLA工作表（阶段、触发条件、负责人、响应时间、备选方案）。
旅程待办看板（创意、已排序、开发中、已上线、度量中）。
GTM Agents 活动规划清单——收录营销总监手册内容 @puerto/README.md#183-212。
KPI管控表——通过最小/最大阈值追踪触达量、参与度、SQL影响、CAC回收期。
状态报告包模板——每周单页更新，镜像GTM Agents项目经理格式 @puerto/TEAM-STRUCTURE.md#193-204。

Tips

小贴士

Limit simultaneous journeys per contact; define prioritization rules.
Include manual checkpoints (CSM/AE) for high-touch segments.
Document every assumption so experiments can deliberately challenge them.
Lock KPIs before build starts and refuse scope creep until metrics + owners are confirmed.
Borrow GTM Agents's cadence: Plan → Build → QA → Launch → Inspect so reporting lines know when to approve or intervene.
Pair every automation change with a "rip-cord" procedure the Sales Director or Ops Lead can trigger if leading indicators degrade.

限制每个联系人同时参与的旅程数量；定义优先级规则。
为高触达细分群体设置人工检查点（CSM/AE）。
记录所有假设，以便实验可以针对性地验证这些假设。
在开发开始前锁定KPI，在指标和负责人确认前拒绝范围蔓延。
借鉴GTM Agents的节奏：Plan → Build → QA → Launch → Inspect（规划→开发→测试→上线→检查），以便汇报线知晓何时批准或介入。
为每一项自动化变更配套“紧急终止”流程，当领先指标下滑时，销售总监或运营负责人可触发该流程。

GTM Agents Campaign Blueprint (Adopted)

已采纳的GTM Agents活动蓝图

Use this five-stage blueprint when large GTM initiatives require orchestration across demand gen, lifecycle, and RevOps teams:

Stage 1 – Briefing & Alignment
- Confirm objective, ICP, offer, timeline, and budget.
- Capture cross-functional stakeholders (Marketing Director, Sales Director, RevOps Lead) and escalation paths.
Stage 2 – Architecture
- Map lifecycle stages to channels + automations.
- Define entry/exit criteria, personalization logic, and compliance constraints.
- Assign data availability checks (Serena) + documentation pulls (Context7) if needed.
Stage 3 – Build & QA
- Break work into swimlanes (journey build, content, data, QA) and track in backlog.
- Require Playwright or similar browser QA for every externally facing experience.
Stage 4 – Launch & Monitor
- Set Day 0/Day 7 KPI guardrails (e.g., form conversion ≥ 4%, unsubscribe ≤ 0.4%).
- Route anomalies to the Operations Lead with a rollback procedure.
Stage 5 – Inspect & Iterate
- Use Sequential Thinking to run structured retros (what worked, what failed, hypotheses for next wave).
- Feed learnings back into lifecycle heat map + SLA matrix.

当大型GTM计划需要协调获客、生命周期以及RevOps团队时，使用这个五阶段蓝图：

阶段1——简报与对齐
- 确认目标、ICP、优惠方案、时间线和预算。
- 记录跨职能利益相关者（营销总监、销售总监、RevOps负责人）和升级路径。
阶段2——架构设计
- 将生命周期阶段映射到渠道+自动化程序。
- 定义进入/退出标准、个性化逻辑和合规约束。
- 如有需要，分配数据可用性检查（Serena）和文档调取（Context7）任务。
阶段3——开发与测试
- 将工作拆分为不同泳道（旅程开发、内容、数据、测试），并在待办事项中追踪。
- 所有面向外部的体验都需要使用Playwright或类似的浏览器测试工具进行测试。
阶段4——上线与监控
- 设置上线当日/第7日的KPI管控阈值（例如，表单转化率≥4%，退订率≤0.4%）。
- 将异常情况上报给运营负责人，并配套回滚流程。
阶段5——检查与迭代
- 使用Sequential Thinking进行结构化回顾（哪些有效、哪些失败、下一轮的假设）。
- 将学习成果反馈到生命周期热力图和SLA矩阵中。

Status Reporting Template

状态报告模板

Campaign: <Name>
Week Ending: <Date>

1. Highlights (wins, blockers, escalations)
2. KPI Snapshot (target vs actual vs guardrail)
3. Journey Coverage (stage, channel, live %)
4. Next 5 Actions (owner, due date)
5. Risks & Decisions Needed (include GTM Agents-style RAG)

Use this template to sync with Sales Director, Partnership Manager, and Project Manager counterparts each week.

Campaign: <Name>
Week Ending: <Date>

1. Highlights (wins, blockers, escalations)
2. KPI Snapshot (target vs actual vs guardrail)
3. Journey Coverage (stage, channel, live %)
4. Next 5 Actions (owner, due date)
5. Risks & Decisions Needed (include GTM Agents-style RAG)

使用此模板每周与销售总监、合作伙伴经理和项目经理同步。