| Subcribe via RSS

Why Pragmatic Business Process Management

March 30th, 2010 | No Comments | Posted in Pragmatic BPM, Pragmatic BPM Case

It might seem obvious, that the greatest benefits can be reaped from complex business process management focusing on the core processes of a company. This however would imply that they haven’t really been optimized. Being at the center of the business, this doesn’t seem likely.

Especially when taking the pragmatic BPM approach, non-critical processes make a convincing case for process automation. Extensive planning and alignment efforts account for a majority of the BPM project costs. Cutting these to a minimum provides a clear advantage to the pragmatic approach. Being able to automate processes faster and with less effort allows companies to benefit from improvements earlier and generate even greater profits.

While there are good reasons for strategic BPM, pragmatic BPM requires attention to identify the  greatest benefits  BPM can bring to a company. Let’s have a look at an example.

Consider you have to hire new people constantly and your staff is spending more time writing rejection letters than working on tasks for new or existing employees. Applicants are calling in all the time for inquiries on the status of their applications, why they haven’t heard anything yet, or even if their application arrived. Setting up a process can take up as little as two days to have the process automated – from application entry, automatic confirmation, evaluation and automatic rejection. No integration necessary, implementation without coding and with the ability to change routes, recipients, rules, etc. within minutes. The HR team can now focus on the important tasks of selecting the right applicants, scheduling interviews or even setting up new employees in the company. While the process obviously doesn’t cover the whole application process nor all options possible, it provides tremendous value and can be extended at any time.

There are clear benefits and we will have a look at them in detail in the following post.