Ep. 72: "The BPM Technology Manager: From Tool Guardian to Integration Orchestrator"

In this episode, Russell and Caspar examine the BPM technology and tooling manager role—a position that has evolved dramatically from its origins as a technical gatekeeper to today's integration-focused facilitator. They explore how this person manages the BPM platform ecosystem including process repositories, modeling tools, automation platforms, and process mining solutions while ensuring they remain fit for organizational purpose. The discussion reveals how the role's importance has shifted over time, from the days of on-premises systems requiring deep database schema knowledge and complex upgrades to today's cloud-based environments where new features appear automatically. The hosts debate whether one person typically owns all BPM tooling or if modeling, mining, and automation platforms are managed by different specialists in larger organizations.

Through candid conversation, they examine the tension between becoming a product expert wedded to one vendor versus maintaining objectivity and vendor independence to serve the organization's needs. The episode explores critical character traits including technical adaptability, the ability to train users appropriately without overwhelming them with advanced features they'll never use, and understanding how BPM tools fit into the wider enterprise application ecosystem. They emphasize the importance of working collaboratively with BPM architects to extend methodology and integrate with other systems like risk management, quality management, and project management tools. This is essential listening for understanding how the BPM technology manager role has transformed from maintenance-focused to integration-oriented in the modern cloud era.

5 Key Takeaways:

1. The Role Has Evolved Dramatically: BPM technology managers have shifted from being on-premises system gatekeepers who controlled upgrades and configurations to cloud-era facilitators who focus on integration, user enablement, and ecosystem management—the old model of "you must come to me for everything" is history.

2. Vendor Independence Is Critical: The tooling landscape changes rapidly and this person must evaluate options objectively rather than becoming emotionally attached to a single vendor's roadmap—the job is serving organizational needs, not defending a particular product or becoming its evangelist.

3. Train for Actual Use Cases, Not Product Mastery: Like teaching household budgeting versus investment banking in Excel, BPM training should focus on what users actually need (typically 10-15% of tool capabilities) rather than overwhelming them with advanced features they'll never use—practical enablement trumps comprehensive product knowledge.

4. Integration Thinking Beyond BPM: Modern tooling managers must understand how BPM platforms connect with the wider enterprise ecosystem—JIRA for project management, document management systems for quality, process mining tools, risk and control systems—and facilitate smooth integration rather than treating BPM as an isolated island.

5. Partner with Architects for Evolution: The technology manager and BPM architects must work hand-in-hand to expand capabilities—architects need technical feasibility input for methodology extensions, while tooling experts need architectural context to propose automation, dashboards, and integrations that make ambitious use cases practically achievable.

If you have suggestions or questions, please reach out to us via questions@bpm360podcast.com

If you enjoy our content, please like, rate, subscribe… we do appreciate that…