What creates the task? / Hebrew

What creates the task? / Hebrew

If you don’t chew a nut, don’t eat the kernels either

Earlier in the article “What is a task?” we described what mandatory attributes a task should have. Then they explained what the target result is. They told how to separate non-functional tasks and pseudo-tasks. The differences between the task and the goal and action were clarified. That is, they learned to identify tasks.

Now let’s examine what is generated by the task?

We will try to understand what becomes the source of the task? Where do they “grow” – take roots?

Thanks to this, we will learn to identify tasks as early as possible – near the sources. And this will allow us to build task generation algorithms in the future.

The task is generated by a problem (from the Greek. problema – an obstacle, difficulty, obstacles), that is, a meeting with resistance, an obstacle, an obstacle, difficulties.

Overcoming a problem (obstacles, difficulties) consists in formulating the need for its elimination, in the further search for a defect[1]which creates a problem and in choosing an imaginary way of influencing the object (or regarding the object) to achieve the desired final state and/or position of the object[2].

As written above in the article “What is a task?”, an imaginary image of a variant of an object is chosen – and there is a task.

And the desired final state and/or position of the object is the target result of the task. What we wrote about in the article “What is the target result?”.

So, the image of the variant on the object is known – this is a task, not known – a problem.

From here, the task arises as a problem.

If we turn to the explanatory dictionary, we will see that the Greek word “problema” has another meaning – task.

That is why I say that it is necessary to do it simply, turn the problem into a task and then carry out the task, managing the tasks, or rather the flow of tasks[3]since at every moment of time they are generated and executed in great numbers and of various types.

Thus, generating tasks is much easier than problems. That is, first you need to define a problem, then find a way to overcome this problem and formulate a task.

The output cycle: problem-task. It can be repeated cycle after cycle.

As a result, problems arise from task after task.

Well, it is clear that from all the above it follows that, if there is no resistance to the satisfaction of the need at all (that is, if there are no problems), there is no need to formulate and define the task, that is, no work is needed[4]. And neither physical nor intellectual.

The full version of the article is available in my book “Tasks are wonderful, or Kozyrna “TUZ” Motaeva!”

With respect to you and your business, Oleksandr Motaev

You can discuss this and other blog articles in our Telegram channel “Task Flow Management”.

[1] – I talk about the flaw further in the article “The concept of “problem”” in the section “The main essence of management – “TASK””

[2] – How this happens, I basically demonstrate throughout the blog, and how it is done algorithmically, I tell in the section “Task Management Technology”

[3] – What is a task flow, see the article “Task flow” in the section “Key one-time problem that prevents the increase of PIT”

[4] – About what “work” is in the context of a real blog, and how it is related to the concept of “task”, I will tell in more detail in the article “Work” in the section “Prerequisites for the emergence of the need to increase the productivity of intellectual work”

[5] – See the article “Principles of the Task Flow Management System” in the section “Task Flow Management System (UPZ System)”

Related posts