Approach
They involve users, workflows, business priorities, technical systems, constraints, and decisions that often need to be made before all the answers are known.
My role is to help teams reduce that uncertainty, make better decisions, and turn what we learn into experiences that can actually be delivered.
01
I don’t assume the request I’m given is the problem worth solving.
I start by understanding the user, their workflow, the product context, and the assumptions behind the request.
That means talking with users, reviewing existing evidence, identifying what we still need to learn, and asking whether the proposed solution actually addresses the underlying need.
Research helps reduce uncertainty before the team commits to a direction.
02
Research only matters when it changes what we do.
I translate what we learn into clear product implications: what needs to change, what matters most, and what we should test next.
I bring research and design thinking into product conversations early enough to influence direction.
03
The more realistic the experience, the more useful the feedback.
When interaction, logic, data, or system behavior matters, static screens may not tell us enough.
I create realistic prototypes so users can respond to the experience itself rather than imagine how it might work.
That can include coded prototypes and AI-enabled development tools when they help me learn faster and expose problems earlier.
04
Technical and business constraints are part of the design problem.
I work closely with product, engineering, and architecture to understand both what the experience needs to accomplish and what the system can realistically support.
Finding the strongest solution across user needs, product goals, technical realities, and delivery constraints.
05
Handoff isn’t the finish line.
I stay close to implementation so the experience that reaches users reflects the intent behind the design.
That means clarifying behavior and workflow decisions, reviewing what gets built, and resolving UX gaps with engineering.
The work is successful when the experience works for users.