Knowledge capture: what it is
Knowledge capture takes what people know and only ever tell each other verbally, and puts it somewhere a new starter and a system can both read. The sources are support threads, handover notes, supplier quirks and the answers senior staff repeat weekly. It is the least glamorous pattern and often the highest leverage.
( The Detail )
What the pattern does
The decision it improves is anything that currently waits on one person. When the answers exist in writing, work can be handed to a junior, an assistant or an AI tool without a quality drop, and the organisation stops paying an interruption cost every time a routine question comes up.
Looked at from this angle
Start with the plain description: what the pattern takes in, what it produces, and who reads the output. If it cannot be described in two sentences without naming a product, it is probably not a pattern yet - it is a tool somebody liked. Naming the shape first keeps the conversation on the work.
A pattern is deliberately general. It describes an arrangement that recurs across quite different businesses, which is why it survives changes in tooling. The specific software is an implementation detail, and it should be the last decision made rather than the first one argued about.
How to approach it
Begin with the decision rather than the tool. Name the recurring judgement this affects, the information it depends on, and the person accountable for acting on the result. That framing keeps the first build small enough to inspect and useful enough to matter.
Keep a human review point in the loop until the quality and the failure modes are understood. A system that shows its working - what it drew on, where it is uncertain, and what it deliberately left alone - is one a business can keep running after the initial build.
( Next Step )
Start small enough to review, but on a workflow important enough to show whether a better system is worth building.