Help creating meaningful tasks and at the right level

I'm somewhat new to GTD, but I'm eager to learn. Hopefully, I don't ask too many dumb questions. I am stuck creating tasks in a few ways:
  1. 1. How detailed should a task be? Lets say I want to learn to cook Japanese food. Which one of these is a valid task?

    1. find recipes (by looking in multiple locations)
    2. read a cookbook
    3. find a recipe in a cookbook
    4. find 10 recipes in a cookbook

    I think the process states that if a task can be done in
 
Next Action definition.

i'llgtd;100320 said:
1. How detailed should a task be? Lets say I want to learn to cook Japanese food. Which one of these is a valid task?

Next Action is the next visible physical activity required to move something forward. It should as granular as needed to not repel you and to not seem silly (for you).

i'llgtd;100320 said:
I think the process states that if a task can be done in
 
If this were me, I would start with a thought process like this one you have started:

(ie: buy tools, buy ingredients, try 1 type of sushi, try a second type of sushi).

So, let's say you need to buy ingredients and tools first. (You are one step ahead of me. I didn't realise you need specialist tools!) Neither of these are next actions because if you turn up at the store, you won't know what to put in the basket. You can't even put it on your errands list in case you end up at the store for something else. Maybe the second time you make sushi you can get away with that but right now you have no idea what you need to buy.

So, you need to make a shopping list but before you do that you need to choose a recipe (or you still won't know what ingredients to buy). Maybe you don't even have a sushi cookbook so before you can even choose a recipe you need to go to the bookshop. In that case your next action might be "Buy a sushi book" on your errands list.
 
TesTeq;100322 said:
Next Action ... It should as granular as needed to not repel you and to not seem silly (for you).

Well said, TesTeq!! That's going beyond a mere specification, and explaining why it's defined that way.
 
1. How detailed should a task be?

Try to visualize yourself starting to do this task. Describe the action in that scene. What do you see? None of the items on the list you included do that for me. You don't need to describe all steps but that first one should be as crystal clear as possible. The idea is to get rid of as much friction associated with starting that task up front, so that later when you see the item it is clear (without additional thinking) what needs to be done. So my rule of thumb is: Close your eyes and imagine it starting to happen. What do I see?

I could write all my tasks so small that they all take
 
Noel;100517 said:
If something comes up that can take less than the time it takes to capture, do it.

Definitely; however, the cutoff time (e.g. 2 minutes) should be longer, usually significantly longer, than the time it takes to capture. Capture might take about 10 seconds. David Allen suggests 2 minutes as the usual cutoff, and his reasoning is not just about the time it takes to capture.

If the activity you're interrupting to do the capture is extremely urgent, then the cutoff time might be close to the capture time; for example, if it takes 10 seconds to capture or 12 seconds to actually do the thing you might decide to capture, but if it takes 11 seconds to do the thing you might still just do it. However, normally the cutoff time will be much longer: capture might be 10 seconds and a 2-minute rule may still usually be most appropriate.

David Allen justifies the two minutes on the basis of whether it's worthwhile to capture the item, review it later at least once and perhaps multiple times, perhaps recopy it from one system to another, eventually erase it, etc. Whether this is worthwhile depends on a number of factors. It's not just a simple comparison of whether the total time spent capturing and reviewing the item takes longer than doing it.

Factors one can consider include: what does one gain by delaying? One can gain accomplishing some other, more important things first, and possibly even deciding never to do the captured item as less important. That can be valuable and is an important part of GTD. However, if you already know that the item is sufficiently important in relation to the stuff you usually do that you're just about certain to want to do it, and if what you're doing now anyway is not unusually urgent, then there might be little or no gain there.

There are psychological factors: I found when I started GTD that applying the 2-minute rule made me feel great, as if I'd been freed up and empowered and able to take first steps on a bunch of projects I'd been wanting to do. Adding an item to a list of actions makes the list longer and may add to a psychological burden. GTD is supposed to let you feel stress-free, but some people feel bothered by long lists.

There could be risks: occasionally I can't read my own handwriting or decypher my own wording. I lose a small number of items, and for some others I spend time figuring out what they are. At the time I figure "I'll understand this", but later I'm in a different frame of mind. One could also misplace a notebook or run out of batteries on an electronic gadget.

You're going to eventually do the thing anyway and it will take as long as it takes, so the choice is not "do this or capture it"; the choice is "do it now, or capture it and also review it and do it later", which takes more total time. The added time is not automatically justified just because it's slightly less than double the time it would have taken anyway. It has to be justified by actual added value due to doing other more important things first. In most cases, I believe, the capture time would have to be a small fraction of the doing time in order to justify capture rather than immediate doing.
 
I would define the project as "Learn to make Japanese Food", and the first subproject is "Sushi". So in my project plan I would brainstorm and write possible actions for making sushi. Some of these I can do straightaway, and I could pick one or several as the next actions.
If I were making sushi, my next actions could be:
- Check Youtube for how to make sushi (context Home Computer)
- Buy recipe book for sushi (context Errands)

You mentioned a possible action as "find recipes (multiple locations)"
Try and keep the tasks specific to a specific context. Finding a recipe in a book you are buying is on the Errands context, but finding a recipe in a book you already have at home would be on the Home context. Finding recipes on the internet would be on the Computer context. Note that you could have all three of these on your lists at the same time, it doesn't matter how many actions you have on your list as long as they can all be done next. Buy ingredients requires a recipe first, and is not a next action (unless you already have one).

< 2 minutes to find a recipe? Do you really think so?
 
Top