Most people don’t feel unproductive because they lack the right tools. They feel unproductive because the tools they do have keep changing.

Every year brings a new app, a new workflow, a new promise that this one will finally stick. The result isn’t clarity, it’s fatigue. Systems are rebuilt, notes are migrated, automations are re-wired, and somehow the work itself never gets any lighter.

The problem isn’t the tools, it’s the assumption that tools are the system.

The uncomfortable truth about modern tools

Digital tools age quickly. Sometimes because they fail. More often because you change.

Your job shifts. Your interests evolve. Your available time shrinks. The context that made a tool feel perfect slowly disappears and suddenly the system feels heavy, brittle, or oddly irrelevant.

When that happens, the default response is replacement:

• A new notes app
• A new task manager
• A new “all-in-one” platform

Switching feels productive because it creates movement. There’s a brief sense of renewal, even optimism, but after enough cycles, a pattern emerges: the rebuild itself becomes the habit and nothing ever quite settles.

What actually lasts

Tools are temporary. Concepts are not.

Beneath every app you’ve ever used are the same enduring needs:

• Capturing information
• Making sense of it
• Storing it safely
• Retrieving it when it matters

These are functions, not features. They existed before software and will exist after today’s platforms are gone.

A durable system starts by separating what you’re trying to do from what you’re currently using to do it.

When those two things are tightly coupled, every tool change becomes a crisis. When they’re decoupled, change becomes manageable.

Systems thinking for individuals

In engineering, resilient systems share a few common traits:

• Loose coupling between components
• Graceful failure instead of total collapse
• Simple interfaces between parts

Personal knowledge systems benefit from the same thinking.

A good system:

• Allows one part to break without taking everything else down
• Assumes imperfect use, not ideal behaviour
• Can be migrated in stages, not all at once

Most importantly, it respects the real constraint: human energy.

A system that only works when you’re motivated, focused, and well-rested is not resilient. It’s fragile.

The hidden cost of tight coupling

Many modern tools encourage you to do everything in one place:

• Think there
• Write there
• Store there
• Automate there

This feels efficient, right up until it isn’t.

When thinking, storage, and workflow logic are inseparable, you can’t change one without disrupting the others. You don’t just switch tools; you dismantle a way of working.

That’s why migrations feel so exhausting. You’re not moving data, you’re trying to move meaning.

Designing for change, not permanence

The goal is not to build a perfect system. It’s to build one that survives change.

That means:

• Fewer hard rules
• Fewer dependencies
• Fewer assumptions about your future self

It means choosing clarity over cleverness, and portability over optimisation.

A system designed to last is one you can neglect for a while and still return to. It bends. It degrades slowly. It forgives gaps.

You’re not behind

If your tools feel messy, it doesn’t mean you’ve failed, it means your life moved faster than your system.

You don’t need to start again. You don’t need a better app. You don’t need to rebuild from scratch.

You need to loosen the coupling.

Design the system first. Let the tools follow.

They always change anyway.