46 pages • 1 hour read
David AllenA modern alternative to SparkNotes and CliffsNotes, SuperSummary offers high-quality Study Guides with detailed chapter summaries and analysis of major themes, characters, and more.
The relationship the author establishes between “open loops” and stress lies at the heart of his methodology. “Open loops” is a term coined by Allen to describe the many uncompleted tasks in our lives. The “stress-free productivity” promised in his book’s title is largely achieved by transforming open loops into actionable material.
Allen suggests that the key problem with open loops is our cognitive inability to keep track of them. The brain dwells over unresolved issues but gives equal significance to minor and major open loops, leaving us in a constant state of anxiety. Furthermore, the brain often triggers reminders in contexts where we can take no action—a stress-inducing waste of thought and energy. Allen highlights the psychological impact of open loops by characterizing them as a nagging voice in the brain. This unwelcome voice is a continual reminder of unresolved commitments, “demanding that you do something about it” (167).
Cluttering of the short-term memory is presented as a further negative impact of open loops. The author argues that the human brain is designed to focus on one thing at a time. Consequently, storing open loops impairs focus on present tasks, again creating stress.
Allen’s solution to the stress caused by open loops is to store them outside of the memory. One of the key steps in his methodology is performing a “mind sweep”— a figurative spring cleaning of the brain where open loops are captured and written down. The author believes that transferring open loops to a system where they will be actioned relieves the brain of the overload and stress created by trying to keep track of them. The book’s promotion of this stress-relieving activity highlights its dual focus on productivity and psychological well-being.
The author’s knowledge of karate comes into play as he incorporates this martial arts simile into his methodology for reducing stress and improving well-being. In karate, “mind like water” describes “the position of perfect readiness” (12) for combat. In Getting Things Done, this concept is translated into the ideal state for productivity. Similar to the idea of flow, mind like water is presented as an alert yet relaxed state. When experiencing it, an individual is free from distractions, calm, fully present, and engaged in the task at hand.
In practical terms, Allen promotes this state as enabling workers to efficiently prioritize their workflow. The author claims that “[m]ost people give either more or less attention to things than they deserve, simply because they don’t operate with a mind like water” (12). Elaborating on the simile, Allen points out that water is not perpetually still but responds “totally appropriately to the force and mass of the input; then it returns to calm” (12). For example, a stone thrown into a pond causes a temporary ripple effect. Therefore, a mind like water responds appropriately to workflow, prioritizing objectively, and smoothly adapting to unexpected input as and when it arises. Getting Things Done presents mind like water as an ultimate goal to aspire to. It is both a practical tool that makes work easier and a spiritual state that increases well-being. Allen suggests this state of serenity can be achieved by his method of capturing and actioning open loops in a trusted organizational system.
Both themes feature heavily in Getting Things Done, underpinning the author’s approach to productivity. The bottom-up approach relates to the different horizons work can be perceived from, with ultimate goals and purpose at the top and day-to-day commitments at the bottom. Allen believes that workflow should be approached from the bottom-up. Meanwhile, front-end thinking is the concept of planning and determining next actions on all projects in advance.
Allen claims his emphasis on a bottom-up approach to work commitments distinguishes GTD from most other productivity models. The author acknowledges that a top-down approach may appear more holistic as it assesses the ultimate goals of an individual or company before anything else. However, he argues that it is neither practical nor workable. Allen points out that trying to adopt “higher-focused thinking” before one has control of actions at ground-level is “like trying to swim in baggy clothing” (22).
The author encourages readers to change their perception of ground-level work. Instead of considering the everyday process mundane, he suggests it should be embraced as ultimately empowering and liberating. Allen argues that taking complete control of work at this level eventually gives individuals the confidence to think more creatively about their higher horizons.
According to Allen, a further source of empowerment in the workplace is the adoption of front-end thinking. This philosophy is inextricably linked to the author’s insistence on deciding next actions on every open loop. While advance planning seems like an obvious productivity strategy, Allen points out that most individuals and businesses fail to do it. Instead, they adopt back-end thinking once events have reached a crisis point where they must be dealt with. This approach not only causes stress but impairs clarity of thought, summed up in Allen’s analogy of “bailing water in a leaky boat” while, at the same time, trying to steer it (251). Front-end thinking allows individuals to feel in charge of their fate rather than being at the mercy of it.
A key theme in Getting Things Done is the correlation between practicality and productivity. Allen recognizes that if a system is easy to implement, individuals are more likely to commit to it. The author relates this idea to several areas of his methodology.
Allen shows psychological insight into working habits through his guidance on ease and efficiency. For example, he recommends keeping capturing tools (pens, pads, etc.) close at hand in all locations, as open loops often cross the mind at inopportune moments. As Allen points out, failure to capture an open loop when it arises inevitably leads to having the same thought again—a waste of time and energy. The author’s approach to setting up a filing system is similarly user-friendly. He recommends an automatic labeler and advises storing reference folders within arm’s reach of the desk. This advice demonstrates Allen’s realistic assessment of how much effort a person is willing to exert for administrative chores, such as filing. He asserts that if such tasks cannot be completed within a minute, “[y]ou will resist the whole process of capturing information” (97).
Allen also suggests that despite increasingly indistinct boundaries in the outside world, it is both practical and productive to impose limits around work. Throughout the book, he reiterates the importance of setting and maintaining boundaries. Allen’s organizational system involves constructing “hard, clean edges” (251) around work both “visually and psychologically” (49). This defining process begins by identifying exactly what “stuff” is from the amorphous mass of incomplete tasks that clutter our heads and physical spaces. It is reinforced by the practical activity of setting up workspace boundaries—taking ownership of one’s desk, clearly labeling one’s files, etc. Allen also creates strict boundaries around working practices: for example, his rule on never returning items to the in-tray. Carving clear limits around work allows individuals to feel fully engaged on a specific task and be their most productive without the nagging worry that they should be doing something else.
Of all Allen’s methods, the “magic” two-minute rule best encapsulates his attitude toward ease and efficiency. The author convincingly claims that two minutes is “the efficiency cutoff” point for deciding and tracking next actions (135). For this reason, if an action takes two minutes or less to perform, it is easier and more practical to undertake it immediately. Allen claims that adopting this habit alone “creates a dramatic improvement in productivity” (135)