Nemedio is a startup that helps medical device engineering teams to compliantly manage their documentation process. I joined in November of 2018 to design and ship the MVP of the product. Over my two years, I also established and maintained Nemedio's design system, shipped additional features and organized the design workflow for easier onboarding for new designers.

In efforts to comply with my non-disclosure agreement, I omitted confidential information in this study. All information and designs are for the sole purpose of the study and does not necessarily reflect the views of Nemedio.


Medical device documentation is extensive paperwork that is hard to track and maintain.

All devices require FDA clearance to register as a medical device. However, the documentation that are required in the FDA rules and regulations are hard to comply with because of extensive paperwork.

I was presented with collection of user pain points with the current paper process that needed to be solved in our software. Outside of addressing users’ needs, I also worked with our quality engineer, who guided me through the requirements for FDA compliance. Because there was a disparity between how the information FDA wants to see documented versus how device engineering teams organized information, there was a lot of back and forth.

My designs principles were to make the documentation user friendly, while still remaining compliant with FDA guidelines.

The goals laid out for the MVP was for the product to be:

  1. Intuitive and easy for users to input and organize data.
  2. View each task laid out in a way that is FDA-compliant while being easy to manage amongst various stakeholders in the engineering process.
  3. Flexible to accommodate for new features down the road.
nemedio quality management system

Key Features

Flexible Viewing 

First we wanted to create a design philosophy that centered around flexibility. The users should be able to view things in a way that makes sense to them, while still keeping compliance in check. 

Item Page with Modular, Re-usable Components

While deciding on if the items will be a modal or a separate page, we decided to create a separate page for each item. While modals would be convenient for quick-viewing for stakeholders to look at all items at once, this item page allowed for more flexibility and functionality when adding various components such as dropdowns, WYSIWYG textboxes.

Tracking Items Efficiently

Each compilation of data was considered its own entity. This part is what would be looked at by the FDA to make sure it is consistent with existing guidelines. The FDA requires a quality officer’s signature on each part. We incorporated a multi step approval workflow for each item type so that it is compliant with the FDA’s requirement of a signature, while also being able to track the status of each part for the users. 

Once a part is released and signed, the system would allow creating multiple versions of the same item to account for revisions. Each item is versionable,  keeping the same title and references to another item. 

Modular Design

Each class of a part has different requirements, which meant I needed to anticipate different types of data incorporated in each part. A modular design allowed the flexibility of adding or subtracting certain information for different parts. 

visual design

Establishing, Maintaining and Expanding a Consistent Design System

As a team we decided to design our platform using Google Material for consistency, and efficiency to build on a tight timeline. Over time, we expanded our design system which became more complex over time. Throughout my time at Nemedio I did my best to maintain a consistent design system while expanding for more complex designs.

Design Documentation

  1. Airtable - we used Airtable to define screen names and associated tasks and overall project management. The names would also be the names of the screens on Sketch for easy back tracking. On Airtable, each ID, (such as SCR-100) would have payload data such as description, associated screens, associated user story, overview of user flow, and links to Zeplin.
  2. Google Doc - I worked on a google doc with our PM and CEO to define the high level requirements, associate user stories and requirements. This also provided links to screens on Zeplin, InVision, Principle, as needed.
  3. Zeplin - I used Zeplin to upload all designs and style guide updates which were also documented on our Google Doc.
Example of flow for our timeline feature and associated dialogs
final thoughts

Learning Points

Design System is ongoing

One of my biggest challenges was keeping up with the constantly expanding design system. Initially, we had only a few components, which made it challenging to stick within those boundaries. I realized that a design system is something that requires ongoing maintenance and expansion. Therefore, I continuously expanded the design system as necessary to keep up with our evolving needs.

Creating a system when choosing which fidelity to present

I initially struggled to choose the appropriate fidelity and presentation style to present our designs. While I wanted to create an all-in-one place where interactions, specs, and designs could be easily accessed, I found it challenging to find an ideal platform. Ultimately, we settled on a Google doc that hyperlinks to all screens, gifs, requirements, and tasks, which were also linked in our Jira/Trello.

Designing for a lot of data

Since database designs require scaling, I had to consider use cases where there is a ton of data. I had to decide when to use modals, when to use drawers, and where information should hide/show.

Balancing Feasibility, Build Time and Design

Working at a startup meant balancing feasibility, build time and design. Acknowledging that pivots will occur, I had to find ways to move quickly without compromising on design. I used Material libraries to identify what was feasible and quick to build and designed around these constraints.

Next Steps

After shipping the MVP, we continued to build out features that were necessary for team management. My next large project was to design the overall employee training module experience.

Special thanks to Nemedio team, Kat, Sabrina and Ayesha.

Next Case Study →