Reviewing your own systems

Most people who take organisation seriously eventually end up maintaining a system that costs more than it returns. The failure is gradual and predictable.

How systems decay

Accretion. Each problem produces a new list, tag, field or rule, and nothing is ever removed.

After two years the system has thirty components, of which six are used, and the twenty-four unused ones impose a cost on every interaction.

The system becomes the work. Time spent organising is visible, feels productive, and produces nothing.

This is the most common failure among people who are good at systems, and it is difficult to notice from inside.

The context changes. A system built for one role continues into another where its assumptions no longer hold.

Trust degrades. A list that is not current stops being consulted, and once it is not consulted it becomes stale faster.

Which is why the single most important property of a personal system is that it is complete enough to be trusted, and why a partly maintained system is worse than a simple one.

The review

Monthly is a reasonable cadence, and it takes about half an hour.

What did I not look at? Any list, tag or file not opened in a month is a candidate for deletion.

Not archiving — deletion. Archives accumulate the same way.

What did I do that was not in the system? If significant work happened outside it, the system does not reflect reality and the gap will widen.

What did I record and never act on? A list of things you will never do is a source of guilt rather than a tool.

Where did I have to think about the system rather than the work? Every such point is friction, and friction is what eventually stops it being used.

What is duplicated? Most people have the same information in three places, and none of them is authoritative.

The bias toward removal

Reviews naturally produce additions, because problems suggest new components.

A useful discipline is to require that anything added is matched by something removed, at least until the system is smaller than it was.

People are systematically worse at considering subtractive changes than additive ones — a documented tendency across design and problem-solving tasks — which means the removal has to be forced rather than expected to occur naturally.

What survives

The components that consistently earn their place across most people's systems are few.

A single capture point. A calendar that reflects commitments accurately. A short list of current work. Some record of things waiting on other people. A way to find documents.

Almost everything else is optional, and much of it is decoration.

Tools

The temptation during a review is to change tool, which is almost always the wrong response.

Migration consumes days, resets habits, and the new tool acquires the same problems within a year because the problems were not the tool.

The reasonable rule: change tool only when a specific, named limitation has caused a specific, named failure more than once.

Not because the new one looks better, which it always does before you have used it.

The annual version

Once a year, a larger question worth asking.

Is this system serving work I still want to be doing? Systems encode priorities, and the priorities encoded may be several years old.

A review that only asks whether the machinery is running efficiently misses whether it is pointed anywhere useful.

The minimal defence

For anyone unwilling to do a structured review, one habit provides most of the value.

When you find yourself avoiding your own system, treat that as information rather than as a discipline failure, and simplify whatever produced the avoidance.

Avoidance of a personal system is almost always a design signal, and it is the earliest one available.

The record worth keeping

One thing that should survive every simplification.

A short log of what was decided and why, particularly for anything you will revisit. Not a journal — a few lines per significant decision.

It is the component with the highest return and the lowest cost, because reconstructing your own reasoning six months later is otherwise impossible, and you will be asked to.