Question 1. Define Human-Computer Interaction.
Model answer: The interdisciplinary study and practice of designing, evaluating and understanding interactive systems for people.
CBE NEXUS · UNDERGRADUATE TEXTBOOK SERIES
Information Systems
Comprehensive undergraduate notes, HCI diagrams, applied case studies and university assessment.
Undergraduate level · Chapter 12 of 16 · Designing inclusive, usable and trustworthy digital experiences
Learning outcomes: Explain HCI principles; conduct user research and task analysis; apply cognitive and usability concepts; design accessible interfaces; prototype and evaluate interactions; and assess ethical and emerging UX challenges.
Human-Computer Interaction (HCI) is the interdisciplinary study and practice of designing, evaluating and understanding interactive computing systems for people. It draws on computer science, psychology, cognitive science, ergonomics, design, sociology and accessibility. HCI considers the complete relationship between a person, a task, a technology and the social and physical environment in which interaction takes place.
A successful interface is not simply attractive. It helps people achieve meaningful goals accurately, efficiently, safely and with an appropriate level of satisfaction. A technically correct system may still fail when terminology is confusing, feedback is missing, workflows conflict with real work or users cannot operate controls. HCI therefore treats usability and user experience as design requirements rather than cosmetic additions.
In practice, the design team should document the target users, primary tasks, context, assumptions and measurable acceptance criteria. Observe complete journeys rather than isolated screens, because friction often occurs between departments, devices or service channels. Record both successful and unsuccessful paths, including interruptions, recovery and exceptional cases. Findings should be prioritised according to severity, frequency, affected users and consequences.
Translate the findings into design decisions that can be tested. Specify the expected user action, the system response, the feedback presented, the error conditions and the recovery route. Check that the design works with realistic content, different input methods and assistive technology. Review the result with users and revise it when evidence shows that the intended mental model, language or workflow does not match actual practice.
Evaluation should combine observed behaviour with user explanations and appropriate quantitative measures. A high satisfaction rating does not prove that a task is safe or error-free, and a short completion time may conceal skipped information. Interpret metrics in context, disclose sample limitations and examine whether outcomes differ across relevant user groups. Keep a record of decisions so that future teams can understand why a pattern was adopted.
Human-centred design places intended users, their tasks and their environments at the centre of development. It begins by understanding context, specifying user requirements, producing design solutions and evaluating those solutions with users. These activities are iterative: evaluation may reveal that the original problem statement or requirements need revision.
The process should involve users throughout the lifecycle, combine multidisciplinary expertise, consider the whole experience and use evaluation to improve designs. Participation should be meaningful and inclusive. A few senior stakeholders cannot reliably represent the needs of all users, especially people with disabilities, low digital confidence, limited connectivity or different language preferences.
In practice, the design team should document the target users, primary tasks, context, assumptions and measurable acceptance criteria. Observe complete journeys rather than isolated screens, because friction often occurs between departments, devices or service channels. Record both successful and unsuccessful paths, including interruptions, recovery and exceptional cases. Findings should be prioritised according to severity, frequency, affected users and consequences.
Translate the findings into design decisions that can be tested. Specify the expected user action, the system response, the feedback presented, the error conditions and the recovery route. Check that the design works with realistic content, different input methods and assistive technology. Review the result with users and revise it when evidence shows that the intended mental model, language or workflow does not match actual practice.
Evaluation should combine observed behaviour with user explanations and appropriate quantitative measures. A high satisfaction rating does not prove that a task is safe or error-free, and a short completion time may conceal skipped information. Interpret metrics in context, disclose sample limitations and examine whether outcomes differ across relevant user groups. Keep a record of decisions so that future teams can understand why a pattern was adopted.
Users are people who directly operate a system, while stakeholders may also include administrators, customers, regulators, support staff, managers and people affected by its outputs. Stakeholder analysis identifies interests, influence, responsibilities, potential harms and information needs. A system designed only for its paying customer may overlook frontline staff or people whose data it processes.
Personas are evidence-informed representations of user groups. A useful persona describes goals, behaviours, context, capabilities, constraints and relevant technology access. Personas should be grounded in interviews, observation and research rather than stereotypes. They help teams discuss design decisions, but they are not substitutes for testing with actual users.
In practice, the design team should document the target users, primary tasks, context, assumptions and measurable acceptance criteria. Observe complete journeys rather than isolated screens, because friction often occurs between departments, devices or service channels. Record both successful and unsuccessful paths, including interruptions, recovery and exceptional cases. Findings should be prioritised according to severity, frequency, affected users and consequences.
Translate the findings into design decisions that can be tested. Specify the expected user action, the system response, the feedback presented, the error conditions and the recovery route. Check that the design works with realistic content, different input methods and assistive technology. Review the result with users and revise it when evidence shows that the intended mental model, language or workflow does not match actual practice.
Evaluation should combine observed behaviour with user explanations and appropriate quantitative measures. A high satisfaction rating does not prove that a task is safe or error-free, and a short completion time may conceal skipped information. Interpret metrics in context, disclose sample limitations and examine whether outcomes differ across relevant user groups. Keep a record of decisions so that future teams can understand why a pattern was adopted.
Interviews explore experiences, motivations and explanations. Contextual inquiry combines observation with questions while people perform real tasks. Surveys can gather broader patterns but depend on clear wording and appropriate sampling. Diary studies capture behaviour over time, while focus groups reveal shared perceptions and disagreements.
Choose methods according to the question. To understand why staff bypass a workflow, observe the task and interview participants rather than relying only on a satisfaction score. Obtain informed consent, minimise collected personal information and explain how findings will be used. Record methods and limitations so that design decisions remain traceable to evidence.
In practice, the design team should document the target users, primary tasks, context, assumptions and measurable acceptance criteria. Observe complete journeys rather than isolated screens, because friction often occurs between departments, devices or service channels. Record both successful and unsuccessful paths, including interruptions, recovery and exceptional cases. Findings should be prioritised according to severity, frequency, affected users and consequences.
Translate the findings into design decisions that can be tested. Specify the expected user action, the system response, the feedback presented, the error conditions and the recovery route. Check that the design works with realistic content, different input methods and assistive technology. Review the result with users and revise it when evidence shows that the intended mental model, language or workflow does not match actual practice.
Evaluation should combine observed behaviour with user explanations and appropriate quantitative measures. A high satisfaction rating does not prove that a task is safe or error-free, and a short completion time may conceal skipped information. Interpret metrics in context, disclose sample limitations and examine whether outcomes differ across relevant user groups. Keep a record of decisions so that future teams can understand why a pattern was adopted.
Task analysis decomposes a goal into activities, decisions, information needs and actions. Hierarchical task analysis represents goals, subtasks and plans; cognitive task analysis investigates knowledge and reasoning; and workflow models show the sequence and relationships between roles and systems.
Analyse frequency, duration, error consequences, interruptions, hand-offs and exceptional cases. A form may appear simple while requiring users to consult several records or seek approval elsewhere. Mapping the complete task can reveal opportunities to remove steps, clarify responsibility, prevent errors and reduce unnecessary cognitive effort.
In practice, the design team should document the target users, primary tasks, context, assumptions and measurable acceptance criteria. Observe complete journeys rather than isolated screens, because friction often occurs between departments, devices or service channels. Record both successful and unsuccessful paths, including interruptions, recovery and exceptional cases. Findings should be prioritised according to severity, frequency, affected users and consequences.
Translate the findings into design decisions that can be tested. Specify the expected user action, the system response, the feedback presented, the error conditions and the recovery route. Check that the design works with realistic content, different input methods and assistive technology. Review the result with users and revise it when evidence shows that the intended mental model, language or workflow does not match actual practice.
Evaluation should combine observed behaviour with user explanations and appropriate quantitative measures. A high satisfaction rating does not prove that a task is safe or error-free, and a short completion time may conceal skipped information. Interpret metrics in context, disclose sample limitations and examine whether outcomes differ across relevant user groups. Keep a record of decisions so that future teams can understand why a pattern was adopted.
Context of use includes physical conditions, social arrangements, organisational rules, devices, connectivity, lighting, noise, mobility and time pressure. The same interface may work well in a quiet office but fail on a small phone in bright sunlight or where network access is intermittent.
Designers should document representative contexts and test under realistic conditions. Consider shared devices, assistive technologies, low bandwidth, battery limits, interruptions and privacy in public spaces. Offline support, autosave, clear synchronisation status and resilient error recovery may be essential for users who cannot maintain continuous connectivity.
In practice, the design team should document the target users, primary tasks, context, assumptions and measurable acceptance criteria. Observe complete journeys rather than isolated screens, because friction often occurs between departments, devices or service channels. Record both successful and unsuccessful paths, including interruptions, recovery and exceptional cases. Findings should be prioritised according to severity, frequency, affected users and consequences.
Translate the findings into design decisions that can be tested. Specify the expected user action, the system response, the feedback presented, the error conditions and the recovery route. Check that the design works with realistic content, different input methods and assistive technology. Review the result with users and revise it when evidence shows that the intended mental model, language or workflow does not match actual practice.
Evaluation should combine observed behaviour with user explanations and appropriate quantitative measures. A high satisfaction rating does not prove that a task is safe or error-free, and a short completion time may conceal skipped information. Interpret metrics in context, disclose sample limitations and examine whether outcomes differ across relevant user groups. Keep a record of decisions so that future teams can understand why a pattern was adopted.
Mental models are the internal explanations people use to predict how a system works. Users transfer expectations from familiar objects, services and previous applications. When an interface behaves consistently with a reasonable mental model, people can predict outcomes; when it violates expectations, they must guess or remember hidden rules.
Working memory is limited, so interfaces should avoid requiring users to remember information across distant screens. Recognition is generally easier than unaided recall. Group related information, use familiar language, show relevant choices and provide contextual help. Do not assume that an icon or metaphor is universally understood.
In practice, the design team should document the target users, primary tasks, context, assumptions and measurable acceptance criteria. Observe complete journeys rather than isolated screens, because friction often occurs between departments, devices or service channels. Record both successful and unsuccessful paths, including interruptions, recovery and exceptional cases. Findings should be prioritised according to severity, frequency, affected users and consequences.
Translate the findings into design decisions that can be tested. Specify the expected user action, the system response, the feedback presented, the error conditions and the recovery route. Check that the design works with realistic content, different input methods and assistive technology. Review the result with users and revise it when evidence shows that the intended mental model, language or workflow does not match actual practice.
Evaluation should combine observed behaviour with user explanations and appropriate quantitative measures. A high satisfaction rating does not prove that a task is safe or error-free, and a short completion time may conceal skipped information. Interpret metrics in context, disclose sample limitations and examine whether outcomes differ across relevant user groups. Keep a record of decisions so that future teams can understand why a pattern was adopted.
Attention selects information for processing, while perception organises sensory input into meaningful patterns. Visual hierarchy, spacing, contrast, alignment and grouping influence what users notice. Important information can be missed when screens contain competing highlights, dense text, unexpected movement or ambiguous labels.
Design should support scanning and prioritisation. Place critical actions and status information where users can find them, use headings that communicate structure and distinguish interactive elements from static content. Avoid relying on colour alone, flashing effects or tiny targets. Test readability and comprehension across screen sizes and user conditions.
In practice, the design team should document the target users, primary tasks, context, assumptions and measurable acceptance criteria. Observe complete journeys rather than isolated screens, because friction often occurs between departments, devices or service channels. Record both successful and unsuccessful paths, including interruptions, recovery and exceptional cases. Findings should be prioritised according to severity, frequency, affected users and consequences.
Translate the findings into design decisions that can be tested. Specify the expected user action, the system response, the feedback presented, the error conditions and the recovery route. Check that the design works with realistic content, different input methods and assistive technology. Review the result with users and revise it when evidence shows that the intended mental model, language or workflow does not match actual practice.
Evaluation should combine observed behaviour with user explanations and appropriate quantitative measures. A high satisfaction rating does not prove that a task is safe or error-free, and a short completion time may conceal skipped information. Interpret metrics in context, disclose sample limitations and examine whether outcomes differ across relevant user groups. Keep a record of decisions so that future teams can understand why a pattern was adopted.
Cognitive load describes the mental effort required to process information. Intrinsic load comes from task complexity, extraneous load from poor presentation and germane effort from building useful understanding. Interfaces cannot remove the inherent complexity of a task, but they can avoid adding unnecessary complexity through confusing navigation or inconsistent controls.
Support learning through progressive disclosure, examples, sensible defaults, clear instructions and immediate feedback. Keep terminology and control placement consistent. For infrequent or high-risk tasks, provide checklists and confirmation of important details. Avoid forcing users to memorise codes, rules or information that the system could safely display.
In practice, the design team should document the target users, primary tasks, context, assumptions and measurable acceptance criteria. Observe complete journeys rather than isolated screens, because friction often occurs between departments, devices or service channels. Record both successful and unsuccessful paths, including interruptions, recovery and exceptional cases. Findings should be prioritised according to severity, frequency, affected users and consequences.
Translate the findings into design decisions that can be tested. Specify the expected user action, the system response, the feedback presented, the error conditions and the recovery route. Check that the design works with realistic content, different input methods and assistive technology. Review the result with users and revise it when evidence shows that the intended mental model, language or workflow does not match actual practice.
Evaluation should combine observed behaviour with user explanations and appropriate quantitative measures. A high satisfaction rating does not prove that a task is safe or error-free, and a short completion time may conceal skipped information. Interpret metrics in context, disclose sample limitations and examine whether outcomes differ across relevant user groups. Keep a record of decisions so that future teams can understand why a pattern was adopted.
Usability is commonly evaluated through effectiveness, efficiency and satisfaction in a specified context. Effectiveness concerns whether users complete goals accurately; efficiency concerns the resources and time required; satisfaction concerns users' perceptions and comfort. Learnability, memorability, error prevention and accessibility are also important quality considerations.
A usability target must be measurable and tied to a task. For example, a defined proportion of representative users may be expected to complete a registration task without assistance, within a specified time and with no critical errors. Report sample characteristics, task conditions and confidence limits where appropriate rather than presenting a small test as universal proof.
In practice, the design team should document the target users, primary tasks, context, assumptions and measurable acceptance criteria. Observe complete journeys rather than isolated screens, because friction often occurs between departments, devices or service channels. Record both successful and unsuccessful paths, including interruptions, recovery and exceptional cases. Findings should be prioritised according to severity, frequency, affected users and consequences.
Translate the findings into design decisions that can be tested. Specify the expected user action, the system response, the feedback presented, the error conditions and the recovery route. Check that the design works with realistic content, different input methods and assistive technology. Review the result with users and revise it when evidence shows that the intended mental model, language or workflow does not match actual practice.
Evaluation should combine observed behaviour with user explanations and appropriate quantitative measures. A high satisfaction rating does not prove that a task is safe or error-free, and a short completion time may conceal skipped information. Interpret metrics in context, disclose sample limitations and examine whether outcomes differ across relevant user groups. Keep a record of decisions so that future teams can understand why a pattern was adopted.
User Experience (UX) includes perceptions and responses before, during and after use. It may include usefulness, trust, credibility, enjoyment, aesthetics, accessibility, frustration and the wider service experience. UX is shaped not only by screens but also by policies, staff interactions, delivery reliability and expectations set by the organisation.
A visually polished interface cannot compensate for a service that loses information or makes unfair decisions. Emotional design should build confidence through clarity, respectful language, predictable behaviour and control. Avoid manipulative patterns that pressure users into purchases, consent or disclosure. Measure experience with qualitative feedback and appropriately interpreted quantitative indicators.
In practice, the design team should document the target users, primary tasks, context, assumptions and measurable acceptance criteria. Observe complete journeys rather than isolated screens, because friction often occurs between departments, devices or service channels. Record both successful and unsuccessful paths, including interruptions, recovery and exceptional cases. Findings should be prioritised according to severity, frequency, affected users and consequences.
Translate the findings into design decisions that can be tested. Specify the expected user action, the system response, the feedback presented, the error conditions and the recovery route. Check that the design works with realistic content, different input methods and assistive technology. Review the result with users and revise it when evidence shows that the intended mental model, language or workflow does not match actual practice.
Evaluation should combine observed behaviour with user explanations and appropriate quantitative measures. A high satisfaction rating does not prove that a task is safe or error-free, and a short completion time may conceal skipped information. Interpret metrics in context, disclose sample limitations and examine whether outcomes differ across relevant user groups. Keep a record of decisions so that future teams can understand why a pattern was adopted.
Common interaction styles include command languages, menus, forms, direct manipulation, natural-language interaction, touch, voice and conversational interfaces. Each style has strengths and limitations. Command interfaces can be powerful for expert users; menus support discovery; forms structure data entry; direct manipulation makes visible objects and actions easier to understand.
Choose interaction styles based on task frequency, complexity, error cost, user expertise, environment and available devices. A voice interface may be useful when hands are occupied but unsuitable in a noisy or privacy-sensitive setting. A graphical workflow may be easier to learn but slower for repeated expert operations. Hybrid designs can support different needs.
In practice, the design team should document the target users, primary tasks, context, assumptions and measurable acceptance criteria. Observe complete journeys rather than isolated screens, because friction often occurs between departments, devices or service channels. Record both successful and unsuccessful paths, including interruptions, recovery and exceptional cases. Findings should be prioritised according to severity, frequency, affected users and consequences.
Translate the findings into design decisions that can be tested. Specify the expected user action, the system response, the feedback presented, the error conditions and the recovery route. Check that the design works with realistic content, different input methods and assistive technology. Review the result with users and revise it when evidence shows that the intended mental model, language or workflow does not match actual practice.
Evaluation should combine observed behaviour with user explanations and appropriate quantitative measures. A high satisfaction rating does not prove that a task is safe or error-free, and a short completion time may conceal skipped information. Interpret metrics in context, disclose sample limitations and examine whether outcomes differ across relevant user groups. Keep a record of decisions so that future teams can understand why a pattern was adopted.
Information architecture organises content, functions and relationships so users can find what they need. Navigation systems include global navigation, local navigation, breadcrumbs, search, tabs and contextual links. Labels should reflect users' language and group related information according to their goals rather than internal organisational charts.
Provide clear location cues, consistent navigation and meaningful page titles. Avoid deep, unpredictable hierarchies and links with vague labels such as 'click here'. Search should tolerate reasonable variations and provide useful empty states. Users should be able to recover from wrong turns without losing completed work.
In practice, the design team should document the target users, primary tasks, context, assumptions and measurable acceptance criteria. Observe complete journeys rather than isolated screens, because friction often occurs between departments, devices or service channels. Record both successful and unsuccessful paths, including interruptions, recovery and exceptional cases. Findings should be prioritised according to severity, frequency, affected users and consequences.
Translate the findings into design decisions that can be tested. Specify the expected user action, the system response, the feedback presented, the error conditions and the recovery route. Check that the design works with realistic content, different input methods and assistive technology. Review the result with users and revise it when evidence shows that the intended mental model, language or workflow does not match actual practice.
Evaluation should combine observed behaviour with user explanations and appropriate quantitative measures. A high satisfaction rating does not prove that a task is safe or error-free, and a short completion time may conceal skipped information. Interpret metrics in context, disclose sample limitations and examine whether outcomes differ across relevant user groups. Keep a record of decisions so that future teams can understand why a pattern was adopted.
Visual design communicates hierarchy and supports comprehension through typography, colour, spacing, alignment, contrast, imagery and composition. A design system defines reusable components, tokens and rules so that screens remain consistent as a product grows. Visual consistency reduces the effort required to interpret each new screen.
Responsive layouts should adapt to available space without hiding essential functions. Use readable type sizes, sufficient contrast, clear focus indicators and appropriately sized controls. Avoid dense tables on narrow screens without a usable alternative. Test layouts with real content, including long names, translated text, validation messages and empty or error states.
In practice, the design team should document the target users, primary tasks, context, assumptions and measurable acceptance criteria. Observe complete journeys rather than isolated screens, because friction often occurs between departments, devices or service channels. Record both successful and unsuccessful paths, including interruptions, recovery and exceptional cases. Findings should be prioritised according to severity, frequency, affected users and consequences.
Translate the findings into design decisions that can be tested. Specify the expected user action, the system response, the feedback presented, the error conditions and the recovery route. Check that the design works with realistic content, different input methods and assistive technology. Review the result with users and revise it when evidence shows that the intended mental model, language or workflow does not match actual practice.
Evaluation should combine observed behaviour with user explanations and appropriate quantitative measures. A high satisfaction rating does not prove that a task is safe or error-free, and a short completion time may conceal skipped information. Interpret metrics in context, disclose sample limitations and examine whether outcomes differ across relevant user groups. Keep a record of decisions so that future teams can understand why a pattern was adopted.
Forms should request only information needed for a stated purpose. Group related fields, use labels that remain visible, indicate required fields and provide examples where formats may be unfamiliar. Choose input controls that match the data and allow users to correct mistakes without losing valid entries.
Validation should be timely, specific and actionable. Identify the field with an error, explain how to fix it and preserve the user's other entries. Distinguish format validation from business-rule validation and server-side verification. Avoid clearing an entire form after one error or relying only on colour to identify invalid values.
In practice, the design team should document the target users, primary tasks, context, assumptions and measurable acceptance criteria. Observe complete journeys rather than isolated screens, because friction often occurs between departments, devices or service channels. Record both successful and unsuccessful paths, including interruptions, recovery and exceptional cases. Findings should be prioritised according to severity, frequency, affected users and consequences.
Translate the findings into design decisions that can be tested. Specify the expected user action, the system response, the feedback presented, the error conditions and the recovery route. Check that the design works with realistic content, different input methods and assistive technology. Review the result with users and revise it when evidence shows that the intended mental model, language or workflow does not match actual practice.
Evaluation should combine observed behaviour with user explanations and appropriate quantitative measures. A high satisfaction rating does not prove that a task is safe or error-free, and a short completion time may conceal skipped information. Interpret metrics in context, disclose sample limitations and examine whether outcomes differ across relevant user groups. Keep a record of decisions so that future teams can understand why a pattern was adopted.
Feedback tells users what happened after an action. Systems should acknowledge input, show progress for longer operations, confirm completion and explain failures. Without feedback, users may repeat actions, submit duplicate payments or assume that information has been saved when it has not.
Response-time design should reflect task expectations and the consequences of delay. Use progress indicators for operations that take noticeable time, preserve user work and provide a safe cancellation or retry route where possible. For asynchronous tasks, explain whether the user may leave the page and how they will know when processing is complete.
In practice, the design team should document the target users, primary tasks, context, assumptions and measurable acceptance criteria. Observe complete journeys rather than isolated screens, because friction often occurs between departments, devices or service channels. Record both successful and unsuccessful paths, including interruptions, recovery and exceptional cases. Findings should be prioritised according to severity, frequency, affected users and consequences.
Translate the findings into design decisions that can be tested. Specify the expected user action, the system response, the feedback presented, the error conditions and the recovery route. Check that the design works with realistic content, different input methods and assistive technology. Review the result with users and revise it when evidence shows that the intended mental model, language or workflow does not match actual practice.
Evaluation should combine observed behaviour with user explanations and appropriate quantitative measures. A high satisfaction rating does not prove that a task is safe or error-free, and a short completion time may conceal skipped information. Interpret metrics in context, disclose sample limitations and examine whether outcomes differ across relevant user groups. Keep a record of decisions so that future teams can understand why a pattern was adopted.
Errors may arise from slips, misunderstandings, invalid data, system failures or external conditions. Prevention includes sensible defaults, constraints, confirmation for consequential actions, clear affordances and checks at appropriate points. Confirmation dialogs should be reserved for actions with meaningful consequences rather than interrupting every routine operation.
Recovery includes undo, redo, version history, autosave, clear error messages and safe retry. Error messages should explain the problem in plain language, indicate what remains intact and offer a next step. Log technical details securely for support, but do not expose stack traces, credentials or sensitive records to ordinary users.
In practice, the design team should document the target users, primary tasks, context, assumptions and measurable acceptance criteria. Observe complete journeys rather than isolated screens, because friction often occurs between departments, devices or service channels. Record both successful and unsuccessful paths, including interruptions, recovery and exceptional cases. Findings should be prioritised according to severity, frequency, affected users and consequences.
Translate the findings into design decisions that can be tested. Specify the expected user action, the system response, the feedback presented, the error conditions and the recovery route. Check that the design works with realistic content, different input methods and assistive technology. Review the result with users and revise it when evidence shows that the intended mental model, language or workflow does not match actual practice.
Evaluation should combine observed behaviour with user explanations and appropriate quantitative measures. A high satisfaction rating does not prove that a task is safe or error-free, and a short completion time may conceal skipped information. Interpret metrics in context, disclose sample limitations and examine whether outcomes differ across relevant user groups. Keep a record of decisions so that future teams can understand why a pattern was adopted.
Accessibility aims to ensure that people with diverse abilities can perceive, understand, navigate and interact with digital services. Consider visual, auditory, motor, speech and cognitive access needs, including temporary and situational limitations. Accessibility is not a special feature for a small group; it improves resilience and usability across a broad population.
Use semantic headings, labels, keyboard operation, visible focus, meaningful alternative text, captions, transcripts, sufficient contrast and correctly announced status messages. Test with screen readers and keyboard-only navigation as well as automated tools. Follow recognised standards such as WCAG and assess conformance in the actual user journeys, not just isolated components.
In practice, the design team should document the target users, primary tasks, context, assumptions and measurable acceptance criteria. Observe complete journeys rather than isolated screens, because friction often occurs between departments, devices or service channels. Record both successful and unsuccessful paths, including interruptions, recovery and exceptional cases. Findings should be prioritised according to severity, frequency, affected users and consequences.
Translate the findings into design decisions that can be tested. Specify the expected user action, the system response, the feedback presented, the error conditions and the recovery route. Check that the design works with realistic content, different input methods and assistive technology. Review the result with users and revise it when evidence shows that the intended mental model, language or workflow does not match actual practice.
Evaluation should combine observed behaviour with user explanations and appropriate quantitative measures. A high satisfaction rating does not prove that a task is safe or error-free, and a short completion time may conceal skipped information. Interpret metrics in context, disclose sample limitations and examine whether outcomes differ across relevant user groups. Keep a record of decisions so that future teams can understand why a pattern was adopted.
Mobile interaction is shaped by small screens, touch input, variable connectivity, orientation, battery use and frequent interruptions. Controls should have comfortable touch targets and sufficient spacing. Important tasks should not depend on hover, precision pointer movement or wide-screen layouts.
Responsive design reorganises content according to the viewport while preserving meaning and task completion. Prioritise essential content, avoid horizontal scrolling for ordinary reading and provide clear input types for mobile keyboards. Test on real devices and network conditions, including low-cost devices and older browsers used by the target population.
In practice, the design team should document the target users, primary tasks, context, assumptions and measurable acceptance criteria. Observe complete journeys rather than isolated screens, because friction often occurs between departments, devices or service channels. Record both successful and unsuccessful paths, including interruptions, recovery and exceptional cases. Findings should be prioritised according to severity, frequency, affected users and consequences.
Translate the findings into design decisions that can be tested. Specify the expected user action, the system response, the feedback presented, the error conditions and the recovery route. Check that the design works with realistic content, different input methods and assistive technology. Review the result with users and revise it when evidence shows that the intended mental model, language or workflow does not match actual practice.
Evaluation should combine observed behaviour with user explanations and appropriate quantitative measures. A high satisfaction rating does not prove that a task is safe or error-free, and a short completion time may conceal skipped information. Interpret metrics in context, disclose sample limitations and examine whether outcomes differ across relevant user groups. Keep a record of decisions so that future teams can understand why a pattern was adopted.
A prototype is an artefact used to explore an idea, test assumptions or communicate behaviour. Low-fidelity prototypes may be sketches or paper screens; medium-fidelity prototypes show more detailed structure; high-fidelity prototypes simulate visual design and interactions. Fidelity should match the question being tested.
Early prototypes make it inexpensive to change structure and workflow before code is written. They should include realistic tasks and representative content. A polished prototype can create false confidence if users are only evaluating appearance rather than the underlying service. Clearly communicate what is functional, simulated or intentionally incomplete.
In practice, the design team should document the target users, primary tasks, context, assumptions and measurable acceptance criteria. Observe complete journeys rather than isolated screens, because friction often occurs between departments, devices or service channels. Record both successful and unsuccessful paths, including interruptions, recovery and exceptional cases. Findings should be prioritised according to severity, frequency, affected users and consequences.
Translate the findings into design decisions that can be tested. Specify the expected user action, the system response, the feedback presented, the error conditions and the recovery route. Check that the design works with realistic content, different input methods and assistive technology. Review the result with users and revise it when evidence shows that the intended mental model, language or workflow does not match actual practice.
Evaluation should combine observed behaviour with user explanations and appropriate quantitative measures. A high satisfaction rating does not prove that a task is safe or error-free, and a short completion time may conceal skipped information. Interpret metrics in context, disclose sample limitations and examine whether outcomes differ across relevant user groups. Keep a record of decisions so that future teams can understand why a pattern was adopted.
Usability testing observes representative participants attempting realistic tasks while researchers collect evidence about completion, errors, time, navigation and experience. Moderated tests allow probing; unmoderated tests can reach more participants but provide less contextual insight. Heuristic evaluation and cognitive walkthroughs offer expert inspection methods.
Prepare neutral task scenarios, consent procedures, test environments and a plan for recording observations. Avoid leading participants toward the expected solution. Distinguish a usability problem from a participant's unfamiliarity with the domain, but do not dismiss repeated difficulties as user error. Prioritise findings by severity, frequency and impact.
In practice, the design team should document the target users, primary tasks, context, assumptions and measurable acceptance criteria. Observe complete journeys rather than isolated screens, because friction often occurs between departments, devices or service channels. Record both successful and unsuccessful paths, including interruptions, recovery and exceptional cases. Findings should be prioritised according to severity, frequency, affected users and consequences.
Translate the findings into design decisions that can be tested. Specify the expected user action, the system response, the feedback presented, the error conditions and the recovery route. Check that the design works with realistic content, different input methods and assistive technology. Review the result with users and revise it when evidence shows that the intended mental model, language or workflow does not match actual practice.
Evaluation should combine observed behaviour with user explanations and appropriate quantitative measures. A high satisfaction rating does not prove that a task is safe or error-free, and a short completion time may conceal skipped information. Interpret metrics in context, disclose sample limitations and examine whether outcomes differ across relevant user groups. Keep a record of decisions so that future teams can understand why a pattern was adopted.
Useful metrics include task completion rate, time on task, error frequency, abandonment, assistance required, satisfaction ratings and accessibility barriers. Metrics need operational definitions. For example, completion should specify whether partial success, assistance or critical mistakes count as failure.
Comparative experiments may test alternative designs, but results depend on sampling, task equivalence, randomisation, learning effects and statistical power. A/B testing is appropriate when outcomes can be measured safely and users are not exposed to unacceptable risk. Qualitative observation explains mechanisms that numerical results alone may not reveal.
In practice, the design team should document the target users, primary tasks, context, assumptions and measurable acceptance criteria. Observe complete journeys rather than isolated screens, because friction often occurs between departments, devices or service channels. Record both successful and unsuccessful paths, including interruptions, recovery and exceptional cases. Findings should be prioritised according to severity, frequency, affected users and consequences.
Translate the findings into design decisions that can be tested. Specify the expected user action, the system response, the feedback presented, the error conditions and the recovery route. Check that the design works with realistic content, different input methods and assistive technology. Review the result with users and revise it when evidence shows that the intended mental model, language or workflow does not match actual practice.
Evaluation should combine observed behaviour with user explanations and appropriate quantitative measures. A high satisfaction rating does not prove that a task is safe or error-free, and a short completion time may conceal skipped information. Interpret metrics in context, disclose sample limitations and examine whether outcomes differ across relevant user groups. Keep a record of decisions so that future teams can understand why a pattern was adopted.
Heuristic evaluation uses recognised usability principles to inspect an interface. Common principles include visibility of system status, match between system and real world, user control, consistency, error prevention, recognition rather than recall, flexibility, minimalist design and helpful recovery.
A cognitive walkthrough examines whether a new or infrequent user can identify the correct action, see that it is available, associate it with the goal and understand feedback. Evaluators should inspect complete task paths and document evidence, severity and recommendations. Expert review is efficient but does not replace user testing.
In practice, the design team should document the target users, primary tasks, context, assumptions and measurable acceptance criteria. Observe complete journeys rather than isolated screens, because friction often occurs between departments, devices or service channels. Record both successful and unsuccessful paths, including interruptions, recovery and exceptional cases. Findings should be prioritised according to severity, frequency, affected users and consequences.
Translate the findings into design decisions that can be tested. Specify the expected user action, the system response, the feedback presented, the error conditions and the recovery route. Check that the design works with realistic content, different input methods and assistive technology. Review the result with users and revise it when evidence shows that the intended mental model, language or workflow does not match actual practice.
Evaluation should combine observed behaviour with user explanations and appropriate quantitative measures. A high satisfaction rating does not prove that a task is safe or error-free, and a short completion time may conceal skipped information. Interpret metrics in context, disclose sample limitations and examine whether outcomes differ across relevant user groups. Keep a record of decisions so that future teams can understand why a pattern was adopted.
UX work in agile teams should be continuous rather than a one-time phase before development. Researchers and designers collaborate with product owners, engineers, testers, support teams and users. Discovery work can inform upcoming iterations while design and engineering validate implementation details together.
Design systems provide reusable components, interaction patterns, accessibility rules and documentation. They improve consistency and speed, but components must remain adaptable to genuine user needs. Teams should include usability criteria in acceptance tests, review implemented interfaces and ensure that design decisions survive responsive behaviour and real data.
In practice, the design team should document the target users, primary tasks, context, assumptions and measurable acceptance criteria. Observe complete journeys rather than isolated screens, because friction often occurs between departments, devices or service channels. Record both successful and unsuccessful paths, including interruptions, recovery and exceptional cases. Findings should be prioritised according to severity, frequency, affected users and consequences.
Translate the findings into design decisions that can be tested. Specify the expected user action, the system response, the feedback presented, the error conditions and the recovery route. Check that the design works with realistic content, different input methods and assistive technology. Review the result with users and revise it when evidence shows that the intended mental model, language or workflow does not match actual practice.
Evaluation should combine observed behaviour with user explanations and appropriate quantitative measures. A high satisfaction rating does not prove that a task is safe or error-free, and a short completion time may conceal skipped information. Interpret metrics in context, disclose sample limitations and examine whether outcomes differ across relevant user groups. Keep a record of decisions so that future teams can understand why a pattern was adopted.
Ethical HCI considers autonomy, informed choice, dignity, fairness, transparency, privacy and the distribution of benefits and harms. Interfaces influence behaviour through defaults, framing, timing and the visibility of choices. Designers should recognise this power and avoid exploiting cognitive biases to obtain consent or purchases.
Dark patterns include obstructive cancellation, hidden costs, forced continuity, misleading urgency, confirm-shaming and confusing consent controls. Trustworthy design makes material terms clear, presents meaningful choices and allows users to change decisions. Collect only necessary data, explain its use and provide understandable privacy controls.
In practice, the design team should document the target users, primary tasks, context, assumptions and measurable acceptance criteria. Observe complete journeys rather than isolated screens, because friction often occurs between departments, devices or service channels. Record both successful and unsuccessful paths, including interruptions, recovery and exceptional cases. Findings should be prioritised according to severity, frequency, affected users and consequences.
Translate the findings into design decisions that can be tested. Specify the expected user action, the system response, the feedback presented, the error conditions and the recovery route. Check that the design works with realistic content, different input methods and assistive technology. Review the result with users and revise it when evidence shows that the intended mental model, language or workflow does not match actual practice.
Evaluation should combine observed behaviour with user explanations and appropriate quantitative measures. A high satisfaction rating does not prove that a task is safe or error-free, and a short completion time may conceal skipped information. Interpret metrics in context, disclose sample limitations and examine whether outcomes differ across relevant user groups. Keep a record of decisions so that future teams can understand why a pattern was adopted.
Conversational interfaces use text or speech to support requests, questions and task completion. They must handle ambiguity, context, interruptions, misunderstandings and recovery. Users need to know what the system can do, what it has understood and whether an action has been completed.
Voice interfaces face challenges involving accents, background noise, speech privacy and recognition errors. Multimodal systems can combine speech, touch, text and visual confirmation. High-impact actions should be confirmed clearly, and users should have alternatives when speech recognition fails or a private environment is unavailable.
In practice, the design team should document the target users, primary tasks, context, assumptions and measurable acceptance criteria. Observe complete journeys rather than isolated screens, because friction often occurs between departments, devices or service channels. Record both successful and unsuccessful paths, including interruptions, recovery and exceptional cases. Findings should be prioritised according to severity, frequency, affected users and consequences.
Translate the findings into design decisions that can be tested. Specify the expected user action, the system response, the feedback presented, the error conditions and the recovery route. Check that the design works with realistic content, different input methods and assistive technology. Review the result with users and revise it when evidence shows that the intended mental model, language or workflow does not match actual practice.
Evaluation should combine observed behaviour with user explanations and appropriate quantitative measures. A high satisfaction rating does not prove that a task is safe or error-free, and a short completion time may conceal skipped information. Interpret metrics in context, disclose sample limitations and examine whether outcomes differ across relevant user groups. Keep a record of decisions so that future teams can understand why a pattern was adopted.
AI-assisted interfaces may recommend content, predict intent, summarise information or automate parts of a workflow. Users need calibrated expectations: the interface should explain when AI is involved, what information supports an output and where uncertainty or limitations remain. Fluent presentation must not imply that an output is always correct.
Adaptive interfaces can personalise content or interaction, but unexpected changes may undermine predictability and control. Provide ways to inspect, correct or disable personalisation where appropriate. Evaluate performance across user groups, monitor automation bias and ensure that users can appeal consequential decisions or reach a human support channel.
In practice, the design team should document the target users, primary tasks, context, assumptions and measurable acceptance criteria. Observe complete journeys rather than isolated screens, because friction often occurs between departments, devices or service channels. Record both successful and unsuccessful paths, including interruptions, recovery and exceptional cases. Findings should be prioritised according to severity, frequency, affected users and consequences.
Translate the findings into design decisions that can be tested. Specify the expected user action, the system response, the feedback presented, the error conditions and the recovery route. Check that the design works with realistic content, different input methods and assistive technology. Review the result with users and revise it when evidence shows that the intended mental model, language or workflow does not match actual practice.
Evaluation should combine observed behaviour with user explanations and appropriate quantitative measures. A high satisfaction rating does not prove that a task is safe or error-free, and a short completion time may conceal skipped information. Interpret metrics in context, disclose sample limitations and examine whether outcomes differ across relevant user groups. Keep a record of decisions so that future teams can understand why a pattern was adopted.
Internationalisation prepares software to support multiple languages, scripts, date formats, currencies, time zones, number conventions and text directions. Localisation adapts content and interaction to a particular linguistic and cultural context. Translation alone may not address local expectations, legal requirements or common workflows.
Allow for text expansion, right-to-left layouts, local address structures and culturally appropriate examples. Avoid assuming that symbols, colours or gestures carry identical meanings everywhere. Test with local users and translators, and keep content separate from code so that updates can be made without rebuilding core functionality.
In practice, the design team should document the target users, primary tasks, context, assumptions and measurable acceptance criteria. Observe complete journeys rather than isolated screens, because friction often occurs between departments, devices or service channels. Record both successful and unsuccessful paths, including interruptions, recovery and exceptional cases. Findings should be prioritised according to severity, frequency, affected users and consequences.
Translate the findings into design decisions that can be tested. Specify the expected user action, the system response, the feedback presented, the error conditions and the recovery route. Check that the design works with realistic content, different input methods and assistive technology. Review the result with users and revise it when evidence shows that the intended mental model, language or workflow does not match actual practice.
Evaluation should combine observed behaviour with user explanations and appropriate quantitative measures. A high satisfaction rating does not prove that a task is safe or error-free, and a short completion time may conceal skipped information. Interpret metrics in context, disclose sample limitations and examine whether outcomes differ across relevant user groups. Keep a record of decisions so that future teams can understand why a pattern was adopted.
In healthcare, transport, education, finance and public administration, interface errors can have serious consequences. Design must account for workload, time pressure, role permissions, auditability, hand-offs and exceptional conditions. Critical information should be clear, and high-risk actions should include appropriate safeguards without creating alert fatigue.
Use hazard analysis, scenario testing, simulation and domain-expert review. Make system state and uncertainty visible. Design for degraded operation and recovery when connectivity or a dependent service fails. Evaluate the complete socio-technical system, including training, procedures, staffing and organisational incentives.
In practice, the design team should document the target users, primary tasks, context, assumptions and measurable acceptance criteria. Observe complete journeys rather than isolated screens, because friction often occurs between departments, devices or service channels. Record both successful and unsuccessful paths, including interruptions, recovery and exceptional cases. Findings should be prioritised according to severity, frequency, affected users and consequences.
Translate the findings into design decisions that can be tested. Specify the expected user action, the system response, the feedback presented, the error conditions and the recovery route. Check that the design works with realistic content, different input methods and assistive technology. Review the result with users and revise it when evidence shows that the intended mental model, language or workflow does not match actual practice.
Evaluation should combine observed behaviour with user explanations and appropriate quantitative measures. A high satisfaction rating does not prove that a task is safe or error-free, and a short completion time may conceal skipped information. Interpret metrics in context, disclose sample limitations and examine whether outcomes differ across relevant user groups. Keep a record of decisions so that future teams can understand why a pattern was adopted.
UX strategy connects user needs with organisational goals and product decisions. It identifies target groups, experience principles, priority journeys, measurable outcomes and the capabilities required to deliver them. Product teams should balance usability, accessibility, reliability, privacy and commercial or service objectives.
Continuous improvement combines analytics, feedback, support requests, field research and usability tests. Quantitative indicators show where friction may occur; qualitative research explains why. Establish a cadence for reviewing evidence, prioritising changes and checking whether interventions improved outcomes without creating new problems elsewhere.
In practice, the design team should document the target users, primary tasks, context, assumptions and measurable acceptance criteria. Observe complete journeys rather than isolated screens, because friction often occurs between departments, devices or service channels. Record both successful and unsuccessful paths, including interruptions, recovery and exceptional cases. Findings should be prioritised according to severity, frequency, affected users and consequences.
Translate the findings into design decisions that can be tested. Specify the expected user action, the system response, the feedback presented, the error conditions and the recovery route. Check that the design works with realistic content, different input methods and assistive technology. Review the result with users and revise it when evidence shows that the intended mental model, language or workflow does not match actual practice.
Evaluation should combine observed behaviour with user explanations and appropriate quantitative measures. A high satisfaction rating does not prove that a task is safe or error-free, and a short completion time may conceal skipped information. Interpret metrics in context, disclose sample limitations and examine whether outcomes differ across relevant user groups. Keep a record of decisions so that future teams can understand why a pattern was adopted.
A university registration portal is difficult to use on phones. Students report unclear programme requirements, repeated form errors and uncertainty about whether submissions have been saved. Administrative staff receive many duplicate enquiries and incomplete applications.
The project team maps the registration journey, interviews students and staff, observes task completion and reviews support logs. It creates personas based on evidence, defines the main tasks and tests a simplified information architecture. The redesign uses persistent labels, clear eligibility guidance, progressive steps, save-and-resume, accessible validation and explicit submission receipts.
The team pilots with students across different devices and access needs. It measures successful completion, time, error rates, support requests and accessibility barriers. Rollout proceeds only after critical defects are resolved and staff are trained to support exceptions.
For a full project report, include a stakeholder map, research plan, task model, journey map, accessibility assessment, prototype evidence, usability findings and release criteria. Identify the trade-offs and unresolved risks. A successful redesign is demonstrated through safer and more effective completion of real tasks, not merely through a more modern appearance.
Customers abandon transfers because fees appear late, beneficiary details are difficult to verify and network interruptions create uncertainty. Some users repeat submissions because they cannot tell whether a transfer has completed.
Researchers observe the journey and identify points of uncertainty. The revised design displays fees and limits before confirmation, separates beneficiary review from final authorisation, provides clear progress and transaction references, and distinguishes pending, successful and failed states. Retry logic checks transaction status to reduce duplicate submissions.
The bank tests the flow with representative customers, including people using assistive technologies and low-bandwidth connections. It monitors completion, duplicate attempts, support contacts, error rates and complaints. Security and regulatory review are completed before release.
For a full project report, include a stakeholder map, research plan, task model, journey map, accessibility assessment, prototype evidence, usability findings and release criteria. Identify the trade-offs and unresolved risks. A successful redesign is demonstrated through safer and more effective completion of real tasks, not merely through a more modern appearance.
A public agency offers an online application that requires precise pointer use, colour recognition and lengthy uninterrupted sessions. Applicants with visual, motor and cognitive access needs struggle to complete it.
The agency conducts an accessibility audit and user research with disabled participants. It introduces semantic structure, keyboard support, visible focus, accessible names, plain-language instructions, flexible time limits and save-and-resume. The process is reviewed to remove unnecessary questions and explain why required information is collected.
The service is tested with assistive technologies and real users across the full application journey. The agency publishes accessible support routes, monitors completion gaps and maintains an ongoing process for reporting and correcting barriers.
For a full project report, include a stakeholder map, research plan, task model, journey map, accessibility assessment, prototype evidence, usability findings and release criteria. Identify the trade-offs and unresolved risks. A successful redesign is demonstrated through safer and more effective completion of real tasks, not merely through a more modern appearance.
A service organisation introduces an AI assistant to answer customer questions. Users cannot tell whether they are speaking to a person or automated system, and some generated answers are inaccurate or fail to account for account-specific restrictions.
The interface clearly identifies the assistant, states its capabilities and limits, grounds answers in approved support content and displays relevant source links. It offers a visible route to a human agent, asks for confirmation before consequential account actions and avoids requesting unnecessary sensitive information.
Evaluation measures resolution, escalation, factual accuracy, repeat contacts, user trust and error severity. High-risk topics are routed to trained staff. Conversation logs are protected, reviewed under governance rules and used to improve the service without treating generated responses as authoritative evidence.
For a full project report, include a stakeholder map, research plan, task model, journey map, accessibility assessment, prototype evidence, usability findings and release criteria. Identify the trade-offs and unresolved risks. A successful redesign is demonstrated through safer and more effective completion of real tasks, not merely through a more modern appearance.
Answer with clear definitions, relevant examples and justification of design choices. The model answers provide concise guidance for core concepts.
Model answer: The interdisciplinary study and practice of designing, evaluating and understanding interactive systems for people.
Model answer: An iterative approach that bases design on users, their tasks, requirements and context of use.
Model answer: A user directly interacts with a system; a stakeholder may influence, support or be affected by it.
Model answer: An evidence-informed representation of a user group, including goals, behaviours and constraints.
Model answer: Interviews, contextual observation, surveys, diary studies, focus groups and usability tests.
Model answer: The decomposition of a user goal into tasks, subtasks, decisions and information requirements.
Model answer: A user's internal understanding of how a system works and what actions will produce.
Model answer: The mental effort required to process information and complete a task.
Model answer: Effectiveness, efficiency and satisfaction.
Model answer: Usability concerns task effectiveness, efficiency and satisfaction; UX includes broader perceptions and responses across the experience.
Model answer: The organisation and labelling of content, functions and relationships to support finding and understanding.
Model answer: They remain available after users enter data and clarify the meaning of each field.
Model answer: Presenting essential information first and revealing additional detail when it is needed.
Model answer: Constraints, sensible defaults, clear labels, inline validation and confirmation for consequential actions.
Model answer: An inexpensive, simplified representation such as sketches or paper screens used to test early concepts.
Model answer: Observing representative users attempting realistic tasks to identify interaction problems.
Model answer: An expert inspection of an interface against established usability principles.
Model answer: A task-focused inspection asking whether users can identify, select and understand actions and feedback.
Model answer: Task completion, time on task, error rate, abandonment, assistance and satisfaction.
Model answer: It enables people with diverse abilities and circumstances to use digital services and improves inclusion and resilience.
Model answer: Semantic headings, keyboard access, visible focus, text alternatives, captions and sufficient contrast.
Model answer: An approach that adapts layout and interaction to different screen sizes and device conditions.
Model answer: An interface design that manipulates or obstructs users into choices they might not otherwise make.
Model answer: It communicates system status and outcomes, reducing uncertainty and repeated or mistaken actions.
Model answer: Internationalisation prepares a product for multiple locales; localisation adapts it to a particular locale.
Model answer: The tendency to over-rely on automated recommendations or outputs, even when they may be wrong.
Model answer: (90 − 60) ÷ 90 × 100 = 33.3% reduction.
Model answer: 18 ÷ 24 × 100 = 75%.
Model answer: The findings must reflect the range of users, tasks, abilities and contexts for which the system is intended.
Model answer: Task success, accessibility defects, support contacts, satisfaction, error rates, retention and qualitative feedback.
Use these official organisations for curriculum guidance, examinations and further learning information.