Lexicon: Isomorphic Architecture

The Origin

A synthesis of the mathematical concept of Isomorphism (a perfect point-to-point mapping between two structures) and software design. It is the direct result of Conway's Law (see today's Main Article).

The Definition

Isomorphic Architecture occurs when the design of a product perfectly mirrors the communication structure of the organization that built it.

If a company has three highly siloed, competing divisions, they will inevitably build a product with three disjointed, poorly integrated user interfaces. The software architecture is mathematically isomorphic to the corporate bureaucracy. You cannot look at the code without seeing the org chart.

The Corporate Application

Most executives try to fix bad products by hiring better designers or rewriting the code. This fails because the code is just a symptom of the structure.

The Inverse Conway Maneuver The Chief Wise Officer does not try to fight isomorphism; they use it to their advantage. This is called the "Inverse Conway Maneuver." If you want to build a fast, modular, and highly integrated product, you must first design a fast, modular, and highly integrated organizational chart.

You reverse-engineer the company to fit the desired product.

• Want microservices? Build micro-teams (squads/pods).
• Want a seamless customer journey? Put all customer touchpoints under a single, unified communication hierarchy.

The Chief Wise Officer's Rule: Stop trying to force a bureaucratic hierarchy to build agile software. The product will always regress to the shape of your communication lines. To change the architecture, change the seating chart.