DQA Redesign
Planting seeds for better patient care
Overview
Osprey Software requested a redesign for key DQA workflows, to improve efficiency, clarity, and usability across both customer-facing and employee-facing ends of interfaces.
The Challenge
Data Quality Analyst (DQA) is an AI-powered SaaS platform that automates document review for the life science industry, assisting teams in managing and validating large volumes of regulatory documentation.
This project gave me hands-on experience with working directly with developers in a real product environment. I learned a significant amount about preparing clean design documentation for developer handoff and designer developer collaboration.
Project Goals
- Improve information hierarchy and reduce cognitive load
- Increase workflow efficiency and clarity
- - Maintain consistency with DQA’s existing design system.
Design Process
For this project I was expected to work on designs for 2 main sections
- Rule Creation Page
- Dashboard Restructure
Rule Creation Page
The Rule Creation page is an internal DQA tool used by Osprey employees to create AI rules and bundle them into rulesets for customer projects. The original layout lacked structure and scalability, making rule creation and expansion inefficient.
Original Page
Redesign
The redesign of the rules page prioritized intentional spacing and proportional field sizing to assist in minimizing clutter and improve hierarchy. Additionally the rule properties were grouped into defined sections and refined the styling for selection to allow for a clearer and more organized workflow.
Dashboard Restructure
The Dashboard is a customer-facing DQA tool where Osprey customers can review and manage all analyzed documents. I was tasked with creating concepts for restructured versions with analytics cards at the top for quick insights and rethinking how documents are displayed to improve scanability and usability.
Original layout recreated for comparison purposes
Dashboard Concepts
I created two versions of the dashboard concepts.
One version retained the traditional list layout for documents but reorganized spacing and hierarchy to make information easier to scan and interact with.
The second version presented documents as individual cards, providing a more visual, modular layout that emphasized key metadata and allowed for quicker recognition of document status.
Reflection
This project strengthened my ability to work in a cross-functional team of developers. It required clarity, consistency, and thoughtful documentation to ensure design decisions translated effectively into implementation. Designing for a data-heavy environment was particularly challenging, balancing the need to include extensive information while maintaining clarity and in consideration of cognitive load.It reinforced the importance of designing not for aesthetics but for efficiency, clarity and implementation