Member-only story
The Cruel Truth of Conway’s Law: Why Your Architecture Always Loses to Department Walls
NGU7 min read·Just now--
Let’s step into a mid-sized fintech company undergoing digital transformation.
In the conference room, Mark, the Chief Architect, was triumphantly presenting the architecture for the next-generation “Notification Center.” The PowerPoint was filled with dazzling diagrams: Kubernetes-based cloud-native architecture, Kafka-driven event streaming, and Serverless functions. The R&D team’s eyes sparkled with excitement; this was the tech stack they had been dreaming of.
The process seemed flawless:
- The architecture design was completed, and Mark presented it at an all-hands meeting.
- Old Zhang, the head of the DevOps team, was present but spent the entire time looking at his phone, saying nothing.
- Mark interpreted Old Zhang’s silence as tacit approval and led Team A into a month-long Proof of Concept (POC).
- The POC was a resounding success, with system response times improving by tenfold.
However, just one week before the project was scheduled to go live, disaster struck.
Old Zhang sent an email copying the CTO, with just a few terse sentences: “The operations team currently consists of only three people who are only familiar…
