It's Business Management, Not BPM

  • April 2, 2013
  • Scott
  • 3 Comments

In John Reynold’s talk at bpmNEXT, he focused on “data-centric-BPM” – by which he meant modeling business entity lifecycle, and not just the processes that intersect or interact with the Business Entity Lifecycle (BEL).

A key takeaway from the talk that had heads nodding was his comment that we need to drop the P from BPM, because it isn’t just Business Process Management, it is Business Management.

As the discussion made clear, business doesn’t care about “process” per se, they care about results and managing to those results.  And so we can’t really ignore the data that feeds processes, and the visibility and governance associated.

Related Posts
  • October 18, 2017
  • Scott
  • 0 Comments

The Institute For Robotic Automation defines RPA as: Robotic Process Automation (RPA) refers to automation wh...

  • October 18, 2017
  • Ariana
  • 0 Comments

Headless BPM from BP3 on Vimeo. In this video, Carmen Galicia walks through using external user interface...

  • October 10, 2017
  • Ariana
  • 0 Comments

Planning Your Project Roadmap from BP3 on Vimeo. In this video, Andrew Paier talks through getting started ...

  • John Reynolds

    Thanks for the shout-out Scott… The most concise plea for BEL + BPM that I’ve come across can be found here: http://www.togaf-modeling.org/models/data-architecture-menu/data-lifecycle-diagrams-menu.html

  • Business may care about processes, but it’s weird for business people to “start a process”. They enter customer’s order, initiate some resource planning etc. These actions do start a process but it shouldn’t be done under the carpet. The typical BPMS user interface item “start an instance” is ridiculous.

    • Good point, Anatoly – “process” is too abstract a term. Concrete actions like order, planning, etc. make more sense.

      Couldn’t agree more about “start an instance” terminology 🙂 sounds like something you might need antibiotics for 🙂