Turn answered questions into help articles

Every support team has a set of questions it answers repeatedly and has never written down. The reason is not laziness. It is that the moment you have the answer is the moment you are busy giving it, and writing it up properly is a separate job that never becomes urgent.

This closes that gap by making the write-up a by-product rather than a task.

Nominate where drafts go

Create a folder in Documents called something like Help Drafts, and treat it as a queue rather than a library. Nothing in it is published, and everything in it is one edit away from being useful.

Keeping it separate from your real docs matters: an employee answering questions searches Documents, and you do not want it answering from an unreviewed draft it wrote itself last Tuesday.

Draft from the answer you actually gave

The valuable material is not the question. It is the reply you sent, because that is where you already solved the problem of explaining it.

Every Friday at 4pm, look at the questions you answered this week.

For any question that came up more than once, or that took more than three
exchanges to resolve, draft a help article in the Help Drafts folder.

Write it from the answer that actually worked, not from the question. Open
with what the reader is trying to do. Use our words, not support-desk
phrasing.

If we already have a draft or a published doc covering it, do not write a
second one. Tell me which existing document should be updated instead.

"Do not write a second one" is what stops this becoming a mess. Left alone, a job like this produces four articles about the same thing over a month, and a folder of near-duplicates is harder to fix than an empty folder. The point is coverage, not volume.

Read them as a person who does not know the answer

The drafts will be accurate and often too knowing, because they were written from an answer given to someone who had already explained their situation.

The specific thing to check: does the article make sense to someone who does not yet know the right words for their problem? That is who will find it.

Feed the good ones back

Once you have edited a draft into something you would publish, move it out of Help Drafts and into your real documents. The next time the question arrives, the employee answers from your edited version and cites it.

That loop is the whole point. The library gets better because the questions keep arriving, rather than in spite of it.

What good looks like

After a month you have eight or nine articles covering the questions that actually recur, written from answers that actually worked.

The number to watch is not articles written. It is how often the employee hands a question to a human because the documents did not cover it. If that number is not falling, the drafts are being written about the wrong things.