English:User Experience Design
User Experience Design
Introduction
User Experience Design, usually shortened to UX design, is the evidence-informed practice of shaping products, services, and systems around the needs, capabilities, goals, and contexts of the people who use them. UX design is broader than visual styling. It includes research, information architecture, interaction design, usability, accessibility, content, prototyping, evaluation, and collaboration with other disciplines.
At university level, you should learn not only how to produce interfaces but also how to justify design decisions. Strong UX work connects observations about people to explicit requirements, design hypotheses, prototypes, and evaluation evidence. A good designer asks: Who is affected? What are they trying to achieve? In what context? What evidence supports this decision? What trade-offs are being made?
By the end of this aiMOOC, you should be able to explain central UX concepts, select suitable research and evaluation methods, create and critique common UX artifacts, address accessibility and ethics, and transfer human-centred design principles to unfamiliar design problems.
What User Experience Design Is
UX design focuses on the quality of a person's experience before, during, and after interaction with a product, system, or service. The experience is shaped by what the system enables, how understandable and efficient it is, how well it fits the user's context, how trustworthy it feels, and whether it supports meaningful goals.
UX, UI, usability, and customer experience
User interface design focuses on the perceivable and interactive parts of a digital system, such as controls, layouts, typography, icons, and feedback. Usability concerns how effectively, efficiently, and satisfactorily specified users can achieve specified goals in a particular context. UX includes usability but also broader perceptions and responses, such as confidence, value, emotion, expectations, and the coherence of the whole experience. Customer experience can be broader still because it may include marketing, purchasing, support, billing, and long-term relationships across many touchpoints.
These concepts overlap, but they should not be treated as synonyms. An interface can look polished yet still create a poor experience if it is confusing, inaccessible, slow, manipulative, or poorly matched to real tasks.
Experience depends on context
A design does not have one fixed user experience independent of circumstances. The same interface may be easy for an expert and difficult for a first-time user, useful on a desktop and frustrating on a phone, or acceptable in a quiet office and unsafe in a high-pressure environment. Context includes devices, physical settings, social conditions, language, prior knowledge, time pressure, connectivity, and the consequences of error.
For this reason, UX designers should avoid designing for an imaginary average person. They investigate relevant user groups and contexts, including people whose needs are often excluded by default assumptions.
Human-Centred Design Process
Human-centred design is iterative. Teams develop an understanding of people and contexts, define requirements, create possible solutions, and evaluate those solutions. Findings from evaluation often send the team back to revise assumptions or redesign parts of the system.
ISO 9241-210 and iterative practice
The current ISO 9241-210:2019 standard describes requirements and recommendations for human-centred design throughout the life cycle of interactive systems. Its principles include explicit understanding of users, tasks, and environments; involvement of users throughout design and development; evaluation that drives refinement; iteration; attention to the whole user experience; and multidisciplinary perspectives.
A human-centred process is not a rigid sequence. Research, design, and evaluation may overlap. Early in a project, you may explore a problem with interviews and field observation. Later, you may test prototypes. After launch, analytics, support data, accessibility reviews, and further research can reveal new needs.
Problem space and solution space
A frequent design failure is moving to solutions before the problem is understood. The problem space concerns goals, behaviors, constraints, motivations, environments, and existing breakdowns. The solution space concerns possible ways to address those findings.
Treat early design ideas as hypotheses rather than facts. A prototype is useful because it makes a hypothesis concrete enough to discuss and test without pretending that it is already correct.
UX Research
UX research reduces uncertainty by producing evidence about users, contexts, behaviors, needs, and responses to designs. Research questions should come before method selection. Asking "Which method should we use?" is less useful than asking "What do we need to learn, from whom, and why?"
Generative and evaluative research
Generative research helps you understand a problem space and discover needs or opportunities. Examples include contextual inquiry, interviews, diary studies, and field observation. Evaluative research examines an existing concept, prototype, or product. Examples include usability testing, heuristic evaluation, accessibility testing, and experiments.
Qualitative methods can explain patterns, motivations, and breakdowns in depth. Quantitative methods can estimate prevalence, compare conditions, or measure behavior at scale. Mixed-methods research can be especially useful when each method addresses a different part of the research question.
Interviews, observation, surveys, and analytics
Interviews are useful for learning about experiences, goals, perceptions, and remembered events, but people cannot always accurately predict or report their own behavior. Observation helps reveal what people actually do in context. Surveys can gather structured self-report data from larger samples, but question wording and sampling strongly influence results. Product analytics show behavioral traces at scale, but numbers alone do not explain motives.
A mature UX practice triangulates evidence. For example, analytics may show that many users abandon a form, usability testing may reveal where they become confused, and interviews may explain why the information being requested feels risky or irrelevant.
Research ethics and inclusion
UX research with people carries ethical responsibilities. Participants should understand what they are agreeing to, what data will be collected, how it will be used, and whether they can withdraw. Researchers should minimize unnecessary data collection, protect confidentiality, avoid coercion, and plan for secure handling of sensitive material.
Inclusion also affects research quality. If a study recruits only highly experienced, able-bodied, well-connected participants, the results may not generalize to people with different disabilities, languages, technologies, ages, cultures, or levels of expertise.
Synthesis and User Models
Research becomes useful for design when evidence is organized into patterns and implications. Synthesis may involve coding notes, affinity mapping, identifying themes, comparing user groups, modeling tasks, and linking observations to requirements.
Personas
A persona is an evidence-based representation of a meaningful user pattern. A useful persona emphasizes goals, behaviors, constraints, and context relevant to design decisions. It should not be a decorative fictional biography built from stereotypes.
The following Wikimedia research artifact shows personas created from contextual inquiry. Study it as an example of how research can be translated into a design communication tool.
Datei:Wikimedia userpersonas v3.pdf
Journey maps and experience maps
A journey map represents how a person moves through stages while pursuing a goal, often across multiple touchpoints. It can show actions, questions, emotions, pain points, opportunities, and responsible organizational units. An experience map is often broader and may describe a general experience beyond one specific product.
Maps are not evidence by themselves. Their value depends on the quality of the research behind them and on whether they help a team identify decisions, gaps, or opportunities.
Information Architecture and Interaction Design
Information architecture organizes content and functionality so that users can find, understand, and navigate what they need. Interaction design defines how actions, system states, controls, feedback, and transitions work together over time.
Structure, labels, navigation, and flows
Useful information architecture often depends on clear grouping, meaningful labels, sensible hierarchy, and navigation that reflects user goals rather than internal organizational structures. Techniques such as card sorting and tree testing can help evaluate how people categorize and find information.
A user flow describes a path through screens or states toward a goal. A good flow makes important choices visible, provides feedback, prevents avoidable errors, and offers recovery when errors occur.
Wireframes and prototypes
A wireframe communicates structure and priority without requiring a polished visual design. A prototype simulates some aspects of interaction so that a team can explore, communicate, or evaluate a design.
Low-fidelity prototypes are fast to change and useful for exploring alternatives. Higher-fidelity prototypes can support detailed interaction testing but cost more to create and may cause stakeholders to mistake an unfinished design for a nearly final product.
Datei:Multimedia Usability - NewUpload Wireframe January 2010.pdf
Choose fidelity according to the question you need to answer. If you are testing whether users understand the overall flow, a simple prototype may be enough. If you are testing precise interaction behavior, motion, or visual hierarchy, more detail may be necessary.
Evaluation and Usability
Evaluation asks whether a design actually works for the intended people and contexts. Different methods reveal different classes of problems, so evaluation should be tied to explicit questions and risks.
Usability testing
In a usability test, representative participants attempt realistic tasks while a researcher observes behavior and listens carefully. The goal is not to test whether participants are intelligent or skilled; it is to learn where the design supports or obstructs successful action.
A strong test uses tasks that describe goals without revealing the interface steps. Facilitators avoid leading participants. Findings should distinguish observed behavior from interpretation and should be linked to evidence.
The following historical Wikimedia study is useful for examining how researchers observe interaction problems. Although the interface is older, the research principle of watching real people attempt realistic tasks remains relevant.
Heuristic evaluation
A heuristic evaluation is an expert inspection in which evaluators compare an interface against general usability principles. Jakob Nielsen's ten heuristics include visibility of system status, match with the real world, user control and freedom, consistency and standards, error prevention, recognition rather than recall, flexibility and efficiency, aesthetic and minimalist design, support for error recovery, and help and documentation.
Heuristic evaluation is faster than recruiting participants, but it does not replace user research. Experts can identify likely problems; users reveal actual behavior in context. The two methods complement each other.
Eye tracking and behavioral measures
Eye tracking can show where visual attention is directed over time, but gaze data must be interpreted carefully. Looking at an element does not automatically mean understanding it, liking it, or finding it useful. Measures such as task success, completion time, error rate, confidence, and qualitative observations provide different evidence.
Useful UX metrics should be connected to user and product goals. A metric becomes misleading when teams optimize the number itself while losing sight of the human outcome it was meant to represent.
Accessibility and Inclusive UX
Accessibility is a core quality of user experience, not an optional final check. Inclusive design considers variation in vision, hearing, mobility, speech, cognition, literacy, language, device access, and situational limitations from the beginning.
WCAG 2.2
The World Wide Web Consortium recommends the Web Content Accessibility Guidelines WCAG 2.2 for current web accessibility work. WCAG is organized around four principles: content should be perceivable, operable, understandable, and robust. Its success criteria are testable and are grouped into conformance levels A, AA, and AAA.
Accessibility work includes, among many other concerns, text alternatives for meaningful images, keyboard access, visible focus, sufficient target sizes, understandable labels and errors, captions for relevant audio content, logical structure, and compatibility with assistive technologies.
Compliance with a checklist is important but does not guarantee an excellent experience. Testing with disabled users can reveal barriers that automated tools and technical reviews miss.
UX in Product Development
UX work happens within economic, technical, organizational, and legal constraints. Designers therefore need to communicate evidence, negotiate trade-offs, and collaborate with disciplines such as software engineering, product management, data science, content design, marketing, and accessibility.
From findings to requirements
A research finding becomes actionable when it is translated into a clear design implication or requirement. For example, if people repeatedly lose progress because they are interrupted, a requirement might state that the system must preserve recoverable progress across sessions. The design team can then explore multiple solutions and evaluate which one works best.
Good requirements should avoid locking the team into an untested interface too early. They describe the user need or system behavior that matters, while leaving room for alternative solutions.
Working iteratively in agile teams
In agile environments, UX research and design should not be compressed into a single activity just before development. Teams can maintain a continuous learning cycle in which research informs upcoming work, designers collaborate with engineers during implementation, and released features generate new evidence.
The most effective collaboration treats UX as a shared product responsibility. Designers contribute specialist methods, but engineers, product managers, researchers, and domain experts also influence the experience.
Ethics, Trust, and Emerging Challenges
UX designers influence choices by controlling defaults, visibility, timing, wording, and interaction costs. This creates power and responsibility. Ethical design avoids deceptive patterns that manipulate people into actions they did not intend, such as hiding cancellation, disguising advertising, or making privacy-protective choices unnecessarily difficult.
Personalization and artificial intelligence can improve relevance and reduce effort, but they can also create uncertainty about how decisions are made, what data is collected, and whether outputs are reliable. UX work for AI-enabled systems should address transparency, user control, error recovery, appropriate reliance, and the consequences of incorrect outputs.
A useful ethical question is not only "Can we increase conversion?" but also "Would users still consider this interaction fair if they understood how it was designed?"
Interactive Tasks
Quiz: Test Your Knowledge
What is the central purpose of user experience design? (To shape products and services around evidence about users and their contexts) (!To maximize visual decoration regardless of user goals) (!To replace software engineering with graphic design) (!To eliminate the need for evaluation)
Which statement best distinguishes UX from UI design? (UX includes the broader experience while UI focuses on interface elements and interactions) (!UX and UI are always identical terms) (!UI includes customer support while UX concerns only typography) (!UX concerns only branding while UI concerns all research)
What should normally come before selecting a UX research method? (A clear research question) (!A finished visual style guide) (!A fixed solution that cannot change) (!A preference for one favorite method)
What is the main purpose of a low fidelity prototype? (To explore and test ideas quickly before expensive implementation) (!To provide legally final product documentation) (!To guarantee that users will prefer the product) (!To replace all later usability testing)
What does a usability test primarily evaluate? (How representative users attempt realistic tasks with a design) (!Whether participants can memorize a design textbook) (!Whether stakeholders agree with the visual style) (!Whether a designer can explain every screen)
What is a persona most useful for when it is well constructed? (Representing evidence based patterns in goals behaviors and contexts) (!Adding fictional demographic detail without research) (!Predicting exact behavior of every individual user) (!Replacing direct contact with users permanently)
Which statement about heuristic evaluation is correct? (It is an expert inspection that complements rather than replaces user testing) (!It measures only page loading speed) (!It requires no usability principles) (!It always produces the same findings as field research)
Which set names the four WCAG principles? (Perceivable operable understandable robust) (!Visible attractive profitable memorable) (!Simple fast colorful responsive) (!Private predictive adaptive automated)
Why can product analytics alone be insufficient for UX research? (They show behavioral patterns but often do not explain motives or context) (!They can never measure any user behavior) (!They are always qualitative) (!They automatically reveal every accessibility barrier)
Which approach best supports ethical UX practice? (Designing for informed choice user control and fair treatment) (!Making cancellation harder than sign up) (!Hiding relevant costs until the final step) (!Using deceptive defaults to increase conversion)
Memory Game
| Persona | Evidence based representation of a meaningful user pattern |
| Wireframe | Low detail representation of interface structure |
| Prototype | Interactive or simulated representation used to explore a design |
| Usability | Quality of achieving goals effectively efficiently and satisfactorily |
| Accessibility | Design quality that supports people with diverse abilities and assistive technologies |
| Journey map | Visualization of stages and touchpoints in pursuit of a goal |
| Heuristic evaluation | Expert inspection against general usability principles |
Drag and Drop
| Match the correct terms. | Topic |
|---|---|
| Contextual inquiry | Study people performing activities in their real environment |
| Card sorting | Explore how people group and label information |
| Usability testing | Observe representative users attempting realistic tasks |
| Heuristic evaluation | Inspect an interface against general usability principles |
| Tree testing | Evaluate whether people can find information in a proposed hierarchy |
...
Crossword Puzzle
| Persona | What evidence based user model represents a meaningful pattern of goals and behavior? |
| Prototype | What design artifact simulates an idea so it can be explored or tested? |
| Usability | What quality concerns effective efficient and satisfactory goal achievement? |
| Affordance | What term describes a property that suggests how an object or control can be used? |
| Accessibility | What design concern seeks to remove barriers for people with diverse abilities? |
| Wireframe | What low detail artifact communicates interface structure and priority? |
LearningApps
Cloze Text
Open-Ended Tasks
Easy
- Interface observation diary: Choose one digital product you use for three days and record moments of ease, confusion, trust, delay, and recovery. Summarize the patterns and propose two design questions.
- Micro usability review: Select a university website page and identify five usability strengths or problems using clear evidence from the interface rather than personal taste.
- Accessibility snapshot: Use keyboard navigation and built in browser tools to inspect a public website. Document barriers you can verify and explain who might be affected.
- User flow sketch: Draw a simple flow for completing one common task in a campus service and annotate where users need feedback, confirmation, or error recovery.
Standard
- Semi structured interview study: Conduct two consent based interviews about how students complete a recurring academic task. Create an interview guide, synthesize themes, and distinguish observations from interpretations.
- Evidence based persona: Build one persona from your interview or observation data. Include goals, behaviors, constraints, and context, and explain which design decisions the persona should inform.
- Prototype and test: Create a low fidelity prototype for improving one university service, test it with at least three representative participants, and revise the design based on observed behavior.
- Journey mapping project: Map a multi step student journey across at least four touchpoints. Identify pain points, moments of uncertainty, responsible actors, and opportunities for improvement.
Advanced
- Comparative research design: Design a mixed methods study comparing two interaction approaches. Define research questions, sampling, measures, qualitative evidence, and a plan for integrating findings.
- Inclusive design audit: Evaluate a digital service using WCAG 2.2 principles, keyboard testing, assistive technology where available, and at least one session with a participant who has an access need. Prioritize findings by impact.
- Ethical redesign case: Find a real interface that uses a potentially deceptive pattern. Analyze the incentives behind it, redesign the interaction for informed choice, and justify the redesign from user and organizational perspectives.
- UX research presentation: Produce a five minute research video or conference style presentation that explains a UX problem, method, evidence, design response, limitations, and next research question for an expert audience.
Learning Assessment
- Research strategy assessment: Given a new campus app concept, formulate three research questions and justify a different method for each by explaining what evidence the method can and cannot provide.
- Design critique assessment: Critique an unfamiliar interface using usability, accessibility, information architecture, and ethical criteria, then rank the three most important issues by user impact.
- Evidence to requirement assessment: Convert a set of interview and usability findings into user needs and design requirements without prematurely prescribing one interface solution.
- Prototype decision assessment: Compare paper, clickable, and high fidelity prototypes for a risky design problem and justify which fidelity should be used at each stage of learning.
- Evaluation plan assessment: Create an evaluation plan that combines expert review, usability testing, accessibility checks, and product metrics, explaining how the methods complement each other.
- Transfer assessment: Apply human centred design principles to a non screen system such as a ticket machine, public service process, laboratory procedure, or physical navigation environment.
Evidence of Learning
- Conceptual knowledge: You can distinguish UX, UI, usability, accessibility, interaction design, information architecture, and customer experience and explain their relationships.
- Research skill: You can formulate research questions, select appropriate methods, collect evidence ethically, and recognize limitations in sampling and interpretation.
- Design skill: You can translate evidence into requirements, flows, wireframes, prototypes, and interaction decisions while keeping alternative solutions open.
- Evaluation skill: You can plan and conduct usability evaluation, heuristic review, and accessibility checks and prioritize findings by user impact.
- Communication product: You can produce clear UX artifacts such as a research brief, persona, journey map, prototype, test report, or evidence based design presentation.
- Ethical judgment: You can identify deceptive or exclusionary design choices and argue for alternatives that improve informed choice, accessibility, privacy, and user control.
- Transfer achievement: You can apply human centred design reasoning to unfamiliar digital, service, and physical systems rather than relying on one fixed design recipe.
OERs on the Topic
Linked Learning Areas
User Experience Design connects human behavior, technology, visual communication, service systems, research methods, ethics, and accessibility. The links below provide a compact map of major learning areas that can be explored before or after this aiMOOC.
