Depth of Modeling

Have you created a process model not knowing how much detail is required for it to be a valuable model? Quite the conundrum because the detail in your process model determines how valuable it'll be.

I talk about the left and right limits of process modeling in this post. That's important. However, it's just as important to identify how 'deep' models go. It's tempting for process professionals to detail every single thing we observe, derive, and elicit. That's usually the 'easy' part. But when do you know it's time to stop? That's just as critical. 

In the context of a process architecture, the depth of modeling is determined by the highest level to the lowest level of modeling. The highest level being the abstract level and the lowest level being the tactical level.

From the abstract to the tactical, modeling standards determine how much granularity is useful. Determining this granularity and keeping it consistent, ensures process models created across your organization are aligned, valuable and predictable for consumers. The right amount of granularity against each level is determined by your modeling purpose. I classify purpose in 2 major categories: communication and improvement.

Communication levels are usually higher and improvement (or automation) requires detailed information is typically at the lower tiers.

Communication:

• Easier to understand for those not familiar with modeling notation
• Captures 80% of process variations
• Refrain from using overly complicated design (which is why aggregation is essential)

Improvement:

• Decomposition of activity including inputs, outputs, enablers and guides
• Describe supporting details of your artifacts such as activity descriptions
• Include process variants

Once you determine the required granularity based on modeling purpose, you are able to document it in the modeling conventions and standards. This exercise ensures those agreed levels are constantly adhered to going forward.