A knowledge management system without maintenance is like a garden without water: it may survive a season, but over time it withers. Accumulated notes lose relevance. The structure that made sense when you designed it no longer reflects how you think now. Projects that ended months ago are still in the foreground, mixed with current ones.

Maintenance is not glamorous. It is also not complicated. It requires consistency and a little regular time.

Why systems rot

Knowledge management systems die through accumulation. Things come in, but nothing goes out. Notes that are no longer relevant are still there. Abandoned projects are mixed with active ones. The inbox grows without being emptied.

Over time, navigating the system becomes so costly that the de facto solution is to start a new system. And the cycle repeats.

The solution is not a simpler system (though that helps). It is having regular maintenance rituals that prevent accumulation.

The weekly review

The weekly review is the most important ritual. If you only do one thing from this chapter, make it this one.

A typical weekly review lasts between thirty and sixty minutes, and includes:

Empty the inbox: process everything that has come in during the week. For each element: delete, convert to task, convert to note, archive. Leave nothing in the inbox without a decision.

Review active projects: what is the status of each project? What remains to be done? Is anything blocked? Has any project ended and needs to be moved to the archive?

Review pending tasks: what was left undone last week? Is it still relevant? Has the priority changed?

Prepare the coming week: what are the priority projects and tasks? Is there anything important you want to do this week that has not been captured yet?

The monthly review

The monthly review looks a little further ahead. It takes between one and two hours, and focuses on the health of the system rather than specific tasks.

Usual points of a monthly review:

Review areas: how are the ongoing responsibilities of your life? Is there any area you are neglecting? Has something changed in your circumstances that should be reflected in the system?

Review resources: is there accumulated material you never use? Are there things in resources that are actually concrete projects? Are there resources that are no longer relevant and can be archived?

Review the month’s learnings: what did I learn this month? Is it captured? If not, now is the time to write a brief reflection.

The annual review

The annual review is the moment to look at the system from a wider perspective. It takes between two and four hours, and has a more reflective character than an operational one.

Usual points:

Review the year’s completed projects: what went well? What went wrong? What did I learn? The answers go into your learning notes.

Review the previous year’s goals: what did I plan that never happened? Why? What happened that I had not planned and was positive?

Review the system itself: which parts of the system do I use? Which parts do I never use? Is there something that generates friction and could be simplified?

Set the focus for the coming year: not a list of resolutions, but a set of areas or projects where you want to put energy.

Pruning the system

In addition to periodic reviews, there are moments when the system needs a deeper clean: when it has grown too large, when the structure no longer works, when there are entire areas you never touch.

Pruning does not mean deleting everything and starting again. It means moving to the archive everything that is no longer active, simplifying the structure, and leaving the main system with only what you are actually going to use.

A good sign that the system needs pruning: it takes you more than thirty seconds to find something that should be easy to locate.

How much time for maintenance?

The honest answer: it depends on how much comes in. If your system has a lot of weekly input, it needs more maintenance time. If it is more selective, less.

A reasonable estimate for an active but not obsessive system:

  • Weekly review: 30–60 minutes.
  • Monthly review: 1–2 hours.
  • Annual review: 2–4 hours.

If maintenance requires much more than this, the system is probably too complex. The solution is almost never more maintenance time; it is almost always a simpler system.

In the next chapter we review the most frequent mistakes people make when building and maintaining these systems, so you can avoid them.