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).