The folks at ebizQ have picked up my debate introduced in this post. Here, I repost the message that I left for Dennis Byron. It’s a nerdy little history of “how Gartner began using the BPM term” from my very personal viewpoint.
Great summary and analysis of the debate! Here’s some personal history on this. At Gartner in 1999/2000, I made the switch from talking about workflow-brokers (a term coined by Regina Casonato) as the next generation of ‘process engine’ and riffed on a term that Roy Schulte and the application integration team (which I managed) used. They had written one big tome that included a tiny section with the term “Business Process MANAGERS.” This was used to define a class of emerging software that correlated to Vitria’s Business Process Automation term. I took the “MANAGER” term and morphed it to Business Process Management, certainly not claiming to be the first to do that. However, I do lay claim to describing how the workflow and application integration worlds would merge to create BPM capabilities and how those legacy markets would transform. I went around the world a few times with that message and it played out exactly as expected.
At the time (2000), I refused to talk about a single BPM market, as BPM was also emerging as a feature (or layer) of ERP, CRM, application servers, etc. I even wrote a research note in December of 2000 called “Business Process Management: The Hot Non-Market.” I was right in 2000, but over time, I relented to market forces (ironically) and we began talking of the “BPM market” under Jim Sinur’s leadership of BPM. I had passed the baton to him as I was working with Roy to drive BAM (Business Activity Monitoring) into the market. That term, of course, is all Roy’s.
Now, we at Gartner talk of BPM as a management discipline, BPMT (T for technology) as the software component of that market, and BPMS (Business Process Management Suite) as the leading example of BPMT. The world has changed a lot since the days when I was trying to explain that BPM was NOT Business Process MODELING. But in the process (ha!), I think we as an industry have muddled some of our terms. BPM is best described as a discipline, even more so than CRM, etc. So with that shift, I think we will see more linguistic confusion, even if a lot of it is academic hand wringing.
Net, net. I support your assertion that the market will define the term. Been there, and accepted that before :> In 1999/2000 the market was trying to digest terms such as E-process, E-workflow, and as I used to say, EGADS! However, as we move BPM more and more to mean the discipline, then using BPM to also mean a class of technology is more problematic. Since BPA (automation) was hanging around with nothing to do, I was wondering if there was any linguistic power to use it, hence the call for debate. But even there we are vexed! BPA also means Business Process ANALYSIS. So we have more overloading than a bad programming language.
Thanks for taking this up and who knows where it will go. What I do know is that I was with a client who was struggling with BPM work. When I determined that they were really just talking the automation portion of the puzzle, their efforts became a lot clearer to them and to me. BPM is a rather broad term. We may have to live with that at this point, but that is why I started the debate.
Read Complimentary Relevant Research
Predicts 2017: Artificial Intelligence
Artificial intelligence is changing the way in which organizations innovate and communicate their processes, products and services. Practical...
View Relevant Webinars
How to Live Without Mobile Device Management
This webinar addresses the growing trend of users refusing to have enterprise management of their mobile devices due to privacy concerns....
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.