How Conway's Law and uncoordinated squad incentives dismantle coherent user experience, and the federated governance model that preserves architectural unity across 1.5M MAU.
Conway’s Law dictates that software architectures mirror the communication structures of the organizations building them. Partitioning engineering into isolated squads produces local sprint optimization at the expense of system coherence.
Customers experience a single continuous journey, not an organizational chart. Without a shared architectural spine, squads invent conflicting navigation patterns, bespoke drawer filters, and disparate form behaviors across adjacent screens.
“Agile squad autonomy without system governance accelerates UI entropy. Squads optimize for sprint velocity; the design architect preserves cross-product integrity.”
This organizational friction was acute at Allianz Türkiye, where the flagship digital customer ecosystem (Allianz'ım) serves over 1.5 million monthly active users and $24M+ in digital premium volume:
| Autonomous Squad | Local Sprint Objective | Systemic UX Disintegration Risk |
|---|---|---|
| Health Squad | Hospital claim limit queries & provision tracking. | Introduced custom floating drawer filters unshared with other lines. |
| Life & Pension (BES) | Government contribution & fund distribution switches. | Created bespoke multi-slider inputs that broke global touch targets. |
| Motor & Casco | Emergency roadside assistance & accident triage. | Implemented fullscreen map overlays that occluded global navigation. |
| Non-Life / Property | Earthquake (DASK) & home policy endorsements. | Utilized multi-step modal dialogs instead of standardized workflows. |
| VAS Club | Partner discount campaigns & lifestyle perks. | Applied marketing-heavy typography violating core accessibility standards. |
To prevent the customer journey from fracturing into five disconnected mini-apps, we established a federated design governance model:
1. Joint Definition of Ready (DoR): Squads cannot pull user stories into active sprints unless the interaction model complies with the shared floorplan taxonomy.
2. Shared Token Kernel: All squad frontends consume a shared design token core. Individual squads customize business logic, but cannot alter typography scale, grid dimensions, or semantic colors.
3. Unified Navigation Spine: Consolidated hospital queries, pension fund switches, and roadside dispatch into a unified bottom-sheet and master-detail paradigm, deflecting 5.4 million customer inquiries away from call centers into digital self-service.
In organizations with high power distance, team members often hesitate to challenge unworkable requirements dictated by senior stakeholders. A formalized control system provides psychological safety: engineers and product managers do not argue personal opinions when the system specification itself enforces what is possible and what is prohibited.
Encoding design rules into the shared platform contract allows the organization to achieve rapid sprint execution without sacrificing user trust or architectural integrity.