How to Interview a Subject Matter Expert Before You Write the Brief

Somewhere in your company sits a person who knows the topic cold. Maybe it is the staff engineer who migrated the billing system. Maybe it is the support lead who has answered the same confused question four hundred times and could recite the fix half asleep. The usual process hands the writer a brief that says "talk to Priya," plus a calendar link, and hopes. Priya gives forty-five polite minutes of generalities. The draft reads like every other page on the first results page.

That outcome is a briefing problem.

The expertise has to land in the brief itself, as specific claims and stories and numbers, before any writer opens a blank doc. That means the person who owns the brief runs the interview, and the interview runs against a plan. This guide covers the plan. If you have never built a brief from scratch, start with how to write a content brief and come back.

Why the strategist runs it

The writer usually gets this job by default, since they are the one who needs the material. It goes badly for a simple reason. The writer arrives knowing the topic, while the strategist arrives knowing the gap, which is the thing that makes an interview worth an expert's time. The strategist has read the ranking pages, seen what all of them repeat, and noticed what none of them say. Those missing pieces are exactly what the interview should extract.

A writer can sit in, and often should. Hearing the expert's phrasing firsthand makes the draft better. But the questions belong to whoever is accountable for the brief's angle.

There is one exception worth naming. A long-term freelancer with real domain depth (a former nurse writing healthcare content, say) may run a sharper interview than anyone in-house. In that case, hand them the gap list and let them drive. The freelance briefing guide covers what else that contributor needs from you.

Do the SERP homework before booking anything

Read the top five results for the target query. Keep two running lists. The first holds everything every page says: the commodity advice, the points you could write without talking to anyone. The second holds what no page says, or says vaguely, or gets subtly wrong.

Take a query like "how to reduce Kubernetes costs." Every ranking page recommends right-sizing pods and using spot instances. None of them describes what happened when a real team moved its batch jobs to spot and the jobs started dying mid-run at 2 a.m. That story is the whole article. Your expert probably has one like it, and they will never volunteer it in response to "what are the best practices?"

The second list becomes your question plan. Aim for six to eight questions, roughly two per gap. More than that and you will rush the follow-ups, which is where the good material hides.

Asking for the meeting

Experts are busy and have been burned by content interviews before. They gave an hour, the article quoted them saying something bland, and nobody showed them the draft. Your ask has to fix those memories in two or three sentences.

Request thirty minutes. Name the topic and the specific angle. Send two of your questions in advance, the two hardest ones, so they can think in the shower instead of on the call. Promise, in writing, that they will review every quote attributed to them before anything publishes, and then keep the promise. If the piece will carry their name and title, say so. Plenty of experts care about that more than they admit.

Avoid sending the full question list. People who see all eight questions write answers in advance, and prepared answers are smooth and useless.

Questions that pull out what only they know

Opinion questions get opinions, which the expert holds in common with everyone else in their field. Story questions get details. The whole craft of this interview is converting "what do you think about X" into "tell me about a time X happened."

• "Walk me through the last time this went wrong." The single most productive question in the set. Failures come with specifics attached: dates, tool names, who got paged, the Slack message someone sent at midnight.
• "What does a beginner do that looks right but isn't?" This surfaces the counterintuitive points that make readers trust a page.
• "Here's what the top-ranking article says. Where would you push back?" Bring a printed quote. Experts love correcting other people's published work, and the correction usually becomes your angle.
• "What number do you look at first?" Practitioners have a metric they check before any other. Asking for it tends to produce the most quotable line of the call.
• "What did you believe about this two years ago that you don't anymore?" Optional, and it fails about half the time. When it works, it gives the article a narrative spine.

Skip anything that starts with "what are the best practices for." You will get the average of the internet, delivered in a nicer voice.

The pause

When the expert finishes an answer, stay quiet and count slowly to five, because the thing they add to fill that silence is almost always the sentence you end up quoting.

Record everything, write down almost nothing

Ask permission to record at the start, on the recording. Then let a transcription tool do the note-taking. Your job during the call is follow-ups, and you cannot listen for the interesting half-sentence while typing the previous one. Jot a timestamp when something lands. That is enough.

Watch the clock. At minute twenty-five, ask the closing question: "Is there anything I should have asked and didn't?" Then end on time, even if the conversation is going well. Ending on time is how you get the second interview.

Turning the transcript into brief fields

A raw transcript attached to a brief is homework for the writer. Most writers will skim it, pull one quote, and fall back on what they already know. The strategist has to do the translation, and it takes about an hour for a thirty-minute call. Read the transcript once straight through. Then map what you found onto the brief.

Angle. If the expert disagreed with the ranking pages, that disagreement is probably the angle. Write it as a claim the article has to defend: "Spot instances save money only for jobs that checkpoint, and most teams find this out the expensive way."

Required examples. Each usable story gets a line with its transcript timestamp. The writer should build a section around at least one of them, told with the concrete details intact. Stripped of the 2 a.m. and the job names, a story turns back into advice.

Proof points. Any number the expert gave, with its source marked as "SME interview, September 2026" and a note on whether it is a measured figure or an estimate. Writers inflate estimates into facts when nobody labels them.

Approved quotes. Two to four verbatim lines, lightly cleaned for filler words and nothing else. These go back to the expert for sign-off before the writer starts, so no one wastes a draft on a quote that gets pulled.

Do-not-soften list. Short and important. Name the claims the writer must keep as sharp as the expert stated them. Editors and writers both drift toward hedged language, and hedging an expert's strongest point is how an interview-backed article ends up sounding like everything else.

The rest of the brief works as usual, and the twelve fields of a good brief still apply. The interview fields sit on top of them.

Close the loop with the expert

Once the draft is edited, send the expert only the passages that quote or paraphrase them, marked up, with a forty-eight-hour window. Frame it as a fact check. The useful replies sound like "that number is wrong" or "I would never say it that way." If they try to rewrite the section anyway, keep the factual corrections and hold the line on voice. The review step belongs in the same approval workflow as every other sign-off, with a named owner and a deadline, so it cannot quietly stall publication for two weeks.

When it goes live, send them the link. It costs you nothing. Experts who see their words handled carefully say yes to the next request, and some start pitching you topics.

When no expert is available

Sometimes the person does not exist or will not answer. The same homework still pays off, just against different sources. Recorded sales calls are full of objections phrased in the customer's own words. Support tickets show exactly where people get stuck, sorted by frequency if your helpdesk exports tags. A single thirty-minute call with a customer can stand in for an internal expert on many topics, and customers tend to tell better failure stories than employees, since they have nothing to protect.

Every team now drafts with the same models, trained on the same ranking pages. What those models cannot produce is the thing your staff engineer said at minute seventeen about the batch jobs. Put it in the brief and protect it through the edit. Then you have a page competitors would have to hire your engineer to copy.