DDBA 8303 Week 8 Saturation Argument Example

Showing Saturation Instead of Claiming It: When New Codes Stopped Appearing in a Case Study of a Software Firm's Remote Onboarding, What Hearing Every Theme Does Not Mean, and Whose Voices Might Still Change the Picture

Student Name

Walden University

DDBA 8303: Qualitative and Case Study Methodology for Business Analysis Research

Instructor Name

Month Day, Year

Showing Saturation Instead of Claiming It: When New Codes Stopped Appearing in a Case Study of a Software Firm's Remote Onboarding, What Hearing Every Theme Does Not Mean, and Whose Voices Might Still Change the Picture

The Usual Sentence and Why It Is Not Enough

Many case studies end data collection with a sentence such as "Data saturation was reached after twelve interviews." The sentence asserts a conclusion without the evidence for it. My case study examines how a composite software firm of about 300 employees in Denver changed its onboarding of new engineers after moving to fully remote work, and asks what strategies its engineering managers used to bring new hires to full productivity. I interviewed 17 people: 7 engineering managers, 6 engineers hired in the past year and 4 people from the people operations team. This paper shows when new codes stopped appearing, distinguishes having heard every theme from understanding it and names the voices that might still change the picture.

When New Codes Stopped Appearing

New codes slowed sharply after the ninth interview and stopped after the fifteenth. Guest et al. (2006) found a similar pattern in a study of relatively similar participants, with most codes identified within the first dozen interviews. By the count of codes, the case reached what Hennink et al. (2017) call code saturation: further interviews were not adding new issues.

Table 1

New Codes by Interview, in the Order Conducted

Codes counted from the codebook revision log; a code counts as new on the date it was first added.

Hearing Every Theme Is Not Understanding It

Hennink et al. (2017) distinguished code saturation, having heard all the issues, from meaning saturation, understanding each issue fully, and found that the second took considerably more interviews. In this case, the distinction matters. The code "buddy assignment," for example, appeared in the third interview and in almost every interview after. But its meaning kept developing until the fourteenth: early interviews described buddies as helpful; later interviews, especially with new hires, described buddies who were too busy and new hires who stopped asking questions to avoid bothering them. Had I stopped at the ninth interview, I would have reported buddy assignment as a success. Two other codes, "documentation gaps" and "first-project choice," also deepened late. On those three codes, meaning saturation came later than code saturation, if it came at all.

Voices That Might Still Change the Picture

Saunders et al. (2018) caution that saturation depends on which voices are included, since a sample that omits a group cannot be saturated for that group's experience. Three voices are missing. New hires who left within their first six months were not interviewed; the firm did not provide contacts, and their experience of onboarding may differ sharply from those who stayed. Engineers outside the United States, about 15 percent of the engineering staff, work in different time zones and may have faced barriers no one I interviewed described. And no senior executive was interviewed; executives set the remote-work policy and may describe its aims differently from managers.

Checking the Count

Counting codes by interview depends on when codes were created, so the count is only as reliable as the revision log behind it. I created codes on the day each transcript was first coded and dated every addition, which makes the table reproducible from the log. A classmate who coded two transcripts independently, the fourth and the thirteenth, produced no codes absent from my codebook for the thirteenth but two for the fourth, which I had merged into broader codes. Those two would have raised the early counts slightly without changing the pattern. The check suggests the table understates early variety a little and is otherwise sound.

What This Means for the Findings

The case will report that new codes stopped appearing after fifteen interviews, that three central codes continued to deepen until late, and that the findings describe onboarding as experienced by those who stayed, in the United States, below executive level. That claim is narrower than "saturation was reached," and the evidence backs it.

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

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(4), 1893-1907. https://doi.org/10.1007/s11135-017-0574-8