Getting Started With Oral History Projects
Oral history is the practice of recording first-hand accounts of historical events through interviews. It seems straightforward until you are actually sitting across from someone with a microphone and realizing your recorder is still in record mode from three days ago. The concept itself is simple enough. You talk to people who were there, you save what they say, and you make it accessible. It is not simply a collection of anecdotes or family stories, though those can be part of it. An Oral History is a structured methodology. You identify a specific time period, event, or community, then systematically interview participants to create a primary source archive. Institutions like universities, libraries, and historical societies use this approach because it captures details that written records simply miss. The lived experience of ordinary people during major events is the core product. I spent a lot of time working on local labor history archives, and the first project I ever managed on my own ran into a problem I had not anticipated. The interviewee was a retired railroad worker in his eighties, and he spoke with such a strong regional dialect that the automated transcription software kept misreading entire sentences. I wasted about two hours trying to clean up garbage output before I realized no machine was going to fix this. I just re-listened to the recording manually, typed the transcript myself while following along, and cross-referenced specific terms with a glossary of regional railroad terminology I found online. It took longer but the result was actually usable.
The Practical Process
You start by defining the scope. What is the event, community, or theme you are documenting? Be specific. "The 1990s tech industry" is too broad. "Software developers at three Seattle companies between 1995 and 1999" is something you can actually work with. Then you identify potential interviewees. Look for people who were directly involved, not just observers. The person who coded the software is more valuable than the person who wrote about it. Equipment does not need to be fancy. A decent USB microphone, a laptop, and free software like Audacity or oH-Rec (the Oral History Association has recommended tools on their site) will get you through most projects. Record in WAV format at 44.1 kHz or higher. MP3s introduce compression artifacts that become a real problem if you ever need to do detailed transcription work later. The interview itself requires preparation that most beginners skip. Draft questions ahead of time but do not read them like a questionnaire. People respond better when the conversation flows naturally. Start with open-ended questions about their experiences, then narrow down as the interview progresses. Silence is useful. When someone finishes a thought, wait a few seconds before asking the next question. They will often fill that silence with something more important than what you planned to ask.
Common Pitfalls That Ruin Projects
The biggest mistake I see is poor file management. I once inherited a project where someone had named their audio files something like "interview1.wav," "interview (2).wav," and "new_file.mp3." There were no dates, no names, no metadata anywhere. The recordings were unsearchable and the transcription notes had been saved on a separate hard drive that was never backed up. The entire archive became functionally useless within a few years because nobody could figure out what any of it was. Name your files consistently from day one. A format like YYYYMMDD_LastName_FirstName_SessionNumber works reliably. Create a spreadsheet log that tracks every file, the date it was recorded, who was interviewed, and where the file is stored. This takes about ten minutes per project and will save you dozens of hours later. Another issue is assuming that recorded equals preserved. Digital files degrade. Hard drives fail. Cloud subscriptions get forgotten. I have seen three separate projects destroyed because someone stored everything on a single external drive with no backup. Use the 3-2-1 rule: three copies, two different media types, one offsite. It is not optional.
Get the Full Details
Transcription And Accessibility
Transcribing recordings is the most time-consuming part of the process. A one-hour interview typically requires three to four hours of transcription work. Automated tools have improved significantly but they still struggle with overlapping speech, background noise, and non-standard accents. I usually run recordings through a tool like oTranscribe or Temi first to get a rough draft, then go back and correct it by ear. The correction step is where the actual accuracy comes from. If you are working with multiple interviewers or volunteers, establish a style guide before anyone touches a recording. Decide whether you will include filler words, how to handle speaker names, and whether you will add contextual notes in brackets. Inconsistency across transcripts makes the archive feel disjointed and harder to use.
When Oral History Fails
Be honest about the limitations. Memory is unreliable. People forget details, revise their own stories over time, and sometimes conflate events that happened years apart. An oral history is not a perfectly accurate record of what happened. It is a record of what someone remembers happening, shaped by decades of reflection and context. That is still valuable, but it is not the same thing as factual documentation. Cross-reference interview accounts with contemporaneous records whenever possible. Some topics are difficult or impossible to approach this way. Events that happened recently may not have enough surviving participants. Highly traumatic experiences can make interviewees reluctant to share details, or their accounts may be inconsistent due to the psychological effects of trauma. In those cases, you may need to supplement with documents, photographs, or other evidence rather than relying solely on interviews.
An Oral History Archive That Lasts
The difference between a project that dies in a drawer and one that actually gets used comes down to organization and accessibility. Store your files in a structured directory with clear labels. Include a README file in the root folder that explains the project scope, the methodology, and where to find everything. Release transcripts alongside the audio. Allow other researchers to search and reference the content without having to listen to every recording from start to finish. I have seen small local history projects outlive their creators simply because someone took the time to make the materials findable and the documentation clear. It is not glamorous work. It is mostly file naming, folder organization, and double-checking that your backups actually work. But that is what separates a permanent archive from a collection of forgotten hard drives.
