Max is three weeks into his first job at MegaWorld Shoes. A customer wants a size 38 that isn't on the shelf. His manager is at lunch. All he has is a process diagram.
Max has been working at MegaWorld Shoes for exactly three weeks. He's 23, fresh out of university, and this is his first real job. So far he's been doing great - friendly with customers, quick on the register, always on time.
But today is different. A woman walks in, picks up a pair of running shoes, and says: "Do you have these in a 38?"
Max checks the shelf. No 38. He looks around - his manager Elena is on lunch break. The other assistant is helping someone else. Max is on his own, and he has no idea whether he should check the warehouse, call another store, or just apologize.
Then he remembers. During his onboarding, Elena mentioned something about a process handbook. He pulls it up on the store tablet and finds: "Missing Shoe Size - What To Do."
It's a diagram. A flow chart, but more precise. It tells Max exactly what to do, step by step, for every possible outcome. This diagram is written in BPMN - and by the end of this chapter, you'll be able to read it too.
Every process has a trigger - something that sets it in motion. For Max, it's the moment a customer asks for a shoe size that isn't on the shelf. That's a start event.
In BPMN, start events are drawn as thin circles. They don't ask anyone to do anything - they describe a situation. Something happened. The process has begun.
At the other end, there's an end event - a thick circle. The process is done. Max has handled the situation, one way or another.
Events are circles. They represent states or situations - things that happen. A thin circle starts the process. A thick circle ends it.
The process tells Max what to do first: check the local warehouse. Not "think about it" or "wait for Elena." A clear, concrete action.
In BPMN, actions are called tasks - rounded rectangles. Unlike events (which just happen), tasks require someone to act. Max has to walk to the back, look through the shelves, and find out if the size 38 is hiding somewhere.
The arrow connecting the start event to the task is a sequence flow. It says: "after this situation occurs, do this."
Tasks are rounded rectangles. They represent work that someone needs to do. Sequence flows (arrows) connect elements and show the order.
Max comes back from the warehouse. Either he found the shoes, or he didn't. What happens next depends entirely on the answer.
This is a gateway - a diamond shape with a question on top: "Shoe in stock?" It's called an exclusive gateway because exactly one path is taken. Yes or no. Never both.
If yes - great. Max grabs the shoes from the rack and sells them to the customer. Two quick tasks and the process ends happily.
Exclusive gateways are diamonds. They represent decisions where exactly one path is chosen. A question sits on top. The answer determines which way the process goes.
Let's say Max is lucky. He walks into the warehouse, spots the box on the second shelf, and pulls out a perfect size 38. Back on the shop floor, he hands them to the customer, rings up the sale, and feels like a professional.
In BPMN, this is called the happy path - the ideal scenario where everything goes right. Start, check warehouse, shoes found, sell, done.
Notice the diamond at the end. That's a closing gateway. It doesn't make a decision - it just collects all the paths back together before the end event. Think of it as a meeting point: no matter which route Max took, the process finishes here.
But today isn't Max's lucky day. The warehouse has plenty of 37s and 39s, but no 38. The customer is waiting. What now?
The process has an answer. The "No" branch tells Max to call the second storeacross town. MegaWorld has two locations - maybe they have it.
Another gateway: "Available at second store?" If yes, Max refers the customer there. If no, there's one last option - call express delivery, find out when the shoes can arrive, and let the customer know.
Three possible outcomes, three different paths, but all leading to the same end. Max always knows what to do next. No guessing, no awkward "let me ask my manager." The process handles it.
Fast forward two months. MegaWorld is growing. Elena hires three more shop assistants. None of them have dealt with missing shoe sizes before. Without the process diagram, Elena would explain the same procedure four times. With it, she points new hires to the tablet on day one.
Growth also brings a new role: a warehouse manager. Pulling shoes from the rack is no longer Max's job. But the diagram needs to show who does what.
A pool represents the organization - "MegaWorld Shoes" is a pool. Inside it, lanes divide responsibility. Adding a "Warehouse Manager" lane means the "take shoes from rack" task moves to the right person.
Pools represent organizations. Lanes divide pools into roles or departments. A sequence flow crossing a lane boundary means the work moves to another role. No extra "handover" task needed.
A common mistake: people think you need an extra task for handovers between roles. "Tell the warehouse manager" or "wait for confirmation." You don't. In BPMN, a sequence flow crossing a lane boundary is enough. The arrow says: the work moves to this role now.
This is Max's complete process. Two decisions, seven tasks, three possible outcomes. It fits on a single screen, and any new hire at MegaWorld can read it on day one.
That's the real point. Not the shapes and arrows - those are just notation. The power is that everyone in the organization agrees on how this works. When Elena hires three more assistants next month, she won't explain the missing shoe size procedure four times. She'll point them to this diagram.
And when MegaWorld eventually hires that warehouse manager, one line in the diagram changes - the "take shoes from rack" task moves to a different lane. The process evolves with the business.
Every BPMN diagram uses the same building blocks: events (what happens), tasks (what needs doing), gateways (decisions), and sequence flows (the order).
Interactive diagram coming soon
This will be a live Crismo canvas you can explore and edit
Model this process yourself
Open a free diagram in Crismo and build what you just learned. No signup needed.
Open in Crismo →