theoretical-saturation
Use when assessing whether categories are theoretically saturated and no new properties emerge from additional data.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Use when assessing whether categories are theoretically saturated and no new properties emerge from additional data.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | theoretical-saturation |
| description | Use when assessing whether categories are theoretically saturated and no new properties emerge from additional data. |
Theoretical saturation is the stopping rule for category development in grounded theory: you keep sampling and comparing until additional data do not change your understanding of a category’s properties, dimensions, or its relationships to other categories in ways that matter to the emerging theory.
Saturation is not “I interviewed enough people.” It is theoretical.
Use this skill when planning sample closure, responding to deadlines, or evaluating whether a category needs more comparative work.
Saturated category: further comparison yields no new properties and no new hypotheses about relationships relevant to the core story—only more examples of the same variation pattern.
Important nuance: you may always collect more stories. Saturation asks whether those stories refine the conceptual structure.
Saturation applies to categories (and key relationships), not to “the dataset” as a blob.
Ask: “Which category am I evaluating?” (e.g., soft framing).
For the focal category, list:
Update this list as comparison proceeds.
Bring in new incidents explicitly chosen to test weak spots (theoretical sampling).
Saturation signals:
Non-saturation signals:
Causes:
Symptoms:
Corrective actions:
Markers:
| Level | What to check | Saturation hint |
|---|---|---|
| Code | Definition stable; splits resolved | Merges hold across new data |
| Category | Properties/dimensions stable | New incidents align to matrix |
| Relationship | Hypothesis stable under tests | Contradictions explained by boundaries |
| Core story | Integrated outline stable | Selective coding yields marginal gains |
Some authors (including Dey) argue “saturation” language can overclaim. Theoretical sufficiency reframes the question:
“Have we developed categories adequately to support a defensible argument for this study’s aims?”
Practical use:
This does not mean lowering standards; it means honest alignment between claims and evidence.
Category / relationship under review:
Properties listed (complete?):
Dimensions listed (complete?):
Boundary statement written in one paragraph:
Negative cases on hand (count + sources):
Unexplained deviance remaining (list):
Last time this category changed meaning (date + why):
Planned next comparisons (if any):
Decision: continue sampling / close category / reopen category
A strong saturation claim typically includes:
Avoid vague “saturation was reached” without category-level specificity.
Sampling and saturation are paired:
theoretical-sampling, constant-comparison, memo-writingselective-coding, substantive-theory (fit, work, relevance, modifiability)glaserian-grounded-theoryUse when writing academic prose for qualitative research — findings, methods, discussion sections with appropriate voice and conventions.
Use when conducting participatory action research (PAR) involving collaborative inquiry, cycles of action and reflection.
Use when formatting academic work in APA 7th edition style — citations, references, headings, tables, and manuscript structure.
Use when designing or conducting case study research following Yin's multiple case study methodology or Stake's approach.
Use when developing and densifying categories with properties, dimensions, conditions, and consequences.
Use when formatting academic work in Chicago/Turabian style — notes-bibliography or author-date systems.