Portfolio index
Selected work
5 case studies
Fleet maintenanceKnow what needs attention before it costs you time.Book a demo
58K+monthly users130+pages1K+events
These case studies show how I move from an unclear problem to a working experience: understand the context, make the tradeoffs visible, design the path, stay close to the build, and keep learning after launch.
Some began as 0→1 products. Others involved simplifying mature systems already in use. Every project had to become clearer, more useful, and real.
All selected work
Five case studies across enterprise software, a 0→1 product, B2B SaaS, nonprofit infrastructure, and public health. Each one shows the problem, what I owned, the decisions that mattered, and how the work moved toward something people could actually use.
Simplifying a high-stakes talent workflow inside a mature enterprise platform, while keeping the case study safely outside the confidential product.
Turning 14+ years in the field into a route-planning product that helps people use a park day better without turning wildlife into live targets.
Rebuilding the path around a complex fleet product so buyers could understand it faster and reach a trial or demo with fewer unanswered questions.
Turning thousands of pages, services, and research into clearer first moves for people seeking help, evidence, or a way to act.
Rebuilding a statewide opioid resource so people could reach help, naloxone, treatment, and useful answers without hunting through the site.
What the work proves
I am most useful where teams lose momentum between the problem, the interface, and the live build.
Research, field context, analytics, stakeholder constraints, and user behavior shape the direction before the interface does.
Ethics, accessibility, business goals, platform limits, and user needs are named early so the team can make a real decision.
Front-end depth keeps responsive behavior, accessibility, content, and design intent connected through implementation and QA.
Testing, analytics, support questions, search behavior, and real use become the next release instead of a post-launch report nobody opens.
How I read the work
The interface matters. So does the question it answers, the behavior it supports, the code it becomes, and the evidence that tells us whether the decision held up.
That connection is what lets me enter at one page or one product problem and still see where the work reaches next.
Clarity, confidence, accessibility, context, and the effort required to move forward.
Value, conversion, trust, qualification, operational reality, and the consequences of the design.
Responsive behavior, content systems, accessibility, performance, CMS limits, and front-end implementation.
Testing, analytics, search behavior, support signals, and honest separation between scale and causation.
Available for full-time roles + select projects
I am looking for a senior product design, UX/UI, or design-engineering role where I can own meaningful work from discovery through launch. I also take select projects when one critical page, flow, or product needs focused help.