Home > Forum > Processes > Best Practice for Defining Process Boundaries

Best Practice for Defining Process Boundaries
0

Hi everyone,

We are working on a consumer lending process.

Before submitting an actual loan application, a customer may go through a consultation stage during which they receive information about the bank's terms and a pre-contractual information document.

After the consultation, the customer may:

* submit a loan application immediately;
* return later and submit an application;
* never submit an application at all.

Our question is:

From a WEBCON BPS modeling perspective, would you treat the consultation as part of the lending process (an initial stage of the same process) or as a separate process that may later lead to the initiation of a lending process?

We are interested in how you define the boundary between these two business cases and what arguments you would use in support of either approach.

MVP

Hi Yordanka,

I prefer to have multiple smaller processes and in this case I would split the two business cases as I assume that the lending process will consist of multiple steps too.
In addition, there are multiple options how the consultation may end and it can be confusing for the customer. Every ERP system I know also splits quotes from orders, this would be similar.

In general I would take a look at:
- Privileges
- Are "internals" shown which shouldn't be visible
- KPIs / Reporting
- Complexity
- Timers / how many versions would be create for a workflow instance
- Starting points
Maybe the lending process could be started from another system without the initial consultation.

Best regards,
Daniel