Chapter 10 — Human factors and cyber policy: quality and troubleshooting

Lesson map

Lesson 10 published. Map, example, EX046.

flowchart TD
  N0["Learning outcomes"]
  N1["10.1 Quality checks"]
  N2["10.2 Troubleshooting"]
  N3["Lab — Housing officer reports by month"]
  N4["10.3 Continuous improvement"]
  N5["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> N5
  N5 --> EX["Worked example"]
  EX --> Q["Exercise EX046"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["10.1 Quality checks"]
  N2["10.2 Troubleshooting"]
  N3["Lab — Housing officer reports by month"]
  N4["10.3 Continuous improvement"]
  N5["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> Q["EX046"]

[Learning outcomes]
    |
    v
[10.1 Quality checks]
    |
    v
[10.2 Troubleshooting]
    |
    v
[Lab — Housing officer reports by month]
    |
    v
[10.3 Continuous improvement]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX046]

Learning outcomes

You will (1) check the quality of the reporting service; (2) troubleshoot a problem; (3) improve the service continuously.

10.1 Quality checks

Grace checks quality monthly: are verdicts sent within one working day; are verdicts correct; are reports from all teams arriving; and are templates clear? She samples ten verdicts each month and asks the IT supplier to confirm them. She also asks two reporters each month, chosen at random, whether the reply was helpful. Quality checks catch slow drift, such as templates becoming outdated or replies becoming curt during busy periods, before staff lose confidence in the service. She logs each result.

10.2 Troubleshooting

In month four, reports from housing officers drop sharply. Grace checks the filter logs and finds no fall in suspicious messages. She asks two officers and learns that a tablet update removed the report button from the mail app. They had assumed reporting was no longer wanted. The IT supplier restores the button and adds a check after updates. Grace sends a message explaining the problem and thanking officers. The lab shows reports per month for housing officers, with the drop and the recovery.

Lab — Housing officer reports by month

# Housing officer reports by month (synthetic).
for m, n in enumerate([11, 14, 16, 2, 15, 17], 1): print(f"month {m}: {n}")

Run with python3 lab_officers.py. Verified output:

month 1: 11
month 2: 14
month 3: 16
month 4: 2
month 5: 15
month 6: 17

10.3 Continuous improvement

Grace keeps an improvement log listing problems, causes, fixes and dates. She reviews it quarterly with Alan and the IT supplier, looking for patterns. Two entries involve updates removing settings, so the supplier adds a standard post-update checklist. One involves a confusing template, which she rewrites. Continuous improvement turns individual fixes into lasting changes, which is important in a small organisation where the same problems would otherwise recur whenever systems change or staff move on. Alan reads the log each quarter.

Worked example

Grace runs monthly quality checks, traces a housing officer reporting drop to a tablet update and keeps an improvement log that leads to a post-update checklist.

Synthetic case. Data are synthetic.

Errors and limits

Samples may miss problems. Logs need review.

Exercises

• EX046 — Quality questions. Name two monthly quality questions.
  Show marking criteria

  Rubric: 3 = verdict speed and correctness;; 2 = two;; 1 = vague;; 0 = none.
• EX047 — Drop cause. What caused the housing officer drop?
  Show marking criteria

  Rubric: 3 = a tablet update removed the report button;; 2 = update;; 1 = fewer attacks;; 0 = none.
• EX048 — Lab drop. How did housing officer reports move across the six months?
  Show marking criteria

  Rubric: 3 = 14 and 16, then 2 in month four, then 15;; 2 = drop and recovery;; 1 = vague;; 0 = none.
• EX049 — Pattern found. What pattern did the improvement log reveal?
  Show marking criteria

  Rubric: 3 = updates removing settings;; 2 = updates;; 1 = vague;; 0 = none.
• EX050 — Supplier fix. What did the supplier add?
  Show marking criteria

  Rubric: 3 = a standard post-update checklist;; 2 = checklist;; 1 = vague;; 0 = none.

Synthesis

Quality checks and an improvement log turn fixes into lasting service improvements.

Continue studying — chapter 10 of 12

← Chapter 09 (draft) · Course chapter index · Chapter 11 (draft) →