.jpg)
Work
Each of these projects started with a messy problem and users just trying to get through their day. My job was to untangle the complexity and design tools that made things easier.
Task Manager App
System Object Map
Wireframes
Prototypes
15.6% reduction in conditioning adjustments
16.8% drop in flagged items
$1.6M in savings in first 9 months
Analytic Config UI
Proto-Personas
Wireframes
Prototypes
DeliverEase – Report Issue Feature
Wireframes
Prototypes
– Avg 17% increase in reported issues
– Avg 2.8% drop in approved claims
– Forecasted $2.4M in savings for 2025
01
Research & Insight Discovery
I get close to users early: observing, interviewing, and mapping workflows to spot the real friction points, not just the ones on paper. I look for patterns in how people really work, find the shortcuts, the workarounds, the pain points, and then use that to define what’s worth solving.
02
System Objects & User Journey Mapping
I break down systems into their moving parts and map out the user journeys, connecting how people think with how things work (or don’t). This helps the team understand the logic behind the chaos and builds a shared mental model of the product or service.
03
Concept Ideation & Wireframes
I move fast from insights to ideas, sketching, wireframing, and gut-checking early concepts to solve core problems before polish distracts. I try not to fall in love with any one solution, just the one that makes things easiest for the user.
04
Prototyping & Testing
I build quick, clickable prototypes and put them in users’ hands as soon as possible, failing fast and learning faster. Feedback comes early, so we’re fixing issues before they get expensive.
05
Performance Analysis & Optimization
After launch, I dig into user behavior and feedback to refine what works, fix what doesn’t, and make sure the tool keeps pulling its weight. Whether it’s behavioral data or stakeholder insight, I treat optimization as part of the design process, not an afterthought.
About me
I was drawn to UX because humans have a knack for over-complicating things, especially technology. I like making things simple, not by dumbing them down, but by getting out of users’ way. The best tools are the ones people barely notice. They just work.
While I aim to build products that are delightful, I care more about usefulness than wow factor.
Who I am
01
Self-directed by default
I don’t need supervision to lead a project from research to rollout. I work independently, take responsibility, and keep things moving.
02
Comfortable in the ambiguity
I’m used to figuring things out in messy, undefined spaces. Give me a vague problem, and I’ll dig in and get to the bottom of things and map the path forward.
03
Team-friendly operator
I’m easy to work with, quick to communicate, and low on ego. I bring clarity to the process, not chaos.
What I do
01
Focused on practical impact
I build tools that help people work smarter, not harder. If it’s not useful, it’s not done.
02
Grounded in real-world observation
I learn the most by watching how people actually work, not how someone thinks they should. Interviews, field visits, and user shadowing help me find the right problems to solve.
03
Prototyping with purpose
I move quickly from insight to interaction by sketching, wireframing, and testing ideas early so we’re not designing in the dark.
What I don't do
01
Chase the latest design trends
I’m not chasing what’s hot on Dribbble. If it doesn’t help someone do their job better, it’s just decoration.
02
Design to farm time and attention
I don’t build apps to keep people scrolling. I design tools that help users get what they need and move on.
03
Treat stakeholder feedback like a suggestion box
I listen closely, ask follow-ups, and translate business needs into actionable designs, not checkboxes.
Design Philosophy
I design with a bias toward action and a focus on real-world impact. I’m less interested in showing off than in solving the right problems in the cleanest way possible. If a tool helps someone do their job faster, with less friction, and without needing a manual, that’s good design.
Usefulness beats cleverness
- Clarity over novelty
- Good design is about serving users, not impressing designers
Design should get out of the way
- Good tools let users focus on their task, not the UI
- If a feature doesn’t help users work faster or smarter, it probably doesn’t belong
Insight comes from observation
- Real problems often show up in the details people don’t mention
- Spend time where the work happens, watching and listening helps you ask better questions
Simple is hard
- Complexity likely means we haven’t solved the problem yet
- Iteration should be used to subtract, not just refine
Collaboration hones ideas
- Early feedback makes good ideas stronger and bad ones easier to kill
- Cross-functional alignment isn’t a chore, but how good products happen