There are phrases that start out with good intentions but end up becoming dogma. “The tool doesn’t matter” is one of them. GTD and personal productivity coaches often say this to remind you that it’s the method that counts, not the app you use to implement it. And they’re right in what they mean. But not in what they say.
Because the tool does matter. A lot.
Imagine you decide to practice the GTD methodology with a tool that isn’t designed for it. You can do it, just as you can hammer a nail with the handle of a screwdriver. But every time you process your inbox, you’ll have to keep track of the methods you’ve improvised yourself. Every time you do your weekly review, you’ll have to “jump” from one place to another to see if the information is up to date. A tool like that doesn’t guide you; it forces you to adapt to it. That adds an extra cognitive load on top of the GTD practice itself. And, paradoxically, cognitive load is exactly what the GTD methodology is supposed to minimize as much as possible.
Now imagine that your tool works perfectly well for GTD, but you find it ugly, clunky, or unintuitive. It has nothing to do with the method, that’s true. But every time you open it, there’s a little friction. A subtle resistance. And that resistance, building up day after day, turns into rejection. You’re not rejecting the method; you’re rejecting the tool. However, in your mind, the method and the tool have become the same thing.
Finally, imagine you decide to practice GTD with pen and paper. It’s not a bad idea; some people do it with discipline and achieve good results, and paper has advantages that no app has fully managed to replicate. But as your system grows (more projects, more contexts, more references), maintaining it becomes a job in itself. Updating lists, searching for a note buried between pages, relocating tasks that have changed status… What should be a weekly review turns into an excavation. The methodology hasn’t failed; the tool has. And when the tool fails, the temptation to abandon the system is almost inevitable.
To make things worse, the phrase “the tool doesn’t matter” throws two different concepts into the same category: the tool and the framework.
A tool is something external that helps you achieve what you want. Todoist, Notion, a spreadsheet, a notebook. You can use it to practice GTD, but the methodology isn’t in the tool—it’s in your head. You’re the one who has to remember the structure, follow the conventions, and maintain the system. A framework is something else entirely. It’s an environment specifically designed to embody a method, a system, or a way of working. It doesn’t require you to remember how GTD works because it’s built on the methodology—it has it embedded. You don’t use a tool adapted to the methodology; you operate directly within the methodology itself.
Notion is a tool. FacileThings is a framework. The difference isn’t in the price or the interface; it’s in who bears the burden of maintaining the system.
So the next time someone tells you that the tool doesn’t matter, understand what they mean: there’s no magic tool that will do the work for you. But don’t make the mistake of taking the phrase literally. It matters that the tool supports the method. It matters that it doesn’t create friction. It matters that it rows in the same direction you’re heading. It matters that it’s, as much as possible, invisible: that it disappears so you can see only the underlying system.
The perfect tool goes unnoticed. But its absence certainly doesn’t.
No comments