◇ OpenCyber Academy
Engineering · Chapter 39 · English

Chapter 39 — Data governance: maintainability

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 39 — Data governance: maintainability

Lesson map

Lesson 39 published. Map, example, EX115.

flowchart TD
  N0["Learning outcomes"]
  N1["39.1 People change"]
  N2["39.2 Knowledge transfer"]
  N3["39.3 Retiring things"]
  N4["39.4 Sustaining effort"]
  N0 --> N1 --> N2 --> N3 --> N4
  N4 --> EX["Worked example"]
  EX --> Q["Exercise EX115"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["39.1 People change"]
  N2["39.2 Knowledge transfer"]
  N3["39.3 Retiring things"]
  N4["39.4 Sustaining effort"]
  N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX115"]
[Learning outcomes]
    |
    v
[39.1 People change]
    |
    v
[39.2 Knowledge transfer]
    |
    v
[39.3 Retiring things]
    |
    v
[39.4 Sustaining effort]
    |
    v
[Worked example] --> [Exercise EX115]

Learning outcomes

You will (1) keep governance sustainable as people and systems change; (2) manage knowledge transfer; (3) retire obsolete controls and data.

39.1 People change

Owners and stewards move jobs. Kofi finds that when the billing steward left, nobody updated tariff reference data for two months. He proposes handover checklists for governance roles, deputies for each owner and steward and an annual confirmation that role holders still hold their roles. Ownership records in the catalogue are linked to the staff directory, so leavers trigger a reminder to the governance lead to assign a successor. Deputies attend the monthly owner reviews, so they already understand current issues when they need to take over a role.

39.2 Knowledge transfer

Much governance knowledge sits in people's heads: why a threshold was set, which vendor contact actually fixes problems. Kofi encourages owners to write short notes in decision records and runbooks. He runs a session where outgoing and incoming stewards walk through open breaks together. He explains that maintainable governance depends on recorded reasons, since new staff otherwise either undo sensible choices or preserve outdated ones without knowing why they exist. The session is recorded in notes and repeated whenever a steward role changes hands.

39.3 Retiring things

Data sets and controls that are no longer needed still cost effort and carry risk. Kofi introduces an annual review of catalogue entries, retiring data sets with no recent use after checking with owners and applying retention rules. He finds old extracts containing customer details last used years ago and arranges their deletion with records of approval. Retiring controls follows the injection test approach from earlier chapters. The review also finds three tables that nobody can explain, which are archived and flagged until an owner is identified or they can be deleted.

39.4 Sustaining effort

Kofi measures governance effort: hours spent by owners and stewards each month. He finds effort concentrated in a few people, which risks burnout and single points of failure. He proposes spreading steward duties and automating repetitive checks. Prof. Varga notes that governance often fails not through bad design but through fatigue, as enthusiastic early participants tire, and that sustainable effort must be planned as deliberately as any control. The governance board agrees to include steward time in job plans, so that the work is recognised rather than done on top of other duties.

Worked example

Kofi adds handover checklists, deputies and directory links, records reasons for knowledge transfer, retires old extracts with approval and spreads steward effort to prevent fatigue.

Synthetic case. Roles are synthetic.

Errors and limits

Governance relying on a few enthusiasts is fragile; plan for turnover.

Exercises

Continue studying — lesson 39 (chapter 39 of 50)

← Chapter 38 · Course chapter index · Chapter 40 →

Continue to the next authored lesson.