Back to Details

cross-functional-collaboration

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Cross-functional Collaboration

跨职能协作

Scope

适用范围

Covers
  • Leading a cross-functional initiative (Product/Engineering/Design/Data/Marketing/Ops/etc.)
  • Turning “we’re misaligned” into explicit goals, roles, decisions, and operating cadence
  • Reducing rework and conflict via shared artifacts (docs/prototypes) and clear decision rights
  • Building trust through conflict norms and credit/recognition practices
When to use
  • “We keep thrashing between PM/Eng/Design—set up a better way of working.”
  • “Create a collaboration charter: roles, responsibilities, decision-making, and cadence.”
  • “We need to work better with Engineering/Design/Data on <initiative>.”
  • “Our cross-functional project is slow due to unclear ownership and decisions.”
When NOT to use
  • You need to define the underlying product problem first (use 
    problem-definition
    ).
  • You need a full decision process for a single high-stakes decision (use 
    running-decision-processes
    ).
  • The issue is primarily a performance or accountability problem with an individual (use 
    having-difficult-conversations
    ).
  • You only need a timeline/milestone plan (use 
    managing-timelines
    ).
涵盖场景
  • 主导跨职能项目（产品/工程/设计/数据/营销/运营等）
  • 将“我们目标不一致”的状态转化为明确的目标、角色、决策和运作节奏
  • 通过共享工件（文档/原型）和清晰的决策权限减少返工与冲突
  • 通过冲突准则和表彰/认可机制建立信任
适用时机
  • “产品经理/工程师/设计师之间总是反复拉扯——需要建立更顺畅的协作方式。”
  • “创建一份协作章程：明确角色、职责、决策流程和运作节奏。”
  • “我们需要在<项目>上与工程/设计/数据团队更好地协作。”
  • “我们的跨职能项目因职责和决策不清晰而进展缓慢。”
不适用时机
  • 你需要先定义核心产品问题（请使用
    problem-definition
    工具）。
  • 你需要针对单个高风险决策制定完整的决策流程（请使用
    running-decision-processes
    工具）。
  • 问题主要是个人绩效或问责问题（请使用
    having-difficult-conversations
    工具）。
  • 你只需要时间线/里程碑计划（请使用
    managing-timelines
    工具）。

Inputs

输入要求

Minimum required
  • Initiative summary: what it is, why now, desired outcomes, and timeframe
  • Functions/teams involved + key stakeholders (including any required subject matter experts)
  • Current symptoms: where collaboration is breaking down (examples help)
  • Constraints: deadlines, non-negotiables, policies/compliance, customer commitments
Missing-info strategy
  • Ask up to 5 questions from references/INTAKE.md.
  • If answers aren’t available, proceed with explicit assumptions and label unknowns.
最低必填项
  • 项目摘要：项目内容、启动原因、预期成果和时间范围
  • 涉及的职能/团队 + 关键利益相关者（包括所需的主题专家）
  • 当前协作痛点：协作出现问题的具体场景（举例说明更佳）
  • 约束条件：截止日期、不可协商事项、政策/合规要求、客户承诺
信息缺失处理策略
  • 从[references/INTAKE.md]中最多提出5个问题。
  • 如果无法获取答案，基于明确的假设推进，并标注未知信息。

Outputs (deliverables)

输出成果（交付物）

Produce a Cross-Functional Collaboration Pack (Markdown in-chat, or files if requested) in this order:
  1. Mission Charter (goals, success metrics, scope, constraints, timeline)
  2. Stakeholder & Incentives Map (owners, approvers, incentives/risks, comms needs)
  3. Roles & Expectations Contract (responsibilities, expectations matrix, decision rights, escalation triggers)
  4. Operating Cadence & Communication Plan (meetings, async updates, doc hub, comms to stakeholders)
  5. Decision Log (initial) + Decision Protocol (what decisions are needed, who decides, how captured)
  6. Collaboration Norms (conflict protocol + credit/recognition plan)
  7. Risks / Open questions / Next steps (always included)
Templates: references/TEMPLATES.md
制作一份跨职能协作工具包（聊天内以Markdown格式呈现，或按要求生成文件），内容顺序如下：
  1. 任务章程（目标、成功指标、范围、约束条件、时间线）
  2. 利益相关者与激励地图（负责人、审批人、激励/风险、沟通需求）
  3. 角色与期望协议（职责、期望矩阵、决策权限、升级触发条件）
  4. 运作节奏与沟通计划（会议安排、异步更新、文档中心、利益相关者沟通方式）
  5. 初始决策日志 + 决策流程（所需决策内容、决策人、记录方式）
  6. 协作准则（冲突处理流程 + 表彰/认可计划）
  7. 风险/待解决问题/下一步行动（必须包含）
