UX & Software Ergonomics
Interaction quality is examined through concrete tasks and observable system behaviour rather than design taste. ISO interaction principles can provide a reference framework, but the report must show how the selected principle connects to the tested interaction.
Short answer
Start with a defined user, task, system state and input method. Use interaction principles as a reference only where they fit the question, record observable behaviour before interpretation and test consistency, controllability and alternative explanations across comparable states.
A finding about one interaction is not a product-wide verdict. The conclusion remains tied to the examined scenario and does not substitute for a legal or contractual conformity assessment.
1. Specify the examination question and usage scenario
Replace broad statements such as “the interface is confusing” with a concrete task for a defined user group. Record goal, system version, device, input method and relevant experience.
The same interaction can be appropriate in one context and problematic in another. An expert administrative tool can assume different knowledge and information density from an infrequently used self-service workflow.
The examination records the concrete task, user group, system version, device or input method and the selected assessment criterion before interpreting the result. An observation on one path is not silently generalised to all users, components or product states. Technical and ergonomic findings are kept separate from a legal conformity assessment, and untested contexts remain outside the conclusion.
2. Use interaction principles as a reference framework
ISO 9241-110 provides general interaction principles for interactive systems. Select only principles relevant to the concrete question rather than using the standard as an automatic checklist for a global score.
Turn a principle into observable criteria: can users recognise the current state, predict the next step, reverse or control an action where appropriate, and rely on consistent behaviour for equivalent functions?
The examination records the concrete task, user group, system version, device or input method and the selected assessment criterion before interpreting the result. An observation on one path is not silently generalised to all users, components or product states. Technical and ergonomic findings are kept separate from a legal conformity assessment, and untested contexts remain outside the conclusion.
3. Assess observable interaction, not design taste
Colours and visual style can influence perception, but preference alone is not a technical finding. More robust evidence includes a required action that cannot be found, an invisible state change or inconsistent reaction to equivalent input.
Describe the interaction first, then explain its effect on the task and why a particular interaction principle is relevant. This keeps observation separate from professional interpretation.
The examination records the concrete task, user group, system version, device or input method and the selected assessment criterion before interpreting the result. An observation on one path is not silently generalised to all users, components or product states. Technical and ergonomic findings are kept separate from a legal conformity assessment, and untested contexts remain outside the conclusion.
4. Compare consistency, expectation and controllability
Compare equivalent functions across screens and states: labels, order, confirmation, cancellation, navigation and response to the same input. Repeated differences can indicate a systematic interaction pattern rather than a local defect.
Controllability depends on what the user can actually influence and understand, not merely on the presence of controls. Include loading, asynchronous operations, disabled states and recovery paths where they affect the task.
The examination records the concrete task, user group, system version, device or input method and the selected assessment criterion before interpreting the result. An observation on one path is not silently generalised to all users, components or product states. Technical and ergonomic findings are kept separate from a legal conformity assessment, and untested contexts remain outside the conclusion.
5. Test counter-hypotheses and learning effects
Missing domain knowledge, unusual test data, network delay, restricted permissions or a nonrepresentative device can create similar symptoms. Test those alternatives before attributing the issue solely to interface design.
Repeated trials can introduce learning. An experienced user may complete a difficult first-use interaction quickly, while a new user may reveal hidden assumptions. Document experience and test order where they matter.
The examination records the concrete task, user group, system version, device or input method and the selected assessment criterion before interpreting the result. An observation on one path is not silently generalised to all users, components or product states. Technical and ergonomic findings are kept separate from a legal conformity assessment, and untested contexts remain outside the conclusion.
6. Limit findings to the tested interaction
State the task, system version, criterion and observed effect. Avoid unbounded claims such as “the software is ergonomic” where only selected interactions were examined.
Not examined user groups, functions, releases and contexts stay outside the conclusion. The technical and ergonomic assessment answers a professional question about behaviour; it does not replace product acceptance or legal conformity analysis.
The examination records the concrete task, user group, system version, device or input method and the selected assessment criterion before interpreting the result. An observation on one path is not silently generalised to all users, components or product states. Technical and ergonomic findings are kept separate from a legal conformity assessment, and untested contexts remain outside the conclusion.
Depth: use interaction principles as a reference framework, not a taste judgment
One observed problem can affect several interaction principles
A confusing workflow may involve self-descriptiveness, controllability, error tolerance and conformity with expectations at the same time. The report should link observations to explicit criteria rather than aesthetic preference.
Context and alternative explanations remain part of the assessment
Task, user group, device, prior knowledge and system state can change how an interaction is experienced. The conclusion should state those conditions and consider technical or content-related alternatives where relevant.
Examination checklist
- Is the user task and scenario defined?
- Are the selected interaction principles relevant to the question?
- Are observable events separated from preferences?
- Were equivalent interactions compared for consistency?
- Was practical user control tested rather than inferred from controls?
- Were learning and environmental alternatives considered?
- Is the conclusion bounded to the tested interaction?
Constructed example
Two confirmation dialogs use similar wording, but one can be cancelled safely while the other starts an irreversible operation immediately. The examination documents the equivalent tasks, the differing system responses and the effect on user control, then limits the conclusion to the tested workflow rather than rating the whole interface.
The example is entirely constructed and does not describe a real engagement, client matter or historical case.
Sources and technical basis
- Normative referenceISO 9241-11:2018 — Usability: Definitions and concepts. Reference framework for usability and context of use. Open source.
- Normative referenceISO 9241-110:2020 — Interaction principles. General interaction principles for interactive systems. Open source.
- Normative referenceISO 9241-210:2019 — Human-centred design for interactive systems. Principles and activities for human-centred design. Open source.
- Methodological basisSources & Methodology documents source hierarchy, counter-hypothesis control and statement boundaries for the English knowledge base.
Further reading
Critical review and methodological limitation
Interaction principles are reference concepts, not automatic scoring rules. Their application depends on the defined task and evidence, and a reviewer should be able to trace each professional judgement back to an observed interaction.
Environmental and learning effects can mimic or mask interaction problems. A defensible report records those conditions and avoids turning one observed path into a universal statement about every user or product state.
Author's technical literature and publications
The following works provide additional technical and methodological context. They do not replace required primary sources, standards, manufacturer documentation or other independent specialist sources. Unpublished manuscripts, drafts and teaching materials are deliberately not presented here as public sources.
UX, Software Ergonomics & Accessibility
Technical and methodological examination of usability, context of use, interaction quality and accessible operation.
Explore this assessment service