A catalog of the pains a knowledge management system can encounter. Recognition has two failure modes: - the cost is absorbed as friction (slow onboarding, repeated questions, duplicated decisions) before it is named - the absence of knowledge has no inventory, because missing things are never listed as missing The step is complete when the gap is named and its cost is felt - not just acknowledged abstractly. Without this step, methodology and tool decisions are solutions in search of a problem. ^awareness ## Personal-track pains ![[Feeling lost in own work#^pain]] ![[Cannot find my own notes#^pain]] ![[Forgetting before recording#^pain]] ![[Notes I no longer trust#^pain]] ![[Tool change loses my notes#^pain]] ![[AI cannot use my notes#^pain]] ![[I cannot articulate what I know#^pain]] ![[My notes scattered across apps#^pain]] ![[Filing fatigue#^pain]] ![[My chat messages are my notes#^pain]] ![[Insights lost to context switching#^pain]] ![[My notes are buried in clutter#^pain]] ![[Notes I capture but never revisit#^pain]] ![[Each note an island#^pain]] ![[Cannot trace my ideas across years#^pain]] ![[Reinventing things I have done before#^pain]] ![[App I trusted shut down#^pain]] ![[Knowledge anxiety#^pain]] ![[My system has become the work#^pain]] ![[Productivity frameworks do not fit my work#^pain]] #discuss [[DIKW]] vs tools #move [[Notes management#^problem-storage]] here > - The problems are clear > - The tools are available > - Nobody has shown how to make them work **[[Scale|at scale]]** ^scale