As we stated earlier, BPMN cannot define how to handle data.
Neither can it define the position or authority of members who execute the business processes.
BPMN also tolerates ambiguous representations of process flows.
To go even further, we would have to say that it is quite possible to draw one business process in multiple ways.
Also, in order to define the detailed specification of a business process, you might need to use separate documents.
In some cases, you might even want to separately summarize the consideration about risks that a business process could suffer from.

However, BPMN business process diagrams can intuitively communicate business processes to many viewers.

Furthermore, by using software such as BPM suites, an organization can grasp the actual process status, including the current situation or the results of a particular time period.

The reasons for learning BPMN differ greatly on the person, but you might want to first consider which of the above goals fits your purpose.

Of course, there is no better way than learning together as a team sharing the same goals.

Not that you could see it in the first place.

Finally, our last chapter together. We find it hard to hold back our tears at the thought of you reading thus far; we can hardly see your face.

The source of a company's competence is in its business processes.

A company must continuously modify its business processes.

And a company must keep on understanding and sharing its ever-changing business processes.

We highly recommend promoting Business Process Management using BPMN, instead of relying too much on the knowledge of long-time employees.