How-to... Principle of process construction

TaskPack is the basic building block of the process.

A process is made up of interconnected TaskPacks.

Interconnection of TaskPacks

TaskPacks are interconnected by their results. Each TaskPack has its own result.

> First TaskPack delivers its result.

> Second TaskPack receives that result as its input.

> Second TaskPack executes its tasks on that input. Creates an additional new value and delivers it as its result to the third TaskPack.

> The third TaskPack receives that result as its input.

And so on, the process continues with the execution of Task Packages until the finished product or service is provided.

Simplified example

Imagine the process where we need to make a wooden toy for a child.

Lumber

Wooden Toy

Let's say that the process starts with "receiving" lumber and finally delivers a finished wooden toy. In the example, it is necessary to successively execute 4 interconnected TaskPacks A, B, C, and D, and the tasks in them. Thus we would complete our process and produce a wooden toy.

TaskPack A): Formatting of lumber	TaskPack B): Shaping formats
Tasks:	Tasks:
Receive the lumber.	Receive formatted material.
Cut the lumber to the size that is suitable for further processing.	Cut the material into the shape of an elephant.
Mark the formatted material and place it on a separate pallet.	Pack the cut-out toy shapes into smaller boxes.

TaskPack C): Sanding shapes	TaskPack D): Placing graphics and packing
Tasks:	Tasks:
Receive a box of cut-out toy shapes.	Receive a box of sanded toy shapes.
Sand the edges and surface.	Transfer the graphics (eye and ear) to the toy.
Return the sanded toy shapes to the box.	Wrap the toy on paper and put it in the sales package.

This example shows how four TaskPacks (A, B, C, and D) are interconnected by handing over results. With that connection, they build a process.

Note: this example of constructing a process is very simplified.

TaskPacks are interconnected with handover tasks

We notice the following:

In the beginning, each TaskPack has a task with a particular role to receive the result of the previous TaskPack.
In the end, each TaskPack has a "specialized" task to create its final result and make it available to the next TaskPack.

We call these tasks handover tasks. TaskPacks connect with each other and build processes with them.

Note

Here, the basic principle of how TaskPaks are interconnected and how they build a process is presented.

In reality, many rules and finesse are used to construct the process. That is why it is good to first focus on TaskPack as the basic building block of the process and then in more detail on the construction of the process itself. In this way, processes can become the driving force of the business, not just documentation of how work is done.

No sequences were mentioned in the example. They are used when a process contains a large number of TaskPacks.