openskills.info
Open Course

Business Process Modeling

Business process modeling represents organizational workflows as structured diagrams showing activities, decisions, events, and handoffs. It makes implicit processes explicit so they can be analyzed, improved, automated, or communicated to stakeholders.

itEngineering leadership and delivery management

Don’t Panic — Business Process Modeling

Business process modeling is how you make repeatable work visible without pretending that a rectangle has personally observed the work. The process is what people and systems actually do. The model is a purposeful version of that behavior, drawn so its sequence, decisions, handoffs, and outcomes can be inspected instead of lurking in a procedure document like an unpaid invoice.

Begin with the boundary. Name the event that starts the work and the outcome that ends it. Then gather recent normal and difficult cases. A BPMN diagram, meaning Business Process Model and Notation, can give that evidence a precise shared grammar: events say something happened, activities show work, gateways choose or join paths, and flows show how behavior moves. The surprise is that more symbols do not make the model truer. A very elaborate diagram can faithfully preserve a very confident misunderstanding.

The useful split is between an as-is model, which records current behavior including detours, and a to-be model, which records an intended design. Mixing them is a small administrative miracle: the evidence and the proposal become impossible to distinguish, and everyone can agree without agreeing on anything. Keep them separate. A model earns trust when people can walk real scenarios through it and identify the performer, input, decision, handoff, and clear outcome at each step.

When participants are separate, message flows show communication between them; sequence flows remain inside one process. That distinction matters because a diagram is not a collection of friendly arrows. It is a claim about what can happen next. Trace a token from the start through normal success, rejection, missing information, timeouts, and parallel work. If it gets stuck or arrives somewhere mysterious, the model has delivered useful news, even if the news is annoying.

Read the Intro for the full vocabulary and the limits of the model. Use Slides for the relationships among pools, lanes, gateways, and flows. Keep the Cheatsheet beside a modeling session for connection rules and review questions. The Practice Reference turns a refund process into a compact modeling session. Then take the Exercise when you need a complete scenario, observable outcomes, and a test of whether the diagram explains work rather than merely decorating it.

Where this skill leads

Relevant careers

See how this topic contributes to broader role-level skill maps.

Sources