TOPIC: 6-Levels model functionality - initial design

This sounds good. I don't like the name 'motive' though. Can the users change this name according to their preferences? What is the time schedule for the feature?

Yes I now agree. I think we should just call them Goals.

We were thinking that an "Area of responsibility" was not really a goal, but to fulfill a responsibility is a goal.

At the moment I make "homeworks" in my little company and I have suggestion:

2 people have 2 opinions, 100 people have 100 ...
Because that - please give us the chance to setup own system.
The best way, in my opinion, is to add 2-3 Critreria to Projects and Actions (Area, Goal, ???) and allow filtering in Projects review in the same way like in Actions Review: In the options add Icon Project Screens (user defined tabs for predefined filers) and allow filtering in the same way like in Actions review.

Implementation of selection of 2 and more Topics, Areas, ... for 1 Project/Action can be little bit complicated, but can significantly rise usability of application. It is synergy: 1+1 >2 (For example 1 Action - skiing with son - realize more Areas, Goals: Fitness, Family, Father, ...

I agree. One of the many wonderful functions of ThinkingRock is its flexibility and customization that allows users to create the perfect GTD environment for them.

I fear that if you hard code the 6 level model with predetermined names you might turn people away from using it as they might not see how it fits into their system.

The levels will be user-defined and you can have as many as you want.

Jeremy would like to keep the levels within a hierarchy (for example a goal for "life purpose" cannot be under a "short-term" goal) but I think it is easier to leave it simple (for the coding as well) and don't enforce a hierarchy.

The SECRET of SUCCESS of TR is: simplicity, usability and configurability.

Dont change your winnig strategy.