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:

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 [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:

1. 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.

2. 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.

3. 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.

4. 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.

5. 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:

1. 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.

2. 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.

3. 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.

4. 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.

5. 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:

1. 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.

2. 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.

3. 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.

4. 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.

5. 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:

1. 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.

2. 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.

3. 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.

4. 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.

5. 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.

In this episode, the hosts dive deep into the critical mistake many organizations make: treating surface-level process issues without addressing the underlying root causes. They introduce the concept of the "iceberg effect" in process management, where visible problems are merely symptoms of deeper systemic issues lurking beneath the surface. The discussion explores how rushing to fix what's immediately obvious often leads to wasted effort, temporary solutions, and recurring problems. Through compelling examples, they demonstrate how what appears to be a process breakdown is often actually a technology limitation, organizational culture issue, or capability gap. The hosts emphasize the importance of taking time to properly diagnose before prescribing solutions, even when stakeholders are pressuring for quick fixes. They share practical techniques for uncovering root causes, including asking "why" multiple times and examining patterns across different process failures. The conversation highlights how addressing symptoms creates busy work while solving root causes delivers exponential value. Listeners learn why investment in proper analysis upfront saves significant time and resources downstream. The episode provides a framework for distinguishing between symptoms and causes in process improvement work. This is essential listening for anyone tired of fighting the same process fires repeatedly.

5 Key Takeaways:

1. Look Below the Waterline: Like an iceberg, most process problems have visible symptoms above the surface, but the real issues—poor system integration, capability gaps, cultural resistance—lie hidden beneath and must be addressed for lasting solutions.
2. Resist the Quick Fix Pressure: When stakeholders demand immediate solutions, invest time in proper root cause analysis first; fixing symptoms creates recurring problems while solving root causes prevents future issues from emerging.
3. Ask "Why" Repeatedly: Use techniques like the "5 Whys" to drill down from surface symptoms to underlying causes—each answer should prompt another question until you reach the true source of the problem.
4. Pattern Recognition is Key: Look for similar issues occurring across different processes or departments; these patterns often reveal systemic root causes rather than isolated process failures.
5. Educate Stakeholders on True Costs: Help leadership understand that rushing to symptom-level fixes wastes more resources over time than investing upfront in root cause analysis—short-term speed often means long-term waste.

In this episode, the hosts tackle one of the most common pitfalls in business process management: when BPM teams become permanent process operators instead of enablers of change. They explore how organizations often fall into the trap of having their BPM experts do the work rather than embedding process excellence into operational teams. The discussion reveals why this creates dependency, prevents scaling, and ultimately undermines the strategic value of process management. Through real-world examples, they illustrate how BPM should function as a catalyst for organizational capability building rather than a permanent fix-it squad. The hosts emphasize that true process maturity means teaching teams to fish rather than fishing for them indefinitely. They examine the delicate balance between providing initial support and knowing when to step back. The conversation highlights how governance, clear boundaries, and outcome ownership are essential to breaking the cycle of dependency. Listeners learn why saying "no" strategically can be more valuable than always saying "yes." The episode provides practical guidance on transitioning from doer to enabler and building sustainable process capabilities. Ultimately, this is a call to action for BPM professionals to reclaim their strategic role and drive lasting organizational change.

5 Key Takeaways:

1. Break the Doer Dependency: BPM teams should enable and empower process owners rather than becoming permanent operators who do the work for them—otherwise you create unsustainable dependency and prevent true organizational capability building.

2. Define Clear Boundaries Early: Establish upfront what the BPM team will and won't do, including time-bound support arrangements, to avoid becoming the default solution for every process problem.

3. Focus on Capability Transfer: The goal is to build process management muscles within operational teams through training, coaching, and gradual handoffs—not to maintain control indefinitely.

4. Tie Support to Outcomes: When providing temporary assistance, link it to measurable outcomes and specific capability development milestones to ensure teams are progressing toward self-sufficiency.

5. Strategic "No" is Powerful: Learning to decline requests that would perpetuate dependency allows BPM teams to focus on higher-value strategic work and forces organizations to develop their own process competencies.

Summary

In this engaging episode, Caspar and Russell sit down with BJ Biernatowski and Zbigniew Misiak, co-authors of "Practical Business Process Modeling and Analysis," to discuss the evolving role of BPM in digital transformation. The guests share their journey of writing a book that took two years and was initially double its final size, revealing just how vast the BPM domain truly is. They tackle the uncomfortable truth that selling BPM is "one of the most unthankful jobs in the world," as organizations often see process modeling as isolated from actual business value. The conversation explores how BPM must shift from creating static BPMN diagrams to providing dynamic insights about organizational dependencies and connections. A major focus emerges around AI's transformative impact: AI needs BPM as "guardrails" to prevent hallucinations and ensure reliable outputs, while BPM needs AI to make process knowledge more accessible and actionable. The guests emphasize that successful BPM isn't about perfect models—it's about connecting processes to enterprise architecture, applications, roles, risks, and regulations in a unified repository. They discuss how AI agents will fundamentally change process work beyond simple sequential automation, requiring new approaches to modeling complex, non-linear workflows.

5 Key Takeaways

Value Over Visualization: Managers don't care about process models—they want results. BPM must focus on delivering measurable value (better communication, faster projects, fewer problems) rather than creating beautiful BPMN diagrams that only the modeler can read.

AI Needs BPM as Guardrails: AI systems require process repositories to provide reliable, context-aware information and prevent hallucinations. BPM gives AI the boundaries, regulations, goals, and organizational context needed to make trustworthy decisions aligned with business strategy.

The Repository Revolution: Modern BPM repositories must evolve beyond static process maps to become dynamic, real-time representations connecting processes, applications, roles, risks, regulations, and enterprise architecture—creating a unified knowledge graph accessible to both humans and AI.

Beyond Sequential Thinking: Traditional process modeling focused on linear sequences (A→B→C→D) suitable for automation, but AI agents enable non-linear, case management approaches requiring new modeling paradigms like object-centric process management to handle organizational complexity.

Convergence Is Coming: The artificial separation between BPM and Enterprise Architecture must end—both disciplines look at the same organization from different angles, and AI-powered tools can finally unite them into consolidated repositories that serve multiple use cases simultaneously.

Book Practical Business Process Modeling and Analysis

Amazon:
https://www.amazon.com/Practical-Business-Process-Modeling-Analysis/dp/1805126741

Packt:
https://www.packtpub.com/en-us/product/practical-business-process-modeling-and-analysis-9781805126386

Additional links:

BPM Skills cycle on BPMTips.com: https://bpmtips.com/category/bpm-skills/

"Is BPM the Scapegoat for AI Failures? A Critical Look at Process Management's Future"

In this candid episode, Caspar and Russell tackle the uncomfortable question: Is BPM destined to become the scapegoat for failing AI initiatives? They dive into Deloitte's Tech Trends 2026 report, which predicts that 40% of AI projects will be cancelled, and explore BPM's role in these failures. Russell questions whether there's a fundamental flaw in BPM methodology that prevents widespread adoption, while Caspar argues it's too early to blame a use case that's only 18 months old. The conversation takes an intriguing turn when they examine the tension between agile methodologies and process governance, with both hosts agreeing that organizations need structure at higher levels while allowing agility at granular levels. They discuss the challenge of integrating BPM into organizations already saturated with methodologies like Lean Six Sigma and Scrum. A key insight emerges: never appoint a perfectionist to lead your BPM project—generalists should be at the top with perfectionists handling the details. They also explore the complexity of defining process ownership, especially the critical role of end-to-end process owners, and debate whether BPM practitioners should adapt their standard role frameworks to fit existing organizational structures. The episode concludes with a promise to tackle the controversial topic of process taxonomy and SAP's influence on enterprise architecture in their next discussion.

1. The Scapegoat Risk: With 40% of AI initiatives predicted to fail by 2027, BPM risks becoming the fall guy despite the BPM-for-AI use case being only 18 months old—too early to judge its effectiveness.
2. Agility Needs Structure: Organizations should allow agile methodologies at granular levels (individual products or use cases) but maintain structured governance at higher levels to prevent chaos across 127+ development tribes.
3. Generalists Lead, Perfectionists Execute: Never appoint a perfectionist to lead BPM initiatives—put pragmatic generalists at the top and save perfectionists for detailed, lower-level work where precision matters.
4. Adapt to Existing Structures: Rather than imposing standard BPM roles on organizations already saturated with methodologies (Scrum, Lean Six Sigma), start with defining the end-to-end process owner and build around existing organizational capabilities.
5. Value Comes from Connections: The true value of BPM isn't in having models—it's in understanding the dependencies between enterprise artifacts (activities, roles, applications, risks) to prevent unintended consequences from changes.

Keywords

AI, business processes, innovation, change management, organizational structure, data quality, Stephen Wunker, BPM, technology adoption, consulting

Summary

In this episode of the BPM 360 Podcast, hosts Caspar and Russell engage with Stephen Wunker, managing director of New Markets Advisors, to discuss the transformative impact of AI on business processes and organizational structures. They explore the importance of adapting to change, the role of innovation in large enterprises, and the necessity of critical thinking in the age of AI. Stephen shares insights from his extensive experience in consulting and his latest book, 'AI and the Octopus Organization,' emphasizing the need for organizations to rethink their processes and embrace AI as a tool for achieving business objectives.

Takeaways

AI is a revolutionary tool that requires rethinking business objectives.

Organizations must adapt to change and embrace innovation.

The octopus serves as a metaphor for adaptability in business.

AI can enhance decision-making but requires human engagement.

Data quality is crucial for effective AI implementation.

Change management involves addressing emotional responses to disruption.

Startups and large enterprises face different challenges in innovation.

Experimentation is key to successful AI integration.

Organizations should prioritize a few key business questions for transformation.

Critical thinking is essential in the age of AI.

Sound bites

"AI is better than a human being."

"You cannot tango on your own."

"AI makes mediocre workers decent."

Chapters

00:00 Introduction and Personal Updates

02:24 The Impact of AI on Business

03:34 Stephen Wunker's Background and Expertise

06:33 Innovation Processes in Large Enterprises

10:13 The Role of Structure in Startups

11:56 AI as an Organizational Enabler

17:39 Rethinking Business Models with AI

21:10 The Importance of Data Quality

23:48 Emotional Aspects of Change Management

30:30 Strategies for AI Integration

33:32 Distributed Intelligence in Organizations

36:29 The Future of AI and Human Collaboration

42:54 Final Thoughts and Dilemmas