When the Domain Is Fuzzy, the UI Pays the Price

In large enterprise systems, design problems are often treated as UI or workflow issues. In practice, many of these problems originate much earlier- in unclear domain boundaries, implicit assumptions, and fragmented mental models across teams.

In this talk, I share an experience report from designing long-lived enterprise platforms at scale, where UX outcomes were directly shaped by the quality (or absence) of shared domain understanding. Working alongside product managers and engineers, I repeatedly encountered situations where design friction was not caused by poor interfaces, but by competing interpretations of the domain itself: what an “order” means, where responsibilities begin and end, and which concepts truly belong together.

From a designer’s perspective, I will walk through several real scenarios where:

ambiguous domain language led to inconsistent user experiences,

missing or misaligned bounded contexts forced design decisions downstream,

and visual artifacts became the first place where domain confusion surfaced.

This session is aimed at practitioners working in complex systems who want to better connect domain thinking with real product outcomes. It offers a design-informed lens on Domain-Driven Design, grounded in enterprise reality, trade-offs, and lessons learned the hard way.