Backward-compatible changes rarely arrive fully formed. We teach participants to title migrations with the user impact, not the column name.
Reviewers ask three questions: who is blocked if this deploy fails, what is the rollback story, and how will we know it worked in production besides “no alerts”.
We simulate a retention policy change for a fictional AU-facing app, which surfaces uncomfortable trade-offs quickly. Legal precision is overview-level; we point to professional advice when needed.
If you already have strong DBA habits, bring them — the rubric is a floor, not a ceiling.