Rollbacks and Failed Deployments
Can the team operate this service after launch with the people, access, budget, and recovery time it actually has? Define and rehearse rollback for code, configuration, and schema changes before a high-consequence release.
What You Will Be Able to Decide
- Explain rollbacks and failed deployments in product and business terms.
- Apply this decision: Define and rehearse rollback for code, configuration, and schema changes before a high-consequence release.
- Recognise this material risk: the team can redeploy old code but cannot reverse incompatible data or configuration changes.
- Use this review: Ask a second operator to deploy the dashboard, find a failed request in logs, and roll back a deliberately broken release.
A founder has a working application and needs a proportionate way to run, monitor, and recover it. This lesson gives you a concrete question to take into a build brief, proposal review, or product decision.
Can the team operate this service after launch with the people, access, budget, and recovery time it actually has? The course example is A small SaaS dashboard with a public marketing site; use it to decide what evidence would justify the choice before a builder implements it.
What Does Rollbacks and Failed Deployments Mean for Your Product?
A founder has a working application and needs a proportionate way to run, monitor, and recover it.
Use the illustrative service for this course (A small SaaS dashboard with a public marketing site) to make the choice concrete. Can the team operate this service after launch with the people, access, budget, and recovery time it actually has?
Technical term
Rollbacks and Failed Deployments
A rollback restores a previously working application state after a release fails, while data changes may require separate recovery planning.
How Should a Founder Use Rollbacks and Failed Deployments?
For a small saas dashboard with a public marketing site, ask what would happen if the team can redeploy old code but cannot reverse incompatible data or configuration changes.
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.
- Decision: Define and rehearse rollback for code, configuration, and schema changes before a high-consequence release.
- Evidence to request: show that the team knows where the product runs, who operates it, and how service is restored after failure.
- Owner: name who will respond if the team can redeploy old code but cannot reverse incompatible data or configuration changes.
- Record the result in the deployment and operations plan.
- Practical review: Ask a second operator to deploy the dashboard, find a failed request in logs, and roll back a deliberately broken release.
How Do You Choose an Approach to Rollbacks and Failed Deployments?
Can the team operate this service after launch with the people, access, budget, and recovery time it actually has? Define and rehearse rollback for code, configuration, and schema changes before a high-consequence release.
The risk is that the team can redeploy old code but cannot reverse incompatible data or configuration changes. Compare a simpler option with the proposed one, including who will operate either choice.
- Describe the user or business outcome that must be protected.
- Identify the most credible failure and its consequence.
- Compare the simplest adequate approach with one realistic alternative.
- Set a review point for when the decision may need to change.
What Evidence Should You Accept for Rollbacks and Failed Deployments?
What Warning Signs Should You Look For?
- The proposal does not address this risk: the team can redeploy old code but cannot reverse incompatible data or configuration changes.
- Nobody can show whether the team knows where the product runs, who operates it, and how service is restored after failure.
- The decision has no named owner or review point.
What Should You Ask a Consultant?
- What changes for the user if we choose this approach to rollbacks and failed deployments?
- How have we reduced or accepted this risk: the team can redeploy old code but cannot reverse incompatible data or configuration changes.
- Can you demonstrate that the team knows where the product runs, who operates it, and how service is restored after failure?
- Who owns the result, and when will we reconsider it?
Key takeaway
Key Takeaway
Define and rehearse rollback for code, configuration, and schema changes before a high-consequence release. Ask for evidence against the specific risk: the team can redeploy old code but cannot reverse incompatible data or configuration changes.