Tech friends, it is time to stop treating BPM as technology

This is a short post for my tech friends, in which I would like to discuss a really common behavior I see in my routine: “How’s BPM sales?”, “How’s that BPM project going?“,“This BPM is scalable and cloud-native!”

BPM, Business Process Management, is not simply the use of software to automate business.

BPM is a discipline used by managers and business analysts to transform business workflows that span across different areas of a corporation. It allows defining flows of tasks executed by proper roles. This results in a better customer experience. Better management by using real data for decision making.

BPM is not directly related to technology use, but it can take advantage of software as: Business Process Management Systems (BPMS) and Business Rules Management Systems (BRMS) .

BPM is a discipline used by managers and business analysts to transform business workflows across different areas throughout a corporation. It is not directly related to technology use, but it can take advantage of it (BPMS).

BPM discipline exists since 2000 and is used by large organizations. Its benefits reach customers, managers and those who execute tasks. Managers notice more satisfied and highly productive teams and identify improvement points in areas presenting defective, slow, unexpected results.

My tech friends, when BPM meets Technology, it’s the state of art.

By using appropriate technology, we allow Business team to:

  • Author (design) executable, self-documented, and versioned business process;
  • Implement rules with Friendly Enough Expression Language (FEEL)
  • Execute and promote business assets across Dev, QA and Production environments, with its own lifecycle and isolated environments;
  • Extract and monitor key performance indicators (KPI) using customized dashboards to conduct decision making;

We can, and should, bring Business team closer by implementing process-driven applications. I also reinforce that hype concepts will be used with this architecture (according to each requirement) like decoupling, isolation, resilience, scalable, cloud-native and orchestrated or choreographed services.

If you want to know more about this, feel free to get in touch.