THE SHORT ANSWER
Create a shared outcome, define each function's contribution and constraints, map dependencies, assign decision rights, establish a common operating rhythm and escalate unresolved priority conflicts. Influence grows through clarity, evidence, reliability and understanding other functions' incentives.
Functions optimize different parts of the system
Marketing may seek demand, sales may seek near-term conversion, product may protect coherence, technology may protect reliability and operations may protect repeatability. A shared goal must make trade-offs visible rather than pretending these concerns are identical.
Create a lightweight team charter
| Element | Question |
|---|---|
| Outcome | What result belongs to the team as a whole? |
| Scope | What is inside and outside this work? |
| Decision rights | Who recommends, decides and must be consulted? |
| Dependencies | Which handoff can block another function? |
| Cadence | When are progress, risk and decisions reviewed? |
| Escalation | Who resolves competing priorities? |
Build influence without pretending authority
- Understand each function's objective and constraint.
- Bring evidence and a clear request.
- Keep commitments and expose delays early.
- Translate specialist language into shared consequences.
- Escalate the unresolved decision, not the character of another team.
Inspect the whole journey
A local improvement can move delay or risk to another function. Map the customer or operating journey end to end and measure the shared outcome.
The existing guide to working with developers provides a focused product-and-technology collaboration example.
Evidence & context: GOV.UK Service Manual · National Academies of Sciences, Engineering, and Medicine
Sources & further reading
- The Science and Practice of Team Science
National Academies of Sciences, Engineering, and Medicine. A 2025 consensus study on varied, interdependent and cross-disciplinary teams. Its findings emphasize context, goals, coordination, leadership and collaboration; research-team settings require adaptation to other workplaces.
- Map and understand a user's whole problem
GOV.UK Service Manual. Public-service guidance on mapping journeys, collaborating across boundaries and locating pain points. The module adapts the method to business workflows.
Examples and exercises are illustrative unless attributed to a source. No independent expert review is claimed.
A correction, a counterexample or an experience worth sharing?
Join the conversation ↗