Senior UX/UI Designer · Portfolio 2026

Designing clarity in
complex systems.

I help teams turn fragmented workflows, technical constraints, and growing product complexity into experiences people can navigate with confidence. Focused on enterprise workflows, product ecosystems, and technical user experiences.

Selected work.

Three projects, each solving a different kind of complexity: navigating large product catalogs, improving technical workflows, and creating clearer digital experiences from the ground up.

01 / Selected work Redesign

Order History

Unified three disconnected order journeys into one self-service experience.

Industrial · 2024–2025 Explore
02 / Selected work Redesign

Configuration Tool

High-complexity technical workflows, made navigable for novices and faster for experts.

Industrial · 2023–2024 Explore
03 / Selected work New feature

Software Sales

Software added to a hardware checkout — without breaking the existing flow.

Industrial · 2025 Explore
See all work
Strengths

The work I'm built for.

The value I bring isn't just in designing screens. It's in bringing clarity to complex products, creating systems that scale, and seeing ideas through from problem to delivery.

Calm out of clutter.

I simplify cluttered B2B tools and large product catalogs so people can complete tasks with less effort and more confidence. The depth stays for the experts who need it; the noise goes.

Systems, not screens.

When a product has drifted into a dozen inconsistent screens, I pull it back into one set of components and rules. First-timers and everyday power users both stop guessing.

The whole arc.

From user conversations and flow mapping to testing, accessibility, and delivery, I stay involved throughout the process to make sure the final product works as intended — not just on the design file.

Kickoff to handoff.

  1. Listen first.

    Talk to the people who use the thing every day. Read the docs. Sit with the friction before naming a solution.

  2. Pick a path.

    One direction, defended. Trade-off named in writing. Decisions belong in docs — not in someone's memory of last week's call.

  3. Ship to engineering.

    Every state covered. Accessibility on by default. Handoff a developer can actually build from without a Slack thread to confirm.