It happens. A new job, a bad month, a project that consumed everything. The weekly review slipped once, then twice, then you stopped counting. The inbox is 300 items. The idea of going back in feels like climbing a mountain.
The instinct is to start over. Empty the inbox. Delete the old notes. Design a new system.
Almost always the wrong move. Here's why: the system that crashed was probably fine. What crashed was the behavior. A new system doesn't fix behavior. It just gives you a new system to neglect in the same way.
Use triage instead. It's not a rebuild and it is not a full cleanup. It is a short restart that gets you functional today and creates a path to recover the rest.
Why This Works Better Than a Rebuild
A rebuild is seductive because it feels like a fresh start. But a fresh start has no content — no history, no context, no understanding of what actually matters. You build the perfect system for the context you imagine, not the context you have.
Triage keeps your system's useful history while separating live commitments from old debt. The notes, projects, and reference materials that are still relevant are still there. The commitments you can't keep are either archived or deliberately renegotiated. You're not starting from zero. You're starting from where you actually are.
When It's Actually Time to Rebuild
Sometimes a rebuild is right. Not when the system is messy — mess is fixable. When the structure itself no longer fits your life.
You changed careers. Your categories are organized around a job you no longer have. Your task system is built for a role that no longer exists. The structure is wrong, not just the maintenance.
This is rare — less than once every three years for most people. But when it's true, it's real.
When it's time: archive the old system. Don't migrate it. Move it somewhere you'll keep for reference but won't work from. Build something designed for where you are now.
The old system is a record of who you were. The new one is for who you are.
