In this special guest episode, Russell and Caspar welcome Walter Bril, co-creator of Universal Process Notation (UPN), for a candid conversation about making process management practical and useful rather than academically perfect. Walter shares his journey from UNIX administrator to process management thought leader, explaining how he became intrigued by the patterns and thinking behind business operations rather than just faster technology. The discussion centers on UPN's philosophy of simplicity—using fewer symbols and making process models more accessible to non-technical audiences while maintaining the ability to capture essential business logic. Walter challenges the notion that more complexity equals better modeling, advocating instead for "good enough" documentation that people actually use. The conversation explores the tension between BPMN's comprehensive but complex approach versus simpler notations that prioritize adoption and practical value.

They examine how AI and automation are changing the documentation game—from generating initial models from unstructured information to enabling process analysts to shift from creation to validation. Walter emphasizes the importance of getting out of the "dark corner" by demonstrating business value rather than forcing process models down people's throats.

The episode provides refreshing honesty about what works in real-world BPM implementations. This is essential listening for practitioners tired of academic approaches that don't translate to business results.

5 Key Takeaways:

1. Keep It Practical, Not Academic: Don't pursue mathematically correct or theoretically perfect process models—focus on what businesses can actually use and benefit from, even if it's not as comprehensive or precise as academic standards would demand.

2. Automate Documentation Creation: The future of process modeling is shifting from manual creation to automated generation using process mining, configuration mining, and AI extraction from unstructured information—analysts should focus on validation and refinement rather than starting from scratch.

3. Simplicity Drives Adoption: Using fewer symbols and simpler notations (like UPN's approach) makes process models more accessible to business users and increases the likelihood they'll actually be used, which matters more than comprehensive technical detail.

4. Don't Force Processes Down People's Throats: Early in his career, Walter learned that telling people "you must look at these diagrams because processes are important" doesn't work—models must demonstrate clear business value to gain organic adoption and escape the "dark corner" of the organization.

5. Documentation Is Not Automation: Process models and notations serve primarily as communication and understanding tools, not as automation specifications—don't confuse the purpose of business process documentation with workflow automation or orchestration requirements.

If you have questions or suggestions about our podcast, please shoot us a message at [email protected]

If you enjoy our content, please like, rate, subscribe and follow us on LinkedIn, Spotify, SubStack or whatever rocks your boat.

Enjoy this episode...