How to read a process map
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-28-2024 09:05 AM
Can you please explain how to read this process map shared below-
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-28-2024 11:47 AM
4 items have gone through the process:
- 2 went down the "true" path and 2 went down the "false" path. No idea what field is providing the true false field value.
- The numbers written on the arrow lines are the quantity of records and the average time on that journey.
- This is showing that 2 records moved from New to Problem Analyzers, and 2 others went to Assess. Remember again, the arrows are showing you quantities and average times. This can help you explain (at scale) why certain things take so long.
- This section is just showing you that all 4 items went in a strictly linear fashion down through the other states in order. Once again, lines show you how many and average time. This is a lovely visual way to tell you what parts of the process are consuming the most time.
These maps get WAY more interesting the larger and more varied the data set.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-29-2024 04:24 AM
Thanks Rob for the assist.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-29-2024 04:28 AM
There are a number of great resources to help you get started with Process Mining. Including reading the visualized process maps and how they help you identify process inefficiencies. This Guide to getting started post packages up some key resources. There is a link to a quick demo which will give you a good feel for the solution, a recording that details the different aspects of a Process Mining project and how to create one, there is a recording that walks through how to use the map, and then a recording that highlights the top 10 use cases. Take a look at those and let us know if you have questions.