Mapterial 2.0 — COVID Testing Administration System
Led UX design for a rebuild of Mapterial's COVID-19 testing and administration platform — covering user research, onboarding flows, Material Design system, and high-fidelity prototypes.
Why this page is a summary: this work is covered by an NDA, so the artifacts — screens, research captures, and prototypes — are not public. What follows is the problem, how I worked it, and the decisions I made, which is the part that transfers anyway. The full case study is available on request, or behind the password below if you already have it.
The Problem
Mapterial's COVID-19 testing and administration platform had grown past what it was built for. The company wanted a rebuild that served two audiences with very different needs — the administrators running testing operations and the people being tested — while scaling to a growing client base. I drove the design from research through prototype handoff.
What I Did
The work behind the wall.
Ran user interviews and synthesized client product feedback into a requirements document
Built a hierarchical functionality list to surface priorities and dependencies before any design work
Designed a self-initiated onboarding flow so new users could start without an administrator
Created a Material Design style guide — color, typography, component library — plus reusable layout templates
Delivered high-fidelity prototypes of the key flows, including the LEAP Pickup experience
Decisions
The calls I made, and why.
The screens are confidential. The reasoning is not, and it is the part worth reading.
Requirements as a hierarchy, not a list
A flat backlog hides the thing that actually matters, which is what depends on what. Structuring the functionality as a hierarchy made the dependencies visible before anyone drew a screen, and it turned prioritization from an argument about preference into a conversation about sequence.
Onboarding that does not require an administrator
In the original system a new user could not get started without someone on staff setting them up. That is a support cost on every single signup and a delay for every new user. The self-initiated flow was the single change with the clearest compounding return for both audiences at once.
Generic templates instead of bespoke pages
With a growing client base, every page designed as a one-off is a page someone has to maintain and adapt per client. Designing a small set of layout templates that adapt to multiple content types meant the system could absorb new functionality without new design work each time.
What's in the full case study
The Figma files — the requirements hierarchy, the self-initiated onboarding workflow, the style guide and component library, the layout templates, and the LEAP Pickup prototype.