Week 2 Audit: Auditing a live migration
The second audit --- the same close-reading habit from week 1, applied to an industry whose ending we don't already know
1 March 2027
Week 1 practised the audit skill on a case with a known outcome. This week’s notice — call-centre automation — is still in progress, so there’s no answer key. The habit is the same: read for the seam, check whether the parts agree with each other, and don’t let confident prose stand in for evidence either way.
Before the session#
Read this week’s notice once for the pitch, once for the audit, and bring one sentence from each you’re not sure you’d trust without more evidence.
In the session#
Short demos of what each pair found, then group discussion on where “we don’t know yet” is the honest answer versus where the notice already gives you enough to judge.
Afterwards#
Your Weekly Audit Log entry for this week is the first one that isn’t practising on a resolved case. Say what you’d still need to know to be confident either way, not just what you concluded.
The spec
What you bring to the session. Written so a reader can tell whether it has been met without asking you.
- you can point to a sentence in this week's pitch that would need the breaking-changes section to be false for the pitch to hold
- you can distinguish "the rollback plan is inconvenient" from "the rollback plan is impossible," and say which this week's is
- your weekly audit-log entry for this week names one claim you'd want more evidence for before believing it either way
Teaching team
- Idris Fenn — tutor