Writers are often told to “hop on a quick call with the product person.” Thirty minutes later they have warmth, jargon, and almost nothing they can cite. The fix is not a longer call. It is a better brief for the interview itself: what the piece must prove, which gaps the SERP leaves open, and which questions will extract examples instead of abstractions. Pair this with a solid content brief and you stop treating SME time as optional colour.
Decide what the interview must produce
Before you book the meeting, write three outcomes on a page. Example: two concrete customer objections with how the product answers them; one walkthrough of a workflow competitors describe badly; three claims we must not make. If you cannot name outcomes, you are not ready to spend expert time.
Share those outcomes with the SME in advance. Experts prepare better when they know the job. Surprise interviews get polite generalities.
Prep materials worth sending ahead
- Draft outline or section list for the piece
- Top ranking pages and the gaps you intend to cover
- Questions grouped by theme, not a random laundry list
- Any claims legal or compliance already flagged
- Permission note for recording and attribution
If the SME has never done this, tell them you want stories and specifics: numbers they can stand behind, screens they can describe, mistakes customers make. Abstract vision statements are usually useless in a draft.
Question design that pulls examples
Swap “How does the product work?” for “Walk me through what happens when a new admin sets this up for a 50-person team.” Swap “What makes you different?” for “What do buyers believe that is wrong, and how do you correct it without insulting them?” Concrete prompts produce concrete answers.
Leave room for follow-ups. The gold is often in the second question: “Can you give an example without naming the customer?” or “What did you try that failed?” First-hand experience shows up in those details, which is what E-E-A-T-minded pages need.
| Question type | Example prompt | Usable output |
|---|---|---|
| Process | Walk me through X step by step | Outline sections, screenshots notes |
| Objection | What do prospects push back on? | FAQ and landing page blocks |
| Mistake | Where do users get stuck? | How-to warnings, support angles |
| Comparison | Where do alternatives win? | Honest comparison material |
| Boundary | What should we never claim? | Compliance and voice rules |
Run the call like an editor, not a fan
Start with permission to record. Confirm attribution preferences: named quote, anonymized, or background only. Keep the outline visible. When the expert drifts into roadmap fantasy, steer back: “For this article we can only use what exists in production today.”
Silence is a tool. After a short answer, wait. Experts often fill the pause with the example you needed. Interrupt jargon gently: “If I said that on the page, would a first-week user understand it?”
Turn the recording into draft fuel
Same day, pull a structured note: claims, examples, quotes, open questions, banned statements. Map each item to an outline section. Do not paste the transcript into the brief and call it done. Writers drown in transcripts. They ship from curated notes.
Flag anything that needs legal or founder approval before it hits a public URL. Regulated topics in health, finance, and legal need a qualified reviewer; the interview is an input, not a green light. Our SEO content writing process assumes that gate exists when the subject requires it.
When you only half understand the subject
You can still run a useful interview. Admit the limits. Ask the expert to correct your outline live. Bring a junior question list without pretending expertise you lack. More on that posture in how to brief a writer who does not know your product.
Common failure modes
- No agenda sent ahead, so the expert freestyles
- Recording lost, notes never written
- Quotes used without approval
- Interview scheduled after the draft is “done”
- Too many stakeholders on the call, nobody goes deep
Fix the operating rhythm: interview before draft, notes within 24 hours, approval loop for named quotes, one primary interviewer. Add a second person only for regulated review, not for spectator seats.
How this changes the published piece
Pages built from SME material sound different. They name constraints. They describe failure modes. They avoid the floating advice that could sit on any competitor blog. That difference is information gain, which is what search and generative engines increasingly reward when they choose what to cite.
It also reduces revision pain. When the expert already validated the angle, the first draft misses less. Feedback becomes precision edits instead of “this does not sound like us,” which often means “this does not sound like anyone who has used the product.”
Remote interviews and async follow-up
Remote calls work when agendas are tight and recordings are shared promptly. Send the writer the summary, not the raw audio, unless they request specific timestamps for quote verification.
Async follow-up should be limited to factual gaps, not new outline sections. If the interview reveals the brief was wrong, fix the brief and schedule a short second call rather than stretching email threads for a week.
For global SMEs, offer two time slots and a written fallback questionnaire. Partial written answers beat a cancelled call when deadlines are fixed. Respect declines; forcing experts into bad calls burns access for the whole programme.
Building an SME interview library
Archive curated notes by product area, not only by post. When a refresh arrives six months later, the writer starts from validated facts instead of rebooking the same expert for baseline questions.
Tag notes with approval status and expiry for time-sensitive claims. Pricing, integrations, and regulatory statements age faster than thought leadership anecdotes.
Writers should receive the library link in the brief, not hunt for notes after the draft is due. One link beats three forgotten Drive folders.
Start executive quote approval the same day as the interview when attribution is named on the page. Late approvals force writers to guess or delay publish.