This medical company adapted their laboratory for COVID-19 testing to help meet the huge demand for COVID-19 testing. Employers were interested in keeping their workforce safe by providing testing and directing COVID positive employees to self-quarantine and if necessary, seek medical help. To get-to-market ASAP, we leveraged existing products and features.
We were given the task of leveraging a recently built product to help expand the availability of COVID-19 testing and management of test results.
The platform has 4 user groups. Largest to smallest are:
Each user group has access to data and features specific to their needs. In the product section I dig deeper into each user group.
The non-internal users are generally not tech people. Their jobs are focused on human interaction and providing health care. Expected daily app usage is at most one hour.
User needs:
These are in the Product section.
B2B User Needs
Employee User Needs
We needed to create a flexible and scalable MVP with many unknowns such as virus symptoms, testing, employer needs and legal boundaries.
Goals included:
There are two parts of this platform:
I'll present this product in the chunks below.
Chunk | Notes |
---|---|
High level flows | These describe how the data, patient and specimens flow through various platforms and how all platforms are connected. |
Design system | This product was an extension of an existing product we created. I simply extended the component set and incorporated the branding. |
Mocks | I kept the UI simple. The B2B user facing product is essentially a SPA with tabular data. The patient facing product is minimally designed for low daily usage on a smartphone. |
This product incorporated platforms from various teams and companies. I created, maintained and presented flows which describe each parties' role and how their product fits in the COVID product experience. I gathered user needs from sales team members in conversation with potential buyers.
The flow below describes the journey from the patient (employee) and medical provider view. From the patient view the basic steps are:
This flow was used to show each team's specific role in the journey. Each team is represented by their own lane and color.
Due to many unknowns and constant discoveries, I created separate flows for distinct parts of the main journey. This let us focus on flows with higher priority and fewer unknowns.
The flow below only focuses on the experience a patient has when they are directed towards PCR COVID-19 testing.
Additional flows I created and maintained were:
Once the flows were 60-70% established, I mocked UI for handling the numerous user tasks and cases. Given a tight deadline and the fact we were leveraging a recently created product, I made a kit to ensure consistency between two products and marketing content.
Below is a sample of the kit.
The B2B portal had the largest scope. It was designed to be scalable and flexible to accomodate the various user roles below.
Role | Main tasks/needs | Show PHI? |
---|---|---|
HR/Employer | I need to check who is at risk. I need to see who shouldn’t come to work. |
Depends on client |
Provider (medical professionals) | I need to order COVID-19 testing. I need to give test results to patients. |
Yes |
Super users | I need to see what’s going on at Account X. I need to help Account Y. I need info about a lab test. |
Depends on user |
A B2B user sees a list of employees with high risk after logging in. These employees require action.
I sometimes add notes such as: requirement references, API notes, and whether the content or feature is a future item. It made presenting much more efficient.
Medical users (e.g. physicians) and super admins can see a list of test orders to make, and a list of test results. A physician user's main tasks are to create test orders, and to disclose test results.
Clicking on an employee's name leads to a view containing additional information including: more personal info, work info, contact info and historical data (e.g. past assessments and testing results).
We provided a simple set of metrics which answers questions such as:
Employees accessed the assessment and their COVID-19 test results in a separate portal. Expected daily usage was under 5 minutes for most cases. We expected most users to access the portal while at work on their phones.
Note - The risk assessment (i.e. questionnaire) was designed and developed by another team and company.
Role | Main tasks/needs |
---|---|
Employee |
I need to sign up. I need to take the COVID-19 risk assessment. (If high risk) I need instructions on receiving a testing kit. I need to get my COVID-19 testing results. I need to know when and how to return to work. |
HR asks employees to register at a unique URL. During sign up employees provide some personal info, work info, contact info and give consent.
The user can access their assessment after logging in. They may also access general COVID-19 information, testing results, and historical data.
The employee portal was designed as a responsive web app. Certain tasks, such as opening testing results in PDF format, are easier on desktop.
We completed the MVP version shortly before my contract ended. The product is currently on the market.
I hope it’s saving lives and keeping people employed.
I was the sole product designer on a small remote team. I took on more PM responsibilities due to the circumstances.
I created and maintained large workflows involving numerous parties, APIs and data sources. I also tried to collect and maintain product requirements.
Looking back this was a fun challenge and I'm glad to have helped. We completed the MVP requirements and design shortly before my contract ended. It was fun learning about virology and COVID testing.