Skip to content
Content8 min read

Getting expertise out of busy experts

Every company we work with has the same untapped asset: two or three people who understand the problem better than anyone outside the building. Every company has also already tried getting them to write, and it has already failed.

Why the usual approach dies by month three

The standard plan is a content calendar with partner or engineer names next to dates. The first piece arrives late, the second arrives after two reminders, and by the third month the calendar is a source of friction that everyone quietly abandons.

This isn't a discipline failure. Writing well is a distinct skill from knowing something well, and the people with the deepest expertise are usually the ones with the highest opportunity cost for their time. Asking a partner billing at several hundred an hour to spend four hours drafting a blog post is a bad trade that they correctly decline.

The mistake is treating the bottleneck as motivation. It's throughput. Change what you're asking them for and the same people participate happily for years.

If your expert content programme depends on experts writing, it has a shelf life of about three months.

The interview, and what to actually ask

Forty-five minutes, recorded, with a writer who has read enough to ask a second question. The expert talks; nobody asks them to produce prose. That single change is what makes the programme survivable.

What separates a useful interview from a wasted one is the questions. Topic-level prompts — 'tell me about X' — produce the same generic material anyone could write. Specificity produces the material only they have.

  • Ask about a specific case

    "Walk me through the last time this went wrong." Concrete incidents carry detail, numbers and consequences that general explanation never does.

  • Ask what they disagree with

    "What does everyone in your field believe that you think is wrong?" This is the single most productive question we ask, and it produces the only genuinely differentiated content most companies have.

  • Ask what beginners get wrong

    Common mistakes are inherently useful to a reader and easy for an expert to list without preparation.

  • Ask for the number

    "Roughly how often does that happen?" Experts hold quantities in their heads that never make it into writing because nobody asked.

  • Follow the hesitation

    When someone says "well, it depends" and trails off, that is where the nuance is. Push there rather than moving on.

Turning it into something publishable

The writer's job is structure and clarity, not invention. Everything substantive should be traceable to something the expert said — if a draft contains a claim the transcript doesn't support, that's a defect rather than a flourish.

The most common failure at this stage is smoothing away the specificity that made the interview valuable. A writer unfamiliar with the domain will generalise an unusual detail into a safe statement because it reads more fluently. That safe statement is exactly what makes content indistinguishable from everyone else's.

Send the draft back with the timestamps for any claim you're unsure about. It makes review faster and it keeps the expert's confidence that they're not going to be misrepresented under their own name.

Review, and why the byline matters

The expert reviews for accuracy and by-lines the finished piece. Twenty minutes, typically, against the four hours drafting would have cost.

The byline is not a courtesy. In YMYL categories especially — health, finance, legal — content without demonstrable authorship struggles to rank at all, and a real named author with checkable credentials is the baseline rather than a nice-to-have. It's also what makes the expert care about accuracy, because their name is on it.

Keep the review scope narrow and say so explicitly: is anything here factually wrong or misleading? Not: would you have phrased it this way? Opening the door to stylistic rewriting reintroduces exactly the time cost the process exists to remove.

Making it survive

The programmes that last share a few operational habits, none of them complicated.

  • Batch the interviews

    Three or four in one afternoon each month is far easier to protect in a calendar than a recurring weekly slot that gets moved.

  • Never ask twice for the same thing

    If a detail was covered in a previous interview, find it in the archive rather than asking again. Experts disengage fast when their time feels wasted.

  • Show them what it produced

    Send the rankings, the traffic, the sales team using it in deals. Participation continues when people can see it mattered.

  • Keep one editor accountable

    A programme owned by everyone is owned by nobody. Someone has to chase the review and hold the publishing cadence.

We do this for a living

If you'd rather not build this yourself, these are the services where it lives.

Rather not DIY

We'll run this on your account.

A free 30-minute teardown of your funnel, ads, and analytics. You keep the findings whether or not we work together.