<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1907245749562386&amp;ev=PageView&amp;noscript=1">
Event_bg

The Leonardo Blog

All Posts

Are You Modeling Too Many Processes?

Modelling processes

Too often, the theory, practice and aspirations of process-based management are reduced just to process modeling. A stated intent in some organizations is that “we will model all of our processes”, and this is said as though achievement of this goal would solve some serious business problem. In reality, there is never a business problem called “we don’t have enough process models”, and an inappropriate focus on modeling severely handicaps the achievement of genuine process management.

Why model processes?

There are four general purposes for process modeling: document, understand, improve, automate.

  1. Document: describing how a process is meant to work enables consistency, quality and standardisation
  2. Understand: understanding the detail of how a process works gives insight into what works well and what might be able to work better
  3. Improve: discovering ways in which the process might work better is enabled by modelling and testing the possible changes
  4. Automate: using the process models as input to a process execution system is increasingly the way that IT applications will be built.

Enterprise Process Architecture (EPA)

Every organization should have an Enterprise Process Architecture (EPA), a hierarchical model of the first three levels of its business processes. Individuals processes in the EPA, and there may be hundreds of them, need only be identified as a single object (a box of some form depending on the graphic notation being used). The EPA model is about identifying relationships between processes, rather than the details of individual processes. Modeling the process detail is then undertaken on demand; it’s done to address a particular problem or opportunity. Therefore, detailed process modeling should be done as part of a process improvement project that has a very clear organizational performance goal.

Should we model all of our processes?

Some processes will never be modeled if there is never a good reason to do so. Looking through an EPA, we should find that some processes have been modelled in lots of detail and to many levels, others will have been modeled only at higher levels, and others will have never gone lower than the original single box. Addressing process issues will always be a matter of prioritizing scarce analysis resources. Modelling ‘everything’ is waste.

Next time someone says “We should model all of our processes”, ask the important question “Why?”

Related Posts

Leonardo at the Red Hat Forum in Sydney

Leonardo will be exhibiting and presenting at the Red Hat Forum in Sydney at the Hyatt Regency.  Our presentation topic will be 'Using Processes-as-Microservices to Drive Better Customer Experiences' which presents an approach that combines digitised processes, business rules, and microservices that collectively deliver improved customer experiences through event-driven digital “micro-moments” – those brief interactions with your customers that can sometime be neglected.

Leonardo partners with Trisotech for greater client success

Leonardo announced today that they have formed a partnership with Trisotech - a leading provider of highly visual and interactive software tools that help organizations innovate, transform and improve their operations. According to Adam Mutton, Managing Director of Delivery for Leonardo, “Trisotech enables Leonardo Consulting to foster an innovative, collaborative approach for the subject matter experts at its clients. Trisotech’s Digital Enterprise Suite is a modelling environment that helps Leonardo design, model and execute its customers’ business processes & business rules. Organisations globally are demanding digital and mobile enablement to streamline and automate their processes to improve the customer experience and drive revenue. Trisotech’s modelling platform delivers BPMN, CMMN and DMN which are crucial artefacts to drive consistency that connects business strategy to automation, integration and implementation for Leonardo’s clients.”

Leonardo partners with University of Melbourne’s Apromore

Leonardo and the University of Melbourne’s Apromore team today announced a partnership whereby Leonardo will be assisting the Apromore team in developing the platform strategy and implementing it through an agile methodology, and by providing industry-strength development power to improve the platform. According to Leonardo Managing Director of Deliver Adam Mutton, “Apromore’s unique selling point is that its process mining capabilities are ahead of the curve, given that they are directly informed by many years of academic research, combined with numerous applications in the field. We have substantial experience in supporting open-source initiatives and are confident we can transfer this experience to the Apromore Initiative”.