- [[{4.4b1} store next actions by context]], e.g, create context lists that “filter” your next actions by location, circumstance, or tool so you know what you are currently *able* to do. - i think people tend to interpret this as working only *within* a specific context list for a given work block – as in, they assume that gtd discourages working by project. - either is fine; contexts just help you figure out how to start, but you choose how to continue. - for example: - imagine you have the contexts `design software`, `phone`, and `email`. - and imagine project `design logo suite` has the next action `call client to discuss v1 feedback` on your `phone` list. - once you call the client, you might decide to make all of the other calls on your `phone` list. - *or*, based on the phone call, your next action for the logo suite project is to `increase font size per feedback`; you might complete that action, figure out what to do next, and keep going on this project even if next actions have changing contexts. - note that the second next action wouldn’t have been discernable without the first; this is how [[{4.4b} next actions in gtd|next actions]] differ from planning traditional tasks. - context lists aren’t meant to keep you *constrained* in a given context, but to make getting started easier by eliminating everything you *can’t* do at the moment.