UX As A System, Not A Deliverable
UX is often treated as something you deliver: a flow, a feature, a redesign.
Chemss Salem
Welcome to Chems Labs a mini-series about real-world UX, complex systems, and the decisions that shape experience beyond interfaces.
“UX is often treated as something you deliver: a flow, a feature, a redesign.
In reality, UX is not an artifact. It’s an emergent property of a system.
Policies, incentives, KPIs, governance, tooling, and people all interact to produce experience - whether intentionally or not.
In an energy management platform, operators complained about confusing software. Multiple redesigns failed. The real issue was systemic: regulatory reporting KPIs conflicted with real-time operational KPIs. The system forced users to choose between compliance and efficiency.
No interface could resolve that conflict.
When UX issues persist despite good design, it’s rarely a design problem. It’s a system alignment problem.
Understanding UX as a system is the foundation for meaningful audits - because it shifts the question from “Is this usable?” to “What is this system optimizing for?”
Next episode: discovery versus delivery.”
© by Chemsseddine SALEM | Lead UX Designer & Researcher | Enterprise SaaS & UX Strategy | UX Governance | Finance & Energy Sectors | 2026
