Russell reports live from the ARIS Roadshow in Frankfurt, where the vendor is publicly repositioning its process repository from a process documentation tool to a context provider that enables AI agents to deliver business outcomes. The roadshow messaging centers on how comprehensive organizational models—spanning processes, enterprise architecture, and balanced scorecards—create the "digital twin" of a company that AI systems require. Russell observes that ARIS is articulating exactly what Caspar and Russell have been theorizing in their context mini-series: different types of information (why, now, temporal, stakeholder) must be combined to create the context that AI needs to operate effectively and compliantly.

A critical shift is emerging across the vendor and customer ecosystem: process models are no longer the end goal of BPM initiatives but rather delivery mechanisms for contextual information that powers AI and drives genuine business transformation. Russell notes that this represents a fundamental reorientation away from traditional BPM's focus on tool features and user capabilities toward outcome-based thinking where value is measured by business impact, not by model creation or certification.

The conversation highlights the acceleration of market dynamics and the need for rapid feedback loops between vendors, partners, and customers to navigate the AI transformation successfully. Russell emphasizes that customers, vendors, and consulting partners now must engage in deeper discussions about which context dimensions matter most for their specific use cases and how to operationalize context across platforms and tools—these conversations are just beginning but represent the real work ahead.

5 Key Takeaways:

1. Process repositories are being repositioned from process documentation systems to context layers that fuel AI decision-making and business outcomes.

2. Process models are transitioning from deliverables to delivery mechanisms—the goal is no longer the model itself but what the model enables AI and humans to accomplish.

3. Complete organizational models spanning processes, enterprise architecture, and balanced scorecards create the "digital twin" context that AI agents require to operate compliantly and effectively.

4. Business outcome and transformation impact are now heavily stressed by vendors and customers, displacing the traditional BPM focus on tool features and process modeling skills.

5. Vendors, customers, and partners must engage in dialogue about context dimensions and operationalization rather than assuming tools automatically provide the context AI needs.

If you have suggestions or questions, please reach out to us via [email protected]

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

In this fourth episode of their context mini-series, Caspar and Russell examine temporal and seasonal patterns as critical dimensions of process context essential for AI decision-making. They begin with a powerful real-world example: the Ever Given container ship blocking the Suez Canal created a temporal disruption that reverberated through global supply chains—an event that AI systems without proper temporal context cannot account for or mitigate.

The discussion establishes that "when" matters profoundly in process interpretation: the time of day, day of week, shift patterns, and seasonal cycles all influence how data should be understood and how processes should respond.

Russell introduces the concept that temporal patterns operate at multiple granularities—from intraday variations between day and night shifts to seasonal cycles spanning months or years. The hosts explore how cultural and operational factors amplify these patterns; for example, sales behavior differs dramatically during holiday seasons, and production capacity decisions must account for predictable seasonal demand fluctuations. They debate whether these temporal and seasonal elements are essentially the same thing (both affecting process behavior over time) or distinct phenomena requiring separate treatment in context models.

Caspar shares a compelling case study from supply chain forecasting where incorporating three years of historical data with seasonal pattern analysis improved forecast accuracy from 20-34% to 85%, enabling far more effective production planning. The hosts conclude that while recurring seasonal patterns are data-driven and mathematically manageable for AI systems, disruptive temporal events remain the harder challenge—balancing the ability to predict regular cycles with preparing for unprecedented disruptions is where context models prove their greatest value.

5 Key Takeaways:

1. Temporal and seasonal patterns are distinct context dimensions: temporal refers to one-off disruptive events (like ship blockades), while seasonal reflects recurring cycles that repeat predictably across time periods.

2. "When" data occurs matters as much as "what" or "where"—intraday timing, day-of-week effects, cultural calendars, and shift patterns all change how process behavior should be interpreted and managed.

3. Recurring seasonal patterns are easier for AI to manage through data analysis because they can be mathematically identified, validated against historical data, and converted into reliable predictive rules.

4. Disruptive temporal events remain AI's greatest challenge because they're non-recurring, unprecedented, and their ripple effects across business systems are difficult to predict or model in advance.

