> Term
Organizational Interface
The formal and informal boundaries, APIs, and communication structures between different teams.
Detailed Explanation
Just as software systems have APIs to communicate, organizations have interfaces—meetings, Slack channels, Jira boards, and planning cycles. When an organizational interface is poorly defined, the teams attempting to collaborate experience the equivalent of dropped packets and integration failures. The Conway's Law states that software architecture will mirror these organizational interfaces.
Why It Matters
Failing to define clear boundaries between teams leads to duplicated work, finger-pointing during incidents, and chaotic cross-team dependencies.
Common Failure Mode
Practical Example
Production Manifestation
Two teams building the same caching layer because neither knew the other was doing it, or a severe incident caused by a team changing an internal API without notifying dependents.
Frequently Asked Questions
What is Organizational Interface in short?
The formal and informal boundaries, APIs, and communication structures between different teams.
What is the most common failure mode?
Assuming that just putting people in a shared Slack channel creates a reliable organizational interface, without establishing clear contracts or service level expectations.
AI Summary
The formal and informal boundaries, APIs, and communication structures between different teams. Failing to define clear boundaries between teams leads to duplicated work, finger-pointing during incidents, and chaotic cross-team dependencies.
