Rollbacks and Failed Deployments

The Founder Situation

A founder has a working application and needs a proportionate way to run, monitor, and recover it.

The immediate question is rollbacks and failed deployments. The technical label matters only because it changes a product decision, a responsibility, or the evidence required before launch.

What Matters in Practice

Start with the product consequence, then choose the simplest technical treatment that protects it. A longer tool list is not a stronger plan.

For this decision, the useful standard is that the team knows where the product runs, who operates it, and how service is restored after failure.

• Make the decision explicit: Define and rehearse rollback for code, configuration, and schema changes before a high-consequence release.
• Ask what evidence would show that the chosen approach works.
• Name the person or provider responsible when the approach fails.
• Record the result in the deployment and operations plan.

A Proportionate Decision

Define and rehearse rollback for code, configuration, and schema changes before a high-consequence release.

The principal risk is that the team can redeploy old code but cannot reverse incompatible data or configuration changes. This does not require the most expensive possible solution. It requires the consequence to be understood and the control to match it.

1. Describe the user or business outcome that must be protected.
2. Identify the most credible failure and its consequence.
3. Compare the simplest adequate approach with one realistic alternative.
4. Set a review point for when the decision may need to change.

Strong Evidence and Weak Reassurance

Warning Signs

• Nobody can explain how rollbacks and failed deployments changes a user or business outcome.
• The proposal does not address this risk: the team can redeploy old code but cannot reverse incompatible data or configuration changes.
• The only evidence is a successful demonstration of the easiest path.
• The decision has no named owner, boundary, or review point.
• A provider-specific feature is being mistaken for a permanent product requirement.

Questions to Ask a Consultant

• What decision are we making about rollbacks and failed deployments?
• Which user or business outcome does the recommendation protect?
• How have we reduced or accepted this risk: the team can redeploy old code but cannot reverse incompatible data or configuration changes.
• What evidence can I review without relying on the original implementer?
• What is deliberately deferred, and when will it be reconsidered?
• Who owns the accounts, data, documentation, and recovery process?