Chapter 37 — Evidence review seminar

Chapter 37 — Evidence review seminar

Lesson map

Lesson 37 published. Map, example, EX109.

flowchart TD
  N0["Learning outcomes"]
  N1["37.1 The seminar"]
  N2["37.2 Judging strength"]
  N3["37.3 Constructive feedback"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4
  N4 --> EX["Worked example"]
  EX --> Q["Exercise EX109"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["37.1 The seminar"]
  N2["37.2 Judging strength"]
  N3["37.3 Constructive feedback"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX109"]

[Learning outcomes]
    |
    v
[37.1 The seminar]
    |
    v
[37.2 Judging strength]
    |
    v
[37.3 Constructive feedback]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX109]

Learning outcomes

You will (1) critique governance evidence presented by peers; (2) judge evidence strength; (3) give constructive feedback.

37.1 The seminar

In the evidence review seminar, each student presents the evidence behind one governance claim from their placement. Sofia presents the claim that Elmfield's backups work, supported by the laboratory restore test, the retest after the fix and the monthly backup job reports. A classmate presents a claim that phishing risk fell, supported only by fewer reported suspicious emails. The class discusses which claims are well supported and why. Her backup claim draws on three types of evidence, while the phishing claim relies on one count.

37.2 Judging strength

The group ranks evidence types. Independent re-performance and tests rank highest. System-generated reports rank next. Owner statements and questionnaires rank lowest. They note that fewer reported emails could mean less phishing, better filtering or less reporting, so the classmate's claim is weak. Sofia's claim is strong for the files tested but cannot prove every system is backed up. She learns that judging evidence means asking what else could explain it and how much it covers. Her claim's scope must exclude the housing system, which the supplier backs up and she never tested.

37.3 Constructive feedback

Dr. Haddad asks students to give feedback that helps. Sofia suggests her classmate add data on filtered emails and a short survey of reporting habits. She receives feedback that her claim should state its scope: the file share only, not the housing system, which the supplier backs up. She revises the claim. She learns that peer review improves claims when feedback is specific, respectful and focused on evidence rather than on the person. Stating that the claim covers only the file share keeps the board from assuming the housing system was tested as well.

Worked example

Sofia ranks evidence types, spots alternative explanations in a peer's claim and narrows her own claim's scope after feedback.

Synthetic case. The seminar and claims are synthetic.

Errors and limits

Rankings are general guides. Feedback can be too polite to help.

Exercises

• EX109 — Weakest evidence. Which evidence types rank lowest? Rubric: 3 = owner statements and questionnaires;; 2 = statements;; 1 = tests;; 0 = none.
• EX110 — Phishing alternatives. What else could explain fewer reported suspicious emails? Rubric: 3 = better filtering or less reporting;; 2 = alternatives;; 1 = vague;; 0 = none.
• EX111 — Scope correction. How did Sofia revise her backup claim? Rubric: 3 = limited it to the file share;; 2 = scope;; 1 = vague;; 0 = none.

Synthesis

Evidence review asks what else could explain a claim and how much it covers.

Continue studying — chapter 37 of 40

← Chapter 36 (draft) · Course chapter index · Chapter 38 (draft) →