Why we teach rollback before rollout

When teams rehearse rollback paths first, they surface brittle assumptions about database migrations, feature flags, and traffic shifting. That sequencing does not slow delivery; it shortens the time spent guessing during incidents.

In our CI/CD Foundations Lab Sprint, participants capture rollback notes alongside promotion steps so reviewers see both sides of the change. The habit also makes audits less theatrical because evidence already exists in the merge request.

We still teach progressive patterns, but only after rollback drills feel boring. Boredom here is a feature: it means defaults exist when pager alerts arrive at inconvenient hours.

If your organization cannot rehearse rollback because environments diverge, that gap becomes the first backlog item—not an afterthought buried in a postmortem template.