Turning Engagement Experience into Firm Knowledge
Every firm has a knowledge repository, and in most of them the most recent useful document is several years old.
The pattern is consistent enough to be predictable. A repository is created, contribution is encouraged, a burst of material arrives, and within eighteen months it is a graveyard: hundreds of documents, no way to tell which are current, and everybody asking a colleague instead.
The failure is not cultural. It is that contributing and using were designed as separate activities, so contributing is pure cost to the person doing it and the benefit lands on someone else, later, invisibly. Anything built on that arrangement decays.
What actually gets reused
Study what people ask colleagues for and a short list emerges. It is not insight or thought leadership; it is the things that save an hour at the start of a piece of work.
- Prior deliverables of the same type, to see the structure and depth expected.
- Effort data: what this kind of work actually took, by phase and grade, which is what makes the next estimate defensible.
- The information request list used last time, which is close to reusable and takes a long time to write from nothing.
- The risks and assumptions that turned out to matter, which is a far shorter list than the register they came from.
- Who did it before, which is the most requested item of all and the one a repository handles worst.
Capture as a by-product, not as an act
The habit that makes this work is to stop treating knowledge capture as a separate step. If the plan, the deliverable list, the request list, the registers and the effort data live in the systems where the work is performed, then the record of how this type of work is done exists already, and the only remaining task is to promote a good example into the template.
That reframes the closing question of every debrief. Not "what should we write up", which produces nothing, but "what changes in the template", which produces a specific edit somebody can make in ten minutes.
Currency, which matters more than coverage
A repository with fifty current documents beats one with five hundred of unknown age, because the second requires the reader to assess every item before trusting it, and that cost is higher than asking a colleague.
Give every reusable artefact an owner and a review date, and remove anything that passes its date without review. Removal is the discipline firms find hardest and the one that keeps the collection trustworthy. Material that might be useful later can be archived rather than kept in the working set; the working set should contain only what the firm is willing to stand behind today.
Finding the person, not the document
Since the most common request is for a person rather than a file, it is worth solving directly. A record of which engagements a person has worked on, in which sector, on what kind of work, answers more questions than any document library, and it is derivable from data the firm already holds.
The obstacle is usually not technical but organisational: staffing data lives in one system, engagement data in another, and neither is joined. Joining them is a modest piece of work with an unusually high return, because it converts the firm's most-used knowledge channel from a rumour network into something searchable.
Measuring whether it works
The measure is not contributions or views. It is whether the estimate for a new engagement of a familiar type is now built from evidence rather than from judgment, and whether the second engagement of a kind takes less effort than the first.
Both are measurable from data the firm already produces, and both are honest. A knowledge programme that cannot show either is producing activity rather than value, and it is better to say so and simplify than to keep asking people to contribute to something nothing depends on.