NMVS Core
NMVS Core
Smart Technology for Safer Medicines and Stronger Public Trust
Smart Technology for Safer Medicines
and Stronger Public Trust
Industry
Pharmaceutical
Role
Lead UI/UX Designer
Timeline
Oct 22 - Sept 25
Product type
B2B Saas
Industry
Pharmaceutical
Role
Lead UI/UX Designer
Timeline
Oct 22 - Sept 25
Product type
B2B Saas
THE CHALLENGE
THE CHALLENGE
Modernizing a Legacy System for Expert Users
Modernizing a Legacy System for Expert Users
NMVS Core is the interface pharmacies and healthcare professionals use to verify prescription medicines before they’re given to patients, as part of the European system that protects against falsified drugs. It’s a tool for expert, high-frequency users, and my brief was to redesign an old, table-heavy, desktop-first B2B product while keeping its core functionality intact. The main challenge was to turn a clunky, efficiency-killing experience into a modern, highly usable desktop app that fits today’s expectations, without breaking the workflows people rely on. As a UI/UX designer, this also meant mediating between product, engineering, and power users to align them around a shared vision for that modernization.
NMVS Core is the interface pharmacies and healthcare professionals use to verify prescription medicines before they’re given to patients, as part of the European system that protects against falsified drugs. It’s a tool for expert, high-frequency users, and my brief was to redesign an old, table-heavy, desktop-first B2B product while keeping its core functionality intact. The main challenge was to turn a clunky, efficiency-killing experience into a modern, highly usable desktop app that fits today’s expectations, without breaking the workflows people rely on. As a UI/UX designer, this also meant mediating between product, engineering, and power users to align them around a shared vision for that modernization.
APPROACH
APPROACH
Aligning Direction and Refining the Core Experience
Aligning Direction and Refining the Core Experience
My approach was to optimize the user experience first, mainly through information architecture and a stronger interface, while keeping the core functionality intact for expert users. In a product like this, UI is not just visual polish — it directly shapes usability by making dense workflows easier to read, faster to navigate, and less mentally demanding. At the same time, I focused on alignment: bringing stakeholders in early, making the process transparent in Figma, and creating a shared workflow where product, engineering, and users could react to the same direction as it evolved.
Because the product was complex and highly stakeholder-driven, it was important to work openly and keep feedback loops structured from the start. That helped establish a common understanding of what needed to change, where the biggest friction points were, and how far the visual language could be modernized without breaking the trust expert users already had in the system. So the work was as much about clarity and collaboration as it was about design itself — shaping a calmer, more consistent experience through structure, hierarchy, and interface quality.
My approach was to optimize the user experience first, mainly through information architecture and a stronger interface, while keeping the core functionality intact for expert users. In a product like this, UI is not just visual polish — it directly shapes usability by making dense workflows easier to read, faster to navigate, and less mentally demanding. At the same time, I focused on alignment: bringing stakeholders in early, making the process transparent in Figma, and creating a shared workflow where product, engineering, and users could react to the same direction as it evolved.
Because the product was complex and highly stakeholder-driven, it was important to work openly and keep feedback loops structured from the start. That helped establish a common understanding of what needed to change, where the biggest friction points were, and how far the visual language could be modernized without breaking the trust expert users already had in the system. So the work was as much about clarity and collaboration as it was about design itself — shaping a calmer, more consistent experience through structure, hierarchy, and interface quality.
EXPERIENCE DESIGN
EXPERIENCE DESIGN
Refining the Experience
Refining the Experience
This part of the solution focused on making the product easier to understand and faster to use in day-to-day work. I reworked the information architecture, strengthened hierarchy, and grouped content more intentionally so dense data became easier to scan and core tasks stayed visible. Repeated steps were reduced, priorities became clearer, and less frequent edge cases were moved further into the background. At the same time, the interface was pushed toward a more modern, responsive, and professional look and feel — while still keeping enough warmth and approachability to avoid the typical distance of many B2B tools
This part of the solution focused on making the product easier to understand and faster to use in day-to-day work. I reworked the information architecture, strengthened hierarchy, and grouped content more intentionally so dense data became easier to scan and core tasks stayed visible. Repeated steps were reduced, priorities became clearer, and less frequent edge cases were moved further into the background. At the same time, the interface was pushed toward a more modern, responsive, and professional look and feel — while still keeping enough warmth and approachability to avoid the typical distance of many B2B tools
SYSTEM DESIGN
SYSTEM DESIGN
Building a Scalable Foundation
Building a Scalable Foundation
Beyond the screens themselves, the work also needed to hold up as a system. I translated the design direction into a more centralized but flexible design foundation that could scale across features, customers, and future requirements without becoming rigid. That included clearer rules around spacing, structure, and component behavior, as well as a documentation standard that made the work easier to maintain beyond my direct involvement. The goal was a product that not only felt more polished in the present, but also gave product and engineering a stronger base to build on over time
Beyond the screens themselves, the work also needed to hold up as a system. I translated the design direction into a more centralized but flexible design foundation that could scale across features, customers, and future requirements without becoming rigid. That included clearer rules around spacing, structure, and component behavior, as well as a documentation standard that made the work easier to maintain beyond my direct involvement. The goal was a product that not only felt more polished in the present, but also gave product and engineering a stronger base to build on over time
REFLECTION
REFLECTION