Human beings fail...
Failure teaches success...

Anyway, every time you failed, reflect on it. Try hard to prevent recurrence.

Seriously, "Cases of Failure" are 'very important knowledge' for a company. Who and how made the mistake? To share the 'facts' and maintain them to be referred anytime. It doesn't mean to blame a person for the mistake, but to make it a good teacher for not to make the same mistake again.

When the time you looking back a year, or new comer comes, or at the time changing Workflow, it should be good to hold a "looking back Mistakes and Failures meeting".

[Reflection Report flow]

There is a service of 'notification' by email whenever paid into your bank account. But the 'notification' data is not enough at all, for unmanning task of checking invoices to match the payment (Clearing) .

Well, actually it is true that there are many cases of payment confirmation that needs flexible judgment by human, such as 'the phone number of payer' is different than registered, etc. So, it is righteous to put more manpower for checking task. It still is future story, that API connecting to bank account.

But, however,
Yet, we want improve this Clearing task anyhow even a bit. Still too much waste. More than that, to prevent mistakes, omissions and leakage is important. Now, let's think about it.

We would like to think it is problem of business process, rather than blaming the personnel in charge.

[Payment Confirmation flow]

Even abstruse business processes, can be understood by anyone looking at the flow chart of the business(flow diagram)!

Among variety of 'Flow diagram writing', the advantage of "BPMN, method of drawing Workflow" is people can understand just by looking at it even they don't know the word of BPMN.

Recently, not only for companies but, even in government agencies and voluntary organizations, the case of to take advantage of BPMN to review business has been increasing rapidly. It is well-received for "easy to learn to work" to newcomers such as rookies and personnel reshuffling. It is quite reasonable to give priority to BPMN than business manual.

1. Draw in BPMN to exactly share in-house, even if it was a simple business process.
2. Build information system by using defined BPMN. (BPM tool)
3. Furthermore improve business process based on the results of operation of the information system.

By the way, surprisingly it is difficult to operate business process which need to be "in conjunction with paper". Here, we would like to think about "Expense Reimbursement Application" which typical of those 'business in paper'.

※ BPMN: Business Process Modeling Notation (1.x) / Business Process Model and Notation (2.0 and later)
Rules of notation for visualizing business procedures easy-to-understand showing in the drawing. A modeling method that is effective to describe 'series of business process' which multiple human (or machine) involved. It has the feature such as 1. Can be understood at first sight by the people who are not IT engineer, 2. Directly related to system implementation. Fundamental technology of Business Process Management tool. We are using BPMN method in "Workflow Sample" that providing template of business flow.

[Expense Reimbursement flow_Digital Receipt]

Workflow 'A' calls Workflow 'B'.

"Connecting Workflows" is one of the real thrill(??) of high-performance workflow product. It enables to pass business data from 'Process of Sales Department' to 'Process of Manufacturing Department' without any leakage of data. (If you are a Cloud Worker of Google Apps,etc.,Cloud-based Workflow would suit you for handling business information.)

See Workflow Start Another Workflow Automatically during Processing

However... It sure is easy to connect when that is clear about upstream process or downstream process such as 'Sales flow' and 'Manufacture flow, but in cases that continue to connect each other, difficulty goes up straight away.

In terms of Software Engineering, they are "Waterfall model" against "Spiral models". Moreover, for example, in such as "Advisory Contract" or "Maintenance Service", the cycle of "Service delivery" and the cycle of "Continuous orders" will circulate in parallel. That is, the Sales sector is moving toward the next orders, concurrently the Service sector is processing their service delivery. (Double Spiral?)

For such case, we would like to introduce to you how to make 'Parent process cycle' as "Orders Process" ,and 'Child process cycle' as "Service Delivery process".

[Circulating Orders Flow]