If keeping complete records is standard practice, how do you keep the records from quietly eating your focus? The answer, across every field, is structural — not willpower.
No single practice is "the" standard, but the conventions converge: protect focus by separating the inert archive from the active workspace, and cap what can be active at once. Records can be exhaustive as long as they stay inert reference and never become live, competing demands. The recurring moves — a fixed written statement of intent; separating capture from commitment; limiting work-in-progress; timeboxing; and a scheduled pruning ritual — all force a decision now instead of deferring it.
→ Read the exact exchange · Turn 08The difference is replacement versus addition. A clean pivot closes the prior intention — explicitly archived — and names a new one. A convoluted pivot is almost always unrecorded, gradual accretion: locally justified detours that individually pass and collectively sum to total divergence. The best working model is version-control branching: isolate and name the divergence, keep the main line intact, then either merge it or abandon it cleanly.
→ Read the exact exchange · Turn 08Or read it all: The full conversation, word for word →