A [[Lightweight methodology|lightweight methodology]] applied to knowledge management: the smallest set of practices, capture conventions, and stewardship arrangements that satisfies the non-negotiable [[Knowledge management requirements|requirements]] for the clusters currently in scope. Anything not currently paying its keep is deferred, not refused. A lightweight knowledge methodology is the typical output of an early knowledge-management engagement: a deliberately small starting point, operational from day one, and expected to evolve as new clusters surface, new tooling lands, and the organisation learns which practices stick and which gaps surface next. Two anti-patterns it deliberately avoids: - **Catalogue adoption** - choosing a named methodology (a structured wiki, a [[Zettelkästen]]-inspired linked graph, a community of practice, a decision-log discipline) and applying it wholesale before the organisation knows which of its clusters most needs which property. The catalogue is consulted after the requirements are written, not before. - **Provisional placeholding** - declaring the methodology a "starter" or "pilot" that does not yet count, with the result that nobody is held to it. A lightweight knowledge methodology is operational from day one; what changes is its shape, not its status.