BPM360 Podcast - Covering Every Angle

Ep. 62: "The Business Process Architect: Superman or Strategic Designer?"

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 questions@bpm360podcast.com [questions@bpm360podcast.com]. If you want to book yourself as a guest on our show, please use this link: https://koalendar.com/e/bpm360-podcast [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 [https://www.linkedin.com/company/bpm360podcast/about/?viewAsMember=true]) or Substack (https://bpm360podcast.substack.com/ [https://bpm360podcast.substack.com/])

Ep. 61: Stop Hiring 'BPM Experts': Why Your Role Definitions Are Killing Process Excellence

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.

EP. 60: "The Iceberg Effect: Why Your Process Problems Are Just Symptoms"

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.

Ep. 59: "From Firefighting to Flow: Why Your BPM Team Needs to Stop Being the Doers"

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.

Ep. 58: "Beyond the Boxes and Arrows: Why BPM Is More Than Just Drawing Processes"

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 [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 [https://www.packtpub.com/en-us/product/practical-business-process-modeling-and-analysis-9781805126386] Additional links: BPM Skills cycle on BPMTips.com [http://BPMTips.com]: https://bpmtips.com/category/bpm-skills/ [https://bpmtips.com/category/bpm-skills/]