Chapter 12 — Final review and transfer
Lesson map
Lesson 12 published. Map, example, EX056.
flowchart TD
N0["Learning outcomes"]
N1["12.1 Looking back"]
N2["12.2 Transferable methods"]
N3["12.3 Transfer example"]
N4["12.4 Sustainability"]
N5["12.5 Final review"]
N6["12.6 Answers"]
N7["12.7 Development"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> N7
N7 --> EX["Worked example"]
EX --> Q["Exercise EX056"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["12.1 Looking back"]
N2["12.2 Transferable methods"]
N3["12.3 Transfer example"]
N4["12.4 Sustainability"]
N5["12.5 Final review"]
N6["12.6 Answers"]
N7["12.7 Development"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> N7 --> Q["EX056"]
[Learning outcomes]
|
v
[12.1 Looking back]
|
v
[12.2 Transferable methods]
|
v
[12.3 Transfer example]
|
v
[12.4 Sustainability]
|
v
[12.5 Final review]
|
v
[12.6 Answers]
|
v
[12.7 Development]
|
v
[Worked example] --> [Exercise EX056]
Learning outcomes
You will (1) review learning and outcomes across the programme; (2) transfer methods to other SOC problems; (3) plan continued professional development; (4) hand over improvements sustainably.
12.1 Looking back
The programme took Daniel from explicit decision-making (chapter 1) through specialist evidence, ethics, design, evaluation, integration, difficult cases, assurance and research to an applied project. Each chapter added a method that the next used: the expected-cost reasoning from the contractor night reappeared in the partner case, peer baselines fed the fairness indicators, and the controlled evaluation of the triage playbook shaped how the applied project measured its result. Looking back lets Daniel see which methods he now uses without thinking and which still need practice.
12.2 Transferable methods
Expected-cost reasoning, peer baselines, controlled evaluation with robust statistics, structured critique and honest assurance apply beyond claims and contractors. Each has been used at Meridian outside its first setting: expected cost in the partner case, controlled evaluation for the managed provider's escalations, and honest assurance in the half-year report. What transfers is the discipline of stating beliefs, comparisons and uncertainty explicitly, not the particular numbers. The methods also give Daniel a shared language with the board, audit and legal, who meet the same reasoning in their own work.
12.3 Transfer example
Daniel applies controlled evaluation to the managed provider's escalation quality, comparing escalations before and after a template change. The comparison uses the same discipline as the triage evaluation: a defined measure, escalation precision and completeness of the provider's notes, collected the same way before and after the change. Because the template change followed the night P1 whose note lacked the source network, Daniel can check whether that gap closed. He notes that other changes at the provider during the same period could also affect the result.
12.4 Sustainability
Improvements must survive staff changes: playbooks documented, owners named, metrics automated and reviews scheduled. For the contractor project, this means the directory has an owner in procurement, the confirmation step is documented in the runbook, time to contain is reported automatically each month, and the suspension rule is reviewed yearly. If Daniel left Meridian, the improvement would continue without him. The same test is applied to the triage playbook and the service catalogue. Daniel lists each improvement with its owner, its documentation and its review date in a register that his successor would inherit.
12.5 Final review
The programme's final review is a viva with Prof. Achebe and an external SOC leader. Questions probe judgement: "When would you not use expected cost?" "How would you know insider monitoring had become unfair?" Both questions test whether Daniel understands the limits of his methods rather than only how to use them. An external SOC leader brings practical scepticism that a tutor alone might not, which is why the viva includes one. Daniel prepares by rereading his own decision records and the case reviews, since the examiners draw their questions from his submitted work.
12.6 Answers
On fairness, Daniel cites indicators: rising flags concentrated in one team or role without business explanation, or complaints through staff representatives. Such signs trigger a policy review. On expected cost, he answers that he would not rely on it when a legal duty settles the question, as when the business asked to delay notifying policyholders; there the duty decides, and costs only inform how to carry it out. Both answers name a concrete signal or limit rather than a general principle, which is what the examiners were looking for.
12.7 Development
Daniel plans to mentor a senior analyst into team leadership and to present the contractor project at the sector forum. Mentoring a senior analyst addresses the risk shown in March, when the SOC's performance depended on a few people. Presenting the contractor project at the forum returns something to the peers whose comparisons helped him start. Both plans have dates and are recorded with his own development plan, which Prof. Achebe reviews at the end of the programme. He also plans to repeat the analyst survey a year later to see whether metrics changes helped.
Feedback from the team
Daniel asks his analysts what changed for them during the programme. They name fewer night calls, clearer playbooks and the new closure codes; they also say the pace of change was tiring. He plans a quieter quarter focused on consolidation before the next initiative, and records this in his development plan.
Worked example
The external examiner asks what Daniel would do differently. He answers: "Measure baselines before the first incident forces it; I had to reconstruct the contractor baseline from tickets, which was slow and imprecise."
Synthetic case. The review is invented.
Errors and limits
Reflection is partial; colleagues' feedback adds views one cannot see alone.
Exercises
- EX056 — Transferable methods. List four transferable methods from the programme. Rubric: 3 = expected cost, peer baselines, controlled evaluation, critique, assurance (four); 2 = three; 1 = one; 0 = none.
- EX057 — Transfer example. Where did Daniel transfer controlled evaluation? Rubric: 3 = provider escalation quality before/after template change; 2 = partial; 1 = vague; 0 = none.
- EX058 — Sustainability. What makes improvements survive staff changes? Rubric: 3 = documented playbooks, owners, automated metrics, scheduled reviews; 2 = three; 1 = one; 0 = none.
- EX059 — Fairness signals. How would Daniel know insider monitoring had become unfair? Rubric: 3 = flags concentrated without business reason; complaints via representatives; 2 = partial; 1 = vague; 0 = none.
- EX060 — Differently. What would Daniel do differently? Rubric: 3 = measure baselines before incidents force it; 2 = partial; 1 = vague; 0 = none.
Synthesis
Postgraduate practice ends by transferring methods, sustaining improvements and continuing to learn.
Continue studying — chapter 12 of 12
← Chapter 11 (draft) · Course chapter index · Worked results ↓ · Next course via chapter index →