What I do...

Design product experience systems

Information architecture, navigation, and consistency

TLDR
What was broken

Fragmented navigation, terminology, and placement logic made complex products harder to understand.

What I did

I created repeatable systems for information architecture, vocabulary, and decision-making.

Why it mattered

Findability improved and UX goals became easier to connect to business outcomes.

71% → 92%Unified NavigationTask Completion

Philosophy

Experience quality is often an architecture problem before it is a screen problem. When terminology, navigation, and placement logic drift apart, people pay the tax in confusion.

I design systems that make complex environments easier to understand before the interface asks users to act.

Strategy in Action

Navigation consolidation

I led work to simplify fragmented pathways into a more coherent information architecture across complex product areas.

reduced duplicated decision paths

made related workflows easier to find and understand

Shared vocabulary model

I created clearer terminology rules so related concepts behaved consistently across enterprise, business, paygo, and free experiences.

reduced language drift across surfaces

supported clearer mental models for customers and internal teams

Placement decision tree

I turned subjective navigation debates into a repeatable framework grounded in user mental models.

made placement decisions easier to defend

gave partner teams a shared way to reason about where things belong

Builder consistency review

I aligned patterns, labels, and flow logic across related experiences so customers had less to relearn.

improved consistency across related workflows

tied systems work to findability, completion, and sentiment

Outcomes: clearer navigation and stronger findability

Helped teams improve positive feedback from 71% to 92%, consolidate fragmented navigation, and connect UX goals to measurable task completion and customer sentiment.

Listen

Build

Deliver

Measure