A hospital's technology dashboard may show that a system is available while staff repeatedly call the support desk about the same difficult task. Availability and usability are different questions. The support record can reveal friction that never appears in a simple uptime measure, offering useful evidence about how the digital service behaves within ordinary work rather than a controlled demonstration.

The pattern behind individual tickets

Requests should be classified in a way that preserves their practical meaning. Several apparently different complaints may stem from one confusing step or missing permission. Reviewing them with relevant users can help identify the mechanism, avoiding a response that repeatedly explains the workaround without considering whether the underlying design should be improved through an appropriate change process.

A route to product ownership

Support staff need a way to pass recurring issues to the people responsible for the system and workflow. Closing each ticket successfully does not guarantee that anyone considers the aggregate burden. A named owner can assess whether the issue requires training, configuration or supplier discussion, with the relevant professional and security controls maintained throughout the decision.

The cost of tolerated friction

Small difficulties can consume significant time when repeated across many users. Measuring that burden helps prioritise improvements alongside larger projects. The analysis should remain grounded in observed work, rather than assume every request represents a software defect or that automation is automatically preferable to a clearer process and better information for the person completing the task.

Learning from ordinary use

A useful digital service evolves through evidence from the people using it. The support desk is one source of that evidence, not merely a place to absorb frustration. Institutions that connect support patterns to decisions can improve usability without launching a new platform, extracting more value from systems they already own and depend on every day.

References
  1. WHO — digital interventions for health systems ↗
  2. ALFA — ecosystem whitepaper ↗