5. Accurate forecasting combines both dimensions: baseline seasonal patterns provide the foundation, while exception reporting from domain experts captures the disruptive temporal variations that pure data analysis cannot predict.

If you have suggestions or questions, please reach out to us via [email protected]

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

In this third episode of their context mini-series, Caspar and Russell explore "the now"—the current state and condition dimension of context essential for real-time process intelligence and AI decision-making. They establish that understanding where a process currently exists requires bridging two seemingly separate elements: operational data showing what is actually happening (revealed through process mining), and documented processes showing what should happen according to design and policy. Russell introduces a critical challenge: raw operational data is just noise without context to interpret it—knowing inventory levels means nothing without understanding acceptable ranges, product-specific targets, and organizational policy constraints. The hosts explore how process mining captures the "now" operationally, revealing actual process paths over recent periods, but this alone cannot explain business constraints, road closures (policy changes), or alternative routes that haven't been traveled. They distinguish between stable contextual elements like strategic objectives and business models (valid over months or years) and volatile operational state (real-time), requiring different update frequencies and persistence timelines. Caspar emphasizes that AI needs all available information—from operating models through process landscapes to automation data—to contribute meaningfully to strategic targets. They conclude that process documentation, long overlooked in favor of operational metrics, is making a critical comeback as the essential framework for interpreting operational reality and providing AI with genuine context.

5 Key Takeaways:

1. The Now Requires Both Operational Data and Documented Context: Raw operational state (throughput times, inventory levels, process status) is meaningless without context to interpret it—you need both what's actually happening (process mining) and what should happen (documented processes and policies) to understand the real "now."

2. Process Mining Reveals Only Traveled Paths, Not All Options: Mining tools show which routes were taken and patterns over time, but they cannot explain policy changes (road closures), compliance constraints, or alternative pathways that organizational policy permits but hasn't been executed—documented processes provide this missing framework.

3. Context Has Multiple Validity Horizons Across Time: A strategic business model may be valid for years, annual targets for 12 months, quarterly adjustments for 3 months, and real-time operational state updates continuously—effective context architecture must accommodate these different refresh rates and validity timelines simultaneously.

4. Interpretation Rules Form the Bridge Between Data and Insight: Business rules, policies, and KPI targets are the frameworks that transform raw operational data into actionable intelligence—without these interpretation rules, data becomes noise and AI recommendations lose legitimacy and business value.

5. Process Documentation Is Essential Infrastructure for AI: The documented operating model, process landscape, system architecture, and policies have always existed but were overlooked for AI purposes; they're now recognized as critical context infrastructure that AI requires to move beyond hallucination and provide grounded, strategically aligned recommendations.

If you have suggestions or questions, please reach out to us via [email protected]

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

In this second episode of their context mini-series, Caspar and Russell dig deep into the "why layer"—the business logic and decision drivers that form the foundation of meaningful context. They begin by analyzing how major ERP and BPM vendors define context, discovering that most remain introverted, limiting context to data within their own systems rather than understanding the broader organizational landscape. Russell raises a critical distinction between "content" and "context," questioning whether they're the same thing or fundamentally different. The hosts establish that context is not simply data, but rather multiple types of content plus the crucial relationships and dependencies between them. They emphasize that the "why layer" encompasses the rules, compliance requirements, and constraints within which organizations must operate—the parameters that define what's actually possible and permissible. The conversation explores how understanding why decisions are made, rather than just what happened, is essential for both human decision-making and AI reasoning. They introduce the "Five Whys" methodology as a practical tool for uncovering genuine business logic beneath surface-level explanations. The hosts propose that an "overlord agent" orchestrating multiple systems needs the "why" as its ultimate decision-making context, though guardrails are necessary—the "why" cannot simply reduce to "make money" without considering compliance and organizational values. They conclude by proposing to revive the Balanced Scorecard as a model specifically designed to capture organizational "why" context.

5 Key Takeaways:

1. Context Is More Than Data—It's Structure and Relationships: Vendors typically conflate context with their internal data, but true context requires understanding dependencies between different types of content plus the rules and constraints that govern decisions—raw data without this structure is just noise.

