Kaiako Run-Sheet — HCI External (Digital Technologies 1.3)
Level 1 · 5 credits · externally assessed. “Demonstrate understanding of usability in human-computer interfaces.” Everything in this unit is exam preparation, not internal assessment.
1 · What Achieved, Merit and Excellence actually are
Quoted from the achievement standard itself (Achievement Criteria and Explanatory Note 1) — not paraphrased.
| Grade | The criterion | What the explanatory note says it involves |
|---|---|---|
| Achieved | “Demonstrate understanding of usability in human-computer interfaces” | describing the purpose of interfaces · describing usability principles and their use |
| Merit | “Examine the usability of human-computer interfaces” | explaining how principles have been applied · explaining usability in terms of those principles |
| Excellence | “Evaluate the usability of human-computer interfaces” | comparing the usability of interfaces · applying principles to suggest improvements |
The one sentence that matters. The verb progression is demonstrates understanding → examines → evaluates, and Excellence adds exactly two things: a comparison and a principle-grounded improvement. That is the whole of it. Excellence is not “the same answer, longer.”
Say these out loud — Monday, and again Friday
- Achieved — describe what is there. “Tell me what this interface is for, point at something a person could actually see or click, and name the principle it uses. If I can’t picture the thing you’re pointing at, you haven’t described it yet.”
- Merit — explain how it works and what it does to somebody. “Now tell me how that feature applies the principle, what changes for one named person doing one exact task, and why that matters to what the interface exists to do. If your sentence would still be true about a completely different app, it isn’t an explanation.”
- Excellence — compare, judge, improve. “Take the same action in two interfaces. Say which one does it better and why, using the principles. Then propose a specific change that isn’t already there, and say what it would do for that person. That’s evaluation.”
2 · The chain — write it on the board Monday, leave it up all week
feature → principle → evidence → effect on user/task → effect on interface purpose → judgement / trade-off
- Links 1–2 (feature, principle) — Achieved. Get these wrong and everything above is wrong too, however well written.
- Links 3–5 (evidence, effect on the user’s task, effect on purpose) — Merit.
- Link 6, plus a like-for-like comparison and a specific improvement — Excellence.
3 · The same feature, written three ways
Interface: CityLink Events A and B, both on the Task 11 practice pack, so the whole class looks at the same evidence. Feature: how the interface confirms an event was saved. User: Sam, who has low vision and uses a keyboard, saving Saturday’s Harbour workshop.
These three paragraphs were written for this run-sheet to make the difference visible. They are not NZQA exemplars. Show them, then let ākonga write their own.
ACHIEVED — demonstrates understanding
CityLink Events exists to help people find local events and keep track of the ones they want to go to. In Interface B, after the user selects “Save event”, a message appears reading “Saved: Harbour workshop”, with an “Undo” option beside it. This uses visibility of system status, because the interface tells the user what it has just done. The Undo option also uses user control and freedom, because it gives the user a way back out of an action they did not mean to take.
Why it stops here: purpose named, a feature you could point at, two principles with their use described. No mechanism, no named user, no comparison.
MERIT — examines
Interface B applies visibility of system status by returning a written confirmation that names the specific event: “Saved: Harbour workshop”. How it does that matters for Sam, who has low vision. She does not have to notice a small change in a star icon, and she does not have to remember which row she was on when she clicked, because the interface states both the outcome and the thing it happened to. She can also enlarge that text with the A+ control, which she cannot do to an icon’s colour. This removes the step where an uncertain user clicks a second time to check — the step that produces duplicate saves and, worse, a user who arrives on Saturday without the event stored at all. Because Sam can confirm the save at the moment she makes it, the site is better able to do what it exists to do.
Why it’s a Merit: explains how the principle is applied, traces the mechanism through a named user on an exact task, and reaches the interface’s purpose. Still no comparison, no improvement.
EXCELLENCE — evaluates
For the same action — saving the Harbour workshop and confirming it is saved — Interface A gives Sam a star icon that changes state, with no words and no named confirmation, while B returns “Saved: Harbour workshop” with an Undo beside it. B is more effective for Sam on this task. On visibility of system status, A requires her to perceive a small graphic change and infer which event it belongs to; B states the outcome and the object together. On user control and freedom, A offers no visible route back from a wrong save, whereas B’s Undo sits inside the same message. On accessibility, B carries availability in text while A encodes it in a colour key she may not be able to use at all. A is not simply the worse design: it shows more events per screen, so a user who can scan quickly gets more information for less scrolling. That compactness is a genuine trade-off, not a fault.
Two improvements to A. First, give A’s star a text label that changes to “Saved” when the event is stored — this applies visibility of system status and gives Sam B’s confirmation without giving up A’s compact layout. Second, mark availability with text or a shape as well as colour, so meaning is not carried by colour alone — this applies accessibility and lets Sam rule out full events before opening them. Neither change is already present in A.
One limit: a static mock-up cannot show whether either interface is keyboard-operable or whether focus is visible, so I cannot judge the keyboard part of Sam’s task from this evidence.
Why it’s an Excellence: like-for-like comparison (the same action, not two different features) · a judgement about which is more effective · three principles doing the comparing · two specific improvements that aren’t already there · and the trade-off and evidence limit are what make it read as a judgement rather than a preference.
4 · The most common way ākonga fall short
| Grade | The shortfall | The fix, in one prompt |
|---|---|---|
| Achieved | Writing the definition of a principle instead of its use. “Error prevention is when the design stops errors before they happen” is a definition — it scores nothing alone, because the criterion asks for principles and their use. | “Point at it. What would I see on the screen?” |
| Merit | Replacing the mechanism with an adjective — “easier”, “more user-friendly”. Conclusions with the reasoning deleted, true of almost any interface. Second most common: stopping at the user and never reaching the interface’s purpose. | “Easier for whom, at which exact step, compared with what?” |
| Excellence | Writing more rather than differently — a longer Merit with no comparison. Where they do compare, comparing unlike things: a feature in A against a different feature in B. Close behind: proposing an “improvement” the interface already has. | “Same action in both. Which one, and why? What would you change that isn’t already there?” |
5 · Where each task sits on the chain
| Task | Chain links | What it is really for |
|---|---|---|
| Task 6 — Confusing terms | 1 → 2 | Getting the label right when two heuristics are genuinely confusable. Protects every grade above it. |
| Task 7 — Mātāpono Māori | 2 → 3 | Is the label earned by the evidence, or attached after the fact? |
| Task 8 — Accessibility | 1 → 5 + a limitation | First time they run the whole chain to purpose. |
| Task 9 — Precision revision | 2 under time + 6 | Choosing the most precise lens when several fit, and defending it. |
| Task 10 — Studied interface | 3 | Building the evidence bank. The specification requires a studied interface; this is where they get one. |
| Task 11 — External rehearsal | 1 → 6, timed | The Excellence rehearsal: comparison and improvements under time. |
6 · Two things to be ready for on mātāpono Māori
A real exam-room risk. This unit rightly teaches “not evidenced here” as a valid, honest finding. But the marking schedule has carried an OR-branch at Merit requiring candidates to discuss two practical examples of applying Māori usability principles to a scenario. A student trained only to test claims could freeze there and score nothing.
Give them an always-safe base they can write from: accurate te reo Māori; spell-check and text support that works for te reo; and support for tikanga and mātauranga in how content is organised and presented. Teach both moves — test the claim and supply an example.
Our unit sets a slightly higher bar than was actually marked. These pages insist on a trade-off; the standard asks only for comparison + improvement. Treat the trade-off as what makes a judgement convincing, not as a gate that costs a grade.
7 · Verify these yourself — I could not
- The exam date. The specification links the national examinations timetable rather than naming one.
- What candidates may bring in — notes, the Task 10 organiser, screenshots. The specification is silent beyond “computer access”. Assume nothing; check with NZQA or your exam centre.
- The 2026 paper shape and cut scores. Genuinely unknown. Do not tell ākonga a specific mark is Excellence as a 2026 fact — the figures we have are from a previous year’s schedule.
- Whether your associate teacher has covered anything past Task 5 — the hub records only Tasks 1–5 as delivered.