Chapter 26 — Privacy and data protection: operational handoff

Chapter 26 — Privacy and data protection: operational handoff

Lesson map

Lesson 26 published. Map, example, EX076.

flowchart TD
  N0["Learning outcomes"]
  N1["26.1 Runbooks"]
  N2["26.2 Ownership"]
  N3["26.3 Training"]
  N4["26.4 Confirmation"]
  N0 --> N1 --> N2 --> N3 --> N4
  N4 --> EX["Worked example"]
  EX --> Q["Exercise EX076"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["26.1 Runbooks"]
  N2["26.2 Ownership"]
  N3["26.3 Training"]
  N4["26.4 Confirmation"]
  N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX076"]

[Learning outcomes]
    |
    v
[26.1 Runbooks]
    |
    v
[26.2 Ownership]
    |
    v
[26.3 Training]
    |
    v
[26.4 Confirmation]
    |
    v
[Worked example] --> [Exercise EX076]

Learning outcomes

You will (1) hand over controls to operations; (2) write runbooks; (3) confirm ownership.

26.1 Runbooks

Aisha writes runbooks for CCTV checks, SDK reviews, access requests and deletions. Each runbook describes the purpose of the task, when to run it, the steps, the expected results, what to do if results are unexpected and who to contact. Aisha writes them for operations staff, not specialists, so she avoids jargon and includes screenshots from the synthetic test environment rather than real systems. The CCTV runbook, for example, lists the recorder menu path, the expected oldest clip age and the number to call when it exceeds thirty-five days.

26.2 Ownership

Each runbook names an owner in operations. The CCTV runbook belongs to the operations manager, SDK review to the app lead, access requests to the customer service lead and account deletion to the IT service manager. Each owner has a named deputy for holidays. Ownership is written into job descriptions where possible, so responsibilities survive when people move roles. Without named owners, the CCTV deletion check would depend on whoever happened to remember it, which is exactly how the firmware reset went unnoticed for six weeks.

26.3 Training

She trains the owners and watches them run each task. For each runbook, the owner performs the task while Aisha observes and notes where they hesitate or misread steps. The customer service lead struggles with the vendor search for chat transcripts, so Aisha adds clearer steps and a contact name at the vendor. Observation reveals gaps that a document review alone would miss. For the deletion runbook, the IT service manager misreads which vendor confirmation to wait for, so the step now shows an example confirmation message.

26.4 Confirmation

Owners sign acceptance. Mr. Reilly notes that handoff keeps controls alive after a project ends. Acceptance means owners agree the runbook is accurate and they can perform it. The data protection officer keeps the signed acceptances. Aisha schedules a follow-up three months later to check that tasks are running, and she leaves her contact details for questions. Handoff is complete when the tasks run without her help. Three months later, all four tasks have run on schedule without her involvement. Her role then ends.

Worked example

Aisha writes four runbooks, names owners, trains them and gets acceptance.

Synthetic case. Runbooks are synthetic.

Errors and limits

Runbooks age; review yearly.

Exercises

• EX076 — Runbooks. Name two runbooks. Rubric: 3 = CCTV checks, SDK reviews, access requests, deletions;; 2 = two;; 1 = one;; 0 = none.
• EX077 — Training. How did Aisha confirm owners could do the tasks? Rubric: 3 = watched them run each task;; 2 = partly correct;; 1 = vague;; 0 = none.
• EX078 — Purpose. Why hand over? Rubric: 3 = keeps controls alive after the project;; 2 = partly correct;; 1 = vague;; 0 = none.

Continue studying — lesson 26 (chapter 26 of 30)

← Chapter 25 · Course chapter index · Chapter 27 →

Continue to the next authored lesson.