Enterprise UX
Design &
Prototyping
Internal enterprise software is often where good UX goes to die. At Labcorp I work across multiple internal products, running discovery sessions, designing in Figma, and building high-fidelity prototypes that give stakeholders something real to react to before anything gets built.
UX design for internal products that people actually have to use
Internal enterprise tools are a specific design challenge. Users don't choose the software — it is assigned to them. That raises the stakes for usability because there is no option to switch to a competitor, and bad UX just becomes someone's daily frustration.
At Labcorp I lead UX design for internal applications across the full product lifecycle. That means starting with discovery — understanding the actual problem through conversations with users, product managers, and stakeholders — before touching Figma. The design work follows the problem, not the other way around.
I work closely with the developers who build what I design, which helps. I understand the constraints they are working with, and they understand what I am trying to achieve. That back-and-forth produces better outcomes than a one-way handoff.
From discovery to shipped design
I start by talking to the people who will actually use the product. That means interviews, workflow observations, and reviewing any existing research. The goal is to understand the real problem before forming an opinion about the solution.
Before any UI work, I map out what the user is trying to do and what decisions they need to make along the way. Getting the flow right first makes the wireframing and prototyping much faster because the structure is already settled.
Low-fidelity wireframes in Figma, shared early with stakeholders for fast feedback. At this stage the goal is to test structure and layout without getting distracted by visual polish.
Interactive high-fidelity prototypes built using Figma and the component library I built. Stakeholders can click through the prototype and experience the product before a single line of code is written.
Because every component in the Figma file is connected to a real code component via Figma Code Connect, developers see exact code snippets when they inspect the design. The handoff is a link to a Figma file, not a conversation about what I meant.
From gray boxes to the real thing
The internal work can't be shown directly, so here is a recreated example of the same screen at two fidelities — the progression every project goes through. Structure gets validated cheaply in gray boxes before any visual polish is spent.
The user flow behind it
Recreated artifacts with fictional content — representative of the real deliverables.
Tools used across the design process
Prototypes that do the talking
An interactive prototype in a review meeting produces more specific feedback than a static mockup or a written spec. Stakeholders can point to things rather than describe them.
Figma Code Connect means the design file and the code are connected. Developers spend less time interpreting intent and more time building.
WCAG compliance is designed in from the beginning rather than audited at the end. Color contrast, focus states, and screen reader labeling are part of every design review.
Using the component library I built means every design already speaks the same visual language as the other products in the organization.