cross-functional-collaboration

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).
• You want to get buy-in from a specific stakeholder or exec on a one-time decision (use stakeholder-alignment).
• You want to build influence or set expectations with your own manager (use managing-up).
• You need to design recurring team ceremonies like standups, retros, or demos (use team-rituals).

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.