Thanks for the reply - I missed it, but will now subscribe to the thread.
Quote Originally Posted by dalewking View Post
But here many apps follow this exact model of a list of projects which I think is an implementation rooted in paper based system. I call this idea of a single list of projects "heavyweight". The action of making a project here provides some mental resistance. You ask yourself, "Do I really want to make a project for this thing that requires 2 steps?" Unless a project feels big enough you find yourself resisting making projects. Just making projects hierarchical would at least let you bury those smaller tasks instead of having all equally visible.
Being new to GTD I don't want to jump to the wrong conclusions, but I like the option to have these projects or just simple actions. If I know something requires just 3 actions, I'll just write those down. But if I didn't have the option for projects and sub-projects, I could have so many actions staring at me I'd be a mess.

There are other systems where a project is no big deal. It is just a task with sub-tasks. There is much less mental resistance to creating projects here. Some examples are Smthngs and MLO where projects are easier.
Yes that sounds good.

But am I wrong to be thinking I need projects and sub-projects? Is that against GTD?

Thanks