Chapter 25 — Team project studio | Technologist Human factors and cyber policy

Open, free learning for anyone who wants to protect people and technology. No account is required to read this text or its worked answers.

Chapter 25 — Team project studio

Lesson map

Lesson 25 published. Map, example, EX073.

flowchart TD
  N0["Learning outcomes"]
  N1["25.1 The brief"]
  N2["25.2 Testing with users"]
  N3["25.3 Presenting choices"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4
  N4 --> EX["Worked example"]
  EX --> Q["Exercise EX073"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["25.1 The brief"]
  N2["25.2 Testing with users"]
  N3["25.3 Presenting choices"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX073"]

[Learning outcomes]
    |
    v
[25.1 The brief]
    |
    v
[25.2 Testing with users]
    |
    v
[25.3 Presenting choices]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX073]

Learning outcomes

You will (1) work in a team to design a reporting guide for patients; (2) test it with users; (3) present design choices.

25.1 The brief

In the studio, Lucas joins three classmates to design a short guide helping Brightwell's patients recognise fake messages that claim to be from the practice, such as fake payment requests or appointment cancellations with links. The brief asks for a guide that fits on one side of a card and a page on the website. Teams must test their design with at least five people from outside security and present their choices. They divide roles: research, writing, design and testing. Each member keeps a log.

25.2 Testing with users

The team tests a draft with seven people, including two older patients recruited through a community centre with consent. Testers are shown three synthetic messages and asked whether each is genuine using the card. Five of seven correctly judge all three with the card, compared with three of seven without it in an earlier round. Testers ask for larger text and a phone number to check. The team revises the card and repeats the test, with six of seven then judging correctly.

25.3 Presenting choices

The team presents to classmates and the practice manager. They explain why the card focuses on one rule, that Brightwell will never ask for payment by text link, and gives the official phone number to check. They avoid fear-inducing images, following the evidence that fear can backfire. The practice manager asks to print the card for clinics. Presenting design choices with evidence from tests makes the final product easier for others to accept and use. Classmates ask questions about the testing process and the choice of testers.

Worked example

Lucas's team designs a patient guide card, tests it with seven people and revises it to one clear rule and an official number.

Synthetic case. The studio is synthetic.

Errors and limits

Small user tests. Testers may try harder than usual.

Exercises

EX073 — Card rule. What single rule does the card state? Rubric: 3 = Brightwell never asks for payment by text link;; 2 = rule;; 1 = vague;; 0 = none.
EX074 — Test improvement. How did correct judgements change after revision? Rubric: 3 = from five to six of seven;; 2 = improved;; 1 = vague;; 0 = none.
EX075 — Tester request. What did testers ask for? Rubric: 3 = larger text and a phone number;; 2 = readability;; 1 = vague;; 0 = none.

Synthesis

Team design tested with real users produces simple, usable guidance.

Continue studying — chapter 25 of 30

← Chapter 24 (draft) · Course chapter index · Chapter 26 (draft) →