GTD projects) and OmniFocus projects with a type of “single actions” as “single action lists” (i.e.
In this article, I’ll refer to parallel and sequential OmniFocus projects as “projects” (i.e. OmniFocus projects with the type set to “single actions” are used to group related items and can be empty. They’re intended to be used for working towards defined outcomes and are considered “stalled” if they don’t contain any actions. OmniFocus projects that are parallel or sequential are GTD projects. OmniFocus supports three types of projects: parallel, sequential and single actions. If you didn’t, a project such as “Find new garage” might be in order. For example, phoning the garage to make an appointment to book an oil change would likely be the next action, assuming you know where to take the car for service.
In GTD parlance, one-off actions that aren’t tied to a specific outcome are considered next actions. research airfare, book flight, phone travelling companion). planning for a trip to Vancouver is complete) and requires multiple actions (e.g. For example, “Plan Trip to Vancouver” is a project as it has a defined outcome (i.e. It’s important to understand the difference between a project (as defined in GTD) and a single action list.ĭavid Allen describes a project as a defined outcome that requires at least two discrete actions to complete.
We’ll also look at how consistent naming conventions can help you quickly locate related projects and how emojis can be used to add some visual flair. In this article, we’ll look at some best practices for naming projects and single action lists, drawing some wisdom from David Allen’s Getting Things Done (GTD) approach. Conversely, thoughtfully-named projects and single action lists visibly spring to life and encourage action. Project names that are vague and uninspired can make your system (and your life) feel drab and boring. The names you give to your OmniFocus projects and single action lists can have a major impact on your productivity.
0 kommentar(er)
