BPM Quotes of the week

On BI – Ian Gotts

BI is like following horse and looking at the manure to work out what it ate. Now that is important. But how do you get around to the front end to see what is being eaten, or better still deciding what is being fed to the horse.

On the BPM tipping point – Jim Sinur

The more BPM grows the more organizations that will be attracted to BPM. I believe we are at a tipping point where many folks that were on the sidelines are running onto the BPM field. In addition, organizations with BPM success want more

On BPM Visibility – Scott Cleveland

Before implementing a BPM strategy, most companies have little visibility into their processes. Status is hard to come by. Inefficiencies are virtually invisible. Many companies hire a program manager to come up with this information.
However, after implementing a BPM solution the status of a process can be found with the click of a mouse.

On the BPM Focus – Vinaykumar Mummigatti

In many cases the problem is an IT team that becomes very focused on automating processes, without considering other process changes that may need to be made. Automating a flawed process just makes it quicker and easier to achieve subpar results

On Good Governance – Sandy Kemsley

Good governance is less about telling people what to do (and what not to do), and more about educating people on why they need to do certain things and empowering them to make the right choices. Many successful organizations adopt not just centers of excellence, but build communities of practice around those CoEs.

On BPMN and UML – Jordi Cabot

Until now, my way of justifying both languages was to think of BPMN as the right choice when you are modeling the business aspects of the organization and move to Activity Diagrams as soon as you drill down to the technical design of the software system (as a core component of the UML language, activity diagrams are a better fit when having to combine workflow information with other views of the system, expressed also as UML diagrams like class diagrams or sequence diagrams).

On BPMN 2.0 – Max J. Pucher

The trick to make BPMN 2.0 usable for business users is to hide it during design, but offer it as optional visualization of the activities to achieve the defined PROCESS GOALS during execution

On BPMN – Bruce Silver

As I have said in the past, the biggest obstacle most people – business and IT – face in creating good BPMN is attention to proper model structure and labeling… NOT the shape semantics or fuzzy business logic.