About

Design should move the product forward.

For eight years, I have used research, UX, and collaboration to turn complex product problems into decisions teams can move forward with.

A point of view

A screen is only one part of the product decision.

The work begins with the market, the customer, and the evidence. I translate local context into product decisions teams can test, learn from, and scale.

Designing a service

A service moves when its systems, people, and evidence move together.

A service should feel native to its market, not merely translated into it. Service design means understanding the platform, the brand, the customer, and the market at the same time—then using evidence to decide what moves forward.

Good product design lowers uncertainty: it helps people express themselves, feel safe, take the first step, and return. The experience does not begin or end in the app.

01

Product experience

The flows, interfaces, and interactions people use in the moment.

02

Service touchpoints

The moments that reconnect people with the service and make the next action feel timely.

03

Customer journey

Discovery, support, and sharing shape the relationship before and after a person uses the product.

01

Read the platform

Like an engineer tracks a platform update, a designer needs to understand new patterns and components before deciding what to adopt.

Component decision treeComponents are choices, not decoration.
What does the person need next?
  1. DiscoverLanding · store · card
  2. UnderstandOnboarding · guidance · disclosure
  3. ActForm · CTA · sheet · confirmation
  4. ReturnNotification · widget · entry point
  5. ShareReferral · campaign · social card
Select, adapt, and test the pattern that fits the context and the system.
02

Scale the system

In established organizations, quality depends on introducing the right component into both the platform and brand system—not adding a visual layer at the end.

Illustrative system board
A shared base with purposeful variation.
03

Read the customer

Research reveals the context, motivations, and friction behind a request before a team commits to a solution.

Customer voiceQuestions, concerns, support signals
BehaviorActivation path, drop-off, return
ContextMarket patterns, culture, constraints
Team inputFeasibility, content, delivery
Working questionWhere does the first action lose momentum?
Working hypothesisMake the next step more certain.Prototype → test → learn
Illustrative decision workspace
04

Move with the market

Trends are signals to interpret, not styles to copy. The work is understanding what customers will welcome next.

Illustrative signal board
Read signals before choosing a visual answer.
05

Prove the next move

Behavior and validation show whether a direction contributes value, and what should change next.

Illustrative decision brief
Evidence, trade-off, then a practical next move.

Senior judgment

A senior designer makes the next decision clearer.

Good product work is a series of choices: what to question, what to define, what to make, and what not to make. Senior judgment identifies the choice that changes the product most, then gives the team a clear way to act.

01

Choose the leverage point

Decide where a better experience will change the product most—not every surface at once.

02

Make the trade-off visible

Turn ambiguity into a clear bet: the problem, the evidence, the trade-off, and the next decision.

03

Leave a decision system

Ship the solution, then leave the team with a clearer way to make the next one.

Illustrative decision brief
Make the evidence, trade-off, and next move visible to the team.

How I work

Move from a request to the decision that matters.

01

Observe

Read the market, customer behavior, and constraints before choosing a solution.

02

Frame

Turn the visible request into the product problem worth solving.

03

Align

Give specialists one direction, a shared trade-off, and a clear next decision.

04

Make

Turn the decision into clear flows, polished interfaces, interaction details, and implementation-ready systems.

05

Learn

Use behavior and feedback to decide what improves next.

Experience across growth

The user experience starts before the app and continues after the session.

I consider discovery, first use, return, value exchange, and sharing as one connected design system.

A

Acquisition

Make the first impression intentional.

Store · screenshots · identity · landing

Illustrative growth surface
A

Activation

Make the first action feel obvious.

Onboarding · core UI · first action · web-to-app

Illustrative growth surface
R

Retention

Give people a reason to come back.

Return touchpoints · content · widgets · reminders

Illustrative growth surface
R

Revenue

Make value exchange feel clear and fair.

Offers · plans · checkout · membership · commerce

Illustrative growth surface
R

Referral

Create moments worth carrying forward.

Sharing · referral · campaigns · promotion · goods

Illustrative growth surface

What I bring

Four lenses for making a product contribute.

Market Research

Turn local context, customer motivation, and friction into a testable product direction.

System

Protect the system while designing controlled variation for people, markets, and experiments.

Trend

Separate a lasting market signal from a style worth copying.

Evidence

Use behavioral signals, qualitative research, and practical proxies when the full data picture is not yet available.

See the work

See the decisions in the work. See the scope in the career.