Jump to any section
- 1. Business Process Modeling Notation (BPMN)
- 2. UML Diagrams
- 3. Flowcharts
- 4. Yourdon’s Data Flow Diagrams (DFDs)
- 5. Gantt Charts
- 6. PERT Diagrams
- 7. Functional Flow Block Diagrams
- 8. Integrated Definition for Function Modeling (IDEF)
- 9. Petri Nets and Colored Petri Nets (CPNs)
- BPM Software: Best Use of Business Process Modeling Techniques
- Next Steps
While you could probably sum up what your business does in just a few sentences, you know that it’s much more complicated than that. To achieve your business’ outputs, your staff completes a series of tasks that get passed from one person or department to the next until voila! You have tangible results. When you dig down, it’s amazing just how many little things need to be done. Business process modeling techniques allow you to capture all these steps in a format that allows you to visualize just how workflows function.
You may be asking yourself why it’s necessary to do this if you aren’t trying something new. After all, your team knows what to do. But there are several very strong arguments in favor of using business process modeling techniques:
- You can spot tasks that are redundant and eliminate them.
- You can improve process efficiency by looking for areas where work gets held up because of bottlenecks in the process.
- You can ensure that efficient processes are repeated in the same way every time, even when a new staffer must perform part of the process.
Over the years, a variety of business process modeling techniques have been developed. Let’s examine your options.
1. Business Process Modeling Notation (BPMN)
BPMN consists of a series of symbols or “standard objects” to represent tasks and workflows. Of course, there’s nothing to stop you from developing your own set of symbols. However, using standardized ones makes collaboration with outside analysts easier and saves you from having to dream up a visual language of your own.
You're probably wondering who we are. Tallyfy is a product that simplifies and automates your business processes. It's the secret to running smooth operations. Instead of creating process diagrams (which nobody looks at), documentation (which you can only read and never action), emails, chats and chaos - you can create and run any process in your company within seconds.
Settling for basic and cheap project or task management tools is the biggest mistake you can ever make. You get what you pay for. If you try to save a cent - you will lose a dollar. Wasted time (at $40/hour) is far more expensive than the cost of software. There's a huge difference between process management and project or task management. Processes relieve stress, make things predictable - and help you grow and become efficient. Projects and tasks are just ad-hoc, unpredictable chaos.
It's important to understand that context before you carry on reading. Successful people are smart enough to fundamentally change the way they work "right now" and amaze themselves and everyone else with new ideas. You can stop fighting uphill battles every day immediately - and drive more personal success in your career by introducing the modern way of creating, tracking and even enjoying tasks with your coworkers.
Anyway ... sorry for the interruption! Let's resume the rest of the article.
Are you looking to document and run your processes?
Don't use MS Word or Google Docs, and don't use flowcharts.
Documenting your processes using flowcharts might look pretty and nice – but you can’t run them. Even worse – nobody looks at flowcharts.SEE WHY HERE
Many consultants see BPMN as the “Rolls Royce” of business process modeling techniques because most other forms of business process modeling were developed for other purposes and then adapted. In fact, BPMN is the culmination of a process in which businesses sought a best practice method for business process modeling. Nevertheless, there are analysts and consultants who prefer other methods.
BPMN symbols fall into the following categories:
- Flow objects: Events are represented by circles, activities fit into rectangular boxes with rounded corners, and gateways or control points are represented with diamond shapes.
- Connecting objects: Since tasks are interconnected, we join them up to show their sequence. Solid lines indicate task transfers, and dashed ones indicate messages.
- Swim lanes: A single sub-process in your workflow could require the sharing of responsibility. Swim lanes detail how these shared responsibilities are distributed and how they interact. The sub-task is the “pool” and the “lanes” represent people or departments.
Are you interested in truly useful analysis of the latest trends in business tech and ops? Talking from the Trenches is published once every 2 weeks by Tallyfy and it's unmissable. You'll be smarter and better informed automatically. So - don't leave this page without subscribing to it.
Anyway ... we'll continue from where we left off above.
- Artifacts: If you need to add extra information that isn’t a sequence flow or message flow but that helps to explain a process, you can use artifacts. Dotted lines point to the flow object the extra information expands on. Squares outlined with dots and dashes group elements in the diagram, and text annotations are added with a square bracket.
2. UML Diagrams
UML (Unified Modeling Language) diagrams offer an alternative business process modeling technique. The modeling language was developed by software developers, but it can be adapted to business process modeling. There’s just one problem with UML Diagrams, or rather, we should say that there are no fewer than fourteen problems! There are no less than 14 UML diagram types. As you can imagine, this limits UML Diagrams’ usefulness because understanding this type of diagram is a whole lot more difficult than interpreting BPMN-based representations.
Although there’s some debate about which approach is best for business process modeling, most experts agree that BPMN is process oriented while UML is object-oriented and that this makes BPMN better for business process representation.
BPMN is really an evolution of UML, but while UML was initially intended for software developers, BPMN was specifically developed for capturing business processes. Nevertheless, it there are those who prefer it as a means of capturing business processes.
Even if BPMN and UML are new to you, you probably know what a flowchart looks like. In fact, you may be wondering how BPMN differs from a regular flowchart. BPMN is really an evolution of the flowchart. So why not just use regular flowcharts?
The drawback of old-fashioned flowcharts is that they rely on sequential flows and don’t support parallel activities that form part of a process. Because you can’t capture as much information with this type of representation, it is best used for very simple and predictable processes that don’t require much elaboration.
Basic flowcharts were used to capture processes long before BPMN was conceived, and we can see BPMN as being an innovation that makes flowcharts much more informative and useful. This having been said, some consultants find that understanding BPMN isn’t easy for beginners and prefer to use a series of interrelated flowcharts since they don’t require as much of a learning curve.
If you’re mapping relatively straightforward business processes, the flow chart might be just the tool you need to capture your business processes quickly, simply and effectively.
4. Yourdon’s Data Flow Diagrams (DFDs)
Data flow diagrams were developed back in the seventies and their purpose is to represent data flows rather than activities.
While business process analysts give the nod to data flow diagrams, they generally agree that Yourdon’s technique is dated and has one big limitation: it focuses on information rather than action. Data flow diagrams are, by definition, data-focused and don’t provide a clear way to include all stakeholders in the process whereas BPMN can.
Nevertheless, if your workflows are largely data-driven or based on information flows, this form of business process notation could suit your needs.
5. Gantt Charts
In the late nineteenth century, Gantt charts were the gold standard, and they’re sometimes still used. For example, a student preparing a dissertation will often be called on to provide a Gantt chart that breaks the task down into sub-tasks, each of which has a specific time-frame.
It’s still a useful tool, but in the BPM context, it is a little too simplistic to accommodate the many subtasks involved in completing some business processes. However, when preparing for projects with distinct timelines, businesses still find Gantt charts helpful.
Whereas Yourdon’s notation focuses on data, Gantt charts are time-focused, so time-sensitive processes can easily be captured and tracked. It’s easy for the people in charge of different parts of the process to see when they are meant to begin work and by when each task should be complete. Managers can use their Gantt charts to check whether all the subprocesses are running according to schedule.
6. PERT Diagrams
The early twentieth century saw the introduction of Program Evaluation and Review Technique (PERT) diagrams, which seek to break business process flows into timelines by estimating the shortest, longest, and likeliest times for the completion of each step in a business process.
The value of the PERT diagram is that it not only shows the critical path that must be followed towards outcomes but also helps to determine realistic time-frames for the process. That makes it particularly helpful in setting goals and targets and in comparing different process approaches to determine which will be more efficient.
7. Functional Flow Block Diagrams
Functional Flow Block Diagrams may have been around for a few decades, but they still have their uses in business process mapping. Their focus is the order of execution of tasks or functions in a sequence of ordered blocks.
Each functional block can be further broken down in a separate diagram showing the sub-tasks within each functional block. Of course, this results in a whole lot of diagrams representing a single process, but it’s easy to cross-reference them in relation to the first-level diagram.
Some businesses prefer FFDs because, despite the need for several diagrams, they’re relatively easy to follow – even when the process is rather complex.
8. Integrated Definition for Function Modeling (IDEF)
Like functional Flow Block Diagrams. Parent activities give rise to child diagrams. There are various forms of IDEF, but for enterprise modeling, IDEF0 is the permutation to use. It’s certainly a sophisticated system, but its limitation lies in in its complexity.
There are 15 forms of IDEF and each addresses a different type of flow. Thus, there are different forms of IDEF for functions, information, data, simulation model design, process description capture, and so on.
9. Petri Nets and Colored Petri Nets (CPNs)
You may need a course of study before you can effectively use them, but Petri Nets, and their Colored Petri net cousins are worth noting as one of the possible ways in which business processes can be mapped. Unlike flow charts, which struggle with parallel processes, Petri Nets are helpful in mapping processes in which several sub-processes must happen simultaneously or must be synchronized.
The CPN consists of places, transitions, and arcs, and although the mathematical language used to express them is complex, a person who is well-versed in their use can deploy them, and the related math, to test processes out.
BPM Software: Best Use of Business Process Modeling Techniques
While BPM modeling techniques are useful on their own, they’re best used through BPM software.
The software allows you to create process models online, as well as letting you digitize your processes. Meaning, the processes are enforced by the software, making sure that your employees follow the best practices.
To get the most out of your processes, give our BPM software a try.