Blog

Process Glue by

Great post by Craig Reid on “Process Glue” -

Whilst many pieces of software try to package themselves up to service a particular need – an ERP for example fitting the bill for many support processes – a BPMS succeeds because it doesn’t wedge itself into a box. BPMS tools focus on having the fluidity to design processes the way the business needs them without compromise. But more than that they are built to expect that change will happen, and as a result are designed to have flexible and adaptive business rules that can be altered faster than regular “off the shelf” systems.

Very true – BPMS has been competing on shifting ground over the years as packaged products improve or stagnate within organizations.  A BPMS can be the way to extract additional value out of a legacy system, or the way to disintermediate it from your business processes so that it can be decommissioned.

I like to think of a BPMS as process glue. Organisations will always have manual processes and disparate systems. These are the areas where work slips through the cracks, where time is lost, where customers are forgotten. A BPMS helps glue the process together. It provides process visibility, it stops the errors, it speeds the process up, it kills manual work, it provides meaningful data, it gives the customers what they need…(if the process is optimised first!)

Succinct reasoning for why a BPMS has stayed relevant for all these years.

  • Flournoy Henry

    “[BPMS tools] are designed to have flexible and adaptive business rules that can be altered faster than regular “off the shelf” systems.”

    This of course requires that the organization recognizes the adaptive nature of BPMS solutions and can adopt a methodology that supports rapid change. All too often, the organizational methodology of product development fails to evolve fast enough to take advantage of the inherent flexibility in a BPMS.