Capture what you learn while you still remember it

The best knowledge article your team will ever write is sitting in a case someone closed this morning.

It has everything. The symptom in the customer's own words. The two things that did not work. The one thing that did. And by Friday, nobody will remember any of it.

That is the quiet tax on most service teams. People solve the same problem again and again, not because they are careless, but because the lesson lived in one person's head for about a day and then left.

Why the moment matters

Knowledge is cheapest to capture at the point it is created. Straight after a case is resolved, the person who fixed it knows exactly what happened and why. A week later they have a vague memory. A month later they have a guess.

John Sansbury makes the point plainly in The Journey to Service Excellence: "The best way for first-line staff to acquire the requisite knowledge is if second and third-line staff properly record on the incident record the actions they took to fix the incident that potentially the first-line staff could take next time."

Notice what that asks for. Not a polished article. A proper record of what was actually done, written while it is fresh. The article can come from that.

Make the first draft almost free

Most people will not stop to write an article from a blank page at the end of a busy shift. Nor should they have to. A good habit looks more like this:

• When a case closes with a fix that someone else could reuse, the resolver flags it in a click.
• The case notes become a rough first draft, with the symptom, the cause and the steps already there.
• Someone who owns knowledge in that area tidies it, checks it and publishes it.

Tools can now help turn case notes into a readable draft. That is useful. It does not remove the need for a person to check it. A fluent draft is not the same as a correct one.

Reward the capture, not just the closure

If the only number that counts is cases closed, people will close cases and move on. That is a perfectly rational response to what is being measured. If you want knowledge captured, it has to be visible and valued: noticed in team meetings, counted alongside resolution, and thanked when it saves someone else an hour.

Three questions for your team

• Which problem did we solve more than once last month?
• Where does the fix live today: in a record, in an article, or in someone's head?
• What would make writing it down take less than two minutes?

Every resolved case is a lesson. The only choice is whether you keep it.

Next step:

Tell us how your team turns resolved cases into knowledge in the Knowledge and self-service conversation on ESM's Exchange: https://exchange.esm.institute

Tags: knowledge management, service management, self-service, ESM