Home » , , » Getting Things Done - GTD

Getting Things Done - GTD

No comments
Getting Things Done or GTD is a time management method, described in a book of the same title by productivity consultant David Allen. 
The GTD method rests on the idea of moving planned tasks and projects out of the mind by recording them externally and then breaking them into actionable work items. This allows one to focus attention on taking action on tasks, instead of recalling them.

GTD is based on storing, tracking, and retrieving the information related to the things that need to get done. Mental blocks we encounter are caused by insufficient 'front-end' planning. This means thinking in advance, generating a series of actions which can later be undertaken without further planning. The mind's "reminder system" is inefficient and seldom reminds us of what we need to do at the time and place when we can do it. Consequently, the "next actions" stored by context in the "trusted system" act as an external support which ensures that we are presented with the right reminders at the right time. As GTD relies on external reminders, it can be seen as an application of the theories of distributed cognition or the extended mind



References:
Share:

No comments:

Post a Comment

Did you know

Imagination is more important than knowledge. Knowledge is limited. Imagination encircles the world - Albert Einstein
  • Getting Things Done - GTD
    Getting Things Done  or  GTD  is a time management method, described in a book of the same title by productivity consultant David Allen. ...
  • The Pomodoro Technique
    The  Pomodoro Technique  is a time management method developed by Francesco Cirillo in the late 1980s. The technique uses a timer to brea...

Blog Archive

Recent Posts

Label Cloud

GTD (1) management method (1) methodology (1) pomodoro (1) productivity (1)

Methodology vs technique and tool

A true methodology addresses the effectiveness side of the equation (Who, What, When, Where, Why), and a technique addresses the efficiency side (How to). Whereas a methodology defines the work environment, the technique defines how the work is to be performed. The two are obviously complementary and one does not eliminate the need for the other. But comparing one with another is like comparing apples with oranges, they are simply not the same.

Tools implement techniques. Tools provide mechanical leverage for performing a specific task. In this sense, it is an extension of a technique, and like the technique, tools must be deployed at the proper locations along the Assembly Line. This is the reason why many software engineering tools are failing; not because they are bad tools, but simply because companies have not defined their Assembly Lines (methodologies) and haven't specified when the techniques and tools are to be used - it.toolbox