What software architecture can teach us about organisations

Architecture makes relationships visible. It tells us where responsibility sits, how change travels, and what happens when one part of a system fails. Organisations face the same questions, even when their diagrams use different labels.

Healthy boundaries enable cooperation

A boundary is useful when it lowers the cost of coordination without hiding important context. Teams, like services, need clear responsibilities and dependable interfaces—but also a way to renegotiate them when reality changes.