Why expert knowledge needs an interview, not a request for a draft
The usual way to get an expert into a piece is to ask them to "write something". It fails in predictable ways. Experts write for their peers, so they skip the steps that are obvious to them and are exactly what a newcomer needs. They lead with background and arrive at the answer late. Writing is not their job, so the draft slips behind work that is, and when it arrives the editor faces a choice between publishing something hard to read and rewriting it so heavily that the expert no longer recognises it.
The material is still worth the effort. Google's guidance on creating helpful, reliable, people-first content asks whether a page provides original information, research or analysis and shows first-hand experience, as the AI content troubleshooting page and the E-E-A-T guide set out. In most organisations that material sits in a few people's heads: the engineer who has seen the failure, the adviser who knows which option suits which client, the installer who remembers the job that went wrong. The qualities summarised as E-E-A-TExperience, Expertise, Authoritativeness, Trust. come from those people or not at all.
An interview moves the work to the person whose job it is. The expert talks, which takes a fraction of the effort of writing, and the writer does the structuring, drafting and editing. The table compares the common ways teams try to capture expert knowledge.
| Approach | What the expert does | What comes back | The usual problem |
|---|---|---|---|
| Ask the expert for a draft | Writes from nothing, around other work | A piece in the expert's order, often late | Written for peers, with the answer buried |
| Send questions by email | Answers in writing | Short, careful answers | No follow-up, so few cases and fewer reasons |
| Writer researches alone | Nothing | A summary of what is already published | No first-hand material at all |
| Prepared interview | Talks through cases, decisions and mistakes | A transcript full of specifics | Needs drafting skill and a substance check |
Two neighbouring methods are different jobs. A research interview with customers, covered in the customer interviews tutorial, learns how people made a decision so the business can act on it; the customer is a source of insight, not the author. And a programme of expert-led content for business buyers, with a cadence and a role for each expert, is covered under experts as authors in the business-to-business content guide. This tutorial is the unit both depend on: one interview that turns one expert's knowledge into one publishable piece.
Before you start
- An approved brief. The interview serves a piece that already has a question, a reader, an angle and a proof list, written with the content brief tutorial. The proof list is where the expert first appears, as the source for the claims nobody else can make. Without a brief the interview wanders, and the transcript holds several half-pieces instead of one.
- An expert with first-hand experience of the question. Not necessarily the most senior person; the right one has done the thing the reader is trying to do, recently and often.
- Time agreed with the expert's manager. Experts are usually busy with work that earns money. Agreeing the time with whoever sets their priorities stops the interview being the first thing cancelled.
- A recording and transcription tool your organisation already approves, and its rules for storing recordings and transcripts. If there are no rules, ask whoever handles data in the organisation before the first call.
- A byline policy. Who is named as the author of a piece drafted from an interview, how the writer is credited, and who signs off. The AI-assisted content guide sets the accountability rule this tutorial follows.
The steps
Each step produces something the next one uses: the question shapes the reading, the reading shapes the questions, the questions shape the call, and the marked transcript becomes the draft. The first four happen before anyone speaks to the expert, which is where most of the quality is decided.
Choose the expert and the one question
Start from the brief's question, written in the reader's words, and the Search IntentThe goal behind a search query: to learn, to find a site, to compare or to act. it records: whether the reader wants a method, a comparison, a decision or a definition. Then pick the person who answers that question in their work. A support lead who handles the problem every week often makes a better interviewee than the director who designed the policy, because the support lead knows how the problem actually arrives and which explanations land. One question per interview. If the brief really holds two questions, plan two conversations, or go back to the briefer and split the piece. Write the question at the top of your preparation notes, with a line describing the reader as the Buyer PersonaA research-based profile of a typical customer type: goals, problems and buying behaviour. in the brief describes them, so that every later question can be checked against both.
Read what the expert has already said
Before writing a single question, collect what the expert has already put on record: internal documents, training material, support macros, conference talks, previous articles, answers in the team's chat, and anything they post under their own name on professional networks, which the personal branding guide treats as a channel in its own right. Note what they have said publicly, so the piece is consistent with it and the call is not spent repeating it. Note the gaps, the places where they assert something without saying why, and anything that contradicts the brief. Then read the obvious existing pages on the question, inside and outside the organisation. The interview's job is to get what those pages lack, and you can only ask for it if you know what they already say.
Write questions that ask for cases, decisions and mistakes
General questions produce general answers. "What are the best practices for this?" invites the expert to recite what everyone already says. Ask instead for the material only they hold. For cases: "Tell me about the last time a customer came to you with this problem. What had they tried?" For decisions: "When you have to choose between these two approaches, what decides it?" For mistakes: "What do you see people get wrong, and what happens when they do?" For method: "If you sat next to the reader, what would you check first?" For numbers: "Which figure do you look at, and where does it come from?" Ask only for numbers the expert can point to a record for, because a figure from memory has to be checked or cut later. Keep the list short enough to leave most of the call for follow-ups, order it as the reader would ask, and send it to the expert in advance with the brief's question at the top.
Agree the recording, the time and the byline before the call
Ask the expert whether you may record the call, and say why: so that quotes are accurate and the draft reflects what they said rather than your notes. Say who will hear the recording, where it and the transcript will be kept and when they will be deleted, following your organisation's own data rules; the consent practice in the customer interviews tutorial is a good model for how to explain it. If the expert declines, take notes and read back anything you intend to quote before the call ends. Confirm the length of the call and protect it in both calendars. Then settle the byline now, not after the draft: whose name the piece will carry, how the writer will be credited, and the fact that the expert will review the draft before it goes out. An expert who knows the piece will appear under their name, and only after they have checked it, prepares better and answers more carefully.
Open with the reader's problem
Do not open with "tell me about your role". Open with the reader: describe who they are and the situation they are in, then read the question aloud the way they would ask it. Ask the expert how they would answer that person if they walked in today. This puts the expert into explaining mode for a newcomer rather than presenting mode for peers, and the words they use for a newcomer are often the words the piece needs. Listen for the analogies, the warnings and the order in which they explain things, and note the moments where they slow down or simplify, because those are the places a reader is likely to struggle.
Follow every specific with why and how
The prepared questions get the conversation started; the follow-ups get the material. When the expert says something specific, such as "we always check the drainage first", ask why. When they answer, ask why again. The habit is borrowed from the five whys, which keeps asking until it reaches a cause; here it keeps asking until it reaches the reasoning a reader could apply to their own case. Then ask how: what exactly do you look at, what does good look like, what does bad look like. When the answer is "it depends", ask on what. When the answer is a rule, ask for the case that taught them the rule. Leave silences; experts often add the most useful detail after a pause. Do not fill gaps with your own assumptions, and do not argue. If something sounds wrong, ask how they know, and mark it for checking.
Close by checking facts, figures and permissions
Reserve the end of the call for checking. Read back the main points in a sentence each and ask whether you have them right. List every figure, name, product and document the expert mentioned and ask where each comes from; mark anything from memory so it is checked against the record before it appears in the draft. Ask whether each customer, job or colleague mentioned may be named or must be described without identifying details, and whether anything they said was not for publication. Ask for anything that would make the piece more concrete: a photograph, a diagram they drew, a redacted job sheet. If they mentioned another specialist whose view the piece needs, ask who should approach that person. Finish by saying when the draft will arrive and what you will ask them to check.
Draft from the transcript in the reader's order
A conversation moves in the order the expert remembered things; a reader needs the order that answers the question. Mark up the transcript first: the answer, the steps of the method, each case, each mistake, each caveat, each quotable line. Then build the outline from the brief and fill each section from the marked passages, putting the answer first, the supporting method and cases next and the background last, which is the inverted pyramid order. Keep the expert's own phrasing where it is clear, translate jargon where it is not, and apply the editing routine in the writing for the web guide. If you use an AI tool to produce a first draft from the transcript, the AI-assisted content guide records that Google's guidance on AI-generated content rewards helpful content however it is produced; the same guide sets the conditions, and they apply in full. Every claim in the draft must match the transcript or a source, and no sentence may appear in quotation marks that the expert did not say.
Send the draft back for a substance check, not a rewrite
Send the draft with specific questions rather than "any thoughts?". Is anything wrong? Is anything missing that would lead a reader to a mistake? Is every direct quotation something you said and are happy to see printed? Would you stand behind every sentence under your name? Say plainly that the expert owns the substance and the editor owns the structure, the length and the house style, so corrections of fact are accepted without argument and changes of tone are discussed against the brief. Give a date for the review. If the draft comes back rewritten in the expert's academic or technical register, accept every factual correction, then explain which changes would lose the reader and agree a version together. A second short call is often faster than a third round of comments.
Publish with the agreed byline and keep the transcript
Publish under the byline agreed before the call, with an author description that states the experience behind the piece, and link it to the author's page if the site has one; the E-E-A-T guide lists named authors with specific biographies among the practices that help readers see who wrote a page and why they are qualified. Credit the writer as the house policy says. File the transcript and the recording with the brief and the published piece, under the data rules agreed in step four. They are the source for corrections, for the next refresh and for derivatives: the repurposing guide builds short pieces, clips and posts from material like this, within the permissions agreed. Send the expert the link, and later tell them what the piece did. Experts who see their knowledge read are easier to interview the second time.
Bylines, ghostwriting and quotes
The AI-assisted content guide treats a byline as more than a formality. It is the answer to the question Google's helpful content guidance suggests publishers think about, who created the content, how and why, and to a reader's reasonable expectation that someone stands behind the words. The same guide sets a plain rule: no piece goes out under a name that did not review it. For a piece drafted from an interview, that settles most questions. The named author is the person who supplied the substance and approved the final text. The writer is credited as the organisation's policy says, whether that is an editor credit, an "interview by" line or no public credit at all, and the policy is applied the same way to every piece.
Ghostwriting in this sense, a writer drafting under an expert's name from the expert's own knowledge, is common and honest when the substance is the expert's and the expert has approved it. It stops being honest when the expert never read the piece, when the byline claims experience the named person does not have, or when a junior writer's opinions appear under a senior name. The AI troubleshooting page lists adding an expert's name to pages the expert never read among the habits that fail.
Quotations need more care than the surrounding text. An expert's direct quotes come from the transcript, tidied only for false starts and filler words, and are confirmed in the substance check. A quote from anyone outside the organisation, such as a supplier's engineer, a researcher or a customer, needs that person's permission and their exact words. The guide to AI claims and consumer protection warns that a polished quote, or a composite assembled from several people's comments, presents words nobody said. That is true whether a tool or a person did the polishing. When the person interviewed is a customer rather than a colleague, the piece becomes a customer story, with written permission and the customer's approval of the final wording, and the customer case study tutorial takes that process step by step.
| Situation | Byline | Writer's credit | What must be true before publishing |
|---|---|---|---|
| Expert supplied the substance, writer drafted, expert approved | The expert | As the house policy sets, often an editor credit | The expert reviewed the final draft |
| Writer researched and drafted, expert checked accuracy | The writer | The expert credited as reviewer | The expert checked every claim in their field |
| Several experts interviewed for one piece | The writer, or the lead expert if they shaped it | Other experts quoted by name | Each quotation confirmed by the person who said it |
| Expert cannot review before the deadline | Not the expert | Not applicable | Hold the piece, or publish under the writer with claims sourced |
| Outside specialist quoted | Unchanged | Unchanged | Their permission and their exact words, on record |
Whether readers should be told how a piece was produced, including any AI assistance in drafting, is a disclosure decision. The AI-assisted content guide covers the policy; whatever it says, it belongs in the organisation's editorial standards and applies to interview-based pieces like any other.
A surveyor's interview becomes a guide (illustrative)
Hearthpip Insulation turns a surveyor's interview into a guide
Hearthpip Insulation, an invented loft and wall insulation installer, has a brief for a guide answering "why is there condensation in my loft since it was insulated?", a question its office takes several times a month. The writer picks the senior surveyor, who has inspected 40 of these call-backs, rather than the operations director. She reads the surveyor's site notes and the office's standard email reply, then sends seven questions two days before a 50-minute recorded call, with the byline agreed in advance: the surveyor as author, the writer credited as editor. The call surfaces three real jobs, each with a different cause, and one mistake the team stopped making years ago: packing insulation so tightly at the eaves that it blocked the roof's ventilation. Each "why" turns a rule into a check a homeowner can make with a torch. At the close, the surveyor confirms that two of the three households may be described by house type only. The writer drafts answer-first, with the three checks, the cases and then the background. The draft goes back with four questions; the surveyor corrects one figure from a job sheet and rewrites nothing else. The guide is published under the surveyor's name 12 days after the call, with the transcript filed alongside the brief.
Common mistakes
- Asking for a draft instead of an interview. The expert writes for peers, late, and the editor rewrites it until the expert no longer recognises it.
- Interviewing the most senior person. Seniority is not first-hand experience. Choose the person who does the work the reader is trying to do.
- Generic questions. "What are the best practices?" produces what every other page already says. Ask for cases, decisions and mistakes.
- No follow-up. The first answer is the summary; the material is in the second and third why.
- Recording without asking, or not recording at all. The first damages trust; the second produces paraphrased quotes the expert never quite said.
- Drafting in the order of the conversation. The reader gets the expert's memory, not the answer. Put the answer first.
- Letting the substance check become a rewrite. Agree before the call who owns the substance and who owns the structure.
- A byline the expert never earned. No piece goes out under a name that did not review it.
- Polishing quotations. Tidied or merged quotes are words nobody said. Keep them as spoken, confirmed by the speaker.
- Losing the transcript. It is the source for every correction and refresh; file it with the brief.