2. Distinguish Between Content and Context: Content is raw data and information; context is that content plus the relationships, rules, compliance parameters, and dependencies that make it meaningful and relevant to decision-making—AI and humans both need this structured context, not just content.

3. The Why Layer Is About Decision Logic, Not Just Compliance: Understanding why decisions are made goes beyond compliance rules and includes business policies, risk tolerances, organizational priorities, and strategic objectives—this decision logic is what enables proper interpretation of data and aligned AI reasoning.

4. Use the Five Whys to Uncover Authentic Business Logic: Most organizations struggle to articulate their actual decision-making rationale; applying the "Five Whys" methodology systematically reveals the true business drivers beneath surface-level explanations and builds genuine "why" context.

5. Why Needs Guardrails to Prevent Misalignment: An overlord AI agent making decisions based on organizational "why" context requires guardrails—a purely profit-maximizing why without compliance, ethical, and stakeholder considerations will produce decisions that harm the organization despite being logically aligned with stated objectives.

If you have suggestions or questions, please reach out to us via [email protected]

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

In this introductory episode to a new mini-series, Caspar and Russell tackle a concept everyone discusses but few truly understand: context and context models. They reveal that while organizations constantly invoke the need for "context," most stakeholders make vague assumptions about what context actually means without rigorous definition. The hosts outline their research-driven framework identifying six distinct dimensions of context essential to modern BPM: the "why layer" of business logic and decision drivers; state and conditions representing the current process status; temporal and seasonal patterns that vary across business cycles; stakeholder and role perspectives that differ by geography and function; performance baselines and anomaly contexts that define normal versus exceptional; and explainability and audit trails that prevent AI black boxes. The discussion explores implementation challenges beyond the technical, including organizational "ego"—the resistance from vendors and systems to share data in neutral platforms. Russell introduces the concept of a "context orchestrator" that governs how data across multiple enterprise systems relates to each other, without requiring centralized data warehouses. They emphasize that proper context architecture enables AI and intelligent decision-making but requires thinking beyond traditional approaches. The episode sets the stage for a 7-9 episode deep dive into each dimension and how organizations can practically build comprehensive context capabilities.

5 Key Takeaways:

1. Context Has Six Distinct Dimensions: Proper context goes far beyond process models and includes the "why layer" (business logic and compliance), current state and conditions, temporal patterns, stakeholder perspectives, performance baselines, and explainability—each requires separate consideration and governance.

2. Process Management Alone Doesn't Provide Complete Context: The assumption that process management automatically provides sufficient context is incomplete; it's merely one component. Organizations need deliberate, multi-dimensional context architecture that spans business logic, performance data, and organizational perspectives.

3. Organizational "Ego" Is a Major Implementation Barrier: Consolidating context requires extracting data from multiple vendor platforms and systems, which triggers resistance from vendors protective of their data and organizations comfortable in siloed systems—overcoming this ego-driven resistance is as critical as solving technical integration challenges.

4. Context Orchestration Without Data Centralization Is Possible: Rather than copying everything into a new data warehouse like old BI approaches, modern architecture should establish a context governance layer that knows where data lives, how different systems' data relates, and enables referencing across platforms through APIs and connections.

5. Context Enables AI Without Restrictive Performance Requirements: For most organizations (outside high-frequency dealing rooms), context doesn't need to be instantaneously centralized; slightly slower reference-based access to distributed data sources is acceptable—this enables practical architecture that respects existing systems while enabling intelligent orchestration.

If you have suggestions or questions, please reach out to us via [email protected]

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

In this episode, Caspar and Russell explore the fundamental transformation of process modeling's role in business and technology. They trace the evolution from the 1990s-2000s when process models were primarily project deliverables to today's paradigm where process models serve as essential working assets providing context for AI implementations. The discussion reveals how process mining rediscovered the critical importance of process models—not as decorative outputs, but as context providers that enable proper interpretation of data and intelligent decision-making. Russell emphasizes the shift from "working towards" a process model to "working with" process models throughout transformation journeys. They examine the philosophical evolution in vendor strategy, highlighting that the real competitive differentiation won't come from individual tools (modeling, mining, automation, workflow) but from orchestration philosophy—how vendors integrate these tools into a cohesive ecosystem. The conversation explores how AI systems require richer, more complete models than humans need, challenging the traditional approach of "simplifying for readability." They debate the necessity of agnostic AI layers that coordinate across multiple specialized AI tools rather than siloed point solutions. The hosts conclude that vendors demonstrating true understanding of orchestration, context modeling, and holistic ecosystem philosophy will define the next era of BPM and process intelligence, while others will fade in relevance.

