[MLO] Translation of blog.kurganskyi.in.ua/2021/03/30/priority-of-task/

[Mario Seixas Sales]

Planning System Based on MyLifeOrganized

Publication Date: 18.06.2021
Author: Oleksandr Krayovyi
http://blog.kurganskyi.in.ua/2021/03/30/priority-of-task/

A well-tuned mechanism, where all weak links are addressed, and everything 
is clear as day. It's time to share my planning system, which I've been 
using for many years. In some ways, it resembles the American 
Constitution—new additions appear over time, but the foundation remains 
unshakable. All elements are time-tested, refined, and reliable. Nothing 
superfluous. Nothing without explanation or rationale.

Reading forums, I often encounter users' "reinvented wheels." I have 
nothing against it. If it works for someone, that's the beauty of 
MyLifeOrganized. Everyone customizes it to their needs. However, my 
personal belief is that such "handmade" systems can be daunting for 
beginners:
* They scare them off
* They seem overly complicated

This became another reason for writing this article: to show new 
MyLifeOrganized users that the system and product can be understandable and 
convenient, to share my insights and approach with experienced users, and 
to demonstrate the unique capabilities of MyLifeOrganized to those still 
deciding on a planner.

"Let's go!" as cosmonaut Yuri Gagarin once said...

Contents
1. Settings: There are many, but you set them once and that's it!
2. Basic Concepts: What is what?
3. One-time Task
4. Recurring Task
5. Project
6. What I Record in Project Notes
7. Project Statuses - The Basis of My Weekly System Review
8. Goals
9. Review - A Tool for Displaying "Someday" Tasks
10. Reference Information
11. Task Tree: A Complete Life Display
12. Contexts, Flags, Text Tags: Why So Many?
13. Active Actions: Main Working Lists
14. Principles of Working in My System
15. How to Form the Right List for the Current Situation
16. Are You Satisfied with Your Planning System?

Settings: There are many, but you set them once and that's it!
MyLifeOrganized has a lot of properties. Often, I see people using them 
without understanding their purpose or benefits. They just use whatever 
comes to hand. Hence my rule: Assign specific properties to certain types 
of tasks to quickly create a simple list of tasks, projects, and 
information with the necessary sorting. It's essential to understand the 
purpose of each property:
1. Which tasks to assign them to?
2. What does it provide?
3. How will it be applied or used?

In my courses, I always draw an analogy: Assigning properties to tasks is 
like the amount of sugar in tea:
1. The optimal amount is individual for everyone.
2. If there's too little sugar, it feels like something is missing.
3. If there's too much sugar, it feels cloying and uncomfortable.

By the way, there are properties I don't use at all. But this is not due to 
ignorance of their purpose, but my conscious choice. I understand that for 
you, these might be some of the most important properties. To make it 
clearer, I'll give an example of how I analyze properties. It's enough to 
give each value a definition that leaves no room for ambiguous 
interpretation. For example, a deadline. What is it? A deadline is a point 
after which it either makes no sense to complete the task, or certain 
consequences occur after the given date or time (financial loss, letting 
someone down, damaging relationships, etc.). A deadline is assigned only to 
tasks that have one. To determine whether to assign a deadline to a task, 
ask: What will happen if I don't complete this task by the assigned 
deadline? If nothing significant (in my understanding) happens, no deadline 
is assigned. These tasks can be important, urgent, "for yesterday," "for 
the day before yesterday," which will also affect their weight in the list 
of active actions. But they don't have a real deadline. This approach helps 
avoid a large number of overdue tasks, especially those with low priority, 
which undoubtedly affects internal calm and trust in the system.

Assignment: Try to define with unambiguous interpretation what urgency, 
importance, start date, and other properties mean to you.

Basic Concepts: What is what?
One-time Task
In reality, there are very few one-time tasks, especially those that fit my 
definition. For me, a one-time task is one that has the following 
characteristics:
1. Can be completed in one go at one location.
2. All necessary resources are available.
3. Completing the task does not require further development.

Each of these actions is self-sufficient. Done and forgotten! It's 
important to distinguish one-time actions from project sub-tasks. For 
example: scheduling a meeting with a client. It can be done in one go at 
one location. All resources might be available. But the process doesn't end 
there!

Recurring Task
Such tasks can be called areas of responsibility. Their main purpose is: 
What and how often should be done to keep life under control and prevent 
crises? This can also be called crisis prevention. Given that recurring 
tasks 

[MLO] Re: What's new in MLO 4.4.0 for Android

[Grant]

Thanks Alyona and team!  Good to hear form you.  Nice improvements!

On Friday, May 10, 2024 at 5:32:35 PM UTC+2 Alyona (MLO Support) wrote:

> MLO for Android has received a minor update - learn more on our blog 
> 
>

-- 
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 mylifeorganized+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/mylifeorganized/7dd2653a-fd9a-4cc6-b6ca-0d8d57915fefn%40googlegroups.com.