Cross-functional work fails in predictable ways: nobody named the handoff, “done” meant two different things, and escalation waited until people were already frustrated. Soft advice about empathy helps after the interface is defined. It rarely fixes an undefined interface by itself.
This is the How Departments Work Together function hub. Use it when the problem sits between teams: marketing and sales, ops and finance, product and CS, HR and managers. The mandatory first module is a one-page interface card. Relationships still matter. Sequence tools before vibe.
Sibling literacy: How HR works, Finance for non-finance managers, How sales works. Stage context: New Hire, IC, New Manager, Director / VP.
Who this hub is for
Stay here if you are stuck on a handoff, kicking off a multi-team project, clarifying decision rights, or de-escalating a conflict that is really an ownership gap.
Go to a function hub instead if the gap is literacy inside one domain (leave routing, P&L translation, pipeline words). Come back here to design the recurring interface once literacy exists.
Company design still wins: matrix vs. startup vs. agency models differ. Worksheets here are portable practice, not universal org policy.
The insight: interface design, not personality
Frame cross-functional work as interface design, not personality. Before tips on “building relationships,” write down: what we hand off, what “done” means, who decides, who is informed, and how we escalate. Most pain is an undefined interface wearing a people costume.
Module 1 (mandatory): One-page interface card
Copy for each recurring handoff or project boundary. Fill with partners in a working session, not alone in a doc nobody saw.
| Field | Your answers |
|---|---|
| Handoff | What artifact or state moves from Team A to Team B? __ |
| Done means | Acceptance checks both sides agree on (bullets): __ |
| Who decides | Final call on scope / date / exception: __ |
| Informed | Who gets async updates (not necessarily a vote): __ |
| Escalation | If stuck N days or after X attempts: who, via what channel: __ |
| Cadence | Meeting vs async update rhythm: __ |
| Systems of record | Ticket, CRM, doc home: __ |
Optional RACI overlay (not mandatory policy): Responsible (does the work), Accountable (one owner of outcome), Consulted, Informed. If two people claim Accountable, stop and fix that before launching.
Read next after Module 1: run a live 30-minute working session with the other team using this card. Only then open soft collaboration articles.
Module 2: Cross-functional glossary
| Term | Plain meaning |
|---|---|
| Handoff | A defined transfer of work with acceptance criteria. |
| Stakeholder | Someone affected by or needed for the outcome; map interests, not gossip. |
| Decision rights | Who can say yes/no on which choices. |
| SLA (as workplace norm) | A service expectation teams agree to operate against. Not automatically a legal contract. |
| Working group | People doing the work. |
| Steering group | People unblocking decisions and priorities (keep small). |
| RACI | A simple responsibility map; useful when ownership is fuzzy, not a religion. |
| Escalation | Moving a stuck decision up a named path on purpose, early enough to help. |
Module 3: Which function owns this? decision tree
- People process, leave, hiring process, ER risk? Start How HR works Module 1, then HR partners.
- Budget, forecast, P&L, invoices, expense policy? Start Finance for non-finance managers Module 1.
- Pipeline stage, commit language, closed-won handoff? Start How sales works Module 1.
- Recurring handoff between two teams with unclear “done”? Stay here; finish Module 1 interface card.
- Fuzzy strategy or priorities inside one team? Use stage hubs and Strategy your team can execute.
- Meeting load is the symptom? Fix the interface first, then How to run effective meetings and Async updates instead of meetings.
Module 4: Kickoff agenda template (cross-functional)
Timebox 45-60 minutes. Capture decisions in writing the same day.
- Outcome in one sentence
- Out of scope (explicit)
- Interface card draft (Module 1) filled live
- Dependencies and dates (owners named)
- Decision rights for the top three choices
- Communication plan (async default; meeting purpose if any)
- Escalation path and “stuck” definition
- Next check-in and artifact locations
Module 5: Escalation ladder worksheet (blank)
Company-agnostic. Fill with real names.
| Level | Who | When to use | Channel |
|---|---|---|---|
| Team to team | __ | First attempts failed with facts shared | __ |
| Manager to manager | __ | Decision rights unclear or capacity conflict | __ |
| Director / sponsor | __ | Cross-org priority call needed | __ |
| Stop / reset | __ | Goals conflict and no owner can resolve | __ |
Escalation is a design feature. Silence until a blow-up is not politeness; it is missing interface work.
Ordered read-first paths by situation
Complete Module 1 for the live interface before deep reading.
Situation A: Broken or missing handoff
- Interface card with both teams
- Sales to delivery / CS handoff if revenue-to-delivery is the seam
- Delegation without dumping when “handoff” was actually a dump
- Async updates instead of meetings for status without theater
Situation B: Fuzzy decision rights
- Interface card “who decides” row first
- Strategy your team can execute
- Skip-level meetings when signal is trapped under layers (use carefully)
- Stage hub for your altitude: New Manager or Director / VP
Situation C: Conflict between teams
- Separate personality from interface: rewrite Module 1 together
- Difficult conversation scripts at work for the live talk
- Escalate with Module 5 if decision rights sit above you
- Pull function hubs if literacy (HR/Finance/Sales) is the hidden gap
Situation D: New cross-functional project kickoff
- Module 4 agenda + Module 1 card
- How to run effective meetings
- Function hubs for partner literacy before week two surprises
Sample starts (illustrative, no success rates)
- Marketing ↔ sales handoff: Module 1 on lead/opportunity definitions and “done” for accepted pipeline → How sales works vocabulary card → async weekly artifact instead of blame meetings.
- Ops ↔ finance budget change: Module 1 on who owns the number and what “approved” means → Finance for non-finance managers three-map worksheet → escalation ladder if Finance and Ops managers disagree.
Collaboration theater vs. operating agreements
Theater: recurring meetings with no decisions, shared folders nobody owns, and “we should sync more.” Operating agreement: a filled interface card, named Accountable, written “done means,” and an escalation path used early. Prefer agreements.
Asking another department for help
- Send the request template idea from sales literacy: decision needed, deadline, impact, single owner.
- Point to the system of record.
- Offer the acceptance checks you will use.
- Do not open a ticket black hole without a human owner and a date.
- If remote/hybrid: document the interface first; meet second to resolve conflicts in the doc, not to invent the doc live without prep.
Common failure modes this path surfaces early
- Dual goals with one shared deadline and no Accountable
- Late involvement of Finance, Legal, or Sales after commitments are public
- “Done” defined only by the sending team
- Escalation treated as betrayal instead of design
- Personality coaching used to avoid naming a decision owner
When to stop reading and facilitate live
If you already know the teams and the pain is active, facilitate Module 1 in a working session this week. Reading more collaboration essays will not create an owner. Use articles to prepare language, then run the card.
CTA: stage hubs and sibling function hubs
Stage hubs: New Hire (learn the map) · Individual Contributor (influence without authority) · New Manager (design team-to-team interfaces) · Director / VP (portfolio interfaces)
Sibling function hubs: How HR works · Finance for non-finance managers · How sales works
Practice cluster: How to run effective meetings · Async updates instead of meetings · Delegation without dumping · Strategy your team can execute · Difficult conversation scripts at work · Skip-level meetings