Task 10: Studied-Interface Evidence Organiser

1. Closed-book retrieval — six minutes

Keep notes and devices closed. Rebuild what you already know before using the organiser.

Principle families

List the principle families you remember. Add one accurate example of each.

Analytical chain

Rebuild the steps from an observable feature to an effect on interface purpose.

Feature or conclusion?

Explain why a caption button, Back button or colour setting is not automatically a usability principle.

Evidence status

What is the difference between something observed, documented and assumed?

2. Interface selection gate

The 2026 specification requires candidates to study an interface of their own choice before the assessment. Test the scope you will actually study—not an entire product ecosystem.

Chosen interface and exact scope

Purpose

Primary user/context

□ Complex enough

Several states, screens or decisions affect a task—not a single passive screen.

□ Repeatable access

I can revisit and safely repeat actions without relying only on memory.

□ Clear purpose and users

I can name what success means and who is trying to achieve it.

□ At least two task flows

I can observe two complete actions from start state to outcome.

□ Strengths and limitations

I can investigate effective choices and friction rather than defend a favourite.

□ Evidence across principles

Several lenses can be tested, without forcing every family onto the interface.

□ Privacy and safety

I will not expose private data, spend money, publish content or affect another person.

□ No forced Mātāpono

I will use Mātāpono Māori only where language, tikanga, mātauranga or another relevant Māori relationship is genuinely evidenced.

Task flow 1:

Task flow 2:

Back-up interface if access fails:

Kaiako approval:

3. Observation protocol

Frame
Name purpose, user and task.

Run
Complete once, reset, then repeat slowly.

Record
Write what appeared or happened.

Pressure-test
Vary one condition safely.

Label status
Observed, documented or assumed?

Explain
Link mechanism to user and purpose.

Compare
Keep the task or outcome alike.

Improve
Answer an evidenced limitation.

Evidence status: OBSERVED = directly seen or repeated · DOCUMENTED = supported by a named source · ASSUMED = plausible but not yet verified. Write the source beside documented evidence.

4. Evidence bank — what happened?

Complete six evidence rows across at least two task flows. Describe first; label second.

#	Observable feature	User/task	Principle
1
2
3
4
5
6

Evidence and status

#	Evidence	Evidence status: observed/documented/assumed
1
2
3
4
5
6

5. Evidence bank — why does it matter?

Use the same row numbers. Reach the purpose, test your claim, then propose a change grounded in evidence.

#	Effect on usability	Effect on purpose	Counterargument/limitation
1
2
3
4
5
6

Comparison and improvement

#	Comparison	Improvement
1
2
3
4
5
6

6. Peer evidence audit

□ Observable

I can point to what happened; labels such as “easy” or “inclusive” are explained.

□ Specific user/task

The effect belongs to a named person doing a named action.

□ Evidence status

Observed, documented and assumed claims are not blurred together.

□ Effect reaches purpose

The explanation shows why the feature matters to what the interface is for.

□ Like-for-like comparison

The same action, user need or outcome is being compared.

□ Evidence-led improvement

The change answers a demonstrated limitation and notes a trade-off.

□ Principle precision

The chosen lens explains the evidence better than a plausible alternative.

□ No forced Mātāpono

A Māori concept is used only when the relevant Māori context or relationship is evidenced.

One status I changed after the audit, and why:

One evidence record I strengthened:

7. Two response plans

Build two different arguments. Use row numbers so you can see which evidence will do each job.

Response plan 1

Focus or judgement:

Evidence row numbers and principle:

Mechanism → user/task → purpose:

Comparison, limitation or trade-off:

Improvement and why it is suitable:

Response plan 2

Focus or judgement:

Evidence row numbers and principle:

Mechanism → user/task → purpose:

Comparison, limitation or trade-off:

Improvement and why it is suitable:

8. Close the organiser: recall check

Turn this page over or close the tab. Tell a partner your three strongest examples from memory. For each one, include the feature, user/task, principle, effect on usability and effect on purpose. Add one limitation. Reopen the organiser only to check what you missed.

The goal is not to memorise a pre-written paragraph. Learn the relationship between evidence, mechanism, user and purpose so you can adapt it to the question.

What I forgot or blurred:

My next retrieval date: