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 .”
- “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).
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.
Outputs (deliverables)
Produce a Cross-Functional Collaboration Pack (Markdown in-chat, or files if requested) in this order:
- Mission Charter (goals, success metrics, scope, constraints, timeline)
- Stakeholder & Incentives Map (owners, approvers, incentives/risks, comms needs)
- Roles & Expectations Contract (responsibilities, expectations matrix, decision rights, escalation triggers)
- Operating Cadence & Communication Plan (meetings, async updates, doc hub, comms to stakeholders)
- Decision Log (initial) + Decision Protocol (what decisions are needed, who decides, how captured)
- Collaboration Norms (conflict protocol + credit/recognition plan)
- Risks / Open questions / Next steps (always included)
Templates: references/TEMPLATES.md
Workflow (7 steps)
1) Define the mission (and the collaboration mode)
- 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.
2) Map the full cross-functional system (people + incentives)
- 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)
- 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)
- 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)
- 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)
- 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)
- 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.
Quality gate (required)
- Run references/CHECKLISTS.md and score with references/RUBRIC.md before finalizing.
- Always include: Risks, Open questions, Next steps.
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---2name: cross-functional-collaboration3description: Lead cross-functional collaboration by producing a Cross-Functional Collaboration Pack (mission charter, stakeholder/incentives map, roles & expectations contract, operating cadence, decision log, conflict + credit norms). Use for cross-functional collaboration, working with engineering, working with design, reducing execution friction.4---5
6# Cross-functional Collaboration
7
8## Scope
9
10**Covers**
11- Leading a cross-functional initiative (Product/Engineering/Design/Data/Marketing/Ops/etc.)
12- Turning “we’re misaligned” into explicit **goals, roles, decisions, and operating cadence**
13- Reducing rework and conflict via **shared artifacts** (docs/prototypes) and clear decision rights
14- Building trust through **conflict norms** and **credit/recognition** practices
15
16**When to use**
17- “We keep thrashing between PM/Eng/Design—set up a better way of working.”
18- “Create a collaboration charter: roles, responsibilities, decision-making, and cadence.”
19- “We need to work better with Engineering/Design/Data on <initiative>.”
20- “Our cross-functional project is slow due to unclear ownership and decisions.”
21
22**When NOT to use**
23- You need to define the underlying product problem first (use `problem-definition`).
24- You need a full decision process for a single high-stakes decision (use `running-decision-processes`).
25- The issue is primarily a performance or accountability problem with an individual (use `having-difficult-conversations`).
26- You only need a timeline/milestone plan (use `managing-timelines`).
27
28## Inputs
29
30**Minimum required**
31- Initiative summary: what it is, why now, desired outcomes, and timeframe
32- Functions/teams involved + key stakeholders (including any required subject matter experts)
33- Current symptoms: where collaboration is breaking down (examples help)
34- Constraints: deadlines, non-negotiables, policies/compliance, customer commitments
35
36**Missing-info strategy**
37- Ask up to 5 questions from [references/INTAKE.md](references/INTAKE.md).
38- If answers aren’t available, proceed with explicit assumptions and label unknowns.
39
40## Outputs (deliverables)
41
42Produce a **Cross-Functional Collaboration Pack** (Markdown in-chat, or files if requested) in this order:
431) **Mission Charter** (goals, success metrics, scope, constraints, timeline)
442) **Stakeholder & Incentives Map** (owners, approvers, incentives/risks, comms needs)
453) **Roles & Expectations Contract** (responsibilities, expectations matrix, decision rights, escalation triggers)
464) **Operating Cadence & Communication Plan** (meetings, async updates, doc hub, comms to stakeholders)
475) **Decision Log (initial) + Decision Protocol** (what decisions are needed, who decides, how captured)
486) **Collaboration Norms** (conflict protocol + credit/recognition plan)
497) **Risks / Open questions / Next steps** (always included)
50
51Templates: [references/TEMPLATES.md](references/TEMPLATES.md)
52
53## Workflow (7 steps)
54
55### 1) Define the mission (and the collaboration mode)
56- **Inputs:** Initiative summary; timeline; constraints.
57- **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).
58- **Outputs:** Mission Charter (draft).
59- **Checks:** A cross-functional partner can restate the mission, success metric(s), and constraints without you in the room.
60
61### 2) Map the full cross-functional system (people + incentives)
62- **Inputs:** Org context; teams/functions; known stakeholders.
63- **Actions:** Identify owners, approvers, contributors, and informed stakeholders. Capture incentives, concerns, and “hidden constraints.” Ensure required subject matter experts are included.
64- **Outputs:** Stakeholder & Incentives Map + “missing seats” list.
65- **Checks:** No surprise approvers; every team that must execute or sign off is represented.
66
67### 3) Make expectations explicit (write the contract)
68- **Inputs:** Stakeholder map; friction examples.
69- **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.
70- **Outputs:** Roles & Expectations Contract (v1).
71- **Checks:** Each function can answer: “What do I own? What do I expect of others? What decisions can I make?”
72
73### 4) Establish a shared language via artifacts (prototype-first when helpful)
74- **Inputs:** Initiative stage; ambiguity areas; tooling constraints.
75- **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.
76- **Outputs:** Artifact plan + first prototype milestone (or “working slice” plan).
77- **Checks:** At least one artifact concretely reduces ambiguity (fewer interpretation disputes).
78
79### 5) Design the operating cadence (meetings, async, and decision logging)
80- **Inputs:** Timeline; time zones; team size; existing rituals.
81- **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).
82- **Outputs:** Operating Cadence & Communication Plan + Decision Log (seeded with first decisions).
83- **Checks:** Cadence is sustainable and oriented to **outcomes, decisions, and risks** (not “status theater”).
84
85### 6) Set norms for conflict and credit (trust mechanics)
86- **Inputs:** Known tensions; cultural context; prior failure modes.
87- **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).
88- **Outputs:** Collaboration Norms (Conflict Protocol + Credit/Recognition Plan).
89- **Checks:** Norms are specific enough to follow in a real disagreement and in exec/customer updates.
90
91### 7) Quality gate + launch (and monitoring plan)
92- **Inputs:** Draft pack.
93- **Actions:** Run the checklist and rubric. Finalize the pack. Propose the first 1–2 “health checks” to update roles/cadence based on reality.
94- **Outputs:** Final Pack + rubric score + Risks/Open questions/Next steps.
95- **Checks:** If rubric score is low, do one more intake round (max 5 questions) and revise.
96
97## Quality gate (required)
98- Run [references/CHECKLISTS.md](references/CHECKLISTS.md) and score with [references/RUBRIC.md](references/RUBRIC.md) before finalizing.
99- Always include: **Risks**, **Open questions**, **Next steps**.
100
101## Examples
102
103**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.”
104Expected: mission charter, stakeholder map, expectations contract, operating cadence, decision protocol/log, conflict + credit norms.
105
106**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.”
107Expected: decision rights/escalation triggers, seeded decision log, prototype/working-slice plan, and a lightweight cadence.
108
109**Boundary example:** “Help me convince another team to do what I want.”
110Response: 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`.
111
majiayu000