← Back to DashboardBriefing ID: brf-1792315251418
RESEARCH RADAR

One thing worth reading this week

18 October 2026 · Curated for research-led data visualisation & design practice

01SYSTEMS·UX Collective · 2026Article
The Idea

AI interfaces merge previously separate domains—content strategy, knowledge management, and underlying business logic—into a single user experience that reveals institutional silos. When semantic definitions and data sources are misaligned across departments, the AI produces confidently incorrect outputs that break user trust.

Why is this worth your time?

This is useful if you are designing interfaces or data representations that aggregate fragmented enterprise data. It gives you a clear mental model for diagnosing why an output fails, tracing errors back to conflicting domain semantics rather than simple model hallucination. Pay attention to the invoice scenario: it reinforces that research-led practice must interrogate organizational data definitions and system interdependencies before designing the presentation layer.

Read:the opening enterprise scenario to see how semantic gaps between departments cause interface failures, then continue to the breakdown referencing Sarah Gibbons' four types of AI design.
#METHOD#designops#ux#ai
▸Full Academic Abstract & CitationExpand

Full Abstract

“AI is bringing content design, enterprise content strategy, knowledge management, and model behavior into the same user experience. Our ways of working haven’t caught up. Imagine a finance manager trying to understand why a supplier hasn’t been paid. The enterprise application shows that the invoice has been approved. The manager asks the AI assistant when the supplier can expect payment, and the assistant explains that the invoice has completed the approval process and is ready for payment. Except it isn’t. The invoice is blocked because of a discrepancy between the invoiced amount and the purchase order. Approval and payment eligibility are different things, governed by different parts of the business process. The assistant hasn’t necessarily misunderstood the approval status. But it has failed to understand what that status means in relation to everything else. Maybe it retrieved documentation about invoice approvals without the information about payment blocks. Maybe the underlying business concepts aren’t represented consistently across systems. Maybe it didn’t have access to the current payment status. Or maybe it had the right information and still failed to interpret it correctly. Those are different problems, often owned by different teams. But from the user’s perspective, it’s one experience — and it’s broken. This is one of the most consequential challenges emerging as AI becomes part of enterprise software. We’re bringing together content and knowledge ecosystems that we’ve historically managed separately, and we haven’t yet developed the ways of working to manage their interdependence. We’re going to need more than better AI models, better content systems, or better design guidelines. We’re going to need to rethink how these things work together. We’re talking about more than one AI transformation One thing that makes this moment difficult to navigate is that we tend to talk about AI and content as though we’re discussing a single change. We’re not. In a 2026 article for Nielsen Norman Group , Sarah Gibbons articulated four different meanings of “AI design”: designing with AI, designing AI products, designing for AI agents, and designing the AI itself. That distinction is useful because the implications for content work are dramatically different depending on which kind of AI design we’re talking about. Consider two scenarios. In the first, a product team uses AI to accelerate its existing design process. It has a content design system with es”

Source: UX Collective
Feedback:
This Week's Themes
SYSTEMSMETHODDESIGNOPS
One Idea to Keep
“To create durable design interventions, map the visual artefacts not as static deliverables, but as feedback loops within the broader institutional ecosystem.”