What to change
Ask for a bounded comparison that includes the reported failing conditions and a working control. Record frequency cautiously and preserve request identifiers or safe diagnostic evidence when available. The next step may be improved observation rather than immediate code changes. Agree what evidence would justify closure, including a representative period or number of controlled attempts appropriate to the issue. A single success proves only that one attempt worked.
A worked example
Illustrative example
Illustrative test: The same harmless route is checked under the reported condition and an unaffected control.
How to check the result
The conclusion reflects observed reproducibility and clearly states remaining uncertainty.
A mistake to avoid
Repeatedly retrying until success can hide a reliability problem.
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.