Getting an Expert to Write Comprehensibly
I once spent three weeks ghostwriting a technical manual for a renewable energy firm, only to realize I’d spent eighty percent of my billable hours acting as a glorified stenographer for a man who thought “clarity” was a suggestion rather than a requirement. Most gurus will tell you that the secret to a successful project is “leveraging deep domain knowledge,” but that’s just expensive industry shorthand for a nightmare. If you don’t have a system for how to work with subject experts, you aren’t an author or an editor; you are an unpaid administrative assistant drowning in jargon and missed deadlines.
I’m not here to give you a lecture on “synergy” or any other hollow corporate buzzword. Instead, I’m going to tell you exactly how to manage the ego, the acronyms, and the inevitable scheduling conflicts that turn a brilliant idea into a budget-breaking catastrophe. We are going to talk about setting boundaries that actually stick, how to extract the gold from a cluttered brain without losing your mind, and the specific questions that stop a project from bleeding money. This is about the unvarnished reality of the work.
Mastering Sme Interview Techniques Before the Budget Bleeds Out
If you walk into an interview with a physicist or a structural engineer expecting a tidy Q&A session, you are essentially volunteering to work unpaid overtime. Most people approach these meetings as if they are conducting a polite chat, but without refined SME interview techniques, you’ll spend forty minutes drowning in jargon before you’ve even secured a single usable sentence. You aren’t there to learn the science; you are there to translate it. Your job is to act as the filter, ensuring that the knowledge transfer processes actually result in something a reader can digest, rather than a transcript of technical minutiae that no one asked for.
To stop the budget from bleeding, you have to stop being a passive listener. Don’t wait for them to volunteer the “why” behind a concept; hunt for it. If they start spiraling into a lecture on subatomic particles, interrupt—politely, but firmly—and ask them to explain it to a client who is paying for results, not a PhD lecture. Bridging the gap between technical and non-technical teams isn’t about being a translator; it’s about being a gatekeeper who knows exactly when to stop the flow of information before it turns into a drain on your billable hours.
Effective Stakeholder Communication for the Non Technical Writer
The biggest mistake I see—and I’ve seen it cost more than a single month’s retainer—is the assumption that you can simply walk into a room, ask a question, and have a coherent narrative handed to you. It doesn’t work that way. You aren’t just a writer; you are a translator. Your job is bridging the gap between technical and non-technical teams, which is a much more exhausting role than the job description implies. If you approach an engineer or a surgeon as if they are your subordinates, they will shut down. If you approach them like a student, they will patronize you. You have to position yourself as the person who makes their expertise marketable.
This requires a very specific type of effective stakeholder communication. You aren’t looking for a lecture; you are looking for the “why” behind the “how.” When you are extracting information from experts, stop asking them to explain the mechanics and start asking them to explain the implications. If they can’t tell you why a specific data point matters to a layperson, that is a failure of the knowledge transfer process, not a failure of their intelligence. Keep your emails brief, your questions targeted, and always, always respect the clock.
Five Ways to Stop Your Subject Matter Experts from Sabotaging Your Project
- Stop asking “Can you explain this?” and start asking “How would you explain this to a client who is paying you five hundred pounds an hour?” If you give an expert an open field, they will wander into the weeds of minutiae for three hours, and you’ll be the one stuck trying to find the narrative thread at 2:00 AM.
- Respect the “Expert Tax.” When you budget for a project, you need to account for the fact that an SME’s time is rarely free, even if they are technically on your client’s payroll. If you haven’t built in a buffer for their inevitable “quick” follow-up emails or their refusal to look at a draft until the deadline is forty-eight hours away, your timeline is a fantasy.
- Send the “Skeleton Draft” early. Don’t wait until you have a polished, beautiful manuscript to show them. If you wait until the prose is tight, they will spend their energy critiquing your adjectives instead of the accuracy of your facts. Get the structure approved when it’s still ugly; it’s much cheaper to move a heading than to rewrite a chapter.
- Curate the chaos. An expert’s job is to know everything; your job is to decide what is actually worth saying. When they send you a fourteen-page technical appendix that was supposed to be a three-paragraph summary, don’t just swallow it. You have to be the gatekeeper of the reader’s attention, even if it means telling a PhD that their favorite niche data point is irrelevant to the book’s core argument.
- Use a “Feedback Sandbox.” Never send an SME a raw Word document and ask for “thoughts.” That is an invitation for them to rewrite your entire work in their own voice. Instead, give them a specific list of questions or a structured feedback form. Tell them exactly what you need: “Does this technical process hold up?” rather than “Is this okay?”
The Bottom Line: Avoiding the SME Sunk-Cost Fallacy
Stop treating interviews like open-ended chats; if you haven’t sent a specific list of questions forty-eight hours in advance, you aren’t interviewing, you’re just paying for someone’s expensive afternoon.
Respect the “Expert Gap” by translating their jargon into structural milestones—if you can’t explain their complex theory back to them in three simple sentences, you don’t actually have the material ready for a draft.
Protect your margin by setting hard boundaries on “clarification” emails; an expert who treats your inbox like a personal helpline will turn a fixed-fee project into a charity case before you’ve even hit your first milestone.
The SME Mirage
Stop treating your subject matter experts like human encyclopedias you can just query at your leisure; they are busy people with actual jobs, and if you don’t approach them with a structured brief and a respect for their billable hours, they will either give you nothing or, worse, give you everything they know in a forty-minute verbal sprawl that will cost you three days of transcription and a week of structural repair.
Cressida Farrow-Bassey
The Bottom Line on Expert Collaboration
At the end of the day, working with subject matter experts isn’t about being a genius or mastering a specific technical jargon; it is about managing the friction between their deep knowledge and your looming deadline. You have to go in with a rigid structure to prevent the budget from hemorrhaging, treat your stakeholders like partners rather than obstacles, and learn to translate high-level complexity into something a reader can actually digest. If you can master the art of the targeted interview and protect your billable hours from the “just one more detail” trap, you stop being a mere scribe and start becoming an essential part of the production process. It is the difference between chasing facts and actually synthesizing them.
Writing is rarely about waiting for the lightning bolt of inspiration to strike; more often, it is about the quiet, disciplined work of building bridges between different worlds of thought. It can be exhausting to sit in rooms where you feel like the least informed person present, but that is exactly where the most valuable work happens. Don’t let the intimidation of an expert’s intellect keep you from the page. If you approach these collaborations with a clear process and a firm grasp on your own value, you won’t just finish the project—you will produce something that actually matters. Now, go get that invoice sent.
