BPM Quotes of the Week - October 20, 2015

“Successful business transformation programs focus less on tactical measures to keep them on track, but more on the people factor. They have created effective communication strategies that create the required level of awareness for the different stakeholder groups. They are able to relate to the interest of the group and individual.”
-Bas de Baat

“In most cases an iBPMS can solve at least 80% of your technical demands and is great at surrounding existing business functionality or including new and growing functionality. A digital strategy with a iBPMS at the core will allow the leverage of new resources and functionality easily.”
-Jim Sinur

From the BPM Forum

“The dynamic nature of many cases often make more detailed modeleing a bit fruitless, but these high level guidelines are really necessary for establishing the guardrails within which the caseworker operates.”
-John Reynolds

“If you are trying to understand, improve and automate ‘Inquiry to resolution’ then modeling it (hierarchically and in simple business terms) is very useful. If you are trying automate the ‘raise new insurance claim and collect evidence’ then you can probably go straight to the case management app or use CMMN.”
-Ian Gotts

“Of course now that the ‘Model’ can be the Application! Declarative MDE (Model Driven Engineering) opens a new door.”
-David Chassels

“You should start by modeling the process. But, when I say modeling, I mean abstracting the reality in a model. It doesn’t mean a formal model in a BPM tool. My suggestion is to model the process as quick as possible, even in a piece of paper.”
-Juan J. Moreno

“The value of BPM is in the ability to rapidly deliver a minimum viable solution, and then to (just as rapidly) iteratively improve that solution based on feedback from the business, customers, or other users. The result of this agile approach is an application that starts delivering value earlier, and ultimately delivers far more value overall, than any that could be set in stone and dropped into place fully-formed.”
-E. Scott Menter

“So for me the key test when deciding whether I should model a process is a double question set: "does it help me execute it better?" or "does this clarify something to the team?". If the answer is ‘no’ or ‘unclear’, I chose not to model.”
-Bogdan Nafornita