# Generative and Evaluative Research

A distinction between research that explores problems and opportunities and research that assesses a proposed or existing solution.

- Type: framework
- Domain: Research & behavior
- Level: Foundational
- Last reviewed: 2026-09-25
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/generative-and-evaluative-research/>)

## What it means

Generative research develops understanding of people, contexts, needs, and opportunity spaces without requiring a specific design to judge. Evaluative research examines a concept, prototype, or live product against questions such as comprehension, usability, value, or performance. A discovery effort may alternate between both modes.

## Why it matters

The distinction helps teams match evidence to uncertainty. Evaluating a solution cannot establish that the underlying problem matters, while broad exploration may be inefficient when a team needs to diagnose a specific interaction.

## When to use it

Use generative methods when the problem space, audience, or opportunities are uncertain. Use evaluative methods when a concrete proposition or experience can be examined. Combine them when learning about context and assessing a response are both decision-critical.

## How it works

1. Identify whether the immediate uncertainty concerns the problem space, a solution, or both.
2. Frame open learning questions for generative work and explicit criteria for evaluative work.
3. Select participants, context, and methods suited to the evidence needed.
4. Keep problem evidence separate from reactions caused by the proposed solution.
5. Use findings to reframe opportunities, revise the solution, or choose the next research mode.

## A practical example

A clinic team first observes how patients prepare for appointments and discovers coordination failures. It then evaluates two reminder concepts with realistic tasks, keeping the contextual need findings separate from interface usability findings.

## Where it breaks

Generative and evaluative are purposes, not guarantees of rigor, and many methods can serve either purpose. The boundary can blur when a concept prompts new understanding of the problem.

## Common mistakes

- Showing a solution early and calling reactions problem discovery.
- Using exploratory interviews to claim that a detailed workflow is usable.
- Treating the labels as fixed method categories rather than research purposes.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/generative-and-evaluative-research/#visualization-generative-and-evaluative-research>)

## Sources

1. [When to Use Which User-Experience Research Methods](<https://www.nngroup.com/articles/which-ux-research-methods/>) — Nielsen Norman Group · Professional guidance
2. [How the discovery phase works](<https://www.gov.uk/service-manual/agile-delivery/how-the-discovery-phase-works>) — GOV.UK Service Manual · Government service guidance

## Related topics

- [Product Discovery](<https://wiki.soroush.uk/topic/product-discovery/>)
- [Problem Validation](<https://wiki.soroush.uk/topic/problem-validation/>)
- [Solution Validation](<https://wiki.soroush.uk/topic/solution-validation/>)
