GTD

Table of Contents

1. GTD

1.1.

1.3. Definition of GTD

1.3.1. GTD turns stuff into next actions

  • GTD is a system that turns stuff into next actions aligned all the way up to your purpose & principles

1.3.2. GTD is Lean for the brain

  • GTD is “Lean for the brain.” That is, no wasted thinking

1.4. Reviews

https://gist.github.com/mwfogleman/267b6bc7e512826a2c36cb57f0e3d854

  • daily: tasks
  • weekly: projects
  • monthly: goals
  • annual: vision

1.5. Principles

1.5.1. Treat the calendar as sacred

If you write something there, it must get done that day or not at all

1.5.2. 2 minute rule

If the next action can be done in two minutes or less, do it now

1.5.2.1. Apply to all tasks

To more “social” task, e.g. talk to somebody because you like something about him/her
To generate spontaneity

1.5.2.2. When does the 2 minute rule not apply?
  • When you’re processing emails coming back from vacations
  • Before going to sleep
  • Before leaving

In these situations you chain a lot of task that are not worth the effort
If you do not follow the 2 min rule, it creates (to me at least) a lot of psychological noise that prevents you from moving, doing things

1.5.3. Review is essential to build feedback onto your system

1.5.4.

1.6. GTD for teams

1.6.1. The rise and fall of GTD

https://www.newyorker.com/tech/annals-of-technology/the-rise-and-fall-of-getting-things-done
https://webcache.googleusercontent.com/search?q=cache:LbmYDMToHe8J:https://www.newyorker.com/tech/annals-of-technology/the-rise-and-fall-of-getting-things-done
https://news.ycombinator.com/item?id=25131848
I think Newport is absolutely right about the chaos and distraction that characterizes so much white collar work today. I’m not sure how fair it is to lay it at Drucker’s feet. My view from the software world is that there are twin gaps in strategy and leadership in most organizations.
Strategy provides the framework in which groups deploy tactics. Leadership provides the framework in which groups adopt tactics to deploy.

1.6.1.1. “The Rise & Fall of GTD” Controversy | Revue

1.6.3. When, which … Design Thinking, Lean, Design Sprint, Agile? | by Geert Claes | Medium

1.6.4. How to apply Someday/Maybe to teams?

  1. Save for yourself only, in your personal notetaking system
  2. Save in a common task, but then clutters the backlog and has bad discoverability (better in a PKM)

This is (?) because Someday/Maybe is between actionable and non-actionable info?

1.6.5. GTD and Teams - Getting Things Done®

1.7. GTD for Emotions

1.7.2. Why making my tasks emotional increased my productivity

Getting Things Fun (GTF)

“emotional contexts”
How will doing or completing this task make me feel?
The question works even for the nastiest tasks. In fact, completing an awful task often offers the greatest emotional payoff.

-—

  1. Make the emotion dramatic. I’ve used “triumphant”, “massive relief” etc. This increases the allure. It also helps rule out tasks you shouldn’t be putting on your list in the first place. If you’re adding a task that’s not important, difficult, helpful or nasty enough to deliver more than neutral feelings on completion, you think twice.
  2. Experiment with fun and fear. At the moment, all the states or emotions on my list are positive. But I’ve had some success using terms like “avoids physical and psychological meltdown”, “keeps you on the right side of the law”.


Examples from my melodramatic to do list

  1. Triumphant: Client pitches, investment presentations, hiring plans. Mission critical stuff.
  2. Supremely satisfying: Inbox zero (aided by Tony Hsieh’s lovely “Yesterbox” technique), making a tricky phone call, research.
  3. Massive relief: Tax return, sorting out insurance, booking flights.
  4. Highly helpful: Intros, advice, intros, intros.
  5. Basic decency: Thank you notes, keeping promises. I’ve found this list surprisingly revealing. It shows the conflict between two things I value greatly: generosity and integrity. I tend to promise too much. Seeing my impossibly long list in “basic decency” helps me avoid over-promising and jeopardising integrity.
  6. Delight: I’d been meaning for ages to get a print of Raphael’s School of Athens for my office, calling a friend out of the blue.
  7. Fit for Battle: A daily run, 10 minute morning meditation. (I’ve been reading books on war recently, hence the description.)

