Writing/UX Architecture/№05
Essay
Essays on design architecture
In large-scale enterprise environments, a fundamental tension exists between scale and speed. Here is how the friction between platform and divisional UX actually plays out — and what to do about it.
Read
In large-scale enterprise environments, a fundamental tension exists between scale and speed. This friction typically manifests as a structural division between two distinct design roles: Platform UX Designers and Divisional UX Designers.
While both roles operate within a user-centered mandate, their success is measured against opposing priorities. Understanding this dynamic is the key to unlocking both consistency and product velocity.
01
Platform designers own the design system, the component library, and the shared foundations that every product team inherits. Their mandate is coherence at scale — one visual language, one interaction model, one accessibility baseline across dozens of products.
They are measured on adoption, consistency, and the reduction of divergent one-off patterns. Their instinct is to standardize; their fear is fragmentation.
02
Divisional designers work inside a specific product line with a specific user base and a specific commercial target. Their mandate is velocity and fit — solving the exact problem in front of the exact user without waiting for the platform roadmap to catch up.
They are measured on conversion, task completion, and shipped features. Their instinct is to extend or bend the system; their fear is being blocked by governance.
03
A healthy design system moves through stages: from prescriptive rules that guarantee consistency, to a shared vocabulary that enables debate, to an open contribution model where divisional teams upstream their own solutions. The friction is not a bug — it is the mechanism by which the system learns.
04
Federated Contribution Model: allow divisional designers to submit vetted, well-documented components back into the global library. This removes the platform team's gatekeeper bottleneck and ensures the system adapts dynamically to real-world edge cases.
Proactive Exception Architecture: build structural rules directly into the UI framework that account for high data density, extreme text length variances during multi-market localization, and strict accessibility standards. Designing for exceptions protects screen real estate while maintaining system compliance.
Next