✅ Process Models Need Purpose Beyond the Modeler: 

Caspar and Russell argue that too often, process modelers design for themselves—not the end users, system integrators, or future teams who will rely on the documentation. A model is only valuable if it’s understandable and actionable by others. 

✅ Granularity is Key—And Often Overlooked: 

Process models must have consistent granularity across end-to-end processes. If one team dives deep while another stays high-level, the result is a mess of mismatched detail. Defining a common granularity is essential for readability and alignment. 

✅ Hierarchies: Flexible or Fixed? 

Should you enforce a rigid number of levels, or let domains grow organically? 

Russell prefers a fixed hierarchy for reporting and governance, while Caspar argues for dynamic hierarchies—adjusting the layers based on complexity and ownership. Both agree: too many layers create confusion; too few limit clarity. 

✅ End-to-End Workshops Unlock True Understanding: 

A standout story: Russell shares how a customer’s bottom-up process design didn’t match the top-down end-to-end flow—until a workshop revealed gaps in handovers, compliance checks, and system integration. The lesson? Bring people together early and often. 

✅ Naming Conventions: Less Code, More Clarity: 

Caspar warns against stuffing hierarchy codes into process names (“1.2.3.4 Create Sales Order”), favoring clear, descriptive titles that support search and comprehension. Codes belong in metadata, not front and center. 

✅ BPMN Models ≠ Process Hierarchies: 

Russell reminds us: process hierarchies are structures, not actual processes. Don’t confuse categories like “Finance” with executable processes like “Create Invoice.” Keep hierarchies simple, processes precise. 

✅ Process Modelers: Less Ego, More Empathy: 

In a tongue-in-cheek moment, Caspar quips: “Process modelers are selfish bastards. They need to think about others.” The real takeaway: Process modeling is a service, not an art project. 

✅ The Lego Analogy: 

Caspar’s favorite metaphor: Process hierarchies are like Lego boxes—they organize bricks so everyone can build efficiently. Without structure, it’s just a chaotic pile. 

✅ Final Word: 

Process models should serve multiple audiences: the integrators, the rollout teams, the end users, and future generations. Build with empathy, not just logic. 

We hope you enjoy our BPM Podcast.
Subscribe and stay tuned for more.
Please send us your comments and questions to
questions@bpm360podcast.com