When Brand, UX, UI, and Engineering Finally Speak the Same Language
The perennial debate over nomenclature in this discipline has persisted for years. UI/UX, product design, agentic experience, AX—the terminology shifts with each technological epoch, and the energy spent on these semantic distinctions might be better directed toward the substance these terms aim to capture.
Beneath this ongoing debate over terminology lies a far more pertinent question, one that the advent of AI now renders unavoidable: what transpires when brand, UX, UI, and engineering cease to function as isolated silos and instead operate as a unified, integrated system?
The result is not merely improved products and swifter delivery, but a design function that at last aligns with its own rhetoric.
For many years, the fragmentation of design into discrete specialisms represented a rational response to mounting complexity. As digital products grew more sophisticated, the labour was apportioned accordingly: researchers examined behaviour, interaction designers charted flows, UI designers built visual systems, brand teams safeguarded identity, and engineers brought design intentions to fruition. Each specialism cultivated its own lexicon, toolkit, and criteria for completion.
The difficulty did not stem from specialisation itself, but rather from what transpired at the interstices. Research insights were distilled into personas that languished, unconsulted. Brand guidelines lived in PDFs that engineering never even glanced at. UX flows, once handed to UI designers, underwent subtle metamorphoses, only to be further altered when passed to engineering. By the time a product reached its intended audience, the handiwork of four distinct disciplines was evident—unfortunately, so too were the seams between them, manifest in every interaction.
AI has not mended these fissures, but it has rendered them impossible to overlook, for the agentic systems now embedded within products are indifferent to disciplinary demarcations. An AI agent guiding a user through a complex task is, at once, a brand decision, a UX decision, a UI decision, and an engineering decision. Such an entity cannot be conjured by a committee convening at handover points; it demands a team united by a singular understanding of the product’s purpose.
This, then, is the true shift—not a matter of nomenclature, but of operating model.
The newsletter’s assertion that UX transcends mere interface is entirely correct—and, indeed, predates the current discourse on AI by some margin. User experience has always encompassed more than screens: it includes offline touchpoints, physical artefacts, service encounters, tone of voice, and the comportment of support teams in moments of crisis. This breadth is not lost through conceptual muddle, but through structural separation. When UX is partitioned from brand, engineering, and content, the holistic vision survives only in the mind of the most senior figure present, vanishing the instant they depart.
The DaS™ Holistic Experience layer addresses this challenge structurally. It articulates the bridge between strategy, design, behaviour, and customer understanding, insisting that this bridge be built before the division of disciplines, rather than retrospectively. Experience Strategy is not a document the UX team drafts and circulates; it is the common foundation from which all disciplines proceed: the rationale for the product’s existence, the interrelation of its components, and the nature of meaningful interaction across every channel and touchpoint.
This is the essence of true integration: not a perfunctory meeting where four disciplines merely report to one another, but a shared operating model in which brand, UX, UI, and engineering draw upon a common source of truth, make decisions within a unified framework, and assess their contributions against a collective outcome.
The DaS™ Definition of Ready renders this principle tangible. It is not merely a UX specification, but a collaborative artefact uniting UX, UI, development, and content—UI details and components in Figma, process notes and decisions in Confluence, and requirements and stories in Jira. Automation ensures their synchronisation. Each discipline arrives at the pivotal handover with a shared understanding of both what is being built and the rationale behind it. This is not a simple process refinement; it represents a fundamental reconfiguration of how the work itself is structured.
The newsletter’s observation regarding agentic experience—that language, context, ethics, and tone assume heightened importance when users engage with AI—is, in truth, an argument for integration. An AI agent’s response is, at once, a brand decision (how does the company sound?), a UX decision (what does the user require at this juncture?), a UI decision (in what manner is this presented?), and an engineering decision (what is technically feasible and responsible?). Any product team persisting in disciplinary silos will inevitably produce an agent that, while competent in certain respects, remains incoherent as a whole.
Integration is not achieved by mere proclamation; it is realised by establishing the structural conditions that render it inevitable.
Commence with a shared Experience Strategy before any discipline embarks upon its individual remit. The DaS™ Proposition Shaping stage makes this explicit: by the conclusion of the initial phase, every discipline—product owner, senior designer, service designer, solution architect, business analyst, lead engineer—possesses the same documented understanding of scope, objectives, and constraints. This is not a summary passively received, but the product of a workshop in which all have actively participated. The resulting value proposition canvas is neither a UX tool nor a business artefact; it is the collective property of all involved.
Construct the knowledge infrastructure that renders integration genuinely operational. Brand guidelines confined to PDFs are inaccessible; design systems restricted to Figma remain disconnected from engineering; content decisions buried in email threads are untraceable. The DaS™ model is unequivocal: a single source of truth spanning Figma, Confluence, and Jira, synchronised via automation and accessible to every discipline in real time. When a token is altered in the design system, the change propagates across all components; when a content decision is revised, it is immediately visible to the developer implementing the feature. Integration at the infrastructural level eradicates the seams engendered by disciplinary separation.
Approach the agentic experience as a design challenge, rather than an engineering conundrum. The newsletter’s most salient insight is that developers building AI agents must consider the experiential dimension: the nature of the agent’s responses, its behavioural patterns, escalation protocols, and error-recovery mechanisms. This is not a UX embellishment appended to an engineering decision; it is the central design problem, requiring brand, UX, UI, and engineering from the outset. Who does the agent resemble in tone? What constitutes trust within a conversational interface? When ought the agent to be candid about its limitations? These questions span brand, UX, UI, and engineering, and none can be answered in isolation.
‘Integration slows us down; specialisms enable parallel progress.’ Yet parallel progress in isolated lanes incurs integration costs at every juncture of handover. The DaS™ parallel delivery model confronts this issue directly: design and engineering proceed concurrently, with the Creative Technologist validating design assumptions in code as designers prototype in Figma. This approach eliminates the need for sequential handovers without sacrificing specialisation. Each discipline brings its expertise, while the operating model ensures these contributions are harmonised rather than at odds.
“Brand and UX are different functions — they can’t share the same operating model.” Brand defines what the product stands for. UX defines how that position is expressed through behaviour and interaction. UI makes it visible. Engineering makes it real. These are not competing definitions — they are successive layers of the same proposition. An operating model that keeps them separate doesn’t protect the distinctiveness of each specialism. It prevents the proposition from being coherent at any layer.
‘Agentic experience is too novel to warrant a methodology.’ Yet the principles it demands—context-sensitivity, the gradual cultivation of trust, transparency regarding system behaviour, and graceful recovery from failure—are anything but new. They are the bedrock of human-centred design, merely transposed to a novel medium. Every significant technological transition has required designers to adapt established principles to previously uncharted surfaces and interactions; UX itself emerged in precisely this fashion. The imperative now is not to devise an entirely new methodology, but to apply a coherent one—integrating brand, UX, UI, and engineering around a shared conception of excellence.
The ongoing debate over nomenclature—UX, AX, product design, experience design—reflects a deeper structural malaise. When disciplines are fragmented, each seeks to occupy the unclaimed territory left by the others. The proliferation of titles does not signal a profession coming of age; rather, it betrays one that has yet to resolve its integration dilemma.
AI is rendering this problem increasingly costly to disregard. The agentic systems now being woven into products will be experienced by users either as a seamless, coherent interaction or as the disjointed output of four disciplines that convened only at the handover and hoped for the best. The distinction is not one of methodology, but of structure. The convergence of brand, UX, UI, and engineering is not a luxury; it is the only way to create products that convey the impression of being crafted by individuals who truly understood their purpose.
We continue the discourse on what integration looks like in practice—how to build the operating model, shared knowledge infrastructure, and cross-functional accountability that makes it tangible—at designatscale.co.
