What Expert Interviews Can Learn from Oral History

An expert interview can look efficient enough: ask a respected person what they know, record the answer, turn it into something useful, and release them back into a calendar already hostile to reflection.

The method works. It also creates a particular danger: the interviewer can collect polished conclusions while missing the experience that made those conclusions trustworthy.

Oral history offers a useful correction, though I do not mean that an expert interview should pretend to be oral history or that one method is superior. They serve different purposes: oral history often gives a narrator time to develop a retrospective account at their own pace, while an expert interview may concern a current case, an emerging future, or a principle of practice that needs to travel through an organization now.

The difference matters. So does the overlap.

The interview has a future before it has a question

An interview begins before the first question. It begins when someone decides what the resulting account will become.

Will it support a project team? Enter a research archive? Inform a decision? Become training material? Remain available only to a limited group? Outlive the system that first stores it? These are not administrative details to settle after the useful talking is over. They shape the encounter itself.

The narrator should understand the scope of the project, the intended use of the interview, the future benefit being claimed, and the access conditions that will govern the record. In an organizational setting, the interviewer should also be candid about the business value expected from the exercise. If the institution hopes to turn someone’s experience into reusable knowledge, that intention belongs inside the agreement.

This is one of oral history’s firmest lessons. A rich recording without a preservation plan, access decision, or clear account of rights may be moving in the moment and unusable afterward. The same failure appears in corporate expert interviews, merely wearing a cleaner shirt.

Authority changes the answer

An interview is not a neutral pipe between one mind and a repository. Both people occupy positions. Those positions enter the record.

When an interviewer speaks with a high-power individual, the ordinary techniques of inquiry can weaken. Senior experts are often practiced at giving concise, final answers. They may have learned that visible uncertainty invites delay, argument, or political cost. A question meant to elicit reflection receives a finished statement instead. The interviewer accepts it, moves to the next item, and discovers later that the answer contains no path back to the judgment behind it.

That is not necessarily refusal. It may be habit, hierarchy, time pressure, or the interview design itself.

The interviewer’s own position also matters. A junior employee questioning an executive does not have the same freedom as a peer, an outside researcher, or a person with formal authority over the project. If deeper inquiry could sound like challenge, the methodology must account for that before the interview begins. Good intentions do not dissolve an org chart.

Respecting the narrator’s authority does not mean accepting every first answer as complete. It means allowing the narrator to respond in their own style while continuing to explore the areas the project genuinely requires. The balance is delicate: pursue substance without treating the person as raw material.

Ask for the route, not only the result

The most valuable follow-up is often a request for movement.

What happened just before the decision? What made this case different from the usual one? Which signal caused concern? What alternative looked plausible at the time? Who else saw the situation differently? What would make the same answer wrong next year?

These questions do not demand a grand life story. They ask the expert to reopen a conclusion long enough for another person to see how it formed.

That reopening takes practice. Interviewers need enough command of the subject to notice a closed door, enough patience to return to it, and enough restraint to avoid supplying the answer themselves. A single interview may also be the only chance. The expert may retire, leave, become unavailable, or simply never receive another invitation. “We can ask later” is often how knowledge disappears politely.

Preserve the interviewer too

The final record should contain more than the narrator’s words.

Document the preparation, the interview method, the circumstances, the relationship between the participants, and any condition that shaped what could be said. Record where the conversation happened, whether time was cut short, whether another person was present, and where the interviewer chose not to press. The interviewer’s experience is not backstage debris. It helps a future user understand what kind of evidence the interview contains.

Without that context, a repository can make a situated conversation look like a free-standing statement of fact. The recording survives. Its limits do not.

Expert interviews need focus. Oral history needs room. The useful exchange between them is methodological: declare the future of the record, respect the narrator as an equal authority, design around hierarchy, pursue the reasoning beneath polished answers, and preserve the conditions of the encounter.

An organization may call the result an interview, case study, practice note, or knowledge asset; the label matters less than the obligation. A person gave the institution more than an answer, and the record should keep enough of the room, hierarchy, hesitation, method, and intended future for the next person to understand what that answer can bear.