Prevent, don't
treat

Prevent, don't treat

Early diagnostics method development system

Early diagnostics method development system

Confidential

Outcome

The early diagnostics method development system is the pioneering solution providing automated access to life-saving molecular diagnostic data, enhancing medical practitioners' ability to protect and improve their patients' quality of life.

With 100K diagnostics platforms installed, the largest worldwide, 86% fewer manual touch points reduce the potential for human error and protect against cross-contamination, reliably delivering up to 1,600 samples on a single system per 8-hour shift. 



Role

Leadership

Product Strategy

User Research

Prototyping & Testing

Visual design

Challenge

Time consuming  method development process.

Each research step is done manually with a very low degree of automatisation and standardisation.

The absence of a simplified collaboration model, a digital framework to enable guided, step-wise, streamlined analysis method development on the medical instruments. 
Each step had to be standardised and allow, where possible, for automatised experimental planning, execution, and analysis were needed for flexibility of individual results.


Data is stored in folder/file based manner. Method development depends on knowledge of an individual user. Gained knowledge had to be saved in a single source database for the individual analyte and for subsequent analytes, to ensure continuous learning.

Approach

Identified the stakeholders and responsibilities. Requested and studied the documentation. Developed glossary and clarified terminologies. Aligned communication and tailored the UX process to the project needs. Settled expectations on timeline and deliverables. 


Conducted UX workshops with the stakeholders and the project core team. 
Identified features, functionalities, and requirements during UX Discovery Workshops with the stakeholders.
Aligned internally with the Solution Architect.

Created existing processes mapping to align with real-life scenarios and better understand the process and workflow in order to translate this into features. user flows and journey maps.
Put together a high-level navigation concept and afterwards the information architecture blueprint to display a clear overview of the product components and to better identify how the features are connected and how they relate to each other. Created high-fidelity wireframes.


Assessed proposed changes to understand the technical implications, if there is any impact on the delivery timeline, having in mind at all times the business and user goals. Aligned with the technical team regarding requirements and constraints. 

Held internal meetings for review with the project team to ensure that the proposed UX and UI solutions can be implemented in the agreed timeline. Documentation is added in a dedicated Confluence space.

The UX representatives provided support to the project team (development, QA, PM) in order to understand the design solution and deliverables and use them accordingly. 


Validated the implementation so it meets the design requirements and constraints.

Identified the stakeholders and responsibilities. Requested and studied the documentation. Developed glossary and clarified terminologies. Aligned communication and tailored the UX process to the project needs. Settled expectations on timeline and deliverables. 


Conducted UX workshops with the stakeholders and the project core team. 
Identified features, functionalities, and requirements during UX Discovery Workshops with the stakeholders.
Aligned internally with the Solution Architect.

Created existing processes mapping to align with real-life scenarios and better understand the process and workflow in order to translate this into features. user flows and journey maps.
Put together a high-level navigation concept and afterwards the information architecture blueprint to display a clear overview of the product components and to better identify how the features are connected and how they relate to each other. Created high-fidelity wireframes.


Assessed proposed changes to understand the technical implications, if there is any impact on the delivery timeline, having in mind at all times the business and user goals. Aligned with the technical team regarding requirements and constraints. 

Held internal meetings for review with the project team to ensure that the proposed UX and UI solutions can be implemented in the agreed timeline. Documentation is added in a dedicated Confluence space.

The UX representatives provided support to the project team (development, QA, PM) in order to understand the design solution and deliverables and use them accordingly. 


Validated the implementation so it meets the design requirements and constraints.

Identified the stakeholders and responsibilities. Requested and studied the documentation. Developed glossary and clarified terminologies. Aligned communication and tailored the UX process to the project needs. Settled expectations on timeline and deliverables. 


Conducted UX workshops with the stakeholders and the project core team. 
Identified features, functionalities, and requirements during UX Discovery Workshops with the stakeholders.
Aligned internally with the Solution Architect.

Created existing processes mapping to align with real-life scenarios and better understand the process and workflow in order to translate this into features. user flows and journey maps.
Put together a high-level navigation concept and afterwards the information architecture blueprint to display a clear overview of the product components and to better identify how the features are connected and how they relate to each other. Created high-fidelity wireframes.


Assessed proposed changes to understand the technical implications, if there is any impact on the delivery timeline, having in mind at all times the business and user goals. Aligned with the technical team regarding requirements and constraints. 

Held internal meetings for review with the project team to ensure that the proposed UX and UI solutions can be implemented in the agreed timeline. Documentation is added in a dedicated Confluence space.

The UX representatives provided support to the project team (development, QA, PM) in order to understand the design solution and deliverables and use them accordingly. 


Validated the implementation so it meets the design requirements and constraints.

Solution

Reliable model delivering highly accurate results.

Moved from a manual, not standardized individual workflow to a guided, automated workflow and where the method development steps are stored in a digital landscape and can be reviewed in an easy way. Faster development, random access, and tailored to an existing portfolio.

Definition of the whole development workflow as a frame is ready. Implementation of the auto-tuning step is completed. Applied auto-tuning to the prototype instruments. Increased velocity for the entire method development process.

Did you know that a single website visit takes up an average of 1.67 grams of CO²?


Design for Energy Efficiency.

Use simple colour palette and avoiding excessive use of animations or other visual elements that require high levels of processing power.


This web page is cleaner than 79% of web pages tested.

Only 0.20g of CO2 is produced every time someone visits my web page.






 © 2023 by Alexandru Botezatu

Did you know that a single website visit takes up an average of 1.67 grams of CO²?


Design for Energy Efficiency.

Use simple colour palette and avoiding excessive use of animations or other visual elements that require high levels of processing power.


This web page is cleaner than 79% of web pages tested.

Only 0.20g of CO2 is produced every time someone visits my web page.






 © 2023 by Alexandru Botezatu