模板：[references/TEMPLATES.md]

Workflow (7 steps)

工作流程（7步）

1) Define the mission (and the collaboration mode)

1) 定义任务（及协作模式）

  • Inputs: Initiative summary; timeline; constraints.
  • Actions: Clarify the mission, success metrics, and what “done” means. Name the collaboration mode (project/sprint vs ongoing interface) and the stakes (why this matters now).
  • Outputs: Mission Charter (draft).
  • Checks: A cross-functional partner can restate the mission, success metric(s), and constraints without you in the room.
  • 输入：项目摘要；时间线；约束条件。
  • 行动：明确任务、成功指标以及“完成”的定义。确定协作模式（项目/迭代 vs 持续协作）和重要性（为何当前启动此项目）。
  • 输出：任务章程（草稿）。
  • 检查标准：无需你在场，跨职能伙伴也能清晰复述任务、成功指标和约束条件。

2) Map the full cross-functional system (people + incentives)

2) 绘制完整跨职能系统地图（人员 + 激励）

  • Inputs: Org context; teams/functions; known stakeholders.
  • Actions: Identify owners, approvers, contributors, and informed stakeholders. Capture incentives, concerns, and “hidden constraints.” Ensure required subject matter experts are included.
  • Outputs: Stakeholder & Incentives Map + “missing seats” list.
  • Checks: No surprise approvers; every team that must execute or sign off is represented.
  • 输入：组织背景；涉及的团队/职能；已知利益相关者。
  • 行动：确定负责人、审批人、贡献者和需知情的利益相关者。记录激励因素、顾虑和“隐性约束”。确保涵盖所需的主题专家。
  • 输出：利益相关者与激励地图 + “缺失参与方”清单。
  • 检查标准：无意外的审批人；所有必须执行或签字确认的团队均已纳入。

3) Make expectations explicit (write the contract)

3) 明确期望（制定协议）

  • Inputs: Stakeholder map; friction examples.
  • Actions: Run an expectations exercise (each function writes expectations of the others). Convert to a clear responsibilities map, decision rights, escalation triggers, and review cadence.
  • Outputs: Roles & Expectations Contract (v1).
  • Checks: Each function can answer: “What do I own? What do I expect of others? What decisions can I make?”
  • 输入：利益相关者地图；协作摩擦案例。
  • 行动：开展期望对齐练习（各职能团队写下对其他团队的期望）。将其转化为清晰的职责地图、决策权限、升级触发条件和评审节奏。
  • 输出：角色与期望协议（第一版）。
  • 检查标准：每个职能团队都能回答：“我负责什么？我对其他团队的期望是什么？我可以做出哪些决策？”

4) Establish a shared language via artifacts (prototype-first when helpful)

4) 通过工件建立共同语言（必要时优先原型）

  • Inputs: Initiative stage; ambiguity areas; tooling constraints.
  • Actions: Choose the minimum set of shared artifacts (e.g., charter, spec/PRD, prototype, metrics definitions). Add an early “prototype or working slice” milestone when it reduces ambiguity.
  • Outputs: Artifact plan + first prototype milestone (or “working slice” plan).
  • Checks: At least one artifact concretely reduces ambiguity (fewer interpretation disputes).
  • 输入：项目阶段；模糊领域；工具约束。
  • 行动：选择最少数量的共享工件（例如章程、需求文档/产品需求文档、原型、指标定义）。当原型能减少模糊性时，添加早期的“原型或可运行切片”里程碑。
  • 输出：工件计划 + 首个原型里程碑（或“可运行切片”计划）。
  • 检查标准：至少有一个工件能切实减少模糊性（减少解读分歧）。

5) Design the operating cadence (meetings, async, and decision logging)

5) 设计运作节奏（会议、异步沟通和决策日志）

  • Inputs: Timeline; time zones; team size; existing rituals.
  • Actions: Define the cadence, update format, doc hub, and channels. Install a decision log and a lightweight decision protocol (who decides, how disagreements resolve, where decisions live).
  • Outputs: Operating Cadence & Communication Plan + Decision Log (seeded with first decisions).
  • Checks: Cadence is sustainable and oriented to outcomes, decisions, and risks (not “status theater”).
  • 输入：时间线；时区；团队规模；现有惯例。
  • 行动：定义节奏、更新格式、文档中心和沟通渠道。建立决策日志和轻量化决策流程（决策人、分歧解决方式、决策存储位置）。
  • 输出：运作节奏与沟通计划 + 已预填充初始决策的决策日志。
  • 检查标准：节奏可持续，且聚焦于成果、决策和风险（而非“状态汇报走过场”）。

6) Set norms for conflict and credit (trust mechanics)

6) 制定冲突与表彰准则（信任机制）

  • Inputs: Known tensions; cultural context; prior failure modes.
  • Actions: Define a conflict protocol (including a “Yes, and” approach to reconcile valid competing goals). Define credit/recognition practices (who presents, how you share credit, how you recognize partner work).
  • Outputs: Collaboration Norms (Conflict Protocol + Credit/Recognition Plan).
  • Checks: Norms are specific enough to follow in a real disagreement and in exec/customer updates.
  • 输入：已知矛盾点；文化背景；过往失败模式。
  • 行动：定义冲突处理流程（包括采用“是的，而且”方法协调合理的竞争目标）。制定表彰/认可机制（谁负责汇报、如何共享成果、如何认可合作伙伴的工作）。
  • 输出：协作准则（冲突处理流程 + 表彰/认可计划）。
  • 检查标准：准则足够具体，可在实际分歧和向管理层/客户汇报时遵循。

7) Quality gate + launch (and monitoring plan)

7) 质量审核 + 启动（及监控计划）

  • Inputs: Draft pack.
  • Actions: Run the checklist and rubric. Finalize the pack. Propose the first 1–2 “health checks” to update roles/cadence based on reality.
  • Outputs: Final Pack + rubric score + Risks/Open questions/Next steps.
  • Checks: If rubric score is low, do one more intake round (max 5 questions) and revise.
  • 输入：工具包草稿。
  • 行动：运行检查清单和评分标准。最终确定工具包。提出前1-2次“健康检查”计划，以便根据实际情况更新角色/节奏。
  • 输出：最终工具包 + 评分标准得分 + 风险/待解决问题/下一步行动。
  • 检查标准：如果评分较低，再进行一轮信息收集（最多5个问题）并修订。

Quality gate (required)

质量审核（必填）

  • Run references/CHECKLISTS.md and score with references/RUBRIC.md before finalizing.
  • Always include: Risks, Open questions, Next steps.
  • 在最终确定前，运行[references/CHECKLISTS.md]并使用[references/RUBRIC.md]评分。
  • 必须包含：风险、待解决问题、下一步行动。

Examples

示例

Example 1: “I’m leading a cross-functional onboarding revamp across Product/Eng/Design/Data. Create a Collaboration Pack with roles, cadence, and a decision log.”
Expected: mission charter, stakeholder map, expectations contract, operating cadence, decision protocol/log, conflict + credit norms.
Example 2: “I’m an Engineering Manager partnering with PM+Design on a platform migration. Our decisions are slow and we keep re-litigating scope—create a Collaboration Pack.”
Expected: decision rights/escalation triggers, seeded decision log, prototype/working-slice plan, and a lightweight cadence.
Boundary example: “Help me convince another team to do what I want.”
Response: this skill aligns on shared goals/constraints and decision rights; if you need a one-way persuasion narrative or exec escalation, clarify the decision and use 
running-decision-processes
or 
managing-up
.
示例1： “我正主导产品/工程/设计/数据团队的跨职能新员工入职流程改版。请创建一份包含角色、节奏和决策日志的协作工具包。”
预期输出：任务章程、利益相关者地图、期望协议、运作节奏、决策流程/日志、冲突与表彰准则。
示例2： “我是工程经理，正与产品经理+设计师合作进行平台迁移。我们的决策速度很慢，而且总是反复讨论范围——请创建一份协作工具包。”
预期输出：决策权限/升级触发条件、预填充的决策日志、原型/可运行切片计划，以及轻量化的运作节奏。
边界示例： “帮我说服另一个团队按我的要求做。”
回应：本技能用于对齐共享目标/约束条件和决策权限；如果你需要单向说服话术或向管理层升级，请明确决策内容并使用
running-decision-processes
或
managing-up
工具。