A company can employ capable people and still produce inconsistent outcomes. One department completes a request in a day, another needs a week, and a third depends on a particular employee who knows how to resolve unusual cases.<\/p>\n\n\n\n
The challenge is not necessarily the skill of those employees. It may be that the underlying business process has never become a reliable organizational capability. Business Process Maturity Models help explain how to move from local, improvised work to consistent, measurable, and continually improving end-to-end processes.<\/p>\n\n\n\n
BPMM stands for Business Process Maturity Model. The term is sometimes used generically for several process maturity frameworks, so it is important to name the actual model before claiming a score.<\/p>\n\n\n\n
This tutorial uses the Object Management Group (OMG) Business Process Maturity Model<\/strong>. The OMG specification describes a progression through five maturity levels. The purpose is to assess how systematically business processes are managed and to guide improvement.<\/p>\n\n\n\n Business process management (BPM) is the broader management discipline. BPMN, or Business Process Model and Notation, is a notation for drawing processes. BPMM is a maturity assessment model. A BPMN diagram can help document a process, but drawing one does not prove high maturity.<\/p>\n\n\n\n Work practices are inconsistent and depend heavily on individuals. Outcomes vary because the process is not reliably defined or managed. Success may depend on exceptional effort.<\/p>\n\n\n\n Example:<\/strong> Each branch handles customer refunds differently, and nobody owns the process from beginning to end.<\/p>\n\n\n\n Basic workgroup practices are managed, allowing improved repeatability. Responsibilities, expectations, and local discipline are more reliable than at Level 1, even if the enterprise lacks a common end-to-end approach.<\/p>\n\n\n\n Example:<\/strong> Every branch tracks refund cases and supervisors manage workloads, but branches use different processes.<\/p>\n\n\n\n The organization defines and applies standard end-to-end business processes across relevant units. Roles, interfaces, procedures, and governance are understood, with controlled adaptation for justified local needs.<\/p>\n\n\n\n Example:<\/strong> All branches use a common refund workflow, clear exception paths, and comparable performance measures.<\/p>\n\n\n\n Processes are quantitatively understood and managed to produce more predictable performance. Measurement, variation analysis, and process control become central.<\/p>\n\n\n\n Example:<\/strong> The organization can anticipate refund lead times under different demand conditions and detect abnormal variation early.<\/p>\n\n\n\n The organization continually improves and innovates its processes based on quantitative understanding, changing needs, and opportunities for better performance.<\/p>\n\n\n\n Example:<\/strong> The refund process is redesigned using evidence from customers and operations, while improvements are tested and adopted across the organization.<\/p>\n\n\n\n Higher levels build on the capabilities developed at lower levels. A process is not Level 5 simply because one team runs an innovation workshop.<\/p>\n\n\n\n A useful business process has a clear trigger, customers, outputs, ownership, boundaries, and interfaces. Examples include order-to-cash, procure-to-pay, hire-to-retire, request-to-fulfillment, and incident-to-restoration.<\/p>\n\n\n\n Avoid assessing every activity in the enterprise as one process. Start with an important value stream and define where it begins and ends. Include handoffs between departments because that is often where maturity gaps become visible.<\/p>\n\n\n\n Choose a process based on customer impact, risk, volume, variation, and improvement potential. Write down what success means: speed, accuracy, compliance, cost, customer experience, or reliability.<\/p>\n\n\n\n Interview the people doing the work and observe representative cases. Record activities, decisions, handoffs, systems, queues, rework loops, and exception paths. A simple swimlane diagram is enough to begin.<\/p>\n\n\n\n Identify who may change the process, approve exceptions, allocate capacity, and resolve cross-team conflicts. Review whether employees receive consistent guidance and whether compliance controls are actually applied.<\/p>\n\n\n\n Useful evidence includes transaction histories, queue aging, defects, customer complaints, standard procedures, process reviews, exception logs, and records of corrective actions. Sample both ordinary and unusual cases.<\/p>\n\n\n\n Examine which model requirements are satisfied and which remain gaps. A disciplined assessment should look for consistent practices, not isolated examples. Formal maturity determination must follow the OMG model’s appraisal requirements; a workshop estimate is only a preliminary view.<\/p>\n\n\n\n If departments use incompatible procedures, enterprise standardization may be more important than predictive analytics. If the workflow is standardized but performance varies unpredictably, measurement and variation management may be the priority.<\/p>\n\n\n\n Implement carefully selected changes, review performance, check employee adoption, and reassess the affected practices. Improvement should move business results, not merely the assessed label.<\/p>\n\n\n\n A fictional company operates procurement through three independent departments. Requests arrive by email, purchase approvals are inconsistent, suppliers receive duplicate information, and invoice processing generates exceptions.<\/p>\n\n\n\n Initial assessment:<\/strong> Workgroups can often complete purchases, but there is no consistently managed end-to-end process. The evidence suggests that some local practices resemble Level 2 while organization-wide standardization remains weak. This is a preliminary finding, not an official rating.<\/p>\n\n\n\n First improvement:<\/strong> Define the trigger and completion condition of procure-to-pay. Appoint an end-to-end owner. Standardize purchase request fields, approval authority, supplier onboarding, purchase-order references, and exception handling. Establish controls for segregation of duties.<\/p>\n\n\n\n Next improvement:<\/strong> Collect common metrics across departments: total lead time, first-pass invoice match rate, exception frequency, and supplier inquiry volume.<\/p>\n\n\n\n Longer-term improvement:<\/strong> Analyze variation by supplier, request type, or business unit. Introduce targeted prevention and automation only where the process is stable and risks are understood.<\/p>\n\n\n\n The progress illustrates the path from fragmented local operations to standardized, measurable business processes.<\/p>\n\n\n\n For example, if 840 of 1,000 invoices pass matching checks without rework, first-pass yield is Use ten representative invoices, including normal and exception cases.<\/p>\n\n\n\n Deliverable:<\/strong> a process map, evidence inventory, preliminary gap statement, and a prioritized improvement backlog.<\/p>\n\n\n\n BPMM versus BPMN:<\/strong> BPMM evaluates process maturity; BPMN is a way to represent process behavior.<\/p>\n\n\n\n BPMM versus Lean:<\/strong> BPMM focuses on institutionalized process capabilities and their progression; Lean focuses on value, flow, waste, and continuous improvement.<\/p>\n\n\n\n BPMM versus CMMI:<\/strong> Both have roots in process improvement maturity concepts, but their assessed domains and model requirements are not interchangeable.<\/p>\n\n\n\n Can BPMM assess services and knowledge work?<\/strong> Yes. The unit of analysis is a managed business process, not a factory machine.<\/p>\n\n\n\n Does Level 4 require statistical thinking?<\/strong> Yes. Predictability requires quantitative understanding and control of relevant process performance, not simply producing dashboards.<\/p>\n\n\n\n Must every process reach Level 5?<\/strong> No. The appropriate investment depends on process criticality, risk, strategic value, and costs.<\/p>\n\n\n\n Is a self-assessment an official maturity appraisal?<\/strong> No. An informal self-assessment can guide action, but it should not be misrepresented as an externally validated result.<\/p>\n\n\n\n Business process maturity is the journey from relying on individual effort to building predictable organizational capability. Begin by making important work visible, clarify ownership, establish reliable practices, and use data to improve what customers experience.<\/p>\n\n\n\n Further reading:<\/strong> OMG Business Process Management Portal<\/a> and OMG BPMM Specification<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":" A company can employ capable people and still produce inconsistent outcomes. One department completes a request in a day, another needs a week, and a third depends… <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[11138],"tags":[],"class_list":["post-79596","post","type-post","status-publish","format-standard","hentry","category-best-tools"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/79596","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=79596"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/79596\/revisions"}],"predecessor-version":[{"id":79597,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/79596\/revisions\/79597"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=79596"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=79596"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=79596"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}The five OMG BPMM maturity levels<\/h2>\n\n\n\n
Level 1 – Initial<\/h3>\n\n\n\n
Level 2 – Managed<\/h3>\n\n\n\n
Level 3 – Standardized<\/h3>\n\n\n\n
Level 4 – Predictable<\/h3>\n\n\n\n
Level 5 – Innovating<\/h3>\n\n\n\n
Scope your process before you assess it<\/h2>\n\n\n\n
Step-by-step BPMM assessment<\/h2>\n\n\n\n
Step 1: select the process and its business objectives<\/h3>\n\n\n\n
Step 2: map the current process<\/h3>\n\n\n\n
Step 3: document process ownership and controls<\/h3>\n\n\n\n
Step 4: collect operating evidence<\/h3>\n\n\n\n
Step 5: assess maturity against the chosen model<\/h3>\n\n\n\n
Step 6: identify the next necessary capability<\/h3>\n\n\n\n
Step 7: improve and reassess<\/h3>\n\n\n\n
Worked example: procurement from request to payment<\/h2>\n\n\n\n
Metrics that matter<\/h2>\n\n\n\n
\n
840 \/ 1,000 x 100 = 84%<\/code>. Confirm that the denominator includes the full intended population.<\/p>\n\n\n\nBPMM assessment lab: invoice processing<\/h2>\n\n\n\n
\n
BPMM versus BPMN, Lean, and CMMI<\/h2>\n\n\n\n
Common maturity-assessment errors<\/h2>\n\n\n\n
\n
Frequently asked questions<\/h2>\n\n\n\n
The core lesson<\/h2>\n\n\n\n