Oral history gives voice to people and communities whose experiences rarely make it into official records. An elder describing a neighborhood before it was demolished. A civil rights witness recounting what she saw. A craftsperson explaining a technique that has never been written down. These recordings are primary sources. How they get transcribed determines whether they survive intact as historical record or get quietly reshaped by someone else's sense of how people should speak on the page. The stakes are different here from market research or academic interview data. A poorly formatted research transcript wastes coding time. A poorly transcribed oral history misrepresents a person's voice to anyone who reads it for the next hundred years.

Development organizations spend months designing studies, recruiting participants, training field teams, and traveling to remote communities to collect qualitative data. The recordings that come back from that work are often the richest, most direct evidence of program impact that exists. They contain beneficiary voices in their own words, unprompted observations about what's working and what isn't, and context that no survey instrument can capture. Then those recordings sit on a laptop while the donor report deadline approaches and nobody has figured out what to do with them. Transcription is the step that most development organizations treat as an afterthought and then scramble to fix at the end of a project. This post makes the case for treating it as infrastructure instead.

Microsoft Teams has become the default video platform for a large part of the research world, particularly in institutions, hospitals, pharmaceutical companies, and universities where Microsoft 365 is already standard. If your participants are already using Teams for their day-to-day work, running a focus group on Teams reduces friction significantly. They don't need to download anything new or create a new account.