The complexity problem

This insurance claims process has 7 tasks in a row. Scroll right — it keeps going. By the time you reach the end you've forgotten how it started.

Now imagine this in a real enterprise: 30, 50, 100 tasks. Error paths, loops, parallel branches. The diagram becomes impossible to reason about.

Run it — then reflect

Press ▶ Play and watch the token crawl across all 7 steps.

Ask yourself: If someone asked you "what does this process do at a high level?" — could you tell them quickly from this diagram?

> 💡 A good BPMN diagram should communicate *intent* at a glance. If a diagram requires close reading to understand, it needs structure. Sub-processes are that structure.