About me
I get curious about the moments people get stuck, and I think the interface is almost always the reason why.
I design for high-stakes moments where clarity is the whole job. Accessibility is how I think, not a box I check at the end.
I'm drawn to products where getting it wrong has real consequences. Disrupted travel. Financial uncertainty. Nights when anxiety makes sleep feel impossible. That's the work I want to keep doing.
Background
I started in front-end development. That taught me something most designers learn later: the way a system is built and the way a person experiences it are almost never the same thing. It also taught me to think about feasibility, systems, and implementation alongside user needs.
My work keeps pulling me toward the same problem. Someone is already overwhelmed. The clock is ticking. And instead of helping, the product makes it worse. I find that problem fascinating. Not because it's hard, but because small design decisions can completely change the outcome.
I care about the whole flow, not just the screen. What does this system assume about the person moving through it? What happens when those assumptions are wrong? Those are the questions I keep coming back to.
How I Think
Most interfaces fail at the exact moment people need them most: when something goes wrong, gets complicated, or just doesn't make sense.
Three things I keep coming back to:
- The interface should do the work. Not make the user figure it out.
- Accessibility designed in from the start solves different problems than accessibility added after the fact.
- Complexity doesn't have to disappear. It just has to be organized well enough that people can move through it without losing their place.
Currently
Finishing my B.S. in Human-Centered Computing at RIT. Graduating December 2026.
Outside of Design
I spend time outdoors, cook, and I'm always learning something new. Usually a language.
Contact