Why this matters. Business Process Management (BPM) is a discipline, not a software category. Gartner defines BPM as the method of discovering, modelling, analysing, measuring, improving and optimising business processes. Equating BPM with the purchase of a BPMS confuses the timing of tool choice with the purpose of the discipline — and starts in the wrong square.
BPM as a discipline — what it covers
BPM coordinates the behaviour of people, systems, information and things to produce business outcomes that support a business strategy. The IBM definition makes that explicit. A BPMS (Business Process Management Suite) is the application infrastructure that supports the discipline — it is not the discipline itself.
-
BPM as a method covers modelling, governance, measurement and continuous improvement. It lives independently of any tool.
-
A BPMS is the software that unites modelling, execution, monitoring and optimisation in one platform.
-
Workflow engines, RPA, process mining are complementary tools — they may be embedded in a BPMS or run as standalone solutions.
The BPM lifecycle in six phases
The BPM lifecycle is established across industries and runs as a repeating loop. Forrester data shows BPM projects deliver 30 to 50 percent productivity gains in back-office work and 15 to 30 percent among knowledge workers — provided the cycle is run end to end, not shortened.
-
Phase 1 — Discovery: as-is capture, process mining, structured interviews.
-
Phase 2 — Modelling: BPMN 2.0 diagrams, ownership per step, exception paths.
-
Phase 3 — Analysis: metrics, bottlenecks, variability.
-
Phase 4 — Improvement: target concept with measurable goals.
-
Phase 5 — Implementation: workflow engine, ERP extension or organisational change.
-
Phase 6 — Monitoring: KPI tracking, drift detection, scheduled reviews.
BPM versus workflow management — the most common confusion
Workflow management is operational — it drives the execution of a specific process. BPM is strategic — it decides which processes should exist at all, who owns them and how they evolve. Setting up a workflow without doing BPM automates an island with no bridge to the business model.
A typical false start in the mid-market: a BPMS is bought because one department needs workflows. Six months later a module is in production, but no enterprise-level process model exists — and the next department starts its own, incompatible modelling. The result is shadow IT at the BPM level. A methodical ERP selection therefore sets the process model before the tool choice.
What to do next
If you want to set up BPM cleanly in your organisation:
-
Name a process owner per core process.
-
Model first at the enterprise level — a core-process model with at most fifteen processes.
-
Choose BPMS or workflow engine only after the model stands.
If you want to validate the BPM set-up logic vendor-neutrally, we will sit through the methodology with you in twenty minutes — before any BPMS contract is signed.
FAQ
BPM is a discipline (Gartner) with associated methods — modelling, analysis, optimisation. It is broader than a single methodology like Six Sigma or Lean, but integrates those as tools inside its lifecycle.
Six phases — Discovery, Modelling, Analysis, Improvement, Implementation, Monitoring. The loop is repeated, not run once. Forrester measures 30 to 50 percent productivity gains in back-office work when the cycle is established.
Six Sigma and Lean are improvement methods that BPM integrates inside Phase 4 (Improvement). BPM provides the frame — which processes exist, who owns them, how they are measured. Six Sigma and Lean supply the tools for targeted optimisation inside that frame.