Idea

Knowledge capital is worth only what brings it back into decisions

Info

Originally written in French. Translated by AI — the meaning has been preserved, not the prose.

Main idea

An organization can capture its customer interviews, transcribe its sales calls, requalify its support tickets into stakes, connect its objections to segments and share all of it with the functions concerned — and still have capitalized on nothing. The last movement is missing: that this material comes back into the decisions that were waiting for it, the quarter's roadmap trade-off, the writing of the next PRD, the choice of a positioning, the revision of a packaging.

That movement is not a consequence of the previous ones. It has its own moment, which is the moment someone decides, and that moment is not the one when the knowledge was written. A well-kept base that nobody opens at the prioritization review remains a writing expense; a mediocre note the Product Manager reopens before arbitrating has produced more value than it has.

Hence a simple examination, decision by decision: which building blocks of context were actually drawn on to make it? A fuzzy answer doesn't say the base is poor. It says the system still rests on the memory of the people in the room.

Why it matters

This corrects the order in which an organization equips itself. Capture is what shows and what can be priced — a transcription tool, a CRM field, a reporting ritual — and that is where you start; whereas the link that decides the value of all the others is the last one, and nothing tools it.

It also changes the criterion by which a knowledge base is judged. Not its completeness, nor the tidiness of its links: the trace of the times it was drawn on.

Nuances and limits

Feeding back can't be mandated without perverse effects. Requiring a decision to cite the existing capital manufactures retrospective justification: you go looking in the base for what confirms what you were going to do anyway, and the loop closes on itself.

And the absence of reuse is not always a failure of the loop. A building block can sit untouched for three years and then settle a trade-off on its own, when the segment it describes becomes a priority again.

Open questions

  • How do you detect that a decision should have mobilized a building block that existed, and that never surfaced? The gap is silent on both sides: the person deciding doesn't know what they didn't see, and the base signals nothing.