5 Key Takeaways:

1. Models Are Working Assets, Not Project Deliverables: The fundamental shift is from treating process models as the end goal of a BPM project to understanding them as continuously evolving working assets that provide context throughout transformation, mining, automation, and AI initiatives.

2. AI Requires Richer Models Than Humans Need: Process models must now serve machine interpretation for AI and mining, not just human understanding—this means models need to capture complete context, handle edge cases, and answer technical questions that traditional simplified business models could ignore.

3. Process Mining Revalidated the Importance of Models: Process mining initiatives forced organizations to recognize that accurate interpretation of process data requires quality process models as context—mining alone produces data, but models transform that data into actionable business insights and transformation guidance.

4. Orchestration Philosophy Determines Vendor Relevance: The competitive differentiation won't come from individual point solutions (modeling tools, mining tools, workflow automation) but from vendors that architect holistic ecosystems with agnostic AI coordination layers that orchestrate across specialized tools and maintain consistent context.

5. Central Context Models Enable Optimal Decisions Across the Value Chain: Organizations need a single unified context model with an agnostic orchestration layer on top, rather than multiple disconnected AI systems—this architecture enables coordinated optimization across the entire process ecosystem rather than local optimization within individual silos.

If you have suggestions or questions, please reach out to us via [email protected]

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

In this technical deep-dive episode, Russell and Caspar welcome Francis Allan Beechinor, a 20+ year AI and quantum computing expert and serial entrepreneur with multiple patents, who shares his unconventional journey from working in the "uncool" fields of governance, security, and compliance to becoming an inventor of cutting-edge secure AI and quantum computing solutions. Francis discusses his latest venture, EmergeGen, which focuses on creating Secure AI working in parallel with quantum computing and quantum agents—solutions designed for high-end, complex problems that require finesse rather than flashy marketing. The conversation reveals a critical insight often missed in AI hype: AI is still in its infancy in terms of real adoption, despite decades of cycles and recent data-driven breakthroughs. Through concrete examples like high-frequency trading, Francis demonstrates why deterministic, reliable decision-making matters more than sophisticated-sounding hallucinations. The hosts explore the fundamental tension between speed of adoption and safety guardrails, using the automotive metaphor of driving on the Autobahn—you can go fast, but you need airbags, seatbelts, and a reliable vehicle. Francis emphasizes that Small Language Models trained on domain-specific data provide safer, more trustworthy outputs than large language models prone to hallucinations. The episode concludes with discussion of making secure AI accessible to mid-sized companies and "hidden champions" rather than just large tech corporations, with a vision for open-source quantum agents enabling broader adoption.

5 Key Takeaways:

1. AI Is Still in Infancy Despite the Hype: Despite four AI winters and recent successes, AI adoption is still in its early stages—cultural acceptance of technology through smartphones and satellite infrastructure has enabled current adoption, but we're nowhere near mature deployment for mission-critical systems.

2. Hallucinations Make Large Language Models Unreliable for Critical Decisions: Standard LLMs with their tendency toward hallucinations and nuanced but incorrect outputs are fundamentally unsuitable for high-stakes decisions requiring deterministic yes/no binary outcomes—security, medical, financial, and operational use cases demand better alternatives.

3. Small Language Models and Domain-Specific Training Provide Safer AI: By training smaller language models on specific organizational data and domain knowledge (via "super ontology" structured knowledge), you eliminate hallucinations and ensure AI makes decisions based on actual facts rather than probabilistic guessing.

4. Security Infrastructure Must Match Adoption Speed: As companies move fast with AI implementation, security, governance, risk controls, and process guardrails must evolve completely—the responsibility lies with providers to highlight risks and build in safeguards, even when clients pressure for rapid deployment without proper infrastructure.

