What to change
Prioritise with the affected task, audience and available evidence in view. Ask the supplier to describe what users wait for and how many important routes share the problem. A severe defect on a key entry path may deserve attention before an isolated low score elsewhere. Keep low-volume findings in the backlog with their rationale rather than hiding them, and confirm any broad fix against representative pages it could affect.
A worked example
Illustrative example
Illustrative test: Two findings are compared using task impact as well as measured severity.
How to check the result
The repair order has a documented practical reason.
A mistake to avoid
Traffic volume alone should not dismiss a serious issue affecting a smaller audience.
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.