Recognising that knowledge gaps exist and carry measurable cost. The recognition has two failure modes that delay it: - the cost is absorbed as friction - slow onboarding - repeated questions - duplicated decisions - before it is named - and 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 ## The pains #matt/describe [[DIKW]] vs tools #move-here [[Notes management#^problem-storage]] > - I know what problems I want to solve > - I know what tools are available > - But nobody have ever told me **HOW** to use these tools to solve my problems **AT SCALE** ^scale ## The questions #refine figure it out