I design experiences by starting with how people actually work, decide, and move through systems. My focus is on creating interaction models and structures that remain clear as products grow more complex, requirements evolve, and constraints surface.

Design, for me, is not isolated from discovery or delivery. I work closely with product, engineering, marketing, and other stakeholders to ensure that design decisions reflect real user needs, technical realities, and business goals from the start.

In practice, my design work often spans:

• ‍Interaction design for complex workflows, tools, and decision paths
• ‍Information architecture that helps users understand systems, not fight them
• ‍Discovery-informed design, grounded in research insights and real constraints
• ‍Edge-case and error-state design to prevent fragile or misleading experiences
• ‍Design-to-engineering handoff, ensuring intent survives implementation

I prioritize clarity, predictability, and usability so experiences remain understandable even as products scale.

While research has its own dedicated focus area, it is tightly integrated into my design process. I regularly translate research findings, stakeholder input, and quantitative signals into concrete interaction decisions.

Rather than designing in isolation, I use discovery and validation to inform structure, reduce risk, and guide teams toward decisions that hold up over time.

Strong design outcomes depend on strong collaboration. I work closely with:

• Product partners to align experience direction with roadmap and business priorities
• Engineering teams to design within real technical constraints and avoid rework
• Marketing and go-to-market partners when experience decisions affect messaging, positioning, or adoption

This collaboration allows design to move from concept to production without losing coherence or intent.