STUDY GUIDE · GKU 1
User experience design study guide (Information Technology)
A system that works is not necessarily a system people can use. This unit is about finding out what users need, designing an interface that fits how they think, and testing whether it actually works for them. It covers research methods and the human factors behind them (cognitive load, mental models, behaviour), evidence-based personas, interface design techniques and accessibility, heuristic evaluation, prototypes of different fidelity, and usability testing with performance and affective metrics. The worked examples use the tasks and findings an IT team meets: a checkout that users abandon, a hidden button, a test with five participants.
Structured by the official ETEC subject standard for this topic: every listed topic and learning outcome, with formulas, figures and worked examples. The full sections are available to members in the app.
SKU 1.1 · Human-centered design
User research and understanding human interaction
Choosing a research method for the question asked (interview, observation, survey, diary, analytics, A/B test), telling qualitative from quantitative and behaviour from opinion, and the human factors that explain what the findings mean: cognitive load, mental models, affordances, feedback and error.
User personas
What a persona is and is not, how to build one from research rather than stereotypes, which fields carry design decisions (goals, behaviours, context, frustrations), and how proto-personas, anti-personas and multiple personas are used without inventing users.
User interface design techniques
Turning research into screens: layout and visual hierarchy, grouping and consistency, affordances and feedback, error prevention, accessibility and touch size, and the two laws that put numbers on choice and pointing: Hick's law and Fitts's law.
SKU 1.2 · Human-centered evaluation
Heuristic evaluation of user interfaces
Evaluating an interface against recognised usability principles: Nielsen's ten heuristics, how several evaluators inspect independently and consolidate, how to rate severity, and how to turn a finding into a specific, testable recommendation.
Prototyping for usability testing
Choosing a prototype's fidelity and medium for the question at hand (paper, wireframe, clickable, Wizard of Oz, coded), what each can and cannot test, formative versus summative use, and how prototypes support performance and emotional engagement testing.
Usability testing and metrics
Planning a usability test: the task, the participant, the moderator's role, performance metrics (completion, time, errors) and affective metrics (satisfaction, SUS), how many participants a formative test needs, and how to report a finding that a team can act on.
MORE INFORMATION TECHNOLOGY GUIDES
- Information management: data modelling, databases and SQL study guideGKU 6 · 8 sections
- Software fundamentals: from problem to efficient program study guideGKU 8 · 10 sections
- Cybersecurity principles: attacks, risk, detection and cryptography study guideGKU 3 · 7 sections
- Web and mobile systems: how they work and how to build them safely study guideGKU 9 · 8 sections
- Networking study guideGKU 4 · 9 sections
- Platform technologies: the operating system study guideGKU 5 · 5 sections
- Global professional practice: projects, governance and the law study guideGKU 2 · 9 sections
- System paradigms: requirements, modelling and acceptance study guideGKU 7 · 6 sections