Published by TrueFuture Media
An engineer can explain a product for an hour and still leave an editor without a useful opening. The missing piece is often the buyer's question. Before recording, decide what someone needs to understand, which evidence can support the answer, and what the camera needs to capture. That preparation gives the expert a clear job and gives the editor material they can use responsibly.
To interview a product expert for social video, start with a specific buying decision and prepare a short evidence brief. Name the audience, the question they need answered, the product version, and the documents or demonstrations available. Share topics in advance, then ask open questions that bring out explanations, examples, and limits. Record a clear answer before asking for a shorter version. Capture the visual evidence separately when a webcam can't show it well. Afterward, give the editor the source recording, an answer log, approved supporting assets, and the conditions that must stay with each claim. Have the right subject-matter reviewer check the finished edit, including captions and on-screen wording. The interview is ready for production when the team can trace each useful answer back to its evidence.
For a buyer choosing an industrial component or home system, a confident speaker is only part of the answer. They may need to see which model a statement covers or why a familiar installation detail changes the recommendation. An interview brief can bring those questions into the recording before the editor has to chase them. TrueFuture's Social Demand Loop explains how that product knowledge connects to buyer relevance, visible proof, and a useful next step.
Which buyer question should the interview answer?
Choose a question that changes a real decision. “Tell us about the product” leaves the expert to guess how much background the audience needs. “What should a buyer check before replacing this component?” gives the conversation a task. You can still explain the product, but the explanation now has a reason to exist.
Start with questions found in sales conversations, support tickets, site searches, or approved customer research. Remove personal details before putting them in the brief. Keep the customer's wording where it helps the expert hear the uncertainty. If the question is only a marketing team's hypothesis, label it that way and check it with people who speak to buyers.
Google's people-first content guidance asks whether someone will learn enough to help achieve their goal. Apply that test to the planned video: what should the viewer be able to understand or do afterward? Recording an employee doesn't by itself establish that the content answers the question.
Choose the person who can explain the decision
The most senior person isn't always the best interviewee. A product specialist may explain model differences, while a service technician can identify the information needed before recommending a replacement. Match the question to the person's knowledge and approved remit. Bring in a second reviewer when the answer crosses those boundaries.
Write down what the session will leave unresolved. A short explanation of a selection factor may help a buyer prepare for a consultation without settling the entire specification. That boundary protects the usefulness of the video: viewers can see what they've learned and what still needs an individual review.
What should you send the expert before recording?
Send a brief they can review without becoming a copywriter. Include the buyer's situation, the intended use of the recording, and the evidence you want to discuss. Ask them to flag errors, missing conditions, and material they can't share. A draft script can be useful for tightly controlled statements, but it shouldn't hide unanswered factual questions.
The GOV.UK interview guide recommends planning topics, starter questions, and possible follow-ups, then testing the guide with a colleague. Its context is user research. The preparation principle also suits an expert recording: the interviewer should know where the conversation needs to go while leaving room for an unexpected explanation.
| Field | What to include | What it prevents |
|---|---|---|
| Buyer and decision | Who is choosing what, and which uncertainty this video addresses. | A general company introduction replacing the answer. |
| Product scope | Model, version, intended use, and relevant conditions. | A statement about one configuration sounding universal. |
| Evidence | Current document, approved demonstration, or other supporting source. | A confident answer reaching the edit without support. |
| Visual capture | The object, action, or document the viewer needs to inspect. | The editor filling an evidence gap with unrelated footage. |
| Review owner | Who checks technical accuracy and who approves publication. | A finished video waiting for an unnamed approver. |
Separate knowledge from permission to publish
An expert may know something that isn't public, or refer to a customer example the company can't use. Confirm the intended channels, whether paid use is planned, and who has authority to approve the material. Ask for cleared documents and assets rather than assuming anything shown during a call can appear in the final video.
The FTC's advertising substantiation policy requires a reasonable basis for objective advertising claims before they are distributed. An interviewer's practical response is to request the source behind a claim while planning the session. The level of evidence needed depends on the claim; a speaker's confidence doesn't settle it.
Mark missing evidence openly in the brief. You can record a useful explanation of the selection process while holding an unsupported performance claim out of the production plan. If the central answer depends on a document nobody can locate, resolve that gap before building the campaign around it.
Which questions produce useful explanations?
Ask about the reasoning behind a recommendation. “Why is this better?” invites a broad claim and puts the conclusion in the question. “Which conditions would lead you to recommend this option?” lets the expert explain the decision and its limits. Follow with a request for the evidence they use.
GOV.UK advises interviewers to use “open, neutral questions” and pursue real examples. For a product interview, that means giving the expert room to correct the premise. If the answer is “it depends,” ask what it depends on. The qualification may be the most useful part of the recording.
A question sequence to adapt
- What information do you need before you can answer this buyer's question?
- How does that information change your recommendation?
- Can you show the relevant part of the product or source document?
- When would this explanation no longer apply?
- What should the buyer check or ask next?
This is a discussion guide. Change the order when an answer reveals a more useful route through the subject.
Get the full explanation before the short take
Let the expert finish the reasoning once. Then summarize what you heard and ask them to correct it. Only after that should you request a concise take. Starting with a strict sound-bite limit can remove the condition that makes an answer accurate.
Listen for words that carry several possible meanings. “Efficient” might refer to energy use, installation time, or a step in a production process. Ask which meaning applies and how it is supported. Keep the unit, comparison basis, or test condition if it changes what a buyer should conclude.
A useful follow-up also identifies what the camera can show. If the expert says a maintenance task is straightforward, ask which steps they mean and whether the company has an approved demonstration. Don't manufacture a demonstration during the interview when safe handling, training, or controlled conditions are required.
Worked example: explaining a replacement filter
This hypothetical example concerns interview planning, not instructions for a real product.
A marketing team wants a video saying a filter is easy to replace. Before recording, the interviewer asks the product specialist which model the statement covers, who should perform the task, and where the approved procedure is documented. The specialist's answers determine whether the video can show a user task or should explain when to contact a qualified service provider.
The recording plan then names the approved source and the view needed to explain the access point. Any required safety conditions stay with the explanation. If the team can't verify the procedure, the editor receives no instruction to create a how-to sequence from general footage.
What needs to be captured during the session?
Capture clear speech and enough context to understand it. Run a short test with the actual recording setup and play it back. Check for distracting noise, clipped words, a dark face, and framing that leaves no room for the intended crop. A test catches problems while the expert is still available to fix them.
W3C's audio and video production guidance recommends good recording equipment, reduced background noise, clear speech, and explanations of unfamiliar terms. It also advises planning how essential visual information will be described. These choices belong in the recording plan, before captions and final graphics are produced.
Give evidence its own shot
A webcam may be adequate for an explanation and poor for showing a small label or part. Record a separate close view when the viewer needs to inspect that detail. Keep the model and version consistent with the answer. A clean shot of a different product can look convincing while supporting nothing the speaker said.
When an expert points at a document, capture a readable copy through an approved workflow. Ask them to name the relevant section aloud. That gives the editor a way to match the explanation to the correct material, and it helps the audience follow the answer when the visual is difficult to see.
Leave a pause between answers and identify retakes clearly. If the expert corrects an earlier statement, mark the correction in the session notes. The editor shouldn't have to guess whether two different answers represent alternatives or an error.
Plan accessibility responsibilities at the same time. W3C's media planning guidance includes captions, description, transcripts, and responsibilities in the production workflow. TrueFuture's accessible product demo guide explains how those choices help preserve evidence through the finished video.
How do you turn the recording into an edit brief?
Create an answer log while the session is fresh. For each candidate video, record the buyer question, the useful passage, its supporting asset, and any condition that must stay attached. Include timestamps from the actual recording. A transcript can help locate material, but check names, numbers, and technical terms against the audio.
Use the log to decide what is ready. An engaging answer with missing evidence belongs in a follow-up list. A clear answer with verified support can become an edit. Keeping those statuses separate stops an editor from treating every confident sentence as approved copy.
Write an edit instruction the editor can act on
“Make this feel credible” leaves too much open. A usable instruction identifies the answer, the approved supporting view, and the qualification that must remain. It also names the missing shot or review if the segment isn't ready. The editor can then solve a production problem without having to make a technical judgment.
Keep the original recording available to authorized reviewers. If a shorter version changes the sequence of the explanation, review whether the meaning survives. On-screen headings can make a stronger claim than the spoken words, so include them in the same check.
Give each video a suitable destination. A clip that introduces a compatibility question might lead to a maintained product guide or a genuine assessment process. The social landing page guide shows how to carry that question into the page and next step.
What should be approved before the video goes live?
Review the finished video as a buyer will encounter it. Include the cover text, captions, post copy, and linked destination. A technically accurate interview can become misleading if the headline removes a condition or the visuals suggest a result the speaker never claimed.
Release checklist
- The buyer question is clear without the interviewer's original prompt.
- Product names, versions, numbers, and technical terms match the checked sources.
- Supporting visuals show the correct product and approved material.
- Conditions that change the answer remain easy to notice.
- Recording, asset, and publication permissions cover the intended use.
- Captions and any necessary visual descriptions have been checked.
- The destination delivers the promised information or next step.
- The named technical reviewer and publication approver have completed their checks.
If a reviewer finds an error, record what changed and why. Use the correction to improve the next brief. Repeated confusion over a term may call for a clearer opening question. A recurring missing shot may need to become a standard item on the recording plan.
After publication, collect the questions viewers still ask. Keep those separate from assumptions based on view counts. A video can attract attention without resolving the intended buying question. The next interview should respond to what the team has learned, with new evidence when the question requires it.
Key takeaways
- Choose a buyer decision before writing interview questions.
- Give the expert the product scope, available evidence, and review expectations in advance.
- Ask for the full reasoning before requesting a shorter take.
- Capture supporting details separately when the interview camera can't show them clearly.
- Send the editor an answer log with sources and conditions attached.
- Review the final video and its surrounding copy together.
Frequently asked questions
Should a product expert memorize a script?
Usually a topic guide leaves more room for a clear explanation. Use approved wording where precision requires it. Check the facts before asking the expert to rehearse a short version.
How many videos should one interview produce?
The usable number depends on the questions answered, available evidence, footage, and review capacity. Plan around distinct supported answers. Don't divide one answer into extra clips if that removes necessary context.
Can the expert's explanation count as evidence?
It can explain the reasoning, but objective product claims still need appropriate support. Record the source behind the statement and have the qualified reviewer confirm what the evidence establishes.
What if the expert doesn't know the answer?
Mark it for follow-up and identify who or what source can resolve it. Keep that segment out of publication until the answer is verified, or narrow the video to the part the team can support.
Prepare the material your editor will need
Before booking the next recording, write one buyer question and name the evidence that can answer it. Send both to the expert. If the source is missing or the scope is unclear, you have a specific issue to resolve while there's still time to prepare.
If your team has product knowledge but struggles to turn it into useful social videos, a Fit Review can help establish the support needed. Bring a sample buyer question, your available product material, and the people who can provide technical review and publication approval.
Request a Fit ReviewSources
- Google Search Central: creating helpful, reliable, people-first content.
- GOV.UK Service Manual: using in-depth interviews. User-research guidance applied here to interview preparation.
- FTC policy statement regarding advertising substantiation.
- W3C WAI: audio content and video content.
- W3C WAI: planning audio and video media.
Media credits
Notebook photograph: Kelly Sikkema on Unsplash. Microphone photograph: Amr Taha on Unsplash. Used under the Unsplash License. Stock photographs do not depict client work. Answer-log diagram: TrueFuture Media, qualitative illustration.