Good Interfaces Make Good Neighbors
In software, good interfaces allow independent systems to work together without knowing everything about one another. Organizations are not that different.
We tend to treat collaboration problems between teams as relationship problems. Sometimes they are. More often I think they are interface problems.
A good interface makes it obvious who owns what, what they are working on, and how new requests are evaluated. When those things are clear, teams can disagree without every disagreement becoming a conflict. When they aren’t, even well-intentioned people end up spending enormous energy navigating personalities and reverse-engineering decisions.
For collaboration among smaller groups to work, I think we need three things:
1. Clear ownership. Every area of work needs one person who is clearly accountable for it. That doesn’t mean they do all the work or make every decision unilaterally. It means they are responsible for making sure decisions get made and conflicts get resolved. If another team cannot figure out who has that responsibility, the interface is broken.
2. Clear and inspectable priorities. This means an actual ordered list, including the work that is currently below the line. A list containing only the things a team has decided to do is not a priority list; it is a marketing document. The tradeoffs matter just as much as the commitments because they allow dependencies to plan and people to understand why a reasonable request might not be acted on.
3. A clear process for evaluating new work. People should know where to bring a request, who will assess it, what criteria will be used, when they should expect an answer, and where that decision will be documented. A new request should not automatically become the highest priority, but it should reliably get considered. Someone may be disappointed by the answer, but they should not be confused about how the answer was reached.
Only after all three of those exist should escalation be required. Escalation is appropriate when two accountable leaders understand the same priorities and process but still believe their interpretations are in conflict. The escalation then is about understanding the priorities better, not about the specific decision in question.
Every important shared surface should publish three things: its accountable owner, its ordered priorities — including what is below the line — and its process for evaluating new work. Good interfaces won’t eliminate disagreement. They will keep ordinary disagreement from becoming organizational dysfunction.