Depth first - breadth first

[AGrzes]

-- Whenever you complete an action within a project, think what the next action is,
and often go ahead and do it right away; if not, write it on a context list.

I think it is right thing to do but the problem is that I tend to go least resistance route and chose action previously identified because it not require thinking.

I have set my system up that way I see every action that was finished but I did not take time to integrate results into system and determine next action but often I get back to it only during weekly review.

-- Set up a separate context for each project.

This is actually very easy, because I use digital system and I have project view on my action. But from what I understand about GTD context should actual limitations of what can be done instead of arbitrary distinction.

Sometimes, I will work for two hours on a single project if I want to, but it's rare for me to have a list of sequential next actions. I don't necessarily need or even want a list, because when I stop I tend to write a better fresh next action than I would have if I had "planned" things out.

Is not that I have specific list of preplanned actions for project. Often it is the other way round, I tend to have very short actions and only after they are done I can identify next. The problem is that I tend to do the easiest thing and thick of some other action that is already defined and I loose time and focus by switching mental context.