Chapter 15 — Human factors and cyber policy: guided lab
Lesson map
Lesson 15 published. Map, example, EX043.
flowchart TD
N0["Learning outcomes"]
N1["15.1 Test setup"]
N2["15.2 Results"]
N3["Lab — Forwarding versus button task times"]
N4["15.3 Usability problems"]
N5["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5
N5 --> EX["Worked example"]
EX --> Q["Exercise EX043"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["15.1 Test setup"]
N2["15.2 Results"]
N3["Lab — Forwarding versus button task times"]
N4["15.3 Usability problems"]
N5["Synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> Q["EX043"]
[Learning outcomes]
|
v
[15.1 Test setup]
|
v
[15.2 Results]
|
v
[Lab — Forwarding versus button task times]
|
v
[15.3 Usability problems]
|
v
[Synthesis]
|
v
[Worked example] --> [Exercise EX043]
Learning outcomes
You will (1) test a report button with volunteers in a test environment; (2) measure time and success; (3) record usability problems.
15.1 Test setup
In a guided lab, Lucas sets up a test mailbox with synthetic emails and the report button installed. Eight volunteer staff take part, knowing they are testing the button, not being tested themselves. Each volunteer reports two synthetic suspicious emails using the old method, forwarding to an address, and two using the button. The order is alternated so that learning does not favour one method. Lucas records time and success, and notes any hesitation or confusion as volunteers work. Each session lasts twenty minutes.
15.2 Results
The lab compares times. Forwarding takes about forty-five seconds on average, partly because volunteers search for the address; the button takes about seven seconds. Two volunteers sent forwards to the wrong address. All succeed with the button. Volunteers rate the button as much easier. Lucas notes that the test environment is calmer than a busy reception, so real times may be longer, but the difference is so large that the button is clearly worth adopting. He writes the result in a short note for the practice manager.
Lab — Forwarding versus button task times
# Mean task times (seconds) for eight volunteers (synthetic).
fwd = [41, 52, 38, 47, 44, 50, 39, 49]; btn = [6, 8, 7, 7, 6, 9, 7, 6]
print(f"forwarding {sum(fwd) / 8:.0f} s; button {sum(btn) / 8:.0f} s")
Run with python3 lab_button.py. Verified output:
forwarding 45 s; button 7 s
15.3 Usability problems
Lucas records three problems: on the smaller reception screens the button appears only in an overflow menu; volunteers are unsure whether the report was sent because no confirmation appears; and the button does not exist in the mobile email app clinicians use. He reports these to the IT contractor, who adjusts the toolbar layout and enables a confirmation message. The mobile issue requires a different add-in, which is scheduled. Recording problems precisely makes them easier to fix. Each fix is retested.
Worked example
Lucas tests the button with eight volunteers in a test mailbox, finds large time savings and records three usability problems.
Synthetic case. The test is synthetic.
Errors and limits
Calm lab conditions. Small sample.
Exercises
- EX043 — Order alternation. Why alternate the order of methods? Rubric: 3 = so learning does not favour one method;; 2 = fairness;; 1 = vague;; 0 = none.
- EX044 — Lab times. What mean times did the lab show? Rubric: 3 = 45 seconds forwarding and 7 seconds button;; 2 = 38 saved;; 1 = vague;; 0 = none.
- EX045 — Missing confirmation. What problem did the missing confirmation cause? Rubric: 3 = volunteers were unsure the report was sent;; 2 = uncertainty;; 1 = vague;; 0 = none.
Synthesis
A guided usability test shows large gains and specific fixes.
Continue studying — chapter 15 of 30
← Chapter 14 (draft) · Course chapter index · Chapter 16 (draft) →