Thank you Christoph for this relevant advice.
Olivier

Le vendredi 23 octobre 2015 00:24:41 UTC+2, Christoph a écrit :
>
> Am 22.10.2015 um 18:57 schrieb John . Smith: 
> > How do you run your Goals? 
> > I confess that I haven't got a good control of my Goals... 
>
> In MLO, you would create the goal either as a task or a project (if it 
> is a "completable" goal), or as a folder (if the goal it is not really 
> "completable", like "becoming a better father to my kids"). 
>
> MLO does not have specific indicators to distinguish goals from mundane 
> tasks other than the hierarchy. The goals are usually the items at the 
> top level of your hierarchy, the sub-goals and tasks to achieve the 
> goals are at the lower levels. You might want to create special flags 
> for marking important goals. 
>
> When the term "goal" is used by the MLO, it really means a "timeframe" 
> (and it would have been better if they replaced the term "goal" with 
> "timeframe" throughout the program). The view "goals" is particularly 
> confusing, because it does not show only goals, but all tasks grouped by 
> their timeframes. 
>
> The purpose of the "week", "month" and "year" indicator is only to help 
> you in scheduling your tasks (all tasks, not only goals). Every evening 
> (or morning), you go through your tasks marked as goal for the week, and 
> mark those you want to complete the next day with a star (for "to be 
> done today"). During the weekly review you will look at all your tasks 
> marked as goals for "month" and change those that you intend to do the 
> next week to "week". During a monthly review you will look at all the 
> "year" goals and change those for the next month to "month". Also, a 
> weekly goal boosts the computed score, so it appears higher in the todo 
> list, and it is also marked with a red exclamation mark so it really 
> sticks out. 
>
> The timeframes of "week", "month" and "year" are tentative and not 
> absolute. You set absolute dates on tasks only if necessary, otherwise 
> you determine their order by importance and urgency only. 
>
> The urgency setting and the week/month/year setting are in fact 
> overlapping, and I think that is a design flaw, since it forces you to 
> enter redundant information, and makes it possible to enter 
> contradicting values (for instance a goal for month with a lower urgency 
> than another goal for year). Anyway, the urgency setting is useful for 
> the fine grained ordering, the timeframes are for the coarse scheduling 
> during the reviews. 
>
> You can also set "review" dates. This serves to re-evaluate the 
> timeframes you gave to your tasks at the given review dates, since your 
> priorities can change over time, and some tasks become irrelevant if you 
> just wait long enough. Depending on how "stable" you think a assessment 
> of the task is, the longer you can set its review interval. It is also 
> useful for those tasks that do not have any timeframe at all (the famous 
> "someday/maybe" list). At the review date you will have the chance to 
> decide whether a "someday/maybe" task should become concrete, within a 
> timeframe of year, month or week. 
>
> This is how I'm using MLO, in the hope this helps other users. 
>
> -- Chris 
>

-- 
You received this message because you are subscribed to the Google Groups 
"MyLifeOrganized" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/mylifeorganized.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/mylifeorganized/6f001330-6955-412e-a756-8b59901d56e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to