SHARE
Facebook X Pinterest WhatsApp

Five Reasons Why BPM Programs Struggle or Fail to Succeed

Several high-profile business process management (BPM) programs have recently been dropped, and a recent blog post by Elise Olding, research director at Gartner,  examines why BPM is facing more challenges in recent times. Ms. Olding said there are five reasons why some programs struggle or fail to succeed. Click through for five reasons why some […]

Written By
thumbnail
ITBE Staff
ITBE Staff
Mar 1, 2013

Several high-profile business process management (BPM) programs have recently been dropped, and a recent blog post by Elise Olding, research director at Gartner,  examines why BPM is facing more challenges in recent times. Ms. Olding said there are five reasons why some programs struggle or fail to succeed.

Five Reasons Why BPM Programs Struggle or Fail to Succeed - slide 1

Click through for five reasons why some BPM programs struggle, as identified by Elise Olding, research director at Gartner.

Five Reasons Why BPM Programs Struggle or Fail to Succeed - slide 2

Many BPM projects tout results from automating paper-intensive routine activities, many times with little, if any breakthrough re-thinking about the work. This is often because the automation is at the task or activity level. Getting a bunch of people in a room and asking them how to improve their work in a two-hour meeting can’t possibly yield innovative results.

Five Reasons Why BPM Programs Struggle or Fail to Succeed - slide 3

Some organizations create a BPM empire from scratch and don’t play nicely in the sandbox with already mature disciplines like enterprise architecture, project management and applications development. BPMers tout breaking down process silos, while they blindly build their own methods, governance and competency centers.

Five Reasons Why BPM Programs Struggle or Fail to Succeed - slide 4

The BPM group becomes a bottleneck because the team is doing the detailed work. Pretty soon transformation teams, aligned with strategic processes begin to sprout up – especially in large organizations.

Five Reasons Why BPM Programs Struggle or Fail to Succeed - slide 5

Standardization has become synonymous with BPM. Whether right or wrong, Olding hears many execs refer to “standardizing business processes” as their view of what BPM achieves. As an expectation, this road is fraught with politics at the front end and shadow processes at the back end.

Five Reasons Why BPM Programs Struggle or Fail to Succeed - slide 6

Doing things more cheaply is not always the answer. Efficiency is a short-term win – there’s only so much efficiency you can wring out of your organization. Then what? Effectiveness is boundless and radically rethinking how work is done creates long-term value that pays forward.

The advice here is to think bigger, play nice with others, embrace effectiveness and focus on long-term value. BPMers need to radically rethink what the role of visibility, accountability and adaptability will be for the future of their organization.

Recommended for you...

Top Managed Service Providers (MSPs) 2022
Observability: Why It’s a Red Hot Tech Term
Tom Taulli
Jul 19, 2022
Top GRC Platforms & Tools in 2022
Jira vs. ServiceNow: Features, Pricing, and Comparison
Surajdeep Singh
Jun 17, 2022
IT Business Edge Logo

The go-to resource for IT professionals from all corners of the tech world looking for cutting edge technology solutions that solve their unique business challenges. We aim to help these professionals grow their knowledge base and authority in their field with the top news and trends in the technology space.

Property of TechnologyAdvice. © 2025 TechnologyAdvice. All Rights Reserved

Advertiser Disclosure: Some of the products that appear on this site are from companies from which TechnologyAdvice receives compensation. This compensation may impact how and where products appear on this site including, for example, the order in which they appear. TechnologyAdvice does not include all companies or all types of products available in the marketplace.