Why the perfect app never sticks
The short version
- The cycle is familiar: find a new tool, set it up properly, use it for a week and a half, stop. Then find another one.
- Setting up is genuinely useful work and it is also where a lot of the appeal sits, which is why the plainer tool is often the one still open a year later.
- The searching is not wasted. People learn real things about what they need by doing it, and some switches are simply correct.
You found it on a Sunday. You imported everything, chose the colours, built the templates, wrote the tags. By Wednesday it was the best system you have ever had. Some time around day nine you stopped opening it, and a few weeks later you noticed you were back on a list in your phone's notes app, the one with no features, which you have somehow never abandoned.
Setting up is doing something
The setup week is real work and it is often a genuinely productive week. Things get sorted, forgotten commitments surface, the shape of the term becomes visible. None of that is fake.
It is also the most pleasant part of the whole exercise. Setting up a system has everything the work it serves does not: clear steps, visible progress, immediate feedback, an obvious end point, and no risk of doing it badly. Writing the essay has none of those. So the pull towards configuring is not laziness — it is the sensible response of a person choosing the task that is legible over the task that is not.
Novelty is carrying some of the load too, and it cannot keep carrying it. On day one the tool is interesting, so opening it costs nothing. By day twenty it is furniture, and opening it costs exactly what opening any list costs. The system did not get worse. The free energy ran out, and what is left is upkeep — which the plain tool has almost none of, and the elaborate one has a lot of.
What the search actually gives you
It is worth saying plainly that the cycle teaches people things they could not have learnt any other way. You find out that you will never open a tool that is not on your phone. You find out that nested folders never get looked at twice. You find out that you do not, in fact, write long notes, whatever you believed about yourself. That knowledge is only purchasable by trying, and the people who have cycled through six apps usually know their own requirements far better than the people who never tried any.
Some switches are also just right. A tool can stop fitting because your work changed, and staying loyal to it is not a virtue. The instinct that something is not working is usually accurate. It is the conclusion — that the answer is a different application — that is worth examining.
Where the plain tool wins and where it does not
The plain tool wins on upkeep and on portability. It survives a bad fortnight, because there is nothing to fall behind on; you cannot have an out-of-date plain list, only a short one. It exports in seconds, it works on a borrowed laptop, and it never asks you to remember a convention you invented in March.
It loses where work genuinely has many moving parts and several people. A shared project with dependencies, handovers and deadlines is not well held by a text file, and pretending otherwise costs real time and other people's patience. Sometimes the plain tool is plain because it is missing something you actually need, and treating that as your own lack of discipline is both wrong and demoralising. Complexity in the tool is a fair answer to complexity in the work.
What the setting can do
Institutions do this at scale and rarely count the cost. Being moved onto a new learning platform, ticketing system or document store every couple of years is not the reader's doing, and it dissolves whatever anyone had built. Every migration is unpaid work, distributed thinly enough across enough people that nobody has to notice it.
The reasonable asks are specific. When a new tool is introduced, ask what is being retired — adding without retiring is what produces six channels. Ask that migration time be scheduled rather than absorbed. Ask that anything you are required to store can be exported in a standard format, so a change of platform is not a loss of your records. Course reps, staff forums and team leads can raise all three, and they land better than a general complaint about too many tools.
Small things to try this week
- Stay on your current tool for the rest of the month, whatever it is, and write down what it is actually failing at. A specific failure is a good reason to move. Restlessness is not.
- Look at the last tool you abandoned and take one thing you learnt from it into the one you use now.
- Before any future setup, cap it at one sitting. If it cannot be usable in one sitting, it will not survive a bad week.
If you have done all this and the tool is still not being opened after a few weeks, that is information. It usually means the tool was never the difficulty.
Written for Thought Club as general guidance, not medical advice. Free to read, print, and share.