Novartis

data42 is a strategic Novartis initiative to build a next-generation platform for data analytics.

On data42, I designed tools that Novartis scientists use to find and request Real World Data, including the Investigations App and the Medical Code List Builder (MCLB).

What I did

• Planned and ran interviews with scientists who work with Real World Data
• Documented the findings on Confluence and prioritized pain points with the team
• Mapped the user journey with stakeholders and developers to close knowledge gaps about the system
• Designed request and tracking flows, such as the four-step New Investigation Request (select data, provide details, select audience, submit) and tracking each request through approval
• Created new layouts and kept the Blueprint-based design system up to date

This work helped Novartis scientists reduce their research time by 44% through better usability and a more efficient workflow.

In user interviews, I set out to understand the typical tasks people perform with Real World Data and the specific challenges they face using the Medical Code List Builder (MCLB). I asked about their workflow, the tools they use and their pain points.

The interviews revealed common themes and patterns in users' experiences. I used these insights to improve the design and functionality of MCLB and make it more intuitive for people who work with Real World Data.

I documented observations and soundbites on a Confluence page to share the interview findings with my team. Prioritizing users' pain points let us focus on the parts of the tool that would have the biggest impact on the experience.

I also noted where users were satisfied and gave positive feedback. That matters just as much: it shows what's working, so we can build on those strengths. With a clear picture of users' needs and pain points, we could make informed decisions and create a more effective, user-friendly Medical Code List Builder.

A user journey map was a crucial step in closing knowledge gaps about the system, from both the stakeholders' and the developers' perspectives. Visualizing the main flows and users' pain points gave us a deeper understanding of the experience and showed where it could improve.

Presenting the map to stakeholders and developers aligned everyone's understanding of the system and its shortcomings, and opened a discussion about possible solutions and priorities. It became a useful tool for communication between teams, leading to a more effective and user-friendly Medical Code List Builder.

Working with a design system based on the Blueprint framework kept design and development consistent and efficient. I kept the design system up to date as new features were implemented, so every component stayed in sync with the latest standards and guidelines.

Beyond the existing components, I created new layouts to make the system more flexible, designed to be intuitive and easy to use. Building on the design system and adding layouts where needed streamlined design and development, and made the Medical Code List Builder more cohesive and user-friendly.