Research as the compass, design as the map

In my experience, the most valuable design work begins with understanding people (and or other living beings and the environment) in context — their motivations, needs, constraints, and the friction they encounter in their daily lives. I have consistently relied on a combination of qualitative research, quantitative analysis, participatory design sessions, and collaborative workshops to learn directly from users (or key agents or forces) and uncover patterns that are not immediately visible in product metrics alone.

Over time, I've learned that research is not only about validating ideas; it is about building a shared understanding of the problem space. Through interviews, observation, and collaborative sessions, I try to understand how users actually experience a system, where their needs are unmet, and where opportunities exist to improve their workflows and outcomes.

Another important outcome of research work is identifying distinct user segments and the broader ecosystem in which a product operates. Understanding these patterns often influences not only product design but also how teams organize their work. When teams can clearly see the segments and needs they serve — and how those connect to the larger system — they can move with greater clarity and agility.

I also believe strongly in the value of early artifacts and simple prototypes. Paper or digital sketches, diagrams, and lightweight prototypes create space for exploration and dialogue. They allow teams and users to test ideas before committing significant resources or attaching to a solution, and they often reveal insights that are key to discovering in the process.

More recently, the emergence of AI-assisted development and "vibe coding" has significantly accelerated the pace at which ideas can be tested. I've been learning to combine traditional research methods with these new tools to build early product experiences that can be tested with small groups of users in low-risk beta environments. This allows us to observe both qualitative feedback and quantitative signals, such as adoption patterns or friction in the user journey.

Working in this way also influences how I think about product architecture and experience design. It becomes easier to experiment with more modular and adaptive systems that can respond to different user needs while remaining coherent through a design system and shared platform capabilities.

Another area I find particularly interesting is the role of AI-conversational interfaces within interactive experiences. When integrated thoughtfully, they can help users explore complex information, learn faster, and get more value from a product. Designing these experiences requires careful attention to the balance between structured interfaces, conversational interaction, and user control.

For me, research is not a phase — it is an ongoing dialogue between people, ideas, and the systems we design.

The artifacts shown here — insight syntheses, jobs-to-be-done frameworks, journey maps, ecosystem diagrams, and early prototypes — come from my own work across multiple projects. These tools help translate research findings into something teams can reason about together. They anchor conversations around user needs, clarify priorities, and make it easier to identify meaningful design opportunities.

Despite technology changes and new tools, one principle remains constant for me: listening carefully to users is still the foundation of meaningful design.

• Research becomes most valuable when it creates shared understanding. Artifacts such as journey maps, insight syntheses, and prototypes help teams see the same problem space and align on what matters most to users.
• Connect user insight with organizational realities. The best ideas are not only desirable for users — they must also work within the capabilities of the teams and platforms that deliver them.
• AI tools support the process by helping with secondary research, capturing interview notes, and analyzing text, making it easier to synthesize qualitative insights at scale. These tools accelerate discovery, while human judgment remains essential to interpret meaning. AI-assisted prototyping and rapid development have enabled moving from insight to working concepts much faster and testing them with small user groups, allowing teams to combine qualitative feedback with quantitative signals and evolve ideas through fast, low-risk experimentation.

For me, even with advanced tools and analytics, meaningful design still begins with curiosity, empathy, and a willingness to learn from people in their real contexts. This work continues to be a balance between exploration and structure, intuition and evidence, conversation and experimentation — all in service of designing systems that are useful, thoughtful, and meaningful for the people who use them.