Skip to content
Zoevin

Automation problem

Knowledge sharing is everyone’s job. Why is it nobody’s priority?

People are asked to share what they know, while deadlines keep taking priority. Make contributions manageable, give people time, and recognize useful help.

Evidence reviewed through October 1, 2026

Problem

Useful knowledge keeps waiting for a quiet moment

“Could you put that in the knowledge base?” The employee agrees. They’ve just explained how to prepare the weekly activity report to a colleague. Writing it down sounds sensible. Then a customer needs a reply. Another report is due. The manager asks for something urgent. The instructions can wait until Friday. On Friday, they can wait until next week.

Consider a fictional business with 24 employees. It has a shared knowledge base, and the owner regularly encourages everyone to contribute. But people are judged on the work they finish today. Sharing what they know sits outside that work, waiting for a quiet moment. The employee is already helping colleagues. Turning that help into something others can use takes additional effort.

That matters because the next person preparing the report may need the same explanation. The experienced employee gets another interruption. The newer colleague waits, asks around, or tries to work it out alone. Knowledge management gives useful experience a way to reach the people who need it. For that to happen, sharing needs a place in the working day.

Examples

Give sharing a place in the working day

“Make time when you can” leaves the employee to decide which deadline to risk. A manager can make the choice explicit. Which knowledge is worth capturing? Who needs it? How much time can the contributor spend? What other work can move?

In the fictional business, the manager could choose one recurring task: preparing the weekly report. The person learning it drafts the instructions during the walkthrough. The experienced colleague gets a scheduled window to check them. Both people have a defined contribution. Their manager accounts for it when assigning work.

APQC’s guidance on knowledge-management engagement identifies workload, misaligned measures, and lack of trust as barriers to sharing. It also recommends making participation easier for busy experts. A protected window is a starting point. If it keeps getting cancelled, the manager needs to adjust the workload or narrow the task.

Solutions

Make the contribution small enough to finish

“Document everything you know about reporting” is a large, uncertain assignment. “Help the next person prepare this report” gives the contributor a clear purpose.

Start with one useful entry

A short entry could cover:

  • The question or task it helps with.
  • What the person needs before starting.
  • The steps and the expected result.
  • When to ask someone for help.

Build on a real walkthrough

Use the words colleagues use when asking the question. Include a link to the relevant company resource. Have the learner note anything that needed an extra explanation.

The Knowledge-Centered Service approach encourages capturing knowledge during work and improving it through reuse. Applied here, the report walkthrough supplies the first draft. The next person using it can identify what is still unclear.

A useful contribution might also be a correction, a worked example, or a better link in an existing entry. The business needs a simple way to make those contributions without creating another full writing assignment. For the report example, the draft is ready for review when it explains the task well enough for someone else to try it. The experienced colleague checks the steps and limits. The learner handles the initial writing.

Make questions and corrections safe

An employee opens the instructions and cannot find the report’s date range. Do they ask where to find it, or worry that the question will make them look unprepared? Someone else notices that an important step is missing. Do they flag it, or worry that correcting a senior colleague will cause trouble?

These moments affect what reaches the shared knowledge base. APQC’s discussion of knowledge-management culture connects knowledge sharing with trust and people’s willingness to admit what they do not know. Managers can support that trust through ordinary responses. Thank the person who spotted the gap. Ask the author to help clarify it. Explain where a question should go when the instructions do not cover the situation.

Leaders can participate too. Asking a question, acknowledging an uncertainty, and improving an entry shows employees how to contribute. The employee who asks for clarification may have found the exact gap that would stop the next person.

Recognize the help people actually use

An article target is easy to count. It can also encourage people to produce entries simply to meet the target. APQC’s guidance on rewards and recognition warns that poorly aligned rewards can fail to motivate participation, while overly strong incentives can encourage unhealthy competition.

Recognition can be specific: “Your example helped someone prepare the report without repeating the walkthrough.” Credit the person who wrote it and the colleague who checked it. Recognize a useful correction as well as a new entry.

Then check whether the effort is helping:

  • Could someone use the instructions to complete the task?
  • What still required an explanation?
  • How much time did drafting and review take?
  • Was the contribution manageable alongside other work?

Use the feedback to adjust the work

Those answers give the manager a reason to continue, simplify, or change the approach. They also give contributors feedback about why their work mattered.

Use automation to make the contribution easier

Once the contribution has a clear purpose, automation could help with preparation. For the reporting example, a workflow could offer a short template when a walkthrough is completed, attach the relevant company links, and send the draft to the person responsible for checking it.

An AI tool could turn contributor-supplied notes into a draft. The author still needs to check the explanation and remove details that should not be shared. The next step should remain visible: draft prepared, review needed, or ready for colleagues to use.

How Zoevin helps

Start with one recurring question

Start with one recurring question. Give people time to capture the answer, try it with someone who needs it, and ask whether the effort was worthwhile.

At Zoevin, I build scoped automations in a business’s own environment and hand them over on an agreed date.

If preparing and reviewing useful knowledge keeps falling between other tasks, bring one example. We can look at where an automation could make that contribution easier for the people involved.

  • Follow one contribution from a recurring question to reviewed guidance.
  • Identify preparation that automation could make easier for the people involved.

Zoevin has no delivered automation projects yet. Discovery names the seam. If I build, I hand it over on a written date. You get the workflow, the logins, and the write-up. I don't stay on to run it. You buy the software.

Talk through a knowledge-sharing task

Evidence

Sources

Primary reporting first. Open the sources yourself rather than taking this account alone.

  1. primary source

    APQC — Knowledge Management Engagement and Culture FAQ

    June 11, 2026 practitioner guidance on workload, participation, leadership, trust, and support for busy experts. The 24-person business and reporting walkthrough are fictional teaching examples, not client results or measured outcomes.

  2. primary source

    Consortium for Service Innovation — Create Value

    Methodology guidance on capturing knowledge during work, reusing collective experience, and improving knowledge through use. The reporting example is an editorial adaptation, not a documented implementation or guaranteed reduction in effort.

  3. primary source

    APQC — What is Knowledge Management Culture?

    June 11, 2025 guidance connecting knowledge sharing with trust, psychological safety, and willingness to ask questions. Suggested manager responses are illustrative practices, not claims of measured business results.

  4. primary source

    APQC — Rewards and Recognition for Knowledge Management

    January 3, 2025 public collection introduction on participation, misaligned rewards, and unhealthy competition. No claims are drawn from gated reports. The suggested feedback questions and automation are editorial proposals.

Related reading