Every productivity system decays. This is not a failure of will or a sign that your system is bad. It's a feature of how systems work in the world.

The reason is straightforward: you set up your system in a specific context — a specific job, a specific set of priorities, a specific phase of life. The system is designed around that context. Then the context changes. Your job changes. Your priorities shift. You move. A project ends. A new area of responsibility opens up. And the system that made sense six months ago no longer fits.

This is decay. Not dramatic failure — slow drift. The system and the life it was built for gradually fall out of alignment until the friction of using it exceeds the value it provides.

Most people don't notice until it's too late. Either they keep using a system that no longer fits, which produces constant low-grade friction that erodes trust in the system itself. Or they hit a breaking point — an inbox of 400 items, a weekly review that hasn't happened in six weeks — and decide the whole thing needs to be rebuilt from scratch.

Both responses are wrong. Here's how to catch it earlier.

The Diagnostic Tests (Run These Now)

You can catch decay early. Run these three tests on your system today.

Test 1: The Weekly Review Clock.

How long does your weekly review actually take? If it's under 30 minutes, your system is healthy — you're staying on top of it. If it's 45 minutes or more, something has accumulated that shouldn't have. This is fixable without a rebuild. It requires one honest processing session to get back to baseline.

Test 2: The Next-Action Rate.

Count your active projects. For how many of them can you immediately name the single next action? If more than 60% have a clear next action, your system is functioning. If fewer, the system is storing unresolved decisions, not supporting work. The fix is 30 focused minutes going through each project: "What's the next action?" Most will yield an answer.

Test 3: The Retrieval Check.

Think of a project you worked on three months ago. Without using your task system as a guide, try to find every note, decision, and reference related to it. How long did it take? Did you find things you'd forgotten? If you can't retrieve your own work from three months ago, your system has a retrieval problem — which is different from a storage problem. The fix is not better filing. The fix is better linking and a living Layer 1.

The Operating Cadence

Decay is easier to prevent when maintenance has different levels.

Daily: clear commitments. Capture what you promised, decide what must happen next, and make waiting-for loops visible. This is where Slack, email, meetings, and delegation get translated into commitments instead of vibes.

Weekly: reset context. Review active projects, next actions, waiting items, and the next two weeks of calendar. The weekly review is not a full cleanup. It is how you return the system to the current reality.

Monthly: archive and trim. Close finished projects. Move stale resources out of the working field. Clean up shared docs and decision records so the team is not navigating old drafts as if they were current.

Quarterly: check fit. Ask whether the structure still matches your role, responsibilities, and team boundaries. New job, new team, new product surface, new investor cadence — these may require structural changes. A messy week does not.

When Decay Has Gone Too Far

There is a point where the system has decayed past the point of recovery through cleaning. Not often — but it happens.

You know you're there when: the system's categories no longer map to anything in your actual life. When every review produces anxiety instead of clarity. When you've lost trust in the system so completely that you no longer look at it for decisions.

In that situation: a rebuild is appropriate. But it's not a failure — it's a recognition that your life changed enough that the old structure is wrong. Build for where you are, not where you were.