Ep. 68: "The Process Owner Part 1: Accountability Without Authority Across Silos"

Ep. 69: "BPM AI Orchestration: Building the Next Generation of Process Management"

In this guest episode, Russell and Caspar welcome Ahmad Daliri, a process management specialist working at NN in the Netherlands and author of multiple BPM books, for a conversation about the intersection of artificial intelligence and business process management. Ahmad shares his unconventional journey from mechanical engineering to falling in love with BPM after discovering the missing link between operational work and strategic objectives. The discussion explores Ahmad's current work on "BPM AI orchestration"—a concept focused on how AI can make process management more effective and accessible rather than just automating existing processes. The hosts examine the shift from traditional process modeling to AI-assisted approaches, including the emerging capability of converting voice conversations into process models. Ahmad introduces his framework of five layers for BPM AI orchestration: voice-to-BPM conversion, context understanding, rules and responsibility interpretation, intelligence and decision-making, and user interface design. The conversation highlights the critical importance of context and quality data in training enterprise AI agents to understand organizational boundaries and process standards. They debate the current maturity level of AI in BPM, acknowledging that while the technology shows promise, we're not yet ready for fully autonomous AI-driven process management. The episode concludes with insights on preparing for the paradigm shift in how process work will be conducted in the coming years. 5 Key Takeaways: 1. BPM AI Orchestration Is About Making BPM Easier: The goal isn't just automating processes with AI, but using AI to make process management itself more effective and accessible for process specialists—reducing manual work in modeling, analysis, and documentation. 2. Voice-to-Process Modeling Is Emerging: AI is enabling the conversion of natural language conversations with subject matter experts directly into process models, potentially transforming how process knowledge is captured from interviews and workshops into structured BPMN or other notations. 3. Context and Quality Data Are Critical: For enterprise AI to work effectively in BPM, it needs high-quality contextual data including documented processes, compliance frameworks, and operational standards—this organizational knowledge becomes the guardrails that keep AI aligned with requirements. 4. Five Layers of BPM AI Orchestration: Ahmad's framework includes voice-to-BPM conversion, context and knowledge understanding, rules and responsibility interpretation, intelligence and decision-making capabilities, and user interface design—all necessary for comprehensive AI integration in process management. 5. We're in Transition, Not There Yet: While AI shows significant promise for transforming BPM work, the technology isn't mature enough for 100% autonomous process management—the industry is currently in a paradigm shift that requires preparation and gradual adoption rather than immediate wholesale replacement. In case of questions: please reach out at questions@bpm360podcast.com [questions@bpm360podcast.com]. If you like our content, please like, rate and subscribe. We appreciate that.

Ep. 68: "The Process Owner Part 1: Accountability Without Authority Across Silos"

In this episode, Russell and Caspar begin their deep dive into perhaps the most talked-about yet misunderstood role in BPM: the process owner. They immediately tackle the central paradox—being accountable for end-to-end process performance while lacking direct authority over the departments involved. The discussion clarifies a critical distinction: process owners are accountable for improving process performance through optimization and standardization, not for operational outcomes like sales numbers or market conditions. Through detailed exploration, they examine the difference between operational management (filling the sales pipeline) and process ownership (improving pipeline conversion rates through better processes and systems). The hosts distinguish between functional process owners who oversee specific domains like procurement or manufacturing, and end-to-end process owners who orchestrate cross-functional flows like order-to-cash or procure-to-pay. They debate optimal organizational structures, exploring whether end-to-end ownership should be a separate role or combined with functional ownership to avoid role proliferation. The conversation highlights the unique challenge of cross-functional influence—process owners must drive change across organizational boundaries without hierarchical power. This first part sets the foundation for understanding a role that many organizations struggle to implement effectively, with part two promised to cover required experience and enablement strategies. 5 Key Takeaways: 1. Accountability for Process Performance, Not Business Outcomes: Process owners are accountable for improving process metrics (cycle time, quality, compliance) through optimization and standardization—not for operational results like sales numbers, which remain the responsibility of functional managers. 2. Influence Without Direct Authority: The defining challenge of process ownership is driving improvement across departmental silos without hierarchical control—success requires cross-functional influence, credibility, and the ability to facilitate change through persuasion rather than directive power. 3. Functional vs. End-to-End Ownership: Organizations need both functional process owners (procurement, manufacturing, sales) who own vertical domains and end-to-end process owners (order-to-cash, procure-to-pay) who orchestrate horizontal flows across multiple functions. 4. Avoid Role Proliferation Through Dual Assignment: Rather than creating separate positions for functional and end-to-end ownership, allocate end-to-end ownership to one of the functional owners within that flow—for example, the procurement process owner also owns procure-to-pay orchestration. 5. End-to-End Ownership Delivers the Real Value: While functional process ownership is common, the biggest benefits of process management come from establishing effective end-to-end ownership that breaks down silos and optimizes complete business flows from customer request to fulfillment. In case of questions or suggestions, please reach out to us via questions@bpm360podcast.com [questions@bpm360podcast.com] If you enjoy our content, please like, rate and subscribe to our channel.

