Skip to content
Knowledge retention

Involving Subject-Matter Experts Without Overloading Them: Six Objections and What Lies Behind Them

No time, no interest, worry about their own role: why experts hold back from knowledge capture and how to win them over without wrecking their calendar.

Sebastian Walker, CEO, Omnora · 4 min read
Illustration: a full weekly calendar with one short interview slot highlighted
Contents
  1. “I don’t have time for this”
  2. “It’s all in the manual anyway”
  3. “If I hand everything over, I’m no longer needed”
  4. “Nothing came of the last project either”
  5. “I’m not good at explaining things”
  6. “The works council has to sign this off first”
  7. Frequently asked questions

How do you involve subject-matter experts in knowledge capture without overloading them?

Experts can be involved when knowledge capture takes little time in one go and they do not have to write anything themselves. Short conversations with targeted follow-up questions replace long documentation assignments. Equally decisive are recognition rather than a chore and an honest answer to the worry that sharing makes them replaceable. Take these points seriously and even sceptical experts usually come on board.

Key takeaways

  1. Time in small pieces. Half an hour of conversation fits any calendar; a documentation project does not.
  2. Questions, not forms. Asking follow-up questions yields exceptions and reasons; sending templates yields standard procedures.
  3. Raise the role. Sharing knowledge has to pay off for the expert, otherwise it remains a risk for them.

Capturing expertise requires the people who have it, and they are exactly the ones with the least time. The objections below come up in almost every project, and none of them is made up.

“I don’t have time for this”

Almost always true. The most sought-after experts are also the most stretched, and that is no coincidence: people ask them precisely because they know.

The mistake usually lies in how the request is framed. An assignment like “Please document your processes by the end of the quarter” demands a block of time that does not exist in the calendar. It ends up on the list of things that come after day-to-day work. Which means never.

Half an hour, on the other hand, can be found. A conversation in which someone asks targeted questions takes the expert around 30 minutes and needs no preparation. Several such sessions spread over a few weeks fit even into full calendars.

“It’s all in the manual anyway”

Rarely. The manual usually describes the standard case, as it was conceived a few years ago. What makes experts genuinely irreplaceable are the deviations from it: the customer handled differently, the extra check nobody ever required.

To the experts themselves these parts often seem trivial. They have done it this way for years. So they do not mention it until someone asks about a specific case.

“If I hand everything over, I’m no longer needed”

The touchiest objection, and it is rarely voiced out loud. It deserves an honest answer rather than reassurance.

Yes, sharing knowledge reduces a certain kind of dependency. But it shifts the role instead of abolishing it. Someone whose knowledge has been captured is interrupted less by routine questions and has time for the cases that really need experience. At Omnora customers, questions to knowledge holders fell by 20 to 40 percent, measured by us rather than independently. And the person remains responsible for what was captured: they approve it and keep it current. That is a visible role, not a vanished one.

Why this so often hinges on one single person is covered in the article on single points of knowledge.

“Nothing came of the last project either”

Many experts have already sunk hours into a wiki or process documentation that nobody read afterwards. Their scepticism is experience, not stubbornness.

What helps is a visible result after a short time. When a new colleague no longer has to ask a question because the answer from the last conversation can be retrieved, the expert notices the difference themselves.

“I’m not good at explaining things”

No need to be. Explaining is a skill of its own, and many excellent practitioners have never needed it. The work lies in the asking, not the answering.

An AI-led interview takes on exactly that part: it follows up whenever an answer stays general and asks for examples where a rule sounds abstract. Omnora Intelligence Management turns the answers into structured knowledge that the expert then only has to check. How such a conversation runs is shown in the article on AI expert interviews.

“The works council has to sign this off first”

Often true, and better settled early than late. Experts are more sensitive on this point than one might think: nobody wants to feel that an interview might later be used for performance assessment. Across Europe, employee representatives have a say in many such cases, with rules that differ by country.

Transparency helps both sides. What is captured, what is not, who has access and what the result is used for should be clear before the first conversation takes place. The questions that typically come up are covered in the article on works councils and AI knowledge capture.

One last point that no objection mentions: the most convincing invitation to the first conversation rarely comes from HR or management.

It comes from the colleague who waited in vain for an answer last week.

AI interviews draw expertise out of your specialists' heads without anyone having to write: verified, approved and with a named owner.More on capturing knowledge

Frequently asked questions

How much time should knowledge capture ask of experts?

As little as possible in one go. Short conversations of around 30 minutes work better than half days. Several brief sessions spread over a few weeks yield more than one long workshop, because new cases come up in between.

Why don't experts simply document their knowledge themselves?

Because writing takes time that day-to-day work does not leave, and because experts rarely know what is not obvious to others. What they do every day seems too trivial to write down. Targeted questions from outside bring exactly those parts to light.

What if an expert does not want to share their knowledge?

Find out why first. Often it is the worry of becoming replaceable, or a bad experience with earlier documentation projects. It helps to raise the role visibly, for example as the named owner who approves captured knowledge and keeps it current.

Does the works council have to approve AI-led expert interviews?

That depends on the specific set-up and on national co-determination rules. It makes sense to involve employee representatives early and to be open about what is captured and what is not.

Sources

  1. Omnora: around 30 minutes of expert time per AI-led interview [Omnora experience value]
  2. Omnora: 20 to 40 percent fewer questions to knowledge holders, internal measurement from customer projects [Omnora experience value]

Capture the knowledge before it leaves.

An AI interview takes about 30 minutes and costs your experts not a single page of writing. Try it yourself or let us show you on your own case.