=
Critically, in unearthing a task’s emotion, I’ve learned I have first to find the associated “Why” of the task. Emotions need a why. And “Why to do” to is always a better place to begin your day than “What to do”

1.7.3. GTD in Stoa 2022, David Allen more focused in the spiritual/philosophical

1.7.3.1. The magic of the mudane → GTD to become who you really are

GTD allows people to become, to unlock more of who they really are

1.7.3.2. The only thing that moves as fast as the world is you

the only way to catch up to it is relax, let go, be present; then you’re going to be as as fast as the world and as complex as it is

1.8. GTD critique

  • Other frameworks such as Zettelkasten are better suited for research, which is non-linear: you search for a topic, then you realize there are more angles and nuances to the discussion and now your tasks/priorities have changes

1.8.1. Defined Outcome does not apply in a Complex domain

Cynefin
Since you don’t know how your end result looks like (as in a complicated domain), only where do you want to go
Instead you have Vector theory of change

1.8.2. GTD is over complicated, use Bullet Journal

I think the GTD model is bullshit and over complicated. My model is the Bullet Journal model. The fundamental idea wrong with most people and their todo setup is this: you write todos but they get stale, and then you come into your todo app and you see all this shit you don’t want to work on, and isn’t as important to you as the stuff in your head.
It becomes a hassle to update your todos not only in terms of effort, but also because there are todos on your list which on paper have higher priority, but you don’t want to do them, so philosophically you cannot remove them.
The idea with Bullet journal is this: Every day you start off with a clean slate. So let’s say I jotted 10 todo’s yesterday. If I didn’t complete them for whatever reason, I start the next day fresh… so I never run into the stale problem people run into. I can literally ignore everything I’ve ever written and just write todays date, write some stuff I want to get done, and then I get to it.
If some of the todo’s from yesterday I want to get done, I just copy them over. Simple as that.
If there are some todos I want to do but there not super high priority, I bump them to a Monthly log (right now just talking about daily log). I view this every now and then once my high priority stuff is knocked out, and I can move these to my daily log anytime. And if I know I want to get something done but not this month, I move it to my future log. That’s it.
Bullet Journal outside of that is whatever you want it to be. So you can create “projects” but then just link to the project in your daily / monthly log if there’s a part of that you want to accomplish. If you want the context aspect similar to Omnifocus, you can obviously add that to org mode.
So that’s it. The fundamental problem with most people’s todo stuff, is combating STALENESS. Change your setup so you essentially factor that out.

1.9. Complementary to GTD

1.9.1. Making it All Work: Winning at the Game of Work and the Business of Life - YouTube

Practical tricks to implement GTD after having read the book, but also deep-dive in horizons of focus

1.9.1.1. https://www.goodreads.com/book/show/3338850-making-it-all-work

Getting Things Done contained a lot of useful information, but was deeply lacking in some places: the horizons of focus, for one, were mentioned, but not really expanded on, and I was left with the feeling I was supposed to be engaging on another level without really knowing how. GTD’s shortcoming, though, is where MIAW shines, however.
I’d highly recommend both books: GTD is wonderful for people who have some idea of where they’re going but need help taking control of their projects and dealing with the huge pile of unsettled stuff that can accumulate in their lives, while MIAW is really great for those of use who have no clue what we need to be doing and why, while still providing the necessary tools to deal with that terrifying stuff-backlog

1.10. GTD Project Support Materials (pg167) vs Reference (pg178)

Both are resources in PARA. What’s the difference?
I’ve come to think of Project Support Materials as what would be “Projects” in PARA and Reference as “Resources”
I like to mix reference and projects (in org-mode files and in folders too)
Reference is like(?) Archived Projects, if it’s not related to an ONGOING project
Project support belongs to an ONGOING project

1.11. GTD Goals? Why not projects?

Is strange that in GTD Goals/Objectives are like projects (goals are defined as project that take more than 1 year to be completed)
They are all projects, but taking the time to clarify goals starts to pay off if you estimate that the project will take longer than 1 year

Author: Julian Lopez Carballal

Created: 2024-09-16 Mon 06:51