An afternoon designing boards feels better than two finished tasks

And that is the entire trick by which this behaviour sustains itself.

When you rebuild a board, link dependencies and assign colours, you get immediate feedback. It looks better after every change than it did before. It cannot fail. And nobody can contradict you while you are doing it.

The task that is actually due has none of that. It has unclear feedback, it can go wrong, and whether it was any good you only learn later. Between those two options your head reliably decides against you, and because configuring looks like work, nobody notices. Least of all you.

How to spot it

Six symptoms, of which two are enough:

• You have tried more than two task managers in the past twelve months.
• You know your tool’s feature roadmap.
• There are fields in your system you have not filled in for weeks but do not delete either.
• The thought “let me set this up properly first” comes up more often than “let me do this now”.
• You read tool comparison articles although your current one works.
• After the weekly review you feel good, but in the week that follows no more happens than before.

The last one is the most reliable. A system does not exist to feel tidy, it exists so that something happens afterwards.

The two habits that actually change something

In one of our sessions a community member showed the evolution of his system over several years. What was interesting was not the list of tools he had worked through but what made the difference in the end.

It was two things, and neither of them is software.

The weekly review. Once a week, go through the system instead of hoping it keeps itself current. Without that appointment the lists drift so far from reality within two weeks that you no longer trust them, and then you are carrying things in your head again.

Notifications off. All of them. Not out of focus romanticism but because a system you use between two interruptions never actually gets used.

These two habits work in any tool. They work on paper. Whoever does not have them will not find them in any software, and whoever does have them will get by with almost anything.

And the system change was still right

Here it gets interesting, because the same person then rebuilt their entire setup. That sounds like the contradiction I described above, but it is not. The difference lies in the reason.

His previous tool got more expensive, worked only moderately offline, and the data sat with a provider he had no control over. Those are reasons that lie outside the system.

From which a rule can be drawn that I have used for years:

A system change is justified when the reason lies outside the system. Cost, data protection, a company mandate, a platform change, a provider discontinuing the product.

A system change is suspect when the reason is a feature. “The other one does nested subtasks” is almost always tool procrastination with an argument attached.

And the order matters. Habits first, then the system question. Work the other way round and you migrate your chaos into a new interface and wonder about it six weeks later.

His setup, and what it actually costs

He moved to infrastructure he controls himself:

• A Nextcloud at a German host, by his account for just over five euros a month with a terabyte of storage, with full administrative rights.
• Nextcloud Deck as a kanban board for the project overview.
• Super Productivity as a local list manager on desktop and phone, synced over the Nextcloud.
• Plus a document scanner and cloud storage for the paperless archive.

That is a tidy, cheap and field-tested setup. And now the part that is almost always missing from articles like this.

The five euros are not the price. Your own Nextcloud means applying updates, setting up backups and occasionally checking that it still runs. When syncing breaks after an update, nobody is responsible except you, on the day you had other plans. Someone from an IT background factors that in and finds it fine. Someone who does not has taken on a project and is calling it a productivity system.

My honest calculation: hosting plus roughly two hours of operations per quarter, plus half a day for the initial setup. Compared with many subscriptions that is still cheap, but it is not free.

Data ownership, without the drama

The question is a fair one and usually gets asked too broadly. It is more useful in concrete form: which entries in your system would bother you if they sat with a provider in another legal jurisdiction?

In a task manager that is usually not the tasks themselves but the names. Client names in project titles, notes from conversations, in some professions patient or case references too. Anyone working with those has a substantive reason for their own infrastructure. Anyone managing shopping lists and renovation projects does not, and is allowed to see it that way.

Two clarifications, because too much gets claimed here:

A server location in the EU makes things easier but is neither a condition nor a guarantee. Processing outside the EU is lawful when the basis for it is right, for instance an adequacy decision or standard contractual clauses. And a location in Frankfurt makes nothing compliant: compliance depends on what you process, on what basis, how long you keep it and whether the necessary contracts exist. Self-hosted also means you are responsible yourself, including for security. That is more control and more duty, not less.

And the practically most important point in any tool choice is almost always overlooked: can you get out again? An export in a readable format, Markdown or CSV, decides whether the next price rise leaves you over a barrel. Systems whose content sits in text files outlive their providers. That is why I keep my own reference material in Markdown and not in a database only one app can read.

The test before switching

Three questions before you migrate. Answered honestly this takes ten minutes and may save you a weekend.

1. What exactly can my current system not do that I genuinely needed in the past four weeks?
2. Is that a tool problem or a habit problem? If your weekly review gets skipped, it will get skipped in the new tool too.
3. What does the migration cost in hours, and what would I otherwise have done with those hours?

If question one has no concrete answer, the matter is settled.

Where it typically fails

The move turns into system work rather than a migration. “I’ll move my lists” becomes “I’ll rethink my system”, and three weekends later the setup is prettier and the projects are where they were.

Self-hosting without backups. The moment you find out is always the same one.

Forcing everything into one tool. Reference material, projects, tasks and archive do not have to live in the same software. What has to fit together is the logic.

The habits get postponed until after the move. They then do not arrive, because after the move there is the next move.

Common questions

What is tool procrastination?

Working on your productivity system instead of the work it is meant to organise. It sustains itself because configuring delivers immediate, visible feedback and cannot fail, while real tasks offer neither.

When does switching task management tools make sense?

When the reason lies outside the system: rising cost, data protection requirements, a company mandate, a platform change or a discontinued product. A missing feature is rarely a sufficient reason.

What does a self-hosted Nextcloud really cost?

On top of hosting in the single-digit euro range come setup, updates and backups. Realistically half a day at the start and a few hours per quarter in operation. Cheaper than many subscriptions, but not effort-free.

Is an EU server location enough for GDPR compliance?

No, and it is not strictly required either. Processing outside the EU is lawful with the right basis, for instance via an adequacy decision or standard contractual clauses. Compliance depends on purpose, legal basis, retention period and the necessary contracts. With self-hosting, responsibility for security lies entirely with you.

What should I look for when choosing a tool?

The export. If you can get your data out in a readable format such as Markdown or CSV, the next price rise cannot hold you hostage. Systems made of text files outlive their providers.

---

Look at your calendar for the past four weeks and find the hours you spent working on your system rather than with it. If you cannot find them because they were never entered anywhere, that is already the answer.