5. Secure AI Is Accessible Beyond Big Tech: Secure AI and quantum agent solutions are not limited to Google and mega-corporations—approaches like fixed-price consumption models and planned open-source quantum agents enable mid-sized companies and industry-specific "hidden champions" to access and build on enterprise-grade secure AI technology.

#AI #BPM #Governance #SecureAI

If you have suggestions or questions, please reach out to us via [email protected]

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

In this special guest episode, Russell and Caspar welcome Michel Kirsch, a 22-year-old final-year international business student at the University of Paderborn, whose fresh perspective on AI and business process management challenges conventional thinking. Michel discovered BPM through the BPM winter school and is currently researching AI-driven business model innovation for his bachelor thesis. The conversation centers on Michel's provocative thesis: that while AI is a powerful strategic resource, it's also becoming a commodity, and the real competitive advantage lies in how companies leverage AI through business model innovation—yet traditional BPM thinking may actually constrain this radical innovation. The discussion explores the fundamental difference between how startups approach business models from a greenfield perspective versus how established incumbents struggle with legacy structures and capabilities. Russell and Caspar examine the tension between BPM's traditional operational excellence focus and the need for radical business model rethinking in the AI era. They debate whether BPM should expand beyond process optimization to encompass broader operating models, enterprise architecture, and digital twins of entire companies. Michel introduces the concept of "nudging" as a transformation technique and raises the challenge of measuring exploration and innovation—metrics that don't fit traditional BPM's operational KPI frameworks. The episode concludes by questioning whether future business model innovation will require rethinking traditional BPM practices entirely.

5 Key Takeaways:

1. AI Is Strategic but Increasingly Commoditized: While AI represents enormous strategic potential, nearly universal access means competitive advantage no longer comes from having AI—it comes from how companies translate AI into new business models and value propositions through thoughtful innovation.

2. Traditional BPM Can Actually Limit Radical Innovation: Process-focused optimization works well for operational excellence but can constrain the kind of radical business model rethinking needed in the AI era—incumbents stuck optimizing existing processes may miss transformative opportunities that startups embrace with greenfield thinking.

3. Greenfield vs. Brownfield Determines Innovation Capacity: Startups can design business models from scratch for AI and innovation, while incumbents must navigate existing structures, capabilities, and constraints—the key question is: which legacy capabilities enable future value, and which become anchors that must be shed?

4. Expand the Frame Beyond Processes to Operating Models: A complete "digital twin" of the company requires more than just process documentation—it needs operating models, enterprise architecture, capability mapping, and strategic positioning to give AI something meaningful to optimize and reimagine.

5. Innovation Metrics Don't Fit Operational KPI Frameworks: Traditional BPM excels at measuring efficiency and compliance, but measuring exploration, experimentation, and innovation requires different metrics entirely—organizations need new frameworks to balance operational excellence metrics with innovation and capability development indicators.

If you have suggestions or questions, please reach out to us via [email protected]

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

In this special guest episode, the hosts welcome Dr. Linda Ackerman Anderson—known as "Dr. Change"—a pioneering leader in organizational transformation with nearly five decades of experience in the field. Linda shares her remarkable journey from organizational development training through helping pioneer the "transformational change" field in the early 1980s, when practitioners recognized that a fundamentally different type of change was occurring in organizations. She discusses her work with massive organizations including Sun Petroleum Products and her development of the Conscious Change Leadership framework alongside her husband Dean Anderson, which goes beyond traditional change management to address the deeper human and cultural dimensions of transformation. The conversation centers on three critical conversations that must occur in any transformational change: content (business process design), people (their readiness, beliefs, and understanding), and process (the change methodology itself—how to move people through transformation). Linda emphasizes that change happens from the inside out, requiring people to emotionally, intellectually, and behaviorally embrace new ways of working, not just comply with directives. Through candid discussion, she explores how process transformations often reveal deeper organizational structure issues, and how turning project resistors into ambassadors through powerful questioning can unlock valuable insights. The episode provides practical wisdom on creating psychological safety and choice in transformation rather than mandate-driven compliance.

5 Key Takeaways:

