Identify the friction
Go where the system meets real people.
There was no documented workflow to study, so I followed referrals end to end and called every specialist office we referred to, asking each the same four questions.
Psychology taught me to read behavior. Product design lets me build for it. Through behavioral research and systems thinking, I design products that line up human behavior with outcomes you can measure.
Years across healthcare, banking and operations, close to the people a system serves.
Average referral processing time after I built the referral workflow at a free community clinic.
Success in access to care for patients moving through the new referral process.
Primary control contrast in my accessibility redesign of a live-presentation remote.
Four stages that loop: what I measure becomes the next thing I observe. Pick a stage to see what it looked like when I rebuilt the specialist referral process at Mercy Health Center.
Go where the system meets real people.
There was no documented workflow to study, so I followed referrals end to end and called every specialist office we referred to, asking each the same four questions.
The cause, not the symptom.
Patients weren't the problem. Five failures were: no shared mental model, one-size-fits-all packets, no tracking layer, unsupported patient effort, and no closure point.
Fit how people actually think and act.
An SOP with a single accountable owner, a master tracker where every row carries a next action, tailored packets per specialist, and in-person help with applications.
Make it survive without you.
Referral time fell from 12+ months to about 2 weeks. Daily triage and standing partner meetings kept the loop closing after the first push.
Two projects, two kinds of system: a clinic's referral process and a live-presentation app. Each card has a small demo you can play with before you read the full study.
Turning lost referrals into closed loops.
I created the referral workflow at a free community clinic so uninsured patients stop falling through the cracks. I worked as UX researcher and designer alongside care coordinators and providers.
Same patient, same clinic, same specialists. What changed was where ownership lived.
The orange is the brand. The contrast is the bug.
A WCAG 2.2 audit and redesign of ProPresenter Remote for volunteers running services from dim booths: stronger contrast, VoiceOver descriptions, labels that scale with Dynamic Type.
Simplified recreation for illustration. Drag the text size up and compare how each version handles it.
A playable version of the referral tracker I built at Mercy. One row is one referral, and no row is allowed to go quiet. Move referrals forward, let a day pass, then triage. Turn on the notes to see why each piece exists.
Every active referral is visible in one place, so nothing lives only in someone's memory.
A status alone doesn't move anything. A named next step does.
Triage sorts by days without movement, so stalled referrals can't hide.
The old process had no closure point. Now a referral is done only when care happens.
| Patient | Specialty | Next action | Quiet | Status |
|---|
Each one came from a real project, not a poster.
"Patients don't follow through" was the symptom. "No one owns the referral" was the cause. Design for the second one.
Seen in Closing the Care Gap →Asking patients to gather documents alone assumed effort they couldn't spare. So I sat with them and filled out applications in person.
Seen in Closing the Care Gap →Accessibility work doesn't mean erasing identity. The remote kept its orange; only the contrast changed.
Seen in Rethink the Remote →A fix that depends on one person isn't a system. SOPs, a tracker and partner relationships kept referrals closing.
Seen in the framework →
I'm a psychology-trained product designer finishing a B.S. at Kennesaw State, with four years across healthcare, banking and operations.
My psychology background isn't adjacent to design. It's the foundation of how I design. I don't start with screens. I start with behavior, then build the system that moves the outcome.
Understanding behavior. Designing better outcomes.
I'm looking to join a product design or UX research team in Fall 2026, one that designs for behavior and outcomes you can measure.