Chapter 30 — Capstone assessment | 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 30 — Capstone assessment

Lesson map

Lesson 30 published. Map, example, EX088.

flowchart TD
  N0["Learning outcomes"]
  N1["30.1 Evaluating the tool"]
  N2["30.2 Presenting"]
  N3["30.3 Reflecting on the role"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4
  N4 --> EX["Worked example"]
  EX --> Q["Exercise EX088"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["30.1 Evaluating the tool"]
  N2["30.2 Presenting"]
  N3["30.3 Reflecting on the role"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX088"]

[Learning outcomes]
    |
    v
[30.1 Evaluating the tool]
    |
    v
[30.2 Presenting]
    |
    v
[30.3 Reflecting on the role]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX088]

Learning outcomes

You will (1) evaluate the capstone tool; (2) present results to assessors and managers; (3) reflect on the technologist's role in human factors.

30.1 Evaluating the tool

After six weeks, Lucas evaluates the tool. Managers logged callbacks for every bank detail change, compared with about two thirds recorded in the old spreadsheet. The median time to complete a callback fell from about six minutes to about three, because numbers were easier to find. Seven out-of-date numbers were re-verified. Managers rate the tool as easy to use. He notes that six weeks covers only a few payment cycles, so longer monitoring is needed before drawing firm conclusions. He shares the results with managers.

30.2 Presenting

Lucas presents to Marta, an external assessor and the practice manager. He explains the problem, design, tests and results, and shows the documentation. The assessor asks what happens if the tool is down; Lucas shows that the runbook falls back to the printed list kept in the finance office. The practice manager asks whether the tool could include vendors for remote access; Lucas agrees it could and suggests this as a next step. Answers grounded in documentation reassure the assessors. The assessors take notes.

30.3 Reflecting on the role

Lucas reflects on the role of a technologist in human factors. He began thinking his job was to configure tools; he now sees that tools succeed only when they fit people's work, are explained respectfully and are maintained after launch. He notes the value of ethical practice, such as open role-play instead of secret tests. Marta notes his growth and awards a high mark. Lucas accepts a junior role with the IT contractor, continuing to support Brightwell's programme. He thanks the practice manager.

Worked example

Lucas evaluates his tool, presents with a fallback plan and reflects on the technologist's human factors role.

Synthetic case. The assessment is synthetic.

Errors and limits

Six weeks is short. Assessors may favour polished presentations.

Exercises

EX088 — Callback logging. How did callback logging change? Rubric: 3 = from about two thirds to all changes;; 2 = complete;; 1 = vague;; 0 = none.
EX089 — Callback time. How did median callback time change? Rubric: 3 = from about six to about three minutes;; 2 = halved;; 1 = vague;; 0 = none.
EX090 — Fallback. What is the fallback if the tool is down? Rubric: 3 = the printed list in the finance office;; 2 = printed list;; 1 = vague;; 0 = none.

Synthesis

Capstone assessment checks real effects and shows how tools must fit people to succeed.

Continue studying — chapter 30 of 30

← Chapter 29 (draft) · Course chapter index · Worked results ↓ · Next course via chapter index →