Research Governance

Data Saturation

Data saturation is the point in qualitative research where additional data collection is unlikely to add substantially new information relevant to the research question.

Concept facts

Data saturation is the point in qualitative research where additional data collection is unlikely to add substantially new information relevant to the research question.

Also known as
Saturation, thematic saturation, code saturation, meaning saturation.
Used in
Interview studies, field studies, diary studies, usability research planning, qualitative sampling, and research quality assessment.
Interpret with
Sampling strategy, thematic analysis, codebook, research protocol, and triangulation.

Plain-language explanation

Data saturation helps researchers judge whether they have collected enough qualitative data for the purpose of the study. It does not mean every possible user has been studied. It means the research team is no longer finding substantially new patterns that affect the analysis.

In UX and digital service work, saturation can help determine whether more interviews, observations, or usability sessions are needed before making design or service recommendations.

Why it matters

In institutional and development-sector projects, research time is often limited. Teams may collect too little data and miss important user groups, or they may collect more data than needed without improving decisions.

Data saturation supports better planning by connecting sample size decisions to evidence quality, diversity of participants, and research objectives.

Use contexts

Data saturation is used when:

  • planning the number of interviews or observations
  • deciding whether more fieldwork is needed
  • comparing findings across user groups, locations, or roles
  • assessing whether analysis has enough depth
  • explaining qualitative sample decisions to stakeholders

Application guidance

Teams should not use saturation as a vague claim after data collection. They should define what kind of saturation matters for the project.

Code saturation may occur when no new codes appear. Meaning saturation requires deeper understanding of already identified codes and themes. A project may reach one but not the other.

Saturation should also be interpreted in relation to participant diversity, research scope, and the risks of missing marginalized or high-risk users.

Practical example

A healthtech implementation team studies how rural clinics use an electronic referral system. Interviews include community health workers, clinic managers, district supervisors, and hospital referral coordinators.

After early interviews, the team repeatedly hears about connectivity failure and duplicate paper records. But later interviews with district supervisors reveal a new issue: referral acceptance depends on informal phone confirmation before the digital record is trusted.

The team delays claiming saturation until it has covered both frontline and supervisory workflows. This prevents the final design recommendations from focusing only on interface improvements while missing institutional trust and handoff problems.

Interpretive boundaries

Data saturation is not a mathematical rule and should not be reduced to a fixed number of participants.

Saturation claims can be weak if the sample is narrow, the research questions are broad, or the analysis is superficial.

In high-risk services, researchers should consider whether underrepresented users, excluded users, or edge-case workflows have been adequately included.

Applied at Userhub

Userhub uses saturation reasoning to plan and evaluate qualitative UX research, especially when projects involve multiple user groups, service roles, or institutional contexts.

Saturation decisions help determine when findings are strong enough to inform design recommendations and when more data collection is needed.

See Userhub UX Lab for applied UX research and evaluation context.

Sources and references

Guest, G., Bunce, A., & Johnson, L. (2006). How many interviews are enough? An experiment with data saturation and variability. Field Methods, 18(1), 59–82. https://doi.org/10.1177/1525822X05279903

Hennink, M. M., Kaiser, B. N., & Marconi, V. C. (2017). Code saturation versus meaning saturation: How many interviews are enough? Qualitative Health Research, 27(4), 591–608. https://doi.org/10.1177/1049732316665344

Morse, J. M. (1995). The significance of saturation. Qualitative Health Research, 5(2), 147–149. https://doi.org/10.1177/104973239500500201

Saunders, B., Sim, J., Kingstone, T., Baker, S., Waterfield, J., Bartlam, B., Burroughs, H., & Jinks, C. (2018). Saturation in qualitative research: Exploring its conceptualization and operationalization. Quality & Quantity, 52, 1893–1907. https://doi.org/10.1007/s11135-017-0574-8

Cite this entry

APA

Userhub. (2026). Data Saturation. UX Reference. https://userhub.com.bd/reference/data-saturation/