Chapter 12 — Final review and organizational transfer plan
Lesson map
Lesson 12 published. Map, example, EX056.
flowchart TD
N0["Learning outcomes and connection"]
N1["12.1 Why transfer fails"]
N2["12.2 The transfer package"]
N3["12.3 Training and acceptance"]
N4["12.4 Residual issues"]
N5["12.5 Defending trade-offs"]
N6["12.6 Reassessment"]
N7["Chapter synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> N7
N7 --> EX["Worked example"]
EX --> Q["Exercise EX056"]
Logical drawing
flowchart LR
N0["Learning outcomes and connection"]
N1["12.1 Why transfer fails"]
N2["12.2 The transfer package"]
N3["12.3 Training and acceptance"]
N4["12.4 Residual issues"]
N5["12.5 Defending trade-offs"]
N6["12.6 Reassessment"]
N7["Chapter synthesis"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> N7 --> Q["EX056"]
[Learning outcomes and connection]
|
v
[12.1 Why transfer fails]
|
v
[12.2 The transfer package]
|
v
[12.3 Training and acceptance]
|
v
[12.4 Residual issues]
|
v
[12.5 Defending trade-offs]
|
v
[12.6 Reassessment]
|
v
[Chapter synthesis]
|
v
[Worked example] --> [Exercise EX056]
Learning outcomes and connection
You will be able to (1) assemble a transfer package that lets the organization own and sustain the redesigned program; (2) plan training and acceptance; (3) record unresolved issues and residual risks honestly; (4) defend trade-offs before stakeholders; and (5) schedule an evidence-based reassessment. This final chapter completes the Chapter 11 project and the course: specialist work is only valuable if it survives the specialist's departure.
12.1 Why transfer fails
Programs designed by specialists often decay: templates stop being used, owners change jobs, metrics are no longer collected, exercises lapse. Transfer fails when ownership, resources and feedback are not built in. The aim is a program the organization runs without you, with signals that tell it when it is drifting.
Calder's transfer package is designed against each of these causes: owners named in the receiving organization, a monthly report to the CISO, and a 90-day review that would show the handoff template falling out of use.
12.2 The transfer package
Contents: (1) design rationale — the problem, evidence, options considered and why the chosen design; (2) operating documents — procedures, templates, RACI, thresholds; (3) measurement plan — definitions, data sources, owners, reporting cadence; (4) training materials and records; (5) pilot evaluation report with limitations; (6) open issues and residual risks register; (7) reassessment schedule; (8) contacts and decision rights for future changes. Each item has a named owner in the receiving organization.
Calder's package for the handoff template has all eight: rationale with the 9-of-14 finding and pilot results; template v1.2, read-back guidance and RACI; measures with sources and owners; training records; the pilot report; open issues with owners; reassessment dates; and decision rights for future changes.
12.3 Training and acceptance
Train by role, with exercises not just slides; measure acceptance by observed use (for example, percentage of handoffs using the template) rather than attendance. Acceptance by the receiving owner should be explicit and recorded, like service acceptance after recovery.
Calder trained by shift team: a 45-minute role-based session plus a 20-minute handoff drill, with completion and drill observations recorded. Acceptance is measured by the template use rate in the case system, reported monthly, and formally by the group SOC manager as the accountable owner.
12.4 Residual issues
List what the redesign did not solve and why: budget, dependencies on other programs, unresolved evidence questions. Assign each to an owner and a review date, or explicitly accept it at the right level (Chapter 9).
Calder's package lists two: Retail's ticketing system cannot enforce required fields until the tooling project, owned by the IT service management lead with a Q3 review; and night-shift staffing remains thin in one region, accepted by the CISO as residual risk until the budget review. Naming both prevents the rollout from being reported as a complete fix.
12.5 Defending trade-offs
Stakeholders will challenge choices: "why not the tool?", "why this metric?", "the template slows us down". Prepare a trade-off register: decision, alternatives, reasons, evidence, conditions under which you would decide differently. Concede where evidence is weak.
Calder's register answered the Retail CIO's objection that the template adds paperwork with data: about 4 minutes per handoff, against roughly 15 minutes saved before the incoming lead's first action. It also set a condition for changing course: if template time exceeds 10 minutes, the decision is revisited.
12.6 Reassessment
Schedule reassessment based on evidence: a 90-day review of adoption and outcome measures, a 6-month exercise testing the redesigned process, and an annual program review. Define triggers for earlier review: a major incident where the process failed, a significant drop in adoption, organizational change (merger, outsourcing).
Calder's schedule follows this pattern: a 90-day review of template adoption and time to first action, a handoff stress-test exercise at six months, and an annual program review. The earlier-review triggers matter most for Calder's structure: a merger or outsourcing of a division's IT would change who hands off to whom.
12.7 Worked example (synthetic): transferring the handoff redesign
Fictional. The Chapter 11 pilot succeeded in Logistics. The transfer package for group-wide adoption:
- Rationale: 9 of 14 after-action reports cite handoff delays; pilot reduced median time to first action by 36% versus 5% in comparison division; completeness 87%.
- Operating documents: handoff template v1.2; read-back guidance; RACI (SOC shift lead responsible; group SOC manager accountable).
- Measurement: time from shift change to first action (source: case-system events; owner: SOC analytics); template use rate; completeness at closure; time to containment as guardrail metric. Monthly report to the CISO.
- Training: 45-minute role-based session plus a 20-minute handoff drill per shift team; record of completion and drill observation.
- Open issues: Retail's ticketing system cannot enforce required fields until the tooling project (option B) — owner: IT service management lead, review in Q3; night-shift staffing remains thin in one region — accepted by CISO as residual risk until budget review.
- Reassessment: 90-day adoption and outcome review; handoff stress-test exercise at 6 months; triggers as above.
- Decision rights: changes to the template approved by group SOC manager; changes to thresholds by CISO.
Stakeholder defense (fictional): Retail CIO: "The template adds paperwork." Response: "The pilot measured about 4 minutes per handoff on average and reduced time to first action by about 15 minutes. We will track template time and revisit if it exceeds 10 minutes."
12.8 Common errors and limits
- Transfer packages that are document dumps without owners.
- Training measured by attendance.
- Hiding residual issues to declare success.
- No reassessment schedule; programs drift silently.
Calder's package was built to avoid each error: every item has a named owner in the receiving organization; training is measured by template use rate and observed drills, not attendance; the two open issues are listed with owners rather than hidden; and the reassessment dates are fixed. The monthly report to the CISO is the signal that will show drift first.
Exercises — chapter 12
Attempt each exercise before opening the worked results. Every case, organization, person, address and number in an exercise is synthetic unless a cited public source is named.
EX056 — Package checklist. Steps: turn this chapter's transfer package into a checklist with owner and acceptance evidence for each item. Rubric: 3 = eight items with owners and evidence; 2 = six; 1 = list without owners; 0 = none.
EX057 — Adoption metric. Steps: define the template-use rate precisely and its data source, and set a threshold that triggers review. Rubric: 3 = numerator/denominator, source, period, threshold with reason; 2 = vague denominator; 1 = no definition; 0 = none.
EX058 — Trade-off register. Steps: write three entries. Rubric: 3 = decision, alternatives, reasons, evidence strength, reversal conditions; 2 = missing reversal conditions; 1 = list; 0 = none.
EX059 — Reassessment plan. Steps: write the 90-day review agenda with inputs and decisions. Rubric: 3 = adoption, outcomes, guardrails, feedback, open issues; decisions (continue/adjust/stop, B funding); 2 = inputs only; 1 = date only; 0 = none.
EX060 — Final reflection. Steps: in 250 words, reflect on how your approach as a specialist differs from your earlier practitioner approach, using two chapters of this book. Rubric: 3 = specific shifts (framing, structure, evidence integration, ethics, leadership) with examples; honest about limits; 2 = generic; 1 = summary; 0 = none.
Chapter synthesis
Specialist work counts only when the organization can sustain it: transfer a package with owners, train by practice, measure adoption and outcomes, record residual issues honestly, defend trade-offs with evidence and schedule reassessment with triggers.
Continue studying — chapter 12 of 12
← Chapter 11 · Course chapter index · Next course via chapter index →
This is the final chapter of this course; the index links the next course in the full study path.