1. Three Conversations, Not One: Transformational change requires simultaneous attention to content (business process design), people (readiness, beliefs, skills, understanding), and process (the change methodology)—treating change as only a technical exercise while ignoring people and change methodology virtually guarantees failure.

2. Change Happens Inside-Out, Not Outside-In: Telling people what to do (external communication) is necessary but insufficient; genuine transformation requires creating experiences and safe spaces where people emotionally get it, intellectually understand it, and choose to do it rather than feel obligated—this is the difference between compliance and commitment.

3. Readiness Has Three Dimensions: Before designing change interventions, assess people's awareness (do they know change is coming?), knowledge (do they understand what's needed?), and mindset/beliefs (do they believe it's possible and beneficial?)—addressing all three dimensions determines whether people can actually embrace new processes.

4. Turn Resistors into Ambassadors Through Powerful Questions: Instead of marginalizing project opponents, recruit them by asking questions that shift their thinking—"What do you see that we don't see?" and "Why do you think this won't work? What's necessary that isn't in place?"—this offloads resistance energy and converts their expertise into valuable contributions.

5. Process Transformation Reveals Organizational Structure Issues: When stakeholders engage deeply with new business processes, structural inefficiencies often emerge (excessive signature levels, redundant layers, unclear authority)—rather than treating these as out-of-scope, view them as opportunities to redesign organization alongside processes for genuine transformation.

Links to Dr Linda's books:

Beyond Change Management: https://shorturl.at/kZlGY

Change Leaders Roadmap to Organization Transformation: https://shorturl.at/Qt5nf

In this special guest episode, Russell and Caspar welcome Petros Panagiotidis, a deeply experienced BPM and Enterprise Architecture practitioner from Greece with four decades of professional experience and a PhD in Systems Science. Petros shares his unconventional academic journey through Business Administration, Computer Information Systems, Business Systems Analysis and Design, culminating in doctoral research on digital transformation and Industry 4.0. The discussion reveals Petros's counter-intuitive thesis: BPM and EA are fundamentally the same discipline, just using different terminology and marketing language. Through a systems science lens, he demonstrates how all the buzzwords around frameworks and methodologies—BPMN, TOGAF, and others—represent surface-level manifestations of deeper systemic principles. Petros introduces cybernetics and system dynamics as the foundational sciences that explain why processes exist and how they behave. He uses the elegant metaphor of water flowing through a river to describe how processes (the water) move through organizational architecture (the riverbed), making clear that process architecture provides stable structure while individual processes represent the flowing events. The conversation explores feedback loops—both negative (deviation correction toward targets) and positive (exponential amplification)—as the deep structure underlying all organizational systems. Petros emphasizes that understanding these foundational principles from systems science would transform how practitioners approach BPM and EA work, moving beyond tool-centric and marketing-driven thinking to genuine systemic understanding.

5 Key Takeaways:

1. BPM and EA Are Fundamentally One Discipline: What we call Business Process Management and Enterprise Architecture are essentially the same thing expressed in different dialects—the distinction exists primarily for marketing purposes around tools and methodologies, but the underlying systemic logic is identical.

2. System Science Provides the Foundation BPM Lacks: BPM and EA have a ceiling beyond which they cannot fully explain organizational behavior; system science (particularly cybernetics and system dynamics) reveals why processes and architectures exist and emerge the way they do at a deeper structural level.

3. Feedback Loops Are the Deep Structure: Two types of feedback loops—negative (correcting deviations from targets) and positive (amplifying deviations)—create the underlying structure from which all organizational processes and architectures emerge as visible manifestations; understanding these explains organizational behavior at a fundamental level.

4. Process Architecture vs. Process Events Are Interdependent: Process architecture provides stable structure and guardrails, while individual processes are the flowing events that move through this structure—like water finding its way through a riverbed; both are necessary and neither alone is sufficient.

5. Stafford Beer and System Dynamics Should Be Foundational Reading: Business schools and BPM practitioners should study Stafford Beer's work on organizational cybernetics and the viable systems model (five subsystems that enable organizational survival), plus system dynamics literature from the 1970s-80s—these foundational concepts should underpin all contemporary BPM and EA thinking rather than being overlooked in favor of current buzzwords.

If you have suggestions or questions, please reach out to us via [email protected]

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