# Training as a System Compounds Where a Session Decays ## Claim Client or team training holds its value only when it's built as a shared, maintained documentation system rather than delivered as a one-time session, because the underlying product, site, or team keeps changing after the session ends and a static event has no way to keep up. ## Evidence **Source**: [[3. Resources/Literature Notes/Building Training Systems, Not Sessions Andrew Adam]] ## Scope & conditions - Holds when: the same foundational subject matter repeats across many clients, projects, or new hires — a custom framework, product, or process an organization teaches over and over, where writing it once and maintaining it compounds in value with each reuse. - Breaks when: the material really is one-off and project-specific with no repeat audience — there, a live session is cheaper than standing up and maintaining a documentation system for an audience of one. ## Links - [[DevRel MOC]] — because applies-in: a durable-systems argument for the MOC's developer-education and training-program threads. - [[3. Resources/Permanent Notes/AI Documentation Pipelines Need an Explicit Authority Source]] — because applies-in: a maintained documentation system that uses an AI assistant to scale still needs the same explicit, non-negotiable sourcing constraint to stay trustworthy as it grows. - [[3. Resources/Permanent Notes/A Contribution Pipeline Needs a Defined Next Step After Training]] — because contrasts: that note is about what happens after training ends (a next step for the trained person); this one is about what training itself should be built as (a durable system, not an event). <!-- atomicity: 1 idea ✓ --> - [[3. Resources/Permanent Notes/Attention Capacity Is Stable but the Effort It Costs Has Been Repriced]] — evidence-for: sustained attention has always reset at 8–30 minutes on decades of stable instruments, so a system with deliberate resets designs to the evidence and a single long session designs against it.