Getting Things Done - GTD
Don't call it GTD if it's not GTDAUTHOR: Francisco Sáez
"The process is only as good as the weakest link in its chain." ~ David Allen
Can you implement GTD by halves? Sure. Is it still GTD? Nope.
In many blogs and forums I frequent, I read again and again comments from people who say they use GTD partially. Also, I’ve checked out plenty of web tools that are advertised as GTD tools and they just use a few elements and principles of this methodology. If you take off stuff from a methodology and still call it its original name, then the word becomes meaningless and confusing.
I have the feeling that something like that is happening to the term GTD; it’s becoming blurred. Any application related to personal productivity is GTD. Bloggers and journalists call everything GTD, I don’t know whether out of ignorance or to call attention to a product. You can say that it’s inspired by GTD, or that it’s similar to GTD, or that it’s a subset of GTD … but please do not call it GTD.
A methodology is a tool that helps you work more effectively, telling you what to do. It doesn’t tell you everything that you need to do, but it provides a set of elements, rules and guidelines to follow. There is no perfect methodology for all situations. You must choose the option that best suits your particular circumstances.
All methodologies are strict to some extent, that is, they have more or less rules to follow. They are also flexible to some extent, i.e., they leave more or less open spaces where you can accommodate your needs. Contrary to what you might think, the value of a methodology is precisely that it limits your options. A tool that lets you do anything is not very useful.
There are a number of methodologies in almost all fields. For example, Scrum is a methodology used in IT project management, Kanban is used extensively in manufacturing systems and Extreme Programming is one of the options you can choose for software development. Does this mean you should use a methodology to develop an application, manage a specific project or manufacture parts for cars? Of course not. Doing things your way can be valid in some cases. However, you should think that a methodology has been used, studied and optimized by many people for a long time, so using it has several advantages and a greater guarantee of success.
In the field of self-management, GTD is probably one of the best-known methodologies (at least apparently). GTD offers an organized way of doing things so that you can achieve your personal goals as productively as possible. Although the teachings of GTD come from many years of experimentation and observation by its creator, David Allen, some specialists in cognitive psychology have already investigated the validity of its principles.
GTD, like any other methodology, has elements and rules that define it as such. And then, some recommendations on aspects on which it doesn’t insist too much. This means that if, for example, your system doesn’t have a Someday/Maybe list or a Waiting For list (for actions delegated to others), then it is not GTD. If you cannot choose your next step action based on the context you are in, then it is not GTD. If your system doesn’t let you use the collect-process-organise-review-do workflow, it is not GTD.
What about you? Are you implementing a half-way GTD? Or are you really implementing GTD?