Thursday, January 6, 2011

Concepts

I’m taking a new approach to developing organisational and productive systems, in the form of concepts. Simply put, a concept is an idea which can be implemented system wide, as a system component, or other integrated “cog” which should improve the system as a whole.

For example, one of the first concepts for Project Org-Fü/GTD (TooShéy Edition) is the “Plain View Notification Concept”, which can be described as a way of keeping events, tasks, task progress and other important reminders constantly visible for easy, frequent notifications as to what has to be done, what’s being done, and what one should be planning to do next (this particular concept is detailed to the point of specific examples and diagrams being used, so I shall refrain from discussing it at length before I see the idea implemented in a way that fits the concept). 

The reason I pass all this onto you is that I believe that not only the thoroughly engrossed GTD enthusiast has use for planning concepts before use. If you were to think about what might work for you before you go ahead and implement what you think might work for you, you might find yourself saving lots of time that would otherwise be lost to cleaning up the failures of hastily implemented system components, and removing said components altogether in some cases.

In a nut shell, use concepts to plan the use of something before you go out and try to do it without thinking twice.

Notes

  1. makeitmanageable posted this