What to change
Agree a concrete stop condition and an authorised decision-maker before the next deployment. The team should know which failures prevent release, which can be accepted with an explicit reason and how to pause further changes. Use a harmless rehearsal failure to test that authority in practice. The purpose is to make a real decision possible when evidence changes, not to create a checklist whose failures everyone assumes someone else will handle.
A worked example
Illustrative example
Illustrative test: A fictional missing core route causes the release to pause pending an explicit decision.
How to check the result
The stop action, decision owner and resumption evidence are demonstrable.
A mistake to avoid
An alert without authority to act may not prevent a faulty release.
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.
Entries stay in this page and are not submitted to Kay & Co. Download your notes before leaving; the page does not save them.
Further reading
These primary sources provide additional context for the project decisions above.
Related decisions
Turn the brief into a working service
Kay & Co. can help you scope the work, design the experience and deliver the right solution for your organisation.
Explore support & operations services or discuss your project.
Try the free Healthcare Digital Planner to find your starting priority.