cross-domain automation
Zero Trust is not a product but an architectural principle

Cross-domain automation : The next step in your automation journey.

Automation is a typical buzzword that is used frequently but rarely means the same thing. More and more organizations are taking steps toward automation with the belief that it solves problems or increases efficiency.

What we see in practice: organizations struggle not only with automation per se within a single domain, but especially with the desire to directly implement cross-domain automation across multiple domains such as hybrid/on-prem: networking, cloud, systems. Automation is a journey that you go through step-by-step.

It is important not to want to rush and start at the back. In fact, cross-domain automation first requires a solid foundation in single-domain automation. But what exactly do I mean by this, and what is cross-domain automation?

Cross-domain automation

Cross-domain automation is the orchestration of an automation workflow across multiple systems, technologies or domains. It combines multiple integrations and platforms to perform multiple tasks (often belonging to different teams) in an accelerated manner.

These are often processes with long lead times (without automation), with few variables but a lot of repetitive work. Together, these steps form a workflow that reflects how information flows through an organization. It should not matter which internal domains are affected. Cross-domain automation can even extend beyond the boundaries of your own organization to include third-party providers (implementation depending on what they support).

A recognizable example is the onboarding of a new employee. Think about creating accounts, ordering hardware, arranging access and going through HR processes. This is a typical cross-domain process, with activities taking place both inside and outside your organization while you are the manager of the workflow.

The danger of boarding too early!

Sometimes the greatest visible value is in speeding up end-to-end processes, fewer meetings and fewer handovers. The only danger is that it skips the basics. Without mature automation within individual domains, it can actually add additional complexity over time and scale up existing problems.

Organizations additionally invest heavily in automation platforms to drive cross-domain automation, while workflows fail even in single-domains on these platforms. Over-engineering a platform even leads to increased adoption or usage.

These are not exceptions. The bottom line, then, is that technology is rarely the hardest part. Cross-domain automation reinforces what is already there. If things like ownership, practices and unlocking are not in order, you will scale mostly inefficiency rather than the desired efficiency.

No blueprint, but a direction …

There is no standard approach to cross-domain automation. Every organization, landscape and context is different. However, there are different types of solutions that can help, such as data management platforms, workflow orchestrators, API gateways or an internal developer platform (IDP). These can be deployed separately, but also combined.

Several (already ongoing) initiatives in an organization is not a problem, quite the contrary. The question is mainly how they relate to each other and how you unlock them.

Don’t start with tooling

A major pitfall is to start with tool selection let alone tools by themselves, versioning, scripts or X-as-Code. Those are just tools for domain-specific automation.

By choosing a tool right away, you are imposing technical frameworks before you fully understand what you really need.

Therefore, start with the desired functionality and the processes you want to improve. Only from there does it follow which solutions are appropriate. The complexity is rarely in the technology, but mainly in policy, processes, responsibilities and adoption. It is all about insight and cooperation to get the whole thing working. That takes time.

Adoption and approach make the difference

In doing so, connect as much as possible to existing initiatives and solutions within the organization. By reusing what is already there, you create support and trust among teams. Indeed, adoption is at least as important as technology. Don’t engage in a persuasion battle, but take teams through the journey and let them experience what automation delivers.

In addition, clear demarcation is essential. Who is responsible for what part of the workflow? Where are the boundaries between teams and systems? Without this clarity, noise and delays quickly arise.

At the same time, you must avoid getting stuck in analysis. Not everything has to be perfectly thought out in advance. Precisely by working iteratively and improving step by step, you can move with the speed at which technology develops.

And AI?

Definitely valuable but also deliberately not mentioned because I see it primarily as an accelerator and not a starting point. Without a strong foundation and sufficient domain knowledge, AI adds little to your automation journey.

Finally, grow towards it

Cross-domain automation is not an end goal in itself, but a logical consequence of mature automation within an organization. It is the step where separate initiatives come together to create true end-to-end value.

The biggest gains here lie in collaboration, insight and the ability to think across domains. Start small, build from a strong foundation and dare to improve iteratively. Don’t force it, but let it grow together with the employees.

Cross-domain automation is something you grow toward.

Automation should be a common language across teams.

By: Tom – Automation Consultant at One Zero IT