cross-department-translation

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Cross-Department Translation

跨部门信息转换

When to Use

适用场景

Reframe a message, spec, metric, or decision for a different internal audience
Produce dual-audience briefs (e.g., engineering detail + executive summary on one page)
Decode department jargon and unstated assumptions before handoff
Convert meeting notes into action items by owner with RACI clarity
Translate technical specs, incidents, or architecture for business stakeholders
Translate business constraints, policy, or financial limits for engineering implementation
Draft escalation summaries that each function can act on without re-interpretation
Align vocabulary across product, finance, legal, compliance, sales, ops, and actuarial threads

为不同内部受众重新梳理信息、规格、指标或决策
生成双受众简报（例如：同一页面包含工程细节+高管摘要）
在交接前解码部门术语与未明确说明的假设
将会议纪要转换为标注负责人的行动项，明确RACI职责
为业务利益相关者翻译技术规格、事件或架构内容
为工程落地转换业务约束、政策或财务限制要求
起草各职能部门无需重新解读即可执行的升级事项摘要
统一产品、财务、法务、合规、销售、运营及精算线程的词汇表述

When NOT to Use

不适用场景

Company-wide messaging strategy, launches, crisis wording, or brand voice →
```
communication-lead
```
Issue trees, business cases, operating models, or steerCo analysis without audience reframing →
```
business-consultant
```
Multi-team milestones, RAID ownership, dependency maps, launch program governance →
```
technical-program-manager
```
Contract, DPA, or legal redlines and negotiation positions →
```
commercial-counsel
```
Control mapping, audit evidence pipelines, or attestation engineering →
```
compliance-engineer
```
Actuarial engagement SOW, reserve opinions, or regulatory actuarial deliverables →
```
actuarial-consulting
```
Natural-language product localization (locale strings, RTL, cultural adaptation) → route to localization/l10n skills if present
Deep technical modeling execution (pricing triangles, IBNR) →
```
actuary
```

公司层面的 messaging 策略、发布活动、危机措辞或品牌语调 → 对接
```
communication-lead
```
无受众适配的议题树、业务案例、运营模型或SteerCo分析 → 对接
```
business-consultant
```
多团队里程碑、RAID职责、依赖关系图、发布项目治理 → 对接
```
technical-program-manager
```
合同、DPA或法务红线修订及谈判立场 → 对接
```
commercial-counsel
```
控制映射、审计证据管道或鉴证工程 → 对接
```
compliance-engineer
```
精算服务SOW、准备金意见或监管精算交付物 → 对接
```
actuarial-consulting
```
自然语言产品本地化（区域字符串、RTL、文化适配） → 若有相关技能请转至localization/l10n
深度技术建模执行（定价三角、IBNR） → 对接
```
actuary
```

Related skills

Need	Skill
Org-wide narrative, launches, crisis message packs	`communication-lead`
Strategy, business case, issue trees, operating model	`business-consultant`
Program plan, RAID, milestones, cross-team delivery	`technical-program-manager`
Requirements, BRDs, process maps for build teams	`business-analyst`
UX scope and product journeys	`product-designer`
Technical controls and audit evidence	`compliance-engineer`
Actuarial engagement framing and stakeholder packs	`actuarial-consulting`
System architecture and ADRs	`senior-system-architecture`
Commercial terms in handoff documents	`commercial-counsel`

需求	对应技能
全公司叙事、发布活动、危机消息包	`communication-lead`
战略、业务案例、议题树、运营模型	`business-consultant`
项目计划、RAID、里程碑、跨团队交付	`technical-program-manager`
面向开发团队的需求、BRD、流程图	`business-analyst`
UX范围与产品旅程	`product-designer`
技术控制与审计证据	`compliance-engineer`
精算服务框架与利益相关者资料包	`actuarial-consulting`
系统架构与ADR	`senior-system-architecture`
交接文档中的商业条款	`commercial-counsel`

Core Workflows

核心工作流程

1. Identify source and target audiences

1. 识别来源与目标受众

Source — who wrote this; what they assume the reader knows
Target — who must understand, decide, or execute
Decision or ask — one sentence: what changes if they get it right
Sensitivity — legal, regulatory, financial materiality, security, personnel

Load

references/audience_profiles_and_register.md

for register, depth, and vocabulary norms.

来源 — 内容创作者是谁；他们默认读者知晓哪些信息
目标 — 必须理解、决策或执行的对象
决策或诉求 — 一句话说明：理解到位后会带来哪些改变
敏感性 — 法务、监管、财务重要性、安全、人员相关内容

加载

references/audience_profiles_and_register.md

获取受众登记信息、深度要求与词汇规范。

2. Jargon and assumption pass

2. 术语与假设排查

Before rewriting:

