Chapter 5 — Engineering communication | Engineering 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 5 — Engineering communication

Lesson map

Lesson 05 published. Map, example, EX013.

flowchart TD
  N0["Learning outcomes"]
  N1["5.1 Writing for operators"]
  N2["5.2 Presenting without blame"]
  N3["5.3 Adapting the message"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4
  N4 --> EX["Worked example"]
  EX --> Q["Exercise EX013"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["5.1 Writing for operators"]
  N2["5.2 Presenting without blame"]
  N3["5.3 Adapting the message"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX013"]

[Learning outcomes]
    |
    v
[5.1 Writing for operators]
    |
    v
[5.2 Presenting without blame]
    |
    v
[5.3 Adapting the message]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX013]

Learning outcomes

You will (1) write clearly for operators and managers; (2) present behaviour data without blame; (3) adapt a message to its audience.

5.1 Writing for operators

Aiko writes a one-page note for control room operators explaining the report button. She uses short sentences, numbered steps and a screenshot. She avoids terms like phishing vector and uses plain words such as suspicious email. She tests the note with two operators, who suggest putting the most important step first: what to do if they have already clicked. Engineering communication succeeds when the reader can act correctly, quickly and without fear of looking foolish. The revised note is laminated and placed beside each console.

5.2 Presenting without blame

For managers, Aiko presents simulation results as department totals and trends, never individual names. She frames clicking as an expected outcome of good lures and focuses on reporting speed. Lain, Kostiainen and Čapkun (2022) found that reporting by staff can provide a strong signal for detection in organisations. Presenting results without blame keeps staff willing to report their own mistakes, which is when early reporting matters most. She also shows managers how a blame-free approach increased reports of genuine mistakes in the pilot team, which persuades them to keep names out of every report and to praise prompt reporting publicly.

5.3 Adapting the message

Aiko prepares three versions of the same findings: a chart and three bullet points for the board, a page of detail for the security team and the operator note. Each uses the same numbers but different emphasis. The board sees exposure time falling; the security team sees triage workload; operators see what to do. Prof. Kerr notes that adapting messages is not spin, as long as the facts are the same and limitations appear in every version. She keeps all three versions in one folder.

Worked example

Aiko writes an operator note tested with users, presents results to managers without blame and adapts one finding for three audiences.

Synthetic case. Notes and audiences are synthetic; Lain et al. (2022) is real.

Errors and limits

Simplified messages can drop caveats. Department totals can still single out tiny teams.

Exercises

EX013 — Operator suggestion. What did operators suggest moving first in the note? Rubric: 3 = what to do if you already clicked;; 2 = clicked step;; 1 = vague;; 0 = none.
EX014 — Blame-free framing. How does Aiko frame clicking for managers? Rubric: 3 = as an expected outcome of good lures, focusing on reporting speed;; 2 = expected;; 1 = failure;; 0 = none.
EX015 — Same facts. What keeps adapted messages honest? Rubric: 3 = the same facts and limitations in every version;; 2 = consistency;; 1 = vague;; 0 = none.

Synthesis

Clear, blame-free, audience-specific communication helps people act and keeps them willing to report.

Continue studying — chapter 05 of 50

← Chapter 04 (draft) · Course chapter index · Chapter 06 (draft) →