The available rollback target contains an old defect

What to change

Select a known acceptable target based on evidence, not proximity in deployment history. Ask the release owner which version passed the required public checks and whether later operational dependencies remain compatible with it. Rehearse against that version before an emergency where possible. Record any trade-offs, such as losing a recent benign change, so the organisation can make an informed restoration decision rather than assuming every earlier version is safe to restore.

A worked example

Illustrative example

Illustrative test: A candidate version that predates a confirmed defect is compared with the immediate predecessor.

How to check the result

The chosen target has a justified health and compatibility record.

A mistake to avoid

Older does not automatically mean more reliable.

Your action checklist

Use these checks to prepare a discussion with your team or supplier. Tick a check when you have recorded the decision or evidence, rather than when a feature has simply been promised.

Decisions to recordIdentify the last release with recorded acceptance evidence.Review compatibility with current external settings and services.Test the proposed target using the critical public sample.

Evidence, open questions and decisionsNext action and responsible role

Entries stay in this page and are not submitted to Kay & Co. Download your notes before leaving; the page does not save them.