Interfaces between teams beat shared Slack channels

Cross-team collaboration fails when interfaces are social instead of technical: Slack threads instead of contracts, heroes instead of owners.

I will stay on this thesis — no adjacent manifesto, no tour of every neighboring discipline.

On Interfaces between teams beat shared Slack channels, publish the interface: inputs, outputs, done criteria, and who gets paged. More Slack is not a substitute for a contract, and hero translators are a continuity risk.

Measure what you claim to care about. If Interfaces between teams beat shared Slack channels only appears in kickoff slides and never in review, incident, or planning artifacts, it is branding. Put a verification signal where people already look.

How it actually works

Start with controls that are boring on purpose: written owners, verification, and a path for the next person.

Publish “done” definitions across teams before joint work starts — especially for platform and product hand-offs. Ambiguous done is how resentments form.

Working agreements that age well name how to change the agreement. Static culture docs become wallpaper within a quarter.

Conflict as a design input means capturing the disagreement as constraints and options. Personality narratives are a dead end; interface narratives ship.

Escalation paths that rely on knowing the right person are outages waiting for vacation. Publish who decides, by when, and what “stuck” means.

Write the boundary as an API: inputs, outputs, latency expectations, error semantics, and who gets paged. If you cannot write that page, you do not have alignment — you have hope.

Joint incidents need a single incident commander even when two orgs are involved. Dual command is how pages bounce and customers wait.

Write one page while the decision is still warm — context, options, choice, owner, revisit date. Verbal alignment on Interfaces between teams beat shared Slack channels evaporates under ordinary calendar pressure, and Slack archaeology is a poor substitute for a decision record.

Where this shows up

A working group creates a Slack channel for “alignment.” Six weeks later the channel is noise and decisions still live in side DMs. Delete the channel or convert it into a decision log with owners.

Product wants a feature; platform wants stability. Without a capacity envelope and SLO, every conversation becomes moral. With them, the conversation becomes scheduling and tradeoffs.

A hand-off ticket says “ready for platform.” Platform discovers missing authz assumptions in production. Ready now means: runbook, rollback, and a joint drill — not a status emoji.

Tradeoffs

Strict ownership can feel cold. Ambiguous ownership feels warm until the page. Prefer clear primary owners with named collaborators.

Fewer meetings feel risky to managers who equate presence with control. Measure outcomes and escaped misunderstandings instead of seat time.

Written interfaces cost an afternoon. Unwritten interfaces cost a quarter. Choose deliberately.

Resist the urge to expand scope into neighboring slogans. If a control does not make Interfaces between teams beat shared Slack channels more operable for the next person, leave it for another note. Dilution is how coherent essays become stitched scrapbooks.

For Interfaces between teams beat shared Slack channels, the inheritance test is blunt: after a week, can someone outside the original room explain what changed, who owns it, and how you will know if it breaks? If the answer depends on hallway memory, you still have a story — not a practice.

Failure modes

Each of these is a missing control, not a personality problem:

• Meetings used as a substitute for written interfaces — everyone left “aligned,” nobody can explain ownership later.
• Roadmaps that look shared but hide capacity fiction — platform work scheduled as free.
• Hand-offs that drop context so the receiving team re-learns the sender’s scars.
• Hero bridges that mask missing contracts until attrition.

What to do this month

• When stuck: write the disagreement as options with tradeoffs; meet only to choose.
• For every shared system: name a primary owner per failure mode.
• Before joint delivery: publish the interface doc and the escalation path.

Replace status karaoke with a short decision doc: context, options, choice, date, owner. Status belongs in a dashboard or a running doc; meetings are for conflict and irreversible choices.

Treat conflict as design input. Resolve it in the interface, not in personality. Productive disagreement about SLOs and capacity envelopes beats political disagreement about who is more strategic.

Hand-offs that preserve context include decision history, open risks, and the last failed assumption — not only a ticket ID. Context loss is a defect.

Shared roadmaps without shared capacity envelopes are fiction. Publish what each team can actually carry before you celebrate alignment.

Prefer async artifacts for continuity. Use meetings when the decision is contested or irreversible. Calendar density is not collaboration quality.

The meeting you should replace with a doc is the one that only redistributes status. Keep the meeting that resolves contested decisions — and require options in writing before it starts.

Hero bridges — one person who translates between teams — feel invaluable until they burn out and the org discovers it had no interface. Document what the hero knows while they are still standing.

Two orgs share on-call for a boundary service. Without a primary for each failure mode, pages bounce. Shared ownership without primaries is a page-routing bug.

Close

Protocols beat vibes. Write the boundary, name the owner, make failure legible.

Carry the claim as a habit, not a brand: Interfaces between teams beat shared Slack channels either compounds ownership or it was applause.