BPM360 Podcast - Covering Every Angle

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:

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.

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.

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.

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.

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 [email protected]

if you like our content, please like and subscribe...

In this special guest episode, the hosts welcome Jan Scheele, a serial entrepreneur, TEDx organizer, blockchain expert, and World Economic Forum digital leader, for a wide-ranging conversation about AI's impact on work and communication. Jan shares his journey from teenage coder to running multiple ventures across digital agencies, crypto startups, and speaker coaching, offering unique perspectives on staying productive while managing diverse commitments. The discussion explores how AI is rapidly transforming enterprise workflows, moving from simple content generation tools to sophisticated agents that can orchestrate complex business processes autonomously. Jan introduces the concept of becoming an "orchestrator" rather than a specialist—someone who can coordinate AI agents and tools rather than performing tasks manually. The hosts examine how traditional presentation and communication skills remain crucial even as AI handles more routine work, emphasizing the irreplaceable value of human connection and storytelling. The conversation touches on practical AI implementation strategies, from using tools like ChatGPT and Claude for daily workflows to thinking about enterprise-wide deployment with proper guardrails. Jan advocates for first principles thinking—starting from zero-based assumptions rather than retrofitting AI into existing processes—drawing inspiration from mental models used by leaders like Elon Musk. The episode concludes with insights on adapting to rapid technological change while maintaining focus on what truly matters: execution, efficiency, and human-centered communication.

5 Key Takeaways:

Become an Orchestrator, Not Just a Specialist: The future belongs to professionals who can coordinate and direct AI agents and tools rather than performing all tasks manually—companies are already hiring "AI orchestrators" instead of multiple specialists in fields like law, development, and marketing.

AI Agents Are the Next Frontier: We're moving beyond simple prompt-based AI tools to autonomous agents that can execute complex, multi-step business processes independently—early adoption of agentic workflows will create competitive advantages as the technology matures rapidly.

Human Communication Skills Matter More, Not Less: As AI handles routine tasks, the ability to tell compelling stories, present ideas persuasively, and create genuine human connections becomes increasingly valuable and differentiating—these uniquely human skills cannot be automated.

Apply First Principles Thinking to AI Integration: Instead of asking "where can we plug AI into existing processes," start from scratch using zero-based thinking to reimagine workflows entirely—this mental model approach yields more transformative results than incremental improvements.

Process Intelligence Provides AI Guardrails: In enterprise environments, your documented processes, compliance frameworks, and operational standards become the essential boundaries that keep AI aligned with organizational requirements—process management is fundamental to responsible AI deployment at scale.

In case of questions or suggestions, please reach out to us on [email protected]

If you like this content, please like and subscribe! Thank you...

In this episode, Russell and Caspar explore one of the most critical yet under-resourced roles in BPM implementations: the change management lead. They examine why BPM fundamentally reshapes how people work and why this requires someone dedicated to the people side of transformation beyond generic communication plans. The discussion reveals the delicate balance between empathy and persuasive communication, understanding human resistance while translating it into actionable interventions. Through candid conversation, they explore why change management is often the first role to be cut when budgets are tight, despite being essential for success. The hosts debate whether change management is truly a distinct skill set or something project managers can handle alongside their other responsibilities. They examine the critical importance of timing—knowing when to launch communication initiatives, when it's too early, and when momentum will be lost if you wait. The conversation highlights how real change management goes beyond newsletters and training sessions to understanding the psychology of adoption and resistance. Listeners learn why creating FOMO (fear of missing out) is more effective than mandating compliance. The episode provides insight into the sweet spot of when to intensify change efforts during BPM implementations. This is honest discussion about a role everyone agrees is important but few organizations properly staff or fund.

5 Key Takeaways:

Change Management Is About People, Not Just Communication: The role requires genuine empathy to understand human resistance and translate it into actionable interventions—not just generic newsletters, training sessions, and town halls that check boxes without driving adoption.

Timing Is Everything: Change managers must have the experience and feeling for the right moment to communicate—going out too early creates unanswered questions and confusion, while going too late loses momentum and makes people feel excluded from decisions.

The First Role Cut, The Last One Needed: Despite universal agreement that change management is critical, it's often the first role eliminated when budgets are tight, forcing project managers to handle it alongside other duties without the specialized psychology and influence skills required.

FOMO Drives Adoption: Creating fear of missing out is more effective than mandating compliance—people need to feel they're part of something valuable and exciting rather than being forced to adopt new processes through top-down directives.

