What to change
Map the failing action to its immediate dependencies and collect evidence before assigning cause. Ask the supplier to compare the public symptom with the provider's actual response and any relevant official status information. A status notice is context, not proof that every observed fault has the same cause. Preserve a working control where possible, then decide whether the next action is a local fix, an agreed fallback or coordinated supplier escalation.
A worked example
Illustrative example
Illustrative test: A fictional dependency failure is traced without modifying unrelated page code.
How to check the result
The incident has an evidence-based next action and an accountable coordinator.
A mistake to avoid
Blaming a provider too quickly can conceal a simultaneous local defect.
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.