Key takeaway
- UX in software development explained for tech leaders: UX vs UI, user-centred design, WCAG 2.2 accessibility and how to design for AI agents.
User experience (UX) in software development is the work of making a product easy, useful and pleasant to use, from the first idea through to release and support. Nielsen Norman Group (NN/g) defines it as covering "all aspects of the end-user's interaction with the company, its services, and its products", so it is wider than screens and buttons.
For a CTO or head of engineering, the practical point is simple: UX decisions are made in every sprint, whether or not a designer is in the room. This guide explains the core ideas, how UX differs from UI, how to build accessible software, and what changes when your product includes AI agents. For a deeper look at tools, see our guide to user experience design tools and principles.
How do UX, UI and usability differ?
The three terms are often mixed up. NN/g defines usability as "how easily people can successfully complete a task using an interface", and lists five quality components: learnability, efficiency, memorability, errors and satisfaction. UX is the wider experience that usability sits inside.
| Term | What it covers | Who usually owns it |
|---|---|---|
| User experience (UX) | Every part of a person's interaction with the product, service and company | Product, design, engineering and support together |
| Usability | How easily people complete tasks (learnability, efficiency, memorability, errors, satisfaction) | UX research and design, tested with real users |
| User interface (UI) | The screens, controls, layout and visual style people interact with | Visual and interaction designers, front-end engineers |
| Accessibility | Whether people with different abilities can perceive, operate and understand the product | Everyone, checked against WCAG |
Source: NN/g, The Definition of User Experience and Usability 101.
Why does UX matter to enterprise software teams?
NN/g notes that poor usability costs an organisation money, because users spend more time, make more errors and need more training and support. Its 2020 analysis of redesign projects found that the UX metrics each project targeted improved by 75% on average after usability work, with wide variation, and NN/g states this is not a direct return-on-investment estimate. Treat it as a sign that targeted usability work can move the numbers you care about, not as a promise.
For internal enterprise tools the same logic applies to training time, support tickets and error rates. For customer-facing products it also affects adoption and retention. Our article on agentic AI in customer experience and interaction covers the customer side in more depth.
What is user-centred design and how does it run in a sprint?
User-centred design (UCD) is an iterative approach in which users and their needs are considered at each stage of design and development. In practice it means you keep returning to real users instead of designing once and shipping. NN/g groups research methods by the question you are asking at each stage, which maps well onto a delivery cycle.
| Stage | Question | Example methods (per NN/g) |
|---|---|---|
| Discover | What do users need and what are the constraints? | Field studies, user and stakeholder interviews, diary studies |
| Explore | Which design direction works? | Task analysis, journey mapping, card sorting, prototype testing |
| Test | Does the design work for real tasks? | Usability testing, benchmark testing, accessibility evaluation |
| Listen | How is it performing after release? | Surveys, analytics review, search-log analysis, feedback from support channels |
Source: NN/g, When to Use Which User-Experience Research Methods. Empathy matters throughout: designers and engineers need to understand what users are trying to do and how they feel while doing it. Our guide to user research methods goes into each method.
What are the five elements of user experience?
A common way to turn an idea into a design is the five-element model from Jesse James Garrett's book The Elements of User Experience. The layers below are as they are usually taught, from foundation to surface. Confirm the exact names in the book, because the author's site does not list them.
- Strategy: the business goals and user needs the product serves.
- Scope: the features and content you will build.
- Structure: how the product is organised and how people move through it.
- Skeleton: the layout of controls, navigation and information.
- Surface: the visual look and feel.
The order matters for engineering planning: problems at the strategy layer cannot be fixed by polishing the surface, so settle the lower layers before committing build effort.
What are universal, inclusive and equity-focused design?
- Universal design: aims for one solution usable by the widest range of people. Its limit is that a single solution rarely fits every context, so test it with the groups you actually serve.
- Inclusive design: considers differences such as ability, language, age and economic status from the start, and often involves people who are usually left out.
- Equity-focused design: recognises that equal treatment is not always a fair outcome. Equality gives everyone the same support; equity gives each person the support they need to reach a comparable result.
How do you make software accessible?
The World Health Organization estimates that 1.3 billion people, or 16% of the global population, experience a significant disability (WHO fact sheet, 7 March 2023). Accessibility is therefore a core requirement, and designing for disability tends to improve the experience for everyone, for example through captions, keyboard shortcuts and strong colour contrast.
The standard to build against is the W3C's Web Content Accessibility Guidelines (WCAG) 2.2, a W3C Recommendation dated 12 December 2024. It is organised around four principles: content must be perceivable, operable, understandable and robust. It defines three conformance levels: A (lowest), AA and AAA (highest). Which level you need is usually set by your contracts and local law, so confirm it with your legal team.
| New in WCAG 2.2 | Level | What it asks for |
|---|---|---|
| 2.4.11 Focus Not Obscured (Minimum) | AA | Keyboard focus is not hidden by other content |
| 2.5.7 Dragging Movements | AA | Dragging actions have a simpler alternative |
| 2.5.8 Target Size (Minimum) | AA | Controls are large enough to select reliably |
| 3.2.6 Consistent Help | A | Help is found in a consistent place |
| 3.3.7 Redundant Entry | A | Users are not asked to re-enter the same information |
| 3.3.8 Accessible Authentication (Minimum) | AA | Sign-in does not depend on a cognitive test alone |
Source: W3C, What's New in WCAG 2.2 (the table lists the A and AA criteria; the page also lists three AAA criteria, and notes that criterion 4.1.1 Parsing was removed). The "what it asks for" column is a plain-language summary, so read the official criterion text before testing.
What should engineers do in the code?
- Use native HTML first. MDN advises using WAI-ARIA only when you need to, and says that if you want a button and can use a
<button>element, you should. A<button>gives keyboard and screen reader support that a styled<div>does not. - Test with a keyboard only. Every function should work without a mouse, and focus should always be visible.
- Test with a screen reader. NVDA on Windows and VoiceOver on Mac are common choices.
- Check contrast and headings. Use clear heading levels and sufficient colour contrast.
- Add automated checks, then test manually. Lighthouse scores a set of weighted pass or fail audits and lists manual checks, such as focus order, separately. axe from Deque includes a free open-source library, axe-core, which you can run in test pipelines. Deque states, according to its site, that its tools can find up to 80% of issues, without giving a method for the figure, so treat automation as a first pass, not proof of conformance.
How should you design for different devices?
People use desktop, mobile web, mobile apps, tablets, wearables and TVs differently, but they expect a consistent experience across them. Practical guidance for small screens:
- Put the main action where it is easy to reach, for example adding an item to a basket.
- Keep navigation short and limited to the product's core functions.
- Use gestures people already know, such as tapping and swiping, and always offer a simple alternative.
- Reduce visual clutter, and make touch targets large enough to select reliably (see WCAG 2.5.8 above).
- Plan for slower networks and devices, so that pages and screens load quickly.
Who does what on a UX team?
| Role | Focus |
|---|---|
| UX researcher | Interviews, observation and testing to learn how people use or would use the product |
| UX designer | How people interact with the product: flows, structure and wireframes |
| UX writer | Clear product language, labels and messages |
| Graphic or visual designer | The visual appearance of the product |
| Product designer | Links design and engineering so the shipped product matches the design intent |
| UX programme manager | Coordination from discovery to release |
Smaller teams combine these roles. What matters is that someone owns each activity. For more on design principles, see product design principles and interaction design principles and best practices.
What changes when your software includes AI agents?
When a product acts on a user's behalf, the classic usability rules matter more, not less. NN/g's ten usability heuristics (published by Jakob Nielsen in 1994 and last reviewed 30 January 2024) include visibility of system status, user control and freedom, and help users recognise, diagnose and recover from errors. For an agent, these translate into showing what the agent is doing, letting people pause or reverse its actions, and giving clear explanations when it fails.
Conversation is another interface to design. Our guide to conversational user interface best practices covers that, and our article on agentic workflows explains how multi-step agent work is structured and governed. ElixirClaw is an agentic OS platform to build, orchestrate and govern AI agents and automation workflows while keeping humans in control, and ElixirData Context OS keeps governed context, versioned policy and decision traces in one decision layer above AI agents.
How should a team adopt UX practice, step by step?
- Name an owner. Decide who is accountable for UX quality in each product.
- Start with research. Talk to a handful of real users before the next major feature.
- Put accessibility in the definition of done. Include keyboard, screen reader and contrast checks, and automated tests in the pipeline.
- Test prototypes before building. It is cheaper to change a prototype than shipped code.
- Listen after release. Review analytics, support tickets and feedback every cycle.
- Review agent behaviour. Where AI agents act for users, check that status, control and recovery are visible.
When not to over-invest: for a short-lived internal script with a handful of users, light usability checks and basic accessibility are usually enough. Save full research programmes for products with many users or high-risk tasks.
If your product is moving towards agents and you want to map one decision your agents should make, and the context and policy it depends on, book a Context Workshop. See what happens in the workshop.
Frequently asked questions
What is user experience in software development?
It is the quality of a person's whole interaction with a software product and the company behind it. NN/g says it covers all aspects of the end-user's interaction with the company, its services and its products.
What is the difference between UX and UI?
UI is the screens and controls people see and use. UX is the wider experience, including whether people can complete their tasks, how they feel, and the support they receive. UI is one part of UX.
What is user-centred design?
It is an iterative approach in which user needs are considered at every stage. Teams research users, explore designs, test with real people and then listen after release.
Which accessibility standard should software follow?
The W3C's WCAG 2.2, a W3C Recommendation dated 12 December 2024, is the main reference. It defines conformance levels A, AA and AAA. Confirm the level you need with your legal team.
Can automated tools prove my product is accessible?
No. Tools such as Lighthouse and axe catch many issues, but Lighthouse itself lists manual checks, such as focus order, separately. Combine automated checks with keyboard and screen reader testing.
How does UX change for AI agents?
Heuristics such as visibility of system status and user control and freedom become design requirements: show what the agent is doing, allow people to stop or undo it, and explain errors clearly.
Follow XenonStack on LinkedIn: XenonStack on LinkedIn for new guides on agentic AI, data and platform engineering.
Explore the XenonStack platform family: ElixirData · ElixirClaw · ElixirHub · NexaStack · MetaSecure · Neural AI · AgentGRC · AgentSRE · AgentAnalyst · AgentInstruct · AgentRAI · AgentScrum · AgentSearch · AgentForce · AI Aviator · SAIF Aviator · CohortIQ · XenonStack AI · XenonStack UAE