Users experience the organisation that made the product.
They feel every unclear ownership boundary when two journeys do not connect. They see duplicated infrastructure as inconsistent interaction. They wait through the latency of a decision that needs five teams to agree.
Conway’s Law has a user interface
We often treat organisational design as management work and product design as craft work. At scale, that distinction becomes unhelpful.
When I led design across a portfolio of games, the recurring quality problems were rarely solved by a better critique template. They were solved by clarifying which problems belonged to the platform, which belonged to a title, and how craft leaders helped both.
At Sumo Logic, inconsistent object-management pages were not primarily a visual design issue. Multiple scrum teams were independently solving the same platform problem. A reusable framework changed both the interface and the organisational relationship around it.
Structure before ceremony
Teams under stress often add meetings. Sometimes a ritual helps. More often, the missing ingredient is one of these:
- a decision owner;
- an explicit interface between teams;
- a shared primitive;
- a quality bar people can apply without permission;
- or a feedback loop close to the consequence.
Process cannot compensate forever for unclear structure.
Org design is product design because both are acts of deciding where complexity should live — and who should have to carry it.