Research
Research teams understand users both qualitatively and quantitatively, the insight layer product teams build on. UX Research goes deep on how people use a product; Market Research goes wide on how they think and buy.
What you do.
- (01)
Plan studies — define the question, the method, and what a "good" answer looks like.
- (02)
Run research in the field, in labs, and digitally — interviews, usability tests, surveys, diary studies.
- (03)
Analyze mixed-methods data and translate findings into decisions product and marketing teams can act on.
- (04)
Partner with PMs, designers, and marketers to pick the right question at the right stage.
- (05)
Make recommendations that change roadmaps and positioning — not just slideware.
Key skills.
What they look for.
- (01)
Background in psychology, design, anthropology, statistics, or related social-science fields.
- (02)
Evidence you can run a study end-to-end and land a recommendation that moved a decision.
- (03)
Comfort with both qualitative synthesis and quantitative analysis (regression, survey stats, segmentation).
- (04)
Strong written and visual communication — research that doesn't travel doesn't count.
Distinctions.
The same title can mean different things depending on the product, the company, and the stage. Here’s how to pick it apart.
UX Research vs. Market Research
Generative vs. Evaluative
Often confused with.
Roles that sit close to this one — useful to know whether you want the title or the adjacent version.
Prep
Ask yourself.
- (01)
Do you get genuinely curious watching strangers use software?
- (02)
Are you energized by qualitative ambiguity, or do you want the answer to be a number?
- (03)
Can you hold a recommendation under pushback from a PM or exec who wants a different answer?
Open the full file.
File / Research · 3 chapters. Long-form chapters sourced from HTC's internal guides — the kind of reading that pays off on callbacks.