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.

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/)