How can you visualize where your business is and where it should be? This type of prediction is difficult, so thankfully, there’s a tool that can help. Business Process Modeling is a quality management tool that is part of modern Business Process Management (BPM). The tool depicts the current processes of an organization in a formalized way for analysis or improvement. In this article, we focus on two different perspectives: the business perspective and the software engineering perspective. For both fields, processes are of the utmost importance. We look at the nuts and bolts of Business Process Modeling, as well as the different methods, languages, and its future. Along the way, our modeling experts weigh in.
Why Use Business Process Modeling?
Organizations use Business Process Modeling (BP Modeling) in order to visually document, understand, and improve their processes. A part of Business Process Management (BPM), BP Modeling has been used as an organizational tool to map out what is (or “as-is”) as a baseline and to determine the future (or “to-be”) with any improvements assimilated. BP Modeling visually represents all of the connecting activities, events, and resources of the process of a product or service to make it more efficient. BP Modeling often combines the disciplines of process mapping, process discovery, process simulation, process analysis, and process improvement. Within a Business Process Reengineering (BPR) event, BP Modeling is used to illuminate what processes are already in use, and to represent new processes. Some of the other reasons to use BP Modeling are as follows:
- To create visual models of processes - Word-driven documentation is often not sufficient for employees to understand the way a process is performed. Backing it up with visual representations helps provide a comprehensive picture.
- Align operations - With any new business strategy, keeping processes consistent after a change requires figuring out how to stay within the overall organizational strategy. Analyses are also performed to identify bottlenecks and inefficiencies, and enable process agility.
- Improve process communication - Communication is the key to all of the following tasks: formalizing existing processes (that were once informal knowledge), making consistent processes, eliminating guesswork with business rules, handling exceptions, providing regulatory compliance, ensuring business people are in charge, and supporting new initiatives (such as Lean Six Sigma).
- Improve operational efficiency - Modeling processes promotes optimization by allowing simulation and illustrating needed improvements. This reduces cycle time and promotes better resource utilization.
- Gain competitive advantage - A process is better overall when it is constantly refined and aligned with its business’ strategies. This efficiency places the company in a forward-leaning position to be better than the competition.
Business Process Modeling in Software Development
Software development is a risky field. Twenty years ago, the 1995 CHAOS report by the Standish Group reported that 90 percent of software projects fail. Today that numbers are lower, but still reflect that there is work to be done. In the 2015 report by the same group, the rate of success for software development projects was still only 29 percent. The group’s recommendations to improve these numbers over the years have ebbed and flowed with new trends, but one main recommendation holds: communicate with all of the stakeholders, especially the end users, since end users are those who end up defining the requirements in the first place. Experts recommend developing clear models with understandable notation early on in projects in order to validate the requirements of the software. BP Modeling allows software engineers to negotiate with stakeholders to determine the system that needs to be built, based on what is optimal for both groups.
Most BP models have been developed as part of existing enterprise architectures, which shows that the intent during development is that the end user is represented. However, these models have been done from a number of different perspectives including functional, behavioral, organizational, and informational. Experts agree that the combination of these perspectives in process design is the best method.
- The functional perspective shows what process elements are being performed and what information is relevant to them.
- The behavioral (or dynamic) perspective demonstrates the sequence of interaction and how process elements are performed.
- The organizational perspective shows by whom and where the elements of a process are performed.
- The informational perspective represents the origin of information that is produced or analyzed.
Business Process Modeling Languages in Software Business Process Modeling
All of the existing business processing model languages come from different facets of scientific tradition, and have been built to suit one perspective or another. There is significant overlap in the languages, but there are four broad categories of business process modeling languages.
- Traditional process modeling languages: From the management information system (MIS) tradition of information engineering, these languages are meant to be understood and are not typically formal. These include IDEF, Petri Nets, EPC, Role-Activity Diagrams, REA, and BPML.
- Workflow modeling languages: These scripting languages are for describing workflows for a workflow management system (WfMS). These very formal languages include Workflow Process Description Language (WPDL), and proposed interchange formats (PIF, PSL).
- Process integration languages: These languages are for the purpose of integrating between enterprises, and capture different levels of the semantics in processes. These include RosettaNet, ebXML, and BPEL4WS.
- Object-oriented languages: Meant to be understood by both IT and domain experts, these languages represent the software domain. Most of the object-oriented modeling takes into consideration the functional, behavioral, and informational perspectives.
Hafedh Mili et al recommends that teams should use a core language for modeling, and then use different parts that suit the process from other languages. In this field, it appears that experts agree that even the languages should be driven by the tasks.
How to Approach a Business Process Modeling Project
Choosing an approach to BP Modeling is just as essential as performing it. The approach, based upon the actual task itself, is not a one-size-fits-all affair. Some classifications should be made before a project is undertaken. According to Bider, professionals should consider three factors: the actual business processes, the characteristics of the modeling environment, and the intended use of the model. These three factors may be broken down into specific business considerations.
- The business processes – Businesses should consider their active and passive participants, how closely they are meeting their operational goals, how closely the process interacts with its environment, and the nature and orderliness of the process flow.
- The characteristics of the modeling environment - For the modeling environment, businesses should consider the maturity of their existing processes and whether or not there are personnel available that understand the very formal notation.
- The intended use of the model - Businesses should consider their objectives for designing models and what basis they are using to create models. For example, they could be trying to improve the current processes, providing analysis or reengineering, or building a new computer system.
Since there is no universal approach to BP Modeling, experts recommend considering all of the unique business factors. Some pros recommend a specified formal approach that gathers all of the information before choosing tools, while others recommend specific tools that have worked for them in the past. Two of our experts make their recommendations below.
According to Dani Peleva, Managing Director of Local Fame Ltd:
“When approaching a business process modeling task, I’d always break it through the prism of project management as it helps me get an idea of the objective of the system that needs engineering, the time the process needs to be completed for, as well as the resources available. Once you know what the requirements are, i.e. the purpose of the process is, what the deliverables are, the budget/resource constraints and so forth, it is a lot easier to approach the design/engineering stage.
When it comes to process engineering at Local Fame, we always have efficiency and effectiveness in mind - the most cost-effective, timely and optimized manner that a process can flow. For this purpose, I always approach the task from a few different angles - from the start of the process, as well as from the end of the process backwards. When you do not limit yourself with the direction of the process flow you can identify gaps and possible flaws in the strategy and implementation, as well as possible bottlenecks. Once I come up with a few different models I test those applying different scenarios in order to understand how sustainable those are in turbulent environment. This is when usually you sift through the best models and shortlist one or two successful ones.
Additionally, an intrinsic part of business process modelling for me is risk management, more specifically, identifying the potential flaws of the model and where and under what circumstances the model can fail. Identifying those weaknesses of the process helps you create contingency plans and backups, and as you often may find yourself, you get to optimize the process even further and scrap some of the chunks you initially considered essential, but later on realized you could go without. When thinking about risk management, however, one should know a risk could be both a positive and a negative, risk can create opportunities for the process to fail or get delayed, but also speed up and become more efficient, which again leads to the process optimisation and potential changes in the model. Tools I often use when doing business process modelling are Gliffy, Activiti Modeller, and Gantt charts.
To conclude, when modelling a process or re-engineering an existing one, I usually approach the task from a project management perspective analysing the requirements fully before moving to the design stage. After design stage, I test the model numerous times in different scenarios and if needed I return to different stages to optimise and tweak it further. Lastly, I always think about risk management and contingency to make sure that the process is resilient and sustainable.”
Ray McKenzie, Founder and Principal, Red Beach Advisors, recommends, “As a management and business consultant for small- to medium-sized companies, a primary duty of mine is to develop efficient and optimized process for every organization to be productive. I always start with examining the problem and finding out the history of the problem, the different parts of the problem, and the effect the problem has on the business. Understanding the problem and components are core pieces to developing an effective process model to improve. Start with the problem. Examine the parties involved. Understand the current performance and measurements. Define the performance improvement goals. Outline an efficient process which drives results and displays success.”
Workflows and Business Service Oriented Approach (BSOA)
Some experts consider BP modeling for software development to be a before and after prospect that revolves around the introduction of web services. Before the development of the web, the main approach for developing processes was workflows. In the workflow approach, the business processes are pre-determined. The most suitable languages are Business Process Execution Language (BPEL) and Flow Definition Language (FDL). The workflow approach was criticized as not being very flexible in a modern environment.
After the development of web services, the approach for BP Modeling for software development became more focused and identified as the Business Service Oriented Approach (BSOA). Process modeling is based upon the flexible composition of business services. The approach can be tailored to address what the designer’s goals and requirements are in architecture development by using building blocks. Services carry out small tasks, such as data development, or simple service procedures. Taken all together, BSOA makes an extremely reusable system that can be fixed and regularly upgraded. This approach is credited as being Agile, and applicable to many different types of organizations.
Different Ways to Model Business Processes
Between all of the standards and standardized languages, some professionals think that the creativity in designing processes is being leached out. Alternative approaches can restore some of that creativity. Some of the most popular techniques that can stand-alone or even complement more formal approaches are the following:
- Flow Chart Technique
- Data Flow Diagrams—Yourdon’s technique
- Role-Activity Diagrams (RAD)
- Role-Interaction Diagrams (RID)
- Gantt Chart
- Integrated Definition for Function Modelling (IDEF)
- Colored Petri-nets (CPN)
- Object Oriented Methods (OO)
- Workflow Technique
- Business Process Modeling Notation (BPMN)
- UML Activity Diagram
- Transformational Process Models
- Hierarchical Process Models
According to Bernard Lee, President of Charlotte Search Engine Consultants, there are other ways to model your projects visually. He points out that, “As a lifelong entrepreneur who started my first business at 20, I am now 53 and am considered a ‘college dropout.’ It has always been about systems, automation, and measuring risks to achieve our stated goals. This has been true in my career as a wealth manager, a Healthcare IT executive, and now as the founder of a digital marketing agency that specializes in SEO. Yes, SEO is about metrics, analytics, and CTR (click-through rate). Nevertheless, I've found the creative aspects is what separates the pretenders from the achievers. We are Google partners so we believe in the usual success measurements, but get there differently. YouTube, Geo-Tagging, and unorthodox combinations of our client's digital properties consistently land multiple properties on page one for the most important keywords. The visual of multiple positions on page one always has an immediate impact on our client’s brand, traffic, and conversions while moving competitors to page two.”
Process Mapping vs. Process Modeling
Process mapping is a high-level review of an organization as a single entity with interconnecting parts. The flow of business processes through the organization is reviewed to clarify who does what, how processes are performed, and by what standard they are judged. In process modeling, professionals are more focused on how efficient the processes are, using business and economic best practices. Although both depict the processes graphically, process modeling is a deeper dive into the relationships that produce the services and outcomes.
Framework for the Modeling and Evaluation of Software Processes (FMESP)
One of the complicated issues that came from developing standardized business processes is the notion that their efficacy must be determined. In other words, how successful are business processes? FMESP comes in as a set of metrics to evaluate conceptual models of business processes: what they do and what they do not do. FMESP measures the structural complexity of software process models and then the activities, roles, and work products. This framework is intended to give businesses objective information about the maintainability of their models.
Develop Good Business Process Models
How does a professional get started on a BP Model? One of the common approaches advocates picking a problem, selecting the method, and then solving the problem. Keeping it simple ensures that everything relevant is in the model and everything in the model is relevant.
Other professional tips include:
- Ensure that you know who will be your resources. Develop lists of tasks, people, and the time required to complete the model.
- Conduct your interviews in the order the roles appear on the process model.
- Document. Document. Document.
- Recheck all of your symbols, ensure there is a key, and follow each step to ensure that the path takes you either back or ahead.
- Know your desired outcome ahead of time.
- Figure out your start and end points.
- Get ahold of the documents and forms ahead of time that are part of the process.
- Use templates whenever you can.
According to Steve Wallis, Co-Founder/Analyst/Consultant at ASK MATT, Foundation for the Advancement of Social Theory (FAST) - Theory for a better world:
“BPM is incredibly useful for showing ‘what goes on’’ within a business organization. However, it can also create a false sense of comfort. When the map says, ‘You are here’ we feel a sense of security. However, unless the map shows how to get from ‘here’ to ‘there’ it is not going to be very useful. More importantly for the ever-shifting world of business, a map needs to show multiple paths so that leaders can take advantage of new options when unanticipated problems arise (and you know they will). Research in this area suggests that models (maps) which are more complex and have more interconnections are more useful for understanding how organizational processes work, and how they might be changed when the need arises. What does NOT work is a simple, linear model such as:
Image Source: Steve Wallis
Oh, if only life were so easy – and so predictable, however, it is not. Therefore, we looked for a slightly different approach to business process modeling. Calling it Strategic Knowledge Mapping (SKM), we focus on the transformational aspects of modeling. Rather than modeling what is happening on the “surface” level (e.g. Research gives information to manufacturing), we encourage our clients to see what changes occur at all of the interconnected steps of the process. From our research and experience, we have developed two easy techniques for developing good models.
First, in order to understand a transformation in a model, there must be more than one arrow pointing towards each box. For example, if we are talking about making pastries, the process of creation requires raw material (flour, eggs, sugar, chocolate, etc.) and equipment (oven, racks, mixers, etc.) and cooks (with some level of expertise). Therefore, in order to better understand the transformation, we create a model showing how each of those ‘inputs’ combines to create the transformed ‘output.’ To some, that may seem obvious. However, here is the hidden insight (ex: chocolate filling): If you have a model where there is only one arrow pointing towards something, that lack of additional arrows indicates a gap in the model. For managing the process, you are missing an alternative path.
The second tip for making effective models is to understand each arrow as being ‘causal.’ This is one of the great bits of ‘forgotten knowledge’ in the world of business. Causality is the essence of scientific understanding. To understand the transformational process, and business processes in general, it is not enough to simply say, ‘The cook mixes the ingredients and makes the cakes.’ A good manager understands that having more raw materials, more equipment, and more expertise will cause the transformation into a marketable product (or service). And, for managing that process, there may be some tradeoffs between them (a really good expert might be able to stretch the raw material a bit), but each stream is required to create the end product. Without raw materials, I will not have a pastry with my coffee!”
Business Process Model and Notation (BPMN)
BPMN was developed by the Business Process Management Initiative (BPMI) as an open-industry standard, and is now maintained by the Object Management Group (OMG). No software or consulting company owns it. It is a graphical notation for creating process models, similar to flowcharts, that is used and understood industry-wide. Many software tools support BPMN. However, the meaning of the shapes and symbols are independent of those tools, and those meanings are precise. BPMN is a core part of Business Process Management (BPM), an initiative of enterprise architecture. The version of BPMN that is currently in use is v2.0, last updated in 2011. Professionals may become certified in BPMN v2.0 through the OMG exam process. The OMG also offers guides that show how the notation is broken down into the groups of events, activities, flows, data, artifacts, etc. Elements are categorized into four major groups that are referred to as flow objects, connecting objects, swimlanes, and artifacts.
The intent of BPMN is that technical users and business users may be able to understand a common diagrammatic language. BPMN is based upon a flowchart technique similar to one developed from the Unified Modeling Language (UML), and is able to be mapped directly to Business Process Execution Language (BPEL), an XML-based language that is used to define enterprise business services within web services.
Critique of BPMN
Industry opinion varies on the use of BPMN for BP Modeling. Critics argues that BPMN is much more complex and advanced than it needs to be for stakeholders who may not be very close to the actual process. Further, with so many symbols it is easy to make mistakes, defeating the purpose of its use.
Proponents of BPMN say that most professionals only use a handful of symbols - making the knowledge of obscure symbols unnecessary. Some international companies require BPMN’s consistency, especially when languages may be varied. Understanding the processes with a standardized notation is less of a challenge.
Other Types of Notations and diagrams
In 2012, Cristina Venera performed a study of two popular notation languages, BPMN and UML Activity Diagram (UML AD). Among professionals and the literature, she found that both languages are equally easy to understand by stakeholders interested in BP Modeling, and that they in fact both provided similar solutions. However, the difference was that BPMN is able to be mapped to (WS)BPEL, whereas UML AD is not able to be automatically mapped to any BPEL.
Other types of notations include Event Driven Process Chain (EPC), workflow diagrams, and mind maps. EPC is most often used for higher-level business processes, consists of five elements and rules, and always starts with and ends with an event. There are rules in between: “OR,”“AND,” or “XOR” represented as graphical connectors.
Workflow diagrams illustrate stages and relationships between all parts of a business. In workflow diagrams, there is no set of agreed upon (standard) symbols. It is more difficult to compare models done across an organization, but does allow more freedom for creativity.
Mind maps are the least restrictive of any of the techniques listed here. Although they are generally hierarchical, they can be done by hand on a napkin in a pub, if necessary. Mind maps are a way to show relationships around a single concept as well as any associations. They are free-flowing and allow for maximum creativity.
Source: Jennifer Frith
What to Look for in Business Process Modeling Software
From all of the expert opinions and research, there does not appear to be one tool that will fit all of an organization’s forever needs. The major requirements that are recommended for a tool or a suite of tools are that they are fast (to learn) and inexpensive. The BPMN homepage lists 74 BPMN compliant tools. If BPMN compliance is a requirement, then the search is already narrowed. Otherwise, users should specify their objectives and requirements, which tools satisfy their requirements, what are the most significant criteria, and what the potential tools could be for use. Then, TEST. Finding the right tool may be a process, but it will not be a regrettable one.
According to Norbert Nogrady, Managing Director & Co-owner of JCM Ltd: [email protected], Twitter: @kgordos
“I started to reorganize organizational units more than 15 years ago. At the time, the number of available process modeling tools was very limited, much less their functionality. However, as time went by, I witnessed the evolution of such tools. In the beginning, I used large sheets, then Microsoft Word and Visio. However, I had a number of serious issues with these tools. The biggest problem is that BPR projects tend to be lengthy and thus overwhelming. The usual routine at the large corporations I worked for was (one of the following):
- Management appointed the IT department to find a tool for business process management (workflow) that fit the IT requirements.
- Management-level leaders with BPR engineers created their respective processes
- Process diagrams had been created using various tools.
- Processes were then transferred to the IT department, so that they could evaluate if the processes fit the workflow system of their choice.
- After a number of iterations – most usually resulting in compromises regarding the processes – the IT department started programming the processes into the workflow system.
- The processes were implemented in the organization, with the immediate need to re-engineer many of them.
- Points two through six have been repeated for a long time until a somewhat acceptable set of business processes were created.
As it is clear from the above, BPR this way was not easy, but instead very time and resource consuming. In addition, I realized very soon that departments should create their own processes, instead of iterating with IT; therefore, a number of process compromises could be avoided. In addition, it took a really long time to implement the created processes into the workflow system by programming. Both of these issues bothered me to the level that I started to look for a solution that fits the usual IT requirements and fully supports my BPR activities.”
After much trial and error Nogrady finally found a solution that worked for him. After his successful search, he suggests looking for a workflow system that has an integrated process and workflow editor tool with a graphic interface, hence making process programming obsolete. The advantage is that once a process has been created in the graphic workflow editor, it only takes a click of a button to have it run in the workflow system immediately. Therefore, all departments can create their own business processes, without the need for programming. Going this route means there are a little to no compromises in the workflows and most importantly, a lot of time and resources could be spared this way. Finally, a good solution will make testing the processes take much less time and effort. In this manner, if a process could use some improvement, anyone in the department can have their suggestions, and if the department leader approved it, the modified process should be able to run in the workflow system in a couple hours.
The Future of Business Process Modeling
One critical area of concern for the future of BP Modeling includes how modeling approaches could be standardized. Many businesses are moving to a more Agile platform, and BP Modeling does not necessarily go hand-in-hand with Agile processes. A modeling approach may only be considered Agile for some types of processes, according to a recent study by Nancy Alexopoulou.
As Ian Gotts, Founder and CEO at Elements.cloud and columnist at Digital Business also notes, “There are big issues in the BP Modeling space. BPM, automation and workflow software vendors have hijacked BPM, so that the B in BPM has disappeared. Modeling has come to mean defining workflows by IT for IT. However, process visualization (business process modeling) is valuable for end users. They use the business process diagrams to agree on how work is done. That then gives the behind-the-scenes IT perspective. Nevertheless, trying to use the BPMN notation as a model for everyone is difficult to achieve; with so many symbols it looks convoluted, and business people are quickly dis-engaged and wondering why they are doing this.
“There is a notation - Universal Process Notation (UPN) - that works for business people, that has been very successful. It is outlined in Chapter two of the e-book, Analysis, Automation & Adoption for #AwesomeAdmins. The first principle that is relevant here is that we are not building a huge flowchart, but a hierarchical process map, where every diagram is easier to follow. For example, at a bank, there may be 10,000 diagrams for all of the processes, but they are organized in a hierarchy so no diagram is overwhelming. Second, the notation is a simple model using an activity box or step with inputs and output, resources identified (or swimlanes), and hyperlinks to supporting information. This process map is useful for end users, but it is also valuable for compliance, IT, and management where metrics can be viewed in the context of a process. Using this approach is valuable for app vendors to improve adoption. An end-to-end process can make sense of the detailed flow of apps.”
Learn more about Business Process Modeling
Interested in learning more about BP Modeling and how to implement it at your company? The following are lists of resources for further reading that can help.
Books and eBooks
- Analysis, Automation & Adoption for #AwesomeAdmins - Free UPN software handbook
- A Pragmatic Guide to Business Process Modelling, by John Holt
- Essential Business Process Modeling, by Michael Havey
- Business Process Modeling, Simulation and Design, Second Edition, by Manuel Laguna and John Marklund
- Strategic Knowledge Mapping For Improved Policy and Strategic Planning, by Steven E. Wallis & Bernadette Wright.
- Strategic Knowledge Mapping: The Co-Creation of Useful Knowledge, by Steven E. Wallis & Bernadette Wright.
- A List of Free Business Process Modelling Software
- Comparison of Business Process Modeling Notation tools
- Market Guide for Enterprise Business Process Analysis - from Gartner
Other Types of Diagrams
How Smartsheet Can Help Improve Business Processes
Smartsheet is a task and business process management tool with powerful collaboration and communication features that are ideal for business process managers. It is a useful tool for developing intelligence analytics, managing processes, and ensuring communication and collaboration. Use the multiple views – Gantt, Calendar, Card, and Sights – to work the way you want.
With Smartsheet Sights, users can pull data from multiple sources without sharing underlying data - creating an unobtrusive way to highlight key metrics and reports to clients or executives. Sights are easy to build and distribute, and the countless customizable options make it simple to create a highly visual, easy-to-consume dashboard that amplifies and exposes data, progress, milestones, and goals met.
Once you have the new process identified, you can use Smartsheet as a repository to attach files and working BP Modeling documents, and add notes and status details to keep all related documentation in a central location. Organize requirements, track bugs, and drive prioritization while collaborating with your launch team. With several built-in templates, such as a requirements checklist or product feedback survey web form, you can ensure a flawless development process. Use Smartsheet’s powerful collaboration tools to manage discussions, reminders, and attachments, and make changes in real time.
See how easy it can be to develop and maintain your new business processes with Smartsheet.