Process model

In order to be able to visualize your processes, you need to build sequences and structures from them. A process model must describe why, what, who and how through activities that are performed sequentially to satisfy a need. The processes contribute to a natural focus on improvements, as they are a meeting point between the demands placed on the business and the internal capability.

The process model describes cross-functional flows

For good readability in a process model, it is important to always have one or more inputs and equally important to describe what the result of the process will be. Input can be both what is to be further refined and what triggers something to be carried out.

The expected result from an activity is usually input to the activity that follows. By visualizing the result from an activity, we achieve clarity that it is the same output as input between two activities. It also ensures that all results are taken care of, in this or other processes, which is easy to miss if you only map the activities.

In addition to the activity flow, roles and positions are used in the process model to describe who is responsible for a certain activity.

You can read more about the different object types available in 2c8 Apps in this FAQ: Which object should I use in which context?