What to change
Evaluate the dependency and its purpose together. Ask for a controlled comparison with the script enabled and disabled, using an authorised test environment where necessary. Have the business owner explain what the widget contributes and whether a simpler alternative exists. The decision should consider the observed cost, required function and operational consequences, rather than treating every external script as either indispensable or automatically unacceptable.
A worked example
Illustrative example
Illustrative test: A preview comparison shows the performance difference without changing the live visitor experience. Record the exact preview configuration so the performance difference can be reproduced without disabling the live function. A help widget may account for a noticeable part of a page's delay. The supplier isolates it in preview and repeats the same task with the dependency enabled and disabled. The practice lead explains what assistance the widget provides and reviews a simpler alternative. The decision records the measured difference and accepted function, avoiding both an unexplained removal and an assumption that every existing external tool must remain indefinitely.
What this means for your practice
A booking, chat or other external tool may contribute to page delay while also serving a useful purpose. Ask your supplier to isolate its impact in an authorised test environment and compare like-for-like results with and without it. The business owner should explain what function would be lost and whether a simpler alternative is available. Do not remove a dependency just because it is external, or keep it unquestioned because someone once requested it. The decision should record the demonstrated cost and the accepted functional trade-off. Preserve the test setup so the result can be reproduced without repeatedly disabling a live service used by visitors.
How to check the result
The decision records measured impact and the accepted functional trade-off.
A mistake to avoid
Removing a script without checking dependencies can break an important service.
Turn reading into a next step
Your action checklist
Work through these checks with your team or supplier. Tick the ones you have resolved and leave unknowns open.
Record what you know, what is still missing and the answer you need from your team or supplier.
Use project decisions only, without personal, patient or confidential details. Entries stay in this page and are not submitted to Kay & Co. Copy or download before leaving; this page does not save your notes.
Further reading
These sources provide background for the topic. The practice examples and checklist are illustrative planning suggestions from Kay & Co.
Related guides
Need help with this?
Tell us what is getting in the way. Kay & Co. can help you understand the options and turn the next step into something that works for your practice.
Explore support & operations services or discuss your project.
Try the free Healthcare Digital Planner to find your starting priority.