KGTD Tutorials

From 43FoldersWiki

Jump to: navigation, search

Kinkless GTD is a set of Applescripts written for use with OmniOutliner Pro designed to provide a useful toolset for people seeking to implement a GTD–style workflow centered around a contextualized list of next actions.

The software has already been described several places in this wiki and on the 43Folders main site. This page and it's offspring are merely an attempt to provide some tutorials describing the use and features of Kinkless due to popular demand for better documentation.


Contents

[edit] About the Tutorials

These tutorials assume the user is already familiar with GTD and at least a little familiar with OmniOutliner. They also assume the user has installed Kinkless by following the installation instructions.

Note that there is no one-and-only way to use Kinkless. Like GTD itself, Kinkless is flexible. You should explore it thoroughly, looking for ways to use it to your own advantage.

These tutorials are early works in progress. Contributions are welcome.

[edit] Introduction to the Kinkless Environment

Before we start using Kinkless, let's take a look around at the Kinkless document, starting with the Utilities drawer. As you can see, our Kinkless document is already separated into some sections. Each of these sections serves a specific purpose and will be used in a different way in our Kinkless workflow.

I've highlighted the first three sections in Figure 1-1 — Inbox, Projects and Actions. Most of your time spent using Kinkless will inevitably be in these three sections.


  • The Inbox is a staging area for new actions and incoming thoughts. You can add new tasks to this section prior to assigning them to a project or context. This is useful when a sudden brainstorm hits and you realize you need to do something, but you don't yet know how to categorize it in your GTD system. This area is also often used by other applications when adding new tasks to your Kinkless document — for instance when using Quicksilver integration which will be discussed later. Not everyone makes use of the Inbox section, but it may prove useful to you depending on how you setup your Kinkless workflow.
  • Projects is an area for defining and planning the actions of your various projects. For many people, the bulk of their Kinkless editing occurs in this section. Here you can define new projects, add and edit actions within projects, order those actions in a sequence within those projects and just generally get a clear picture of what your projects look like and what you need to do to finish them.
  • Actions is an area for viewing only currently active actions organized by context. For many people, this is where they actually Get Things Done. The Actions section lists all of your currently active contexts (contexts that have uncompleted actions in them) and the next actions for your projects in those contexts.

The beauty of Kinkless is that it keeps these three areas (and others) in sync with each other so you don't have to. Every time you hit the Sync button in the toolbar, Kinkless will check all of the areas for changes or new projects/actions and update the other sections with those changes. This means that once you create an action in your Projects section and assign a context to it Kinkless does all of the work of organizing your context–specific action lists so you don't have to. This syncing works both ways too. Changes and new actions created in the Actions section or the Inbox will be synced back to projects and to each other as well.

So now that we have a broad overview of Kinkless, let's see some step by step examples of using it. Unless otherwise stated in the tutorial, I'm going to use the default Kinkless and OOP settings in my initial examples. I will also be using the default contexts that Kinkless comes preconfigured with. After stepping through the basic examples, I'll describe the steps necessary to customize the context list and then go over some of the other features, sections and settings of Kinkless.

[edit] Kinkless Tutorials

This list is just an idea of where I'd like to go next. It may change (especially if someone else contributes) and is still a work in progress.


Personal tools