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. How detailed should a task be? Lets say I want to learn to cook Japanese food. Which one of these is a valid task?I think the process states that if a task can be done in <2 minutes, do it now. I could write all my tasks so small that they all take <2 minutes and therefore I should do everything now. What is the cutoff for a task?
- find recipes (by looking in multiple locations)
- read a cookbook
- find a recipe in a cookbook
- find 10 recipes in a cookbook
- So pretend I pick sushi. Sushi is complicated and hard to make - definitely more than 1 task and probably more than 1 project. I do want to document what I know. I think the next step would be to make a project called "Make Sushi". My next question: what are the tasks, knowing that at the time of project creation, I have a few high level tasks (ie: buy tools, buy ingredients, try 1 type of sushi, try a second type of sushi). Are they written as tasks in the project, knowing that they have multiple tasks inside them (ie: buy tools will really turn into identify which tools I need, learn how to use the tools correctly, go to store and buy them) or would I just make a separate project called "Make Sushi - Buy Tools"? I think, by the strict definition of GTD, I would make a project since it has 2+ tasks, but that would seem to make an overwhelming number of projects. I could have 5-6 projects just for sushi.
- How many of your tasks do you really write down? Is it truly everything? Are "Try cutting the sushi like <this>" and "try cutting the sushi like <that>" really tasks? It seems like I'll be spending a lot of time writing down tasks. I believe my system is efficient, but I can only write tasks so fast.
Thanks in advance for your input, and I hope you learned I really like sushi.