Mass Movement Requires Resources: While empathy and communication skills are essential, successfully moving large groups of people also requires budget for sustained campaigns, events, recognition programs, and ongoing engagement—change at scale isn't free.

Please like, subscribe or share and if you have questions or ideas for topics: [email protected]

In this episode, the hosts dive deep into one of the most critical yet misunderstood roles in BPM: the business process architect. They explore the fundamental question of what this role actually is and does, examining the balance between systemic thinking and functional depth. The discussion reveals why organizations struggle to find people who can simultaneously see the helicopter view and understand technical details across multiple domains. Through practical examples, they debate where the architect's responsibility ends and the subject matter expert's begins, using the house-building analogy to illustrate the natural handoff points. The hosts examine why business process architects face far greater resistance than building architects despite similar levels of expertise and authority. They explore the organizational positioning of architects—whether they belong in a centralized Center of Excellence or distributed across business units. The conversation distinguishes between content expertise (owned by architects) and methodology definition (owned by methodology specialists). Listeners learn why most organizations need multiple process architects rather than one universal expert. The episode provides clarity on the relationship between architects, analysts, and experts in the process ecosystem. This is essential listening for anyone building or staffing a process management function.

5 Key Takeaways:

Architects Need Depth AND Breadth: The business process architect must combine systemic helicopter-view thinking with functional precision, but expecting one person to cover multiple functional domains (finance, procurement, manufacturing) deeply is unrealistic—plan for multiple architects.

Level 3 Is the Handoff Point: Architects should own the process architecture (Level 1-2) and understand Level 3 process flows, but detailed process execution expertise should come from subject matter experts—architects design the framework, experts fill in the specifics.

Authority Without Credentials Is the Challenge: Unlike building architects who command automatic respect through professional licensing, business process architects must fight much harder to enforce standards and resolve conflicting demands across business units despite having comparable expertise.

Content vs. Methodology Ownership: Process architects own functional content (what goes into finance or procurement processes), while methodology owners define how modeling and documentation work—these are distinct roles that may be combined early but should separate as maturity grows.

Central Positioning Enables Scale: Ideally, process architects should sit in a centralized Center of Excellence or process services group rather than being embedded in individual business units, allowing them to serve the entire organization and maintain consistency across domains.

If you have question or ideas for our podcast, please send them to [email protected].
If you want to book yourself as a guest on our show, please use this link: https://koalendar.com/e/bpm360-podcast
If you want to interact with us, check us out on LinkedIn (https://www.linkedin.com/company/bpm360podcast/about/?viewAsMember=true) or Substack (https://bpm360podcast.substack.com/)

In this episode, the hosts challenge one of the most fundamental mistakes organizations make when building process capabilities: creating vague, catch-all BPM roles that set teams up for failure. They dissect how generic titles like "Process Manager" or "BPM Expert" obscure what people actually do and create confusion across the organization. The discussion reveals why role clarity isn't just an HR issue—it's directly tied to whether your process initiatives succeed or stall. Through real-world examples, they explore the spectrum of process roles from analysts to architects, demonstrating why each requires distinct skills and serves different purposes. The hosts emphasize that lumping everything under one umbrella role leads to mismatched expectations, poor hiring decisions, and frustrated employees. They examine how clear role definitions enable better collaboration, more effective capability building, and stronger career progression. The conversation provides practical guidance on distinguishing between process execution, improvement, design, and governance roles. Listeners learn why specificity in role design translates directly to performance and outcomes. The episode offers a framework for defining roles that actually reflect the work being done. This is a wake-up call for organizations that wonder why their BPM talent keeps underperforming or leaving.

5 Key Takeaways:

Generic Titles Create Generic Results: Vague roles like "BPM Expert" or "Process Manager" obscure what people actually do, leading to mismatched expectations, poor hiring, and unclear accountability across the organization.

Distinguish the Four Core Functions: Separate process execution (running processes), process improvement (optimizing existing processes), process design (creating new processes), and process governance (setting standards)—each requires different skills and mindsets.

Match Skills to Specific Needs: A process analyst needs data analysis and problem-solving abilities, while a process architect requires systems thinking and design expertise—hiring for "BPM" without this distinction leads to capability gaps.

Role Clarity Drives Collaboration: When everyone understands who does what in the process ecosystem, handoffs become smoother, overlaps decrease, and cross-functional work becomes more effective.

Career Paths Need Specificity: Clear role definitions enable meaningful career progression and skill development; without them, BPM professionals lack direction and organizations struggle to retain top talent.