Nielsen’s heuristics
Use when the evidence is about system feedback, match, control/freedom, consistency, error prevention/recovery, recognition, flexibility, minimal design, or help. Classify by what a feature does, not merely how it is triggered.
Level 1 HCI external · Task 9
Precision Revision — Choose the Best Lens
A fast, argument-rich revision lesson. Every example is tempting on purpose: students must choose the most precise lens, point to evidence, and explain why a plausible alternative is weaker.
Most precise lens
Ambiguous evidence
Counterargument
Exam transfer
Conceptual guardrail: this is not an exercise in attaching a Māori term to every interface feature. Mātāpono Māori remain rich Māori concepts, not aliases for generic interface features. Students may recognise the compressed wording used in an assessment resource while still asking whether relationship, language, authority, obligation and context are genuinely evidenced.
Learning Intentions
- Distinguish Nielsen heuristics, consistency/accessibility concepts and well-evidenced uses of Mātāpono Māori.
- Choose the most precise analytical lens when two principles could plausibly apply.
- Justify a choice from observable interface evidence rather than a memorised definition.
- Use a limitation or counterargument to strengthen an exam response.
Success Criteria
- I name the feature and the user task before I name a principle.
- I explain the mechanism linking the feature to usability and interface purpose.
- I can say why another plausible lens is less precise for the evidence available.
- I do not use “Back = rangatiratanga”, “accessible = manaakitanga” or similar equations as definitions.
The Repeatable Analytical Move
Observable featureWhat can a reader actually see, hear or do?
User and taskWho is trying to do what, in what context?
Most precise principleWhich lens explains the evidence with the least forcing?
Effect and purposeHow does it change success, effort, error or access—and why does that matter?
Add the pressure test: “What other lens could fit, and what would we need to know before preferring it?” That sentence turns a label into reasoning.
Lesson Sequence
| Time | Phase | Activity | Check for |
|---|---|---|---|
| 0–5 | Retrieval dump | Without notes, pairs list the three principle families and as many examples as they can. Circle examples that are principles; underline examples that are merely features. | Students notice “caption button” is evidence, not itself the analytical conclusion. |
| 5–12 | Precision reset | Rebuild the three families: Nielsen describes interaction heuristics; consistency/accessibility describe broad usability qualities; Mātāpono Māori require Māori meaning and context, not translated labels. | No claim that the families are identical or interchangeable. |
| 12–25 | Trap round | Project Scenarios 1–6 from the worksheet. Pairs select a lens, then must defend it with user/task evidence. Accept alternatives only when the mechanism is explicit. | Reason precedes answer; “it could be both” is followed by “which is most precise here?” |
| 25–38 | Evidence pressure test | Students classify Scenarios 7–10 as strongly evidenced, possible—more evidence needed, or better explained by ordinary HCI. Use the rangatiratanga authority test where relevant. | Who has authority? Over what? What may they determine, permit, withhold or refuse? |
| 38–48 | Speed round | Run Scenarios 11–12 twice: 30 seconds to choose, then 60 seconds to justify. On the second pass, require a plausible counterargument. | Specific feature → mechanism → user effect → purpose. |
| 48–60 | Timed transfer | Students choose any one scenario and write a six-minute response. Self-check for specific evidence, effect, purpose and limitation; then improve one sentence. | Response goes beyond definition recall and makes a defensible judgement. |
Fast Reference: What Each Lens Is Doing
Consistency and accessibility
Use consistency when patterns remain coherent within an interface or align with established conventions. Use accessibility when a design decision removes or creates a barrier for a named user and task.
Mātāpono Māori
Use when the evidence genuinely involves te reo Māori, tikanga or mātauranga Māori, or a defensible relationship such as care, connection, responsibility or authority. Assessment shorthand is not a complete definition.
More than one plausible lens
State the alternative, then prefer the lens that explains the most important user effect with the strongest evidence. If evidence is missing, say so instead of forcing certainty.
Reasoned Kaiako Key
Teacher guidance — legitimate alternatives require evidence
1. A progress bar appears while a large file uploads.
Visibility of system statusThe system keeps the user informed during a waiting task. Consistency might matter if every upload behaves the same way, but the observed mechanism is feedback about current state.
2. Ctrl+Z reverses an accidental deletion. Trap
User control and freedomAlthough a keyboard shortcut can support efficiency, its function here is an escape hatch from an unwanted state. Classify by purpose, not input mechanism.
3. Every page puts the main navigation in the same place and order.
Internal consistencyThe evidence is repeated patterning within the interface. Nielsen’s consistency and standards is also defensible; a strong student names the overlap and makes clear which vocabulary they are using.
4. A video player offers captions and a transcript. Two lenses
AccessibilityFor a Deaf or hard-of-hearing user accessing spoken information, the alternatives remove a specific barrier and support the player’s communication purpose. User control is secondary because the toggle is not the main consequence.
5. A “Back” button is described as rangatiratanga. Forced-mapping risk
Better explained by ordinary HCIThe button offers user control/freedom, but no meaningful authority relationship has been established. Ask who has authority, over what, and what they can determine or refuse.
6. Search accepts kupu Māori with tohutō and returns the correct te reo content.
Mātāpono Māori — strongly evidencedThe observable support for accurate te reo Māori is directly relevant to usability for Māori-language users and to the interface’s information-finding purpose.
7. Users can comment, so the interface is labelled whanaungatanga. Evidence missing
Possible — more evidence neededA comment feature enables communication, but the claim needs evidence about the relationships fostered, the people involved and how the interface sustains connection. Ordinary communication usability may be more precise on the facts given.
8. An iwi-governed archive lets the iwi set access and reuse conditions for digitised taonga.
Rangatiratanga — strongly evidencedThe authority holder, object and real decisions are all visible: the iwi has authority over access and reuse and may permit, withhold or refuse them.
9. A repairable device is labelled kaitiakitanga because it lasts longer. Plausible, incomplete
Possible — more evidence neededDurability may reduce waste, but a strong claim needs evidence of the responsibility or guardianship relationship being enacted, not a one-word relabelling of sustainability.
10. A large-text setting is classified as flexibility and efficiency. Choose the consequence
Accessibility is usually more preciseIf the named user has low vision and the task is reading interface content, the setting removes a barrier. Flexibility is plausible, but it understates the access consequence.
11. A form prevents impossible dates and then explains how to correct an invalid entry.
Both prevention and recoveryDifferent features do different work: constrained input prevents some errors; the specific message helps users diagnose and recover from another. A precise response separates them.
12. A welcome greeting is labelled manaakitanga. Surface cue
Possible — insufficient by itselfA greeting may contribute to welcome, but the claim needs evidence of care or respect toward real users across the interaction. Tone alone is a weak basis for defining manaakitanga.
Grade Progression: What Changes
Demonstrates understanding
Describes the interface purpose and relevant usability principles with accurate, observable examples.
Examines
Explains how the principle is applied and how that mechanism affects usability for a user completing a task.
Evaluates
Makes and supports a judgement through comparison, significance, trade-off, suitability to user/purpose, and a specific principle-grounded improvement.
Evaluation is not “more explanation”. It adds a supported judgement: which design is more effective for a like-for-like action, how significant the difference is, what trade-off remains, and why a proposed improvement is suitable.
Student Resource
Task 9 — Most Precise Lens
Twelve deliberately ambiguous examples, a claim-strength sort, a timed response and a self-check. The worksheet contains no answers.
Open printable worksheet →Transition and Reflection
- Keep “feature is not principle” visible throughout the retrieval round.
- When students say “both”, require them to name the different mechanism each lens would explain.
- Do not turn the key into a single-label quiz: reward a well-evidenced alternative and challenge an unsupported preferred answer.
- Collect the timed response and use it to group students for Task 10: evidence selection, explanation, or evaluation support.
Which examples exposed memorised equations rather than analysis?
Which students could select the more precise lens but could not yet explain the effect on purpose?
- New Zealand Qualifications Authority. Current Level 1 Digital Technologies achievement standard and 2026 assessment specification.
- NCEA Education. Digital Technologies 1.3 — Unpacking the Standard, including its caution that Mātāpono Māori are richer than their use in an assessment standard.
- Te Taka Keegan. Māori language interfaces (2017).