The best products don’t begin with polished interfaces. They begin with a clear understanding of the problem they’re solving.

Product discovery is the process of reducing uncertainty before development begins. Through customer conversations, behavioral data, AI-assisted analysis, and rapid prototyping, I help teams uncover what users actually need instead of relying on assumptions. The result is a stronger product direction and greater confidence that engineering effort is focused on the right problems.
‍
‍Understand the Problem
‍Every major project starts by understanding the people behind it. I work with stakeholders to define business goals and identify open questions, then establish what success looks like before exploring solutions. From there, I meet with customers to understand their workflows, pain points, motivations, and decision-making processes. Whether through interviews, observation, or usability sessions, the goal is to understand how people actually work—not how we imagine they work.
‍
Learn from Data
‍Qualitative research tells us why people behave the way they do. Product analytics tell us where those behaviors occur.I combine interviews with behavioral data such as session recordings, funnel analysis, feature adoption, and customer feedback to identify patterns that might otherwise go unnoticed. AI-assisted analysis helps synthesize large volumes of research, surface recurring themes, and accelerate insight generation while keeping people at the center of every decision.

‍Explore Quickly
‍Rather than debating ideas in meetings, I prefer to put them in front of users.Rapid prototyping allows teams to validate concepts in days instead of weeks. Using modern AI-assisted tools alongside Figma, I quickly build interactive prototypes that explore different approaches, gather feedback, and test assumptions before engineering resources are committed.This process creates better conversations, faster learning, and stronger product decisions.

‍Turn Insights into Direction
‍Discovery isn’t valuable because it produces research documents. It’s valuable because it creates clarity.Every interview, prototype, and experiment should move the team closer to answering questions like:
• Are we solving the right problem?
• Who benefits most from this solution?
• Where do users experience friction today?
• Which opportunities deserve investment?
• What should we build first?
‍
The outcome is a shared understanding of both the customer and the product strategy, allowing design and engineering teams to move forward with confidence.