BPM Quotes of the Week - June 5, 2018
- Published: June 5, 2018
"BPM is the future of microservices. There are two main problems with microservices: 1) granularity of microservices and 2) complexity of microservices-based applications. BPM solves these two problems naturally."
-Dr. Alexander Samarin
"Businesses can now operate solely on mobile devices with new technologies making connection and collaboration possible. A whopping 62 percent of smartphone users have made a purchase online using their mobile device in the last six months."
From the BPM Forum
"There is a broad misconception that RPA is about 'business process' by itself. I have heard people say that they were going to switch from BPM to RPA. That is strange because the capabilities are quite different. It makes sense to use RPA and BPM together, and sometimes you can use one without the other, but only to solve different problems."
"As RPA continues to mature, common use case scenarios will be made available so that possible future users can easily get a grasp on the 'virtual robotics' as part of their business processes."
"The problem with RPA is that people mistake it for (or: sell it as) a general purpose methodology, although it only does one quite specific thing, which is: Making systems that have UIs, but incompatible APIs, exchange information automatically."
"The biggest misconception I have heard is that RPA is the gateway to enterprise AI adoption. Why? Is it because RPA relies on pattern recognition technologies (like OCR, images etc) in order to extract data and manipulate UI? That's not very interesting, especially since RPA players do not really own the tech, they just API to AI platform providers, who have the scale to deliver pattern recognition services reliably and affordably."
"A microservices architecture is one tool that a provider can use to make its hosted as-a-service proposition cheaper and easier to develop, test, operate, scale and change without service disruption. Business process app technology platform providers (a) shifting to a hosted delivery model and (b) going for a 'pure aaS' model (rather than single-tenant hosted platform) are likely to adopt microservices architecture for this reason."
"The principles of Microservices are absolutely the future of DPA/BPM. However, down the road I don't see a catalogue of microservices as the new DPA/BPM but rather a complimentary capability to be leveraged. There are too many critical definitions and elements wrapped around DPA/BPM and the value of DPA/BPM platform brings discipline and structure to the design and implementation of business capabilities."
"The interesting thing now is the adoption and impact of microservices technology. And it is a technology that must deeply involve business analysts. Microservice scaleability will also help drive the definition business service boundaries. Microservices is a perfect nexus of technology-meets-economics-meets-governance."
"Microservices principally require systematic structuring and maintenance achievable through BPM. Without delimited methodology, dedicated modeling and precious planning complex corporate systems of microservices can easily fall apart burying costly and time consuming IT initiatives. BPM is principal facilitator and enabler for microservices universe."
If There Were a List of Worst Practices for BPM Implementations Today, What Would Be on It?
"Proposing BPM as a tool for strategic planning - strategic planning is not about performing tasks in a certain sequence."
-Karl Walter Keirstead
"Not defining KPIs and Outcomes first."
"'Manage business processes instead of managing business by processes' because this is the root of all BPM evil."
-Dr. Alexander Samarin
"Stay focused on the process and the business value it is designed for. We see amazing project from Amazon, Google, etc, and sometimes we forget about our budget restrictions."
-Juan J. Moreno
"One vital and very common bad practice is missing and that is not starting to design of the process by asking: 'Who is the customer?' and 'What is the customer's process?'"
"Failing to NOT automate the exception and not focusing on the rule (ignoring the Pareto principle)."
"One of the worst and most deeply rooted practices in BPM is doing it without established methodology."