# A Stale Backlog Creates Shadow Systems ## Claim A backlog loses authority when stale items make private tracking more trustworthy than the shared system. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - This holds for shared task and knowledge systems whose value depends on participants trusting that visible items still represent real work. - Archiving is safer than deleting during a cleanup because it restores signal while keeping uncertain history recoverable. - A large backlog isn't automatically stale; the failure begins when nobody can distinguish commitments from abandoned possibilities. ## Evidence [[3. Resources/Readwise/Articles/144 First Week as VP]] describes inherited Notion and Linear spaces full of abandoned systems. Once people stopped trusting the shared backlog, they moved to private lists; an archive-not-delete sweep restored a smaller, explicit boundary for what each tool was for. ## Links - [[AI & the Future of Knowledge Work MOC]] — connects backlog decay and shadow systems to changing knowledge-work operations. - [[Retrieval Quality Is Set by the Unit of Knowledge Not the Retrieval Algorithm]] — extends: retrieval can't restore authority when the underlying collection doesn't distinguish current commitments from abandoned artifacts. - [[An Audit Trail Is Trustworthy Only When It Is a By-Product of the Work]] — contrasts: a shared system stays credible when routine work maintains its record instead of requiring retrospective cleanup. - [[AI-Assisted PKM Replaces Synthesis Work With the Appearance of Synthesis Work]] — applies-in: adding automated retrieval to an untrusted corpus hides the maintenance failure instead of resolving it.