Requirements Discovery

Discovery research that informs product strategy and grounds teams in what users actually need. That includes translating insights into design decisions and practical requirements that technical teams can act on.

• In-depth interviews and contextual inquiries
• Thematic analyses and insight synthesis
• Opportunity mapping and problem framing
• Early-stage product direction recommendations

Start with what already exists

Before strategizing any research, I dig into what the organization already knows. That means reviewing digital analytics, existing documentation, and prior research to understand the landscape before adding to it.

• Audit existing data sources and prior research initiatives
• Identify knowledge gaps that primary research needs to fill
• Review findings with internal stakeholders to pressure-test assumptions before moving forward

Consult internal stakeholders

The people closest to the product have already formed a picture of the user. I want to understand that picture, where it came from, and what organizational goals and constraints are shaping it, before I strategize anything.

• Interview departmental leaders to surface assumptions about users and existing knowledge
• Understand organizational goals and strategic priorities that research outcomes need to align with
• Identify internal constraints that shape what solutions are actually viable

Talk to users

With the internal picture in place, user interviews have sharper focus.

• Conduct semi-structured interviews to explore goals, workflows, and pain points
• Analyze findings thematically to surface patterns across participants
• Validate and build on existing knowledge where prior research is available

Stay involved through design ideation

Findings don't hand themselves off. I push to keep research present in early design and requirements gathering, whether that's a single review or a cross-functional workshop, because the translation step is where insights tend to get lost.

• Contribute research findings to inform initial wireframe directions
• Participate in design reviews and workshops to keep user needs present where the engagement allows
• Help frame user insights as actionable requirements for technical teams

• Current state journey maps showing key findings and recommendations
• Future state journey maps capturing early design direction
• User-informed requirements documentation for technical implementation
• Executive reports connecting user needs to business goals