Every one of them names the rollback before it names the change.
A feature broken into steps a developer can execute and you can check off, with the decisions surfaced instead of buried.
Schema or data migration with the order, the reversibility of each step, and what to do when it stops halfway.
What to provision, in what order, and which parts you must be able to rebuild from scratch.
A pipeline that can refuse a bad release, and a rollback procedure someone can actually follow at 2am.
Which part to change first, how to keep the system working throughout, and where to stop.
Payments, KYC, or any external service: the failure modes, the retry rules and what happens when the other side is down.
Describe the situation in your own words and see the procedure — and its cost — before you spend anything.