A mentoring knowledge base rarely dies because nobody wants to write. It dies because nobody knows when to come back to an entry or who owns the review. The entry format and the review rhythm decide more about its value than the tool it lives in, and both can be specified.
Quick Overview
What you’ll learn:
- Which entry format survives staff turnover and a change of tooling
- Why a named review rhythm matters more than the volume of what is written
- Which roles have to be named before a knowledge base turns into an archive
- What the research says about the programme components worth recording
Who this article is for:
- People running mentoring programmes and accountable for their continuity
- Mentors who want to pass on more than their own notes
- Managers responsible for knowledge management in the organisation
Reading time: 7 minutes
A Knowledge Base Is Not an Archive of Conversations
The common failure starts with the assumption that the base should record what happened. A collection like that grows quickly and stops being read just as quickly, because it answers no question anyone asks afterwards. A meeting note documents a relationship; it is not organisational knowledge.
The base behaves differently when an entry is addressed by a recurring situation rather than by a date. “A mentee moving into a management role avoids conversations about team results” is an address someone will eventually arrive at. “Session of the 14th” is not.
The second difference is the reader. An entry written for oneself ends up as shorthand that only its author decodes; an entry written for the next mentor has to carry the context its author thinks is obvious. That surplus context is precisely what decides whether the base outlives the people who built it.
Entry Format: What After Action Reporting Teaches
Emergency preparedness met this problem long before mentoring did. The after action report (AAR) is a standard knowledge artefact there, and a structured review of such reports published in a peer-reviewed public-health journal (“Int J Environ Res Public Health”) and indexed on pubmed.ncbi.nlm.nih.gov analyses how lessons from responses to real incidents feed practice and exercise design. The authors describe the “lessons-learned” approach as a knowledge management practice applied to the wider idea of organisational learning, and draw their material from a national online repository of lessons learned run jointly by the US Department of Homeland Security and FEMA.
The part that matters most for a mentoring base is the limitation the authors state openly: systematic learning is constrained by weaknesses in how the reports themselves are written. The format is part of the problem, not a neutral container for it.
That converts into a plain instruction for an entry. Describe the situation, the approach taken, the effect observed, and what you would do differently — each as a separate field. Separating observation from interpretation is the only thing that lets a later reader disagree with the author while keeping the author’s material.
Review Rhythm: An Entry Without Revision Is a Hypothesis
A record nobody returns to is a memory rather than knowledge. A base therefore needs a named review rhythm, not good intentions.
A ready scaffold is the Gibbs reflective cycle, used in professional education as a structured path from describing an event, through feelings, evaluation and analysis, to a conclusion and an action plan. A paper in Nurse Education Today indexed on pubmed.ncbi.nlm.nih.gov applies it as the frame for a structured reflection on a research internship: the experience described, the feelings that accompanied it, then the opportunities and challenges evaluated and analysed, closing with an action plan written for the people who come next.
For a mentoring base that frame marks out distinct review moments. The first is a review by the author once the mentoring relationship closes, when it is finally known which part of the proposed approach worked. The second is a periodic review by somebody other than the author, whose job is to check that the entry still describes an organisation that exists.
Write the rhythm next to the entry. A date for the next look is cheaper than a procedure and easier to enforce.
What the Research Says Is Worth Recording
A review of mentoring programmes in the health sciences, indexed on pubmed.ncbi.nlm.nih.gov, looked for the programmatic components and structural features associated with success across the thirty-four individual programmes it covered. Two features recurred among the programmes reporting success: meetings held at least monthly, and content delivered inside a formal curriculum rather than ad hoc. The content categories common to successful programmes clustered around research, funding, teaching and networking.
The authors are candid about the limits of their own material: reporting across the reviewed programmes lacked objective, standardised metrics and often described course content only in general categories, which restricted the conclusions they could draw. That caveat is useful rather than inconvenient — it says that the thing most worth recording in your own base is the thing those papers were missing.
In practice this argues for entries that carry the cadence of contact, the curriculum element they belong to, and an observable outcome, instead of a general impression of how the relationship went.
The Roles Around the Base
The knowledge curator owns the structure and the periodic reviews. It is the only role that sees the whole and notices that two entries say the same thing, or that a third contradicts both.
The mentor authors the entry and owns the separation of observation from interpretation. A name on an entry is not a credit; it is an address for a later question.
The mentee is the source of the material and should know the scope of what is recorded. The ethical boundary of the whole exercise sits here: the base keeps a pattern of a situation, never a portrait of a particular person.
Read Also
- Guide: how to create and develop a mentoring knowledge book — the wider view of the same undertaking
- Mentoring: a guide to the mentee role — the other side of the material that ends up recorded
- Openness to feedback — where the raw material for entries comes from
Build Your Skills
This topic is developed in the Coaching: Stimulating and Supporting Employee Development and Coaching in IT Projects courses. The first organises the craft of the person running development; the second places it inside a technical team. Contact us to match the scope to the programme you run.
Frequently Asked Questions (FAQ)
What does knowledge management mean for a mentoring programme?
It means moving conclusions from individual mentoring relationships up to the level of the organisation, so the next person in a similar position does not start from nothing. The review of after action reports indexed on pubmed.ncbi.nlm.nih.gov frames the lessons-learned approach exactly that way — as a knowledge management practice serving organisational learning, not as archiving.
How do you build a company knowledge base people actually use?
Address entries by situation rather than by date, and name who owns the review. A base in which every entry carries a date for its next look and a named curator stays current; a base without both of those grows and stops being read, however good the tool underneath it is.
How is a mentoring knowledge base different from project lessons learned?
In scope and in the sensitivity of the material. Project conclusions concern how work ran and can be written down directly. A mentoring entry concerns a person, so what is recorded is the pattern of the situation and the approach taken, never the history of an individual. The organising frame is shared; the boundary of what may be written is not.
What tooling does a mentoring knowledge base need?
Less than is usually assumed. A place with revision history, a consistent entry template and a list of reviews with dates will carry it. Pick the tool last, after the format and the rhythm are settled — the reverse order ends with migrating unstructured content into a system that will not impose structure on it either.