Ep. 67: "The COE Lead: Strategic Patience and the Long Game of Process Excellence"

In this episode, Russell and Caspar continue their BPM roles series by shifting focus from implementation to steady-state operations, examining the role of the COE (Center of Excellence) lead or head of process excellence. They explore how this role differs fundamentally from the BPM program manager, requiring a shift from project-focused execution to long-term organizational influence and credibility building. The discussion reveals the paradox at the heart of this role: building a COE that people actually come to for help rather than view as a compliance burden takes years of demonstrating value and earning trust. The hosts examine whether successful program managers can successfully transition to COE leadership, given the dramatically different mindset required—from short-term project delivery to strategic patience and sustained organizational change. Through candid conversation, they debate whether the COE lead role becomes dispensable once process management is fully embedded in organizational culture and career paths. The episode explores the critical importance of this role during disruption—when new technologies, market changes, or strategic shifts challenge established process management practices. They discuss how the COE lead must balance maintaining steady-state operations with preparing for and responding to transformative changes. This is valuable listening for anyone building or leading a process management function beyond the initial implementation phase. 5 Key Takeaways: 1. Strategic Patience Over Project Speed: The COE lead requires fundamentally different character traits than a program manager—shifting from time-and-budget focused execution to years-long credibility building and organizational influence that creates lasting process discipline. 2. Building Trust Takes Years: Creating a Center of Excellence that people actually come to for help, rather than viewing as a compliance function, requires consistent demonstration of value, gravitas, and persistence—this cannot be rushed or mandated from above. 3. The Long Game Mindset: Unlike program managers focused on defined deliverables and timelines, COE leads must embrace uncertainty about long-term direction while maintaining momentum—similar to captaining a ship on a voyage with evolving destinations rather than completing a construction project. 4. Potentially Dispensable in Maturity: In truly mature organizations where process management is embedded in culture, career paths, onboarding, and daily operations, the dedicated COE lead role may become unnecessary—success means working yourself out of a centralized leadership position. 5. Essential During Disruption: The COE lead's most critical value emerges when disruption (new technology, market changes, strategic shifts) challenges established process management practices—they must regroup, reform, and provide direction when the house is burning and existing approaches no longer work. If you have questions or suggestions: find us at questions@bpm360podcast.com [questions@bpm360podcast.com] If you enjoy our content, please like, rate, subscribe, we do appreciate it!

Ep. 66: "No Bullshit BPM: Walter Bril on Keeping Process Management Practical"

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 questions@bpm360podcast.com [questions@bpm360podcast.com] If you enjoy our content, please like, rate, subscribe and follow us on LinkedIn, Spotify, SubStack or whatever rocks your boat. Enjoy this episode...

Ep. 65: "The Process Mining Analyst: Detective Work Between Data and Reality"

In this episode, Russell and Caspar conclude their implementation phase roles series by examining the process mining and analysis specialist—a role that sits at the intersection of data science and process expertise. They explore whether this role is truly necessary during BPM implementation or belongs more in the operational phase of process management. The discussion reveals a common organizational pattern: process mining initiatives often emerge from IT and data-driven teams while process documentation efforts originate from compliance and quality management, creating parallel but disconnected efforts. They examine the evolution from "process management" to "process intelligence" as mining and traditional BPM converge into integrated capabilities. Through a detailed war story, they illustrate the detective work required when data patterns don't match expectations—persistence in connecting data anomalies to real-world business practices and custom processes. The conversation highlights the critical skill of making sense of mining tool outputs by connecting data patterns to actual business operations and root causes. They debate the balance between quick wins from standard connectors versus deep custom analysis that requires SQL expertise and system knowledge. The episode emphasizes that while data doesn't lie, it requires human interpretation and dialogue with process owners to understand what it's truly revealing. This is essential listening for organizations trying to integrate process mining capabilities into their BPM programs effectively. 5 Key Takeaways: 1. Mining and Management Often Start Separately: Process mining initiatives typically emerge from IT and data-driven teams while process documentation comes from compliance/quality groups—this parallel evolution creates missed opportunities for integration that mature organizations must address. 2. Think Mining Into Your BPM Organization Early: Even if you're not immediately implementing process mining, include this role in your BPM capability planning from the start—waiting until later risks creating siloed initiatives that don't connect to your broader process architecture. 3. Standard Connectors Enable Quick Wins: For common ERP systems like SAP, standard process mining connectors can deliver fast results without deep technical skills—this makes mining accessible during implementation for baseline understanding and validation of documented processes. 4. Deep Analysis Requires Detective Persistence: The core capability is connecting data patterns to business reality through dialogue with process owners—analysts must persist in understanding anomalies, even when explanations involve custom business logic or non-standard practices that aren't obvious in the data. 5. Data Shows Symptoms, Not Root Causes: Process mining reveals patterns and deviations, but humans must interpret what the data means—the specialist's value lies in translating mining outputs into actionable business insights by understanding both technical systems and operational context. If you have comments, topics to be discussed or questions, please email us at questions@bpm360podcast.com [questions@bpm360podcast.com] if you like our content, please like and subscribe...