Highlight terms that are department-local or overloaded (e.g., "platform," "risk," "material")
List implicit assumptions (data exists, approval granted, timeline fixed)
Flag ambiguous metrics (gross vs net, ARR vs revenue, calendar vs fiscal)
Build a mini-glossary only for terms that appear in the artifact

See
references/jargon_decoding_and_glossary.md
.

重写前需完成：

高亮部门专属或多义的术语（例如："platform"、"risk"、"material"）
列出隐含假设（数据已存在、已获批准、时间线固定等）
标记模糊指标（毛额vs净额、ARRvs收入、自然年度vs财年）
仅为文档中出现的术语制作迷你术语表

参考
references/jargon_decoding_and_glossary.md
。

3. Requirements and decision briefs

3. 需求与决策简报

Input	Typical outputs
Engineering spec / RFC	Business summary: outcome, constraints, timeline, cost/risk
Business policy / OKR	Engineering brief: acceptance criteria, non-goals, dependencies
Finance ask	Product/engineering impact: effort bands, trade-offs, measurement
Legal/compliance constraint	Implementation checklist: must/must-not, evidence needed

Use pyramid structure for executives; appendices for specialists.

See
references/requirements_and_decision_briefs.md
.

输入	典型输出
工程规格/RFC	业务摘要：成果、约束、时间线、成本/风险
业务政策/OKR	工程简报：验收标准、非目标、依赖关系
财务诉求	产品/工程影响：工作量区间、权衡方案、衡量方式
法务/合规约束	实施 checklist：必须/禁止事项、所需证据

面向高管采用金字塔结构；为专业人员添加附录。

参考
references/requirements_and_decision_briefs.md
。

4. Meeting notes and handoffs

4. 会议纪要与工作交接

Capture decisions (what was decided, not discussed)
Extract actions with one owner, due date, and definition of done
Separate FYI from needs response
Add RACI when multiple teams share work
Include open questions with who resolves them

See
references/meeting_notes_and_handoffs.md
.

记录决策内容（已确定事项，而非讨论内容）
提取行动项，明确单一负责人、截止日期与完成标准
区分仅供参考与需回复内容
多团队协作时添加RACI职责说明
包含待解决问题及负责解决的主体

参考
references/meeting_notes_and_handoffs.md
。

5. Escalation and executive summaries

5. 升级事项与高管摘要

Escalations need: situation, impact, options, recommendation, asks by role, and what not to do yet.

Keep exec sections to one screen; link detail for operators.

See
references/executive_and_escalation_summaries.md
.

升级事项需包含：现状、影响、可选方案、推荐方案、按角色划分的诉求，以及暂不执行的事项。

高管部分控制在一屏以内；为执行人员提供详细内容链接。

参考
references/executive_and_escalation_summaries.md
。

Output standards

输出标准

Lead with decision or ask for executive readers; lead with context and constraints for implementers
Define acronyms once; prefer plain language over metaphor
Separate facts, assumptions, and recommendations
Preserve numeric precision; never round material figures without stating basis
Tag sections when dual-audience:
```
## Executive
```
,
```
## Engineering
```
,
```
## Finance
```
, etc.

Flag

[LEGAL REVIEW]

[COMPLIANCE]

[FINANCE SIGN-OFF]

when content touches those domains

面向高管的内容先呈现决策或诉求；面向实施人员的内容先呈现背景与约束
首字母缩写仅定义一次；优先使用平实语言而非隐喻
区分事实、假设与建议
保留数值精度；未经说明不得对重要数据进行四舍五入
双受众内容需标注章节：
```
## Executive
```
、
```
## Engineering
```
、
```
## Finance
```
等

内容涉及相关领域时标记

[LEGAL REVIEW]

、

[COMPLIANCE]

、

[FINANCE SIGN-OFF]

When to load references

何时加载参考文档

Topic	Reference
Scope, boundaries, translation vs other skills	`references/cross_department_translation_scope.md`
Audience profiles, register, depth	`references/audience_profiles_and_register.md`
Jargon, glossaries, assumption surfacing	`references/jargon_decoding_and_glossary.md`
Specs, decisions, dual-audience briefs	`references/requirements_and_decision_briefs.md`
Notes, actions, RACI handoffs	`references/meeting_notes_and_handoffs.md`
Exec summaries and escalations	`references/executive_and_escalation_summaries.md`

主题	参考文档
范围、边界、信息转换与其他技能的区别	`references/cross_department_translation_scope.md`
受众画像、登记信息、深度要求	`references/audience_profiles_and_register.md`
术语、术语表、隐含假设挖掘	`references/jargon_decoding_and_glossary.md`
规格、决策、双受众简报	`references/requirements_and_decision_briefs.md`
纪要、行动项、RACI交接	`references/meeting_notes_and_handoffs.md`
高管摘要与升级事项	`references/executive_and_escalation_summaries.md`