User Research
Our User Research (UR) focuses on understanding user behaviors, needs, and motivations through observation techniques, task analysis, and other feedback methodologies among several clinical setups. We follow the process of understanding the impact of design on a clinician's audience. The types of user research that we are performing will depend on the type of prototype, timeline, and environment.
Tracking Users ↑
The focus on the UX goals, to drive analytics measurement plans, rather than tracking superficial metrics, provide us core goal identification, of a design, to meaningfully measure it. These UX goals should remain at the forefront when choosing how to measure the success of a design. Rather than jumping directly to what may be simple to track, these UX goals are critical to meaningful measurement. Therefore, we use several trackers in our solution and listed below.
List of used trackers:
The Matomo (Piwik) tracker has a full range of features that allow us to evaluate the entire clinician-journey of everyone who visits our platform. There is no other tool that offers such a complete range of features like this. We can connect to our Matomo Analytics account to access the project dashboard.
Username: mimbcd.ui
All we need to do is to feed it with some data by embedding the following tracking code into our platform, right before the </head> tag or in a .js file:
<!-- Matomo -->
var _paq = window._paq || [];
/* tracker methods like "setCustomDimension" should be called before "trackPageView" */
_paq.push(['trackPageView']);
_paq.push(['enableLinkTracking']);
(function() {
var u="https://breastscreening.matomo.cloud/";
_paq.push(['setTrackerUrl', u+'matomo.php']);
_paq.push(['setSiteId', '1']);
var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0];
g.type='text/javascript'; g.async=true; g.defer=true; g.src=u+'matomo.js'; s.parentNode.insertBefore(g,s);
})();
<!-- End Matomo Code -->
For some further customization of our tracking code, the JavaScript Tracking Client guide might be helpful. Nevertheless, it is recommended for having a look at the User Guides and FAQs to learn more about all the many features.
Related Issues ↑
User Test Evaluations ↑
When reporting results from a user test, we should focus primarily on our findings and recommendations that are differentiated by levels of severity. Including the pertinent information from the test plan and presenting just enough details so that the method is identifiable. By keeping the sections short, we shell use tables to display the metrics and use visual examples to demonstrate problem areas, when possible. The following list is presenting the resources of our User Test Evaluations for the current repository.
List of User Test Evaluations resources: