KPIs · Knowledge Management

Knowledge Management: KPIs

Retrieval success, document currency and the retirement rate, measured because a knowledge base grows by default and only shrinks on purpose.

Markdown. No sign-up, no email.

Every measure here is chosen to resist the same failure: a knowledge base that grows continuously, is never pruned, and slowly becomes an archive of things that were once true.

The six that matter#

MeasureDefinitionTargetHow it gets gamed
Retrieval successQuestions answered from the Brain with correct sourcesAbove 80%Counting an answer as success because one was produced
Median document age at last reviewAcross everything currentUnder 12 monthsRe-dating without re-reading
Retirement rateDocuments superseded or removed per quarterAbove zero, alwaysNever removing anything, which is the default
Duplicate authoritiesTopics with more than one current documentZeroNot looking. Nobody trips over this until an incident
Decisions with recorded reasoningMaterial decisions carrying a whyAbove 90%Recording the decision and omitting the rejected options
Time to find an answerSampled by asking peopleUnder 5 minutesInferring it from search logs, which measure searching rather than finding

Retirement rate above zero is the health check for the whole function. A knowledge base that only grows is one where the share of true content falls every quarter. Nobody notices, because nothing visibly breaks until someone acts on a page from 2024.

Time to find an answer is sampled by asking people, not derived from analytics. Search logs tell you what was searched, not whether the person found what they needed or gave up and asked a colleague.

Two counter-metrics#

Counter-metricCatches
Questions answered by asking a person instead of the BrainThe honest measure of whether this works. If people still ask a colleague first, the Brain is not trusted
Context bundle size per agentGrows silently, costs money, and dilutes what matters. Nobody prunes an agent's reading list unless it is measured

Knowledge risk, reviewed quarterly#

QuestionBad answer
Which knowledge exists only in one person's head?Any critical system or client
Which clients have no written context?Any. This is what makes a departure expensive
Which architecture decisions have no recorded rejected options?Most, usually. That is where re-argument comes from
What would we lose if the longest-serving person left tomorrow?If this cannot be answered, the answer is "a lot"

What is deliberately not measured#

  • Documents created. Growth is the failure mode, not the goal.
  • Wiki page views. Reading is not finding.
  • Contribution counts. Rewards volume over authority, and volume is what breaks this.
  • Search volume. High search with low retrieval success means people are hunting, not finding.

Cadence#

ContinuousCapture at the point of work
MonthlyStaleness flags, duplicate authorities
QuarterlyRetirement pass, context bundle review, knowledge risk register
AnnuallyWhether the structure still matches how people actually look for things

Back to Knowledge Management

Get new material when it is published

Everything here is free and stays free. There is no form in front of any document. If you want to know when new guides and templates go up, leave an email.

Roughly monthly. Unsubscribe in one click. We do not share your address, and we will not call you.