IT/OT Convergence: Still Vague, Still Critical

For years, IT/OT convergence has been a recurring theme in digital transformation conversations. It’s almost become a cliché. Everyone agrees it’s important, but few can define it clearly, and every company seems to have its own “flavor.”

That vagueness is both a challenge and an opportunity. IT/OT convergence is not just about technology stacks, data pipelines, or network architectures. It is about organizations, people, and how digital capabilities become part of the fabric of operations. And in the context of continuous transformation, this conversation remains more relevant than ever.

Why IT/OT Convergence Matters in Continuous Transformation

Digital transformation is not a one-time project—it’s a continuous process of adapting, learning, and embedding new technologies into how we operate. In that context, IT/OT convergence is essential.

Why? Because transformation cannot happen in silos. The systems that plan and account (IT) and the systems that control and execute (OT) must work together seamlessly. If they remain separate—organizationally, technologically, or culturally—you end up with fragmentation that slows down transformation instead of enabling it.

Can We Define It? And Why Does That Help?

One of the reasons IT/OT convergence feels vague is because it is often reduced to a technical exercise—connecting networks, integrating databases, or sharing dashboards. But that misses the bigger picture. To make it actionable, we need a broader and more ambitious definition.

At its core, IT/OT convergence is about making IT and OT inseparable. Not aligned, not just integrated, but merged into one digital foundation for the business.

That means:

• Integration of technology across the entire operation—from planning and engineering, to execution on the shop floor, and even to customer-facing processes. IT and OT must form a continuous digital thread that spans the lifecycle of design, production, quality, logistics, and service.
  
  

• Merging organizational roles and responsibilities—so that IT and OT aren’t two camps negotiating interfaces, but one team co-owning outcomes. The boundaries blur until it becomes irrelevant whether a capability was once “IT” or “OT.”
  
  

• Embedding digital practices into operations—so technology isn’t an external tool to be “applied” to operations, but a core element of how the organization works, improves, and creates value.

One of the most dangerous misconceptions in digital transformation is treating technology as an external layer—something added on top of operations. This is what has been going on for decades, born out of necessity of dealing with super complex monolithic systems. It is a model that creates friction, and this friction is detrimental to progress - it will suffocate any digital adoption initiative.   

Defining convergence in this way is helpful because it reframes the conversation: it’s not about how to connect two separate worlds, but how to design an organization where there is only one world. That shift in mindset is what makes IT/OT convergence transformative.

For digital technology to be impactful, it must be embedded into the way work is done at all levels: from the operator on the line, to the planner in the back office, to the leadership team setting strategy. IT/OT convergence makes this embedding possible.

When data, insights, and digital tools flow seamlessly across operations, technology doesn’t feel like an “extra.” It becomes integral to how people work, decide, and improve.

The Composability Pillar of Agile Operations

Finally, IT/OT convergence is inseparable from the principle of composability. To be agile, organizations need technologies that can be composed, reconfigured, and adapted as needs change.

That means convergence cannot be separated—neither organizationally nor by use. If IT and OT are treated as distinct silos, agility suffers. But when convergence is embraced, composable technologies support operational excellence: flexible enough to adapt, strong enough to sustain, and aligned enough to deliver value across the enterprise.

How Do We Know When It’s Complete? And Does That Matter?

Here’s the truth: IT/OT convergence is never “complete.” Like continuous transformation itself, it’s an ongoing journey. Technologies evolve, organizational structures shift, and new business challenges arise.

The goal is not to check a box that says, converged. The goal is to continually deepen the integration between IT and OT so that technology becomes invisible—it simply is the way you run operations.

So whether or not it’s ever “done” is less important than whether it’s continuously evolving to support value creation.

Moving Beyond the Buzzword

So, is IT/OT convergence vague? Absolutely. But it’s vague not because the idea lacks merit—it’s vague because it was born out of conflict.

IT and OT have so far been separate domains, each with its own responsibilities, budgets, and power structures. IT managed enterprise systems, data security, and corporate standards. OT managed the machines, processes, and operational continuity. Bringing the two together is not just a technical exercise—it’s a challenge to established authority.

That’s why IT/OT convergence often feels like a “hot potato.” Nobody wants to own it fully because it requires organizations to do things that are uncomfortable:

• Merging organizations that were once distinct.

• Relinquishing power as decision-making becomes more distributed.

• Diminishing rigid responsibilities as democratized technologies empower more people to contribute to digital solutions.

At its heart, convergence means releasing control—accepting that digital technologies are no longer the sole domain of one function, but a shared capability that belongs to everyone.

And that’s hard. It’s hard for people who have built careers around defending their territory. It’s hard for organizations that have optimized themselves around silos. It’s hard because it requires a cultural transformation just as much as a technological one.

But here’s the truth: without this convergence transformation halts. You cannot achieve continuous transformation if half the organization is innovating in isolation while the other half is protecting legacy boundaries. The result is friction, fragmentation, and failure to capture the value that digital technologies promise.

This is why IT/OT convergence—however uncomfortable, however vague—remains critical. It is the cultural and organizational foundation on which digital transformation rests.

In the end, convergence is not about IT and OT learning to work better together. It’s about creating a new whole where the distinction ceases to matter. That is the mindset shift. And until organizations embrace it, “transformation” will remain more slogan than reality.

The 5 Pillars of Composability

I am seeing the industry converge on the term Composability to identify and explain the application of digital technologies that can effectively foster digital transformation. For digital transformation to happen, agility, flexibility, and human-centricity are a vital component that increase productivity in operations - the expected outcome. This is where the concept of composability emerges as the collective transformative paradigm. Let's also make it clear that the opposite of composable is monolithic and contrary to monolithic systems, Composable solutions empower manufacturers to adapt quickly, focus on the needs of their operators, and drive continuous improvement. 

Composable solutions are a critical ingredient in digital transformation because they empower manufacturers to enhance productivity by embracing flexibility, agility, and human-centric design. By focusing on the needs of operators and utilizing real-time data, digital tools enable rapid adaptation to changing conditions, boosting efficiency. This approach accelerates time-to-value, enhances collaboration, and supports sustained operational excellence, ultimately leading to higher productivity​.

The Composability Model for Digital Transformation

Let’s dive into the five key pillars that make composability such a powerful approach: Bottom-Up, Agility, Democratization, Human-Centric, and Compliance.

1. Bottom-Up: Building from the Ground Up

In contrast to the rigid, top-down structure of monolithic solutions, composable systems thrive on a bottom-up approach. This allows organizations to build solutions that are tailored to specific processes, activities, and operations. Composability starts at the operational level, focusing on solving problems at the frontline, rather than imposing broad, generic solutions from the top.

By empowering frontline operators and citizen developers to build apps that address their unique challenges, organizations can capture granular data about each activity. This leads to faster problem-solving, more efficient processes, and solutions that are adaptable to rapid changes​. The bottom-up approach is essential for increasing productivity and maintaining agility in a constantly evolving operational environment.

An interesting phenomena is that the bottom-up approach fosters an emergent design, where solutions are built iteratively, from the operational level up. This means frontline workers, who are closest to the challenges, contribute to the system’s development. By decentralizing control, emergent designs allows for rapid adjustments and iterations, ensuring that solutions evolve in real-time, in response to actual needs. This approach significantly reduces the time-to-value, as it enables immediate deployment and incremental improvements, accelerating innovation and aligning solutions with real-world demands​

2. Agility: Embracing Change through Lean and Continuous Improvement

Agility in composable solutions is crucial because it inherently supports Lean principles, which emphasize continuous improvement, waste reduction, and efficiency. Composability takes Lean further by bringing in adoption of digital technologies as a key enablers. Its the reunion of Lean and Agile, allowing for rapid cycles of innovation, quick iterations, and on-demand changes, which are essential for staying responsive in fast-paced environments.

In manufacturing, continuous improvement is key and agility is non-negotiable. Composable solutions, by design, are highly adaptable and enable organizations to iterate quickly. Unlike monolithic systems that lock you into predefined processes, composable systems allow for short test-fail-learn cycles that drive faster innovation. This agility extends to everything from software updates to operational adjustments, ensuring that you can stay ahead of challenges and capitalize on new opportunities. Agility also allows for faster implementation and a reduced time-to-value, meaning that benefits can be realized almost immediately after deployment​.

Augmented Lean represents this evolution of Lean, where digital tools and real-time data empower frontline workers to make immediate, informed decisions, maximizing efficiency and productivity in ways traditional Lean couldn’t achieve.

3. Democratization: Empowering Citizen Developers

The democratization of technology is another cornerstone of composability. This is where no-code and low-code platforms come in, they enable citizen developers - the people close to the operations, such as engineers, technicians, or operators - to create, modify, and maintain apps without needing deep IT or coding expertise.

This critically reduces dependency on a software skills, centralized IT and specialized OT departments - it speeds up the development of solutions that directly address operational challenges. As more people within the organization are empowered to contribute to solution development, it fosters a culture of innovation, encourages experimentation, and accelerates digital transformation​.

Democratization in composable solutions means empowering the people who know the process best, frontline workers and engineers, to create content. When those closest to the operations develop solutions, the results are more accurate, relevant, and effective. This drastically reduces development time because it eliminates communication gaps between IT and operations. With a no-code platform, these citizen developers can quickly build, test, and deploy apps that meet specific operational needs, accelerating time-to-value and promoting continuous innovation​

4. Human-Centric: Augmenting Human Capabilities

In a composable system, technology is designed to serve operators, rather than the other way around. In traditional monolithic systems, operators must conform to rigid workflows dictated by the system, limiting their ability to adapt and innovate. With composable solutions, however, operators are empowered by tools that assist them in performing tasks more efficiently, providing real-time insights, and reducing manual effort. This human-centric approach leverages the unique skills of workers, driving productivity increases by augmenting human decision-making and capabilities​

Therefore composability at its core is human-centric. It is built around augmenting human activity rather than replacing them, automating processes where it makes sense but still including them, ie "human in the loop". In a composable system, the technology is there to serve the operator, providing tools that digitize manual tasks, streamline workflows, and offer real-time data insights.

This focus on human-centric apps leads to more intuitive user experiences, reduced error rates, and improved operator efficiency. By connecting operators with their environment through digital tools, sensors, and IIoT devices, composable systems elevate the performance of the workforce, ensuring that technology acts as a productivity enabler.

5. Compliance: Built-In Validation

In the regulated industries, such as life sciences among others, compliance is a critical pillar and probably needs a deeper dive in a future blog post. Composable solutions, especially frontline operations platforms, must be designed with compliance in mind. They have to allow organizations to build and validate solutions iteratively while maintaining compliance. Digital data has to be captured and available to document all the required aspects such as: version control, audit trails, and automated validation processes.

With compliance built into the system from the ground up, organizations can ensure that their solutions are always aligned with regulatory requirements without stalling innovation. Continuous improvements and app iterations can be made seamlessly while keeping operations compliant​ with automatically captured digital data as evidence. 

Validation 4.0 is an essential component of composable solutions and is part of the Pharma 4.0 operational model. It applies a risk-based approach to testing, ensuring that apps are validated for their intended use without lengthy delays. This iterative process allows for continuous updates and improvements while maintaining compliance. Validation 4.0 integrates seamlessly into the digital transformation, supporting rapid deployment and constant change, enabling businesses to innovate faster without compromising regulatory standards. This agility is critical for modern operations to thrive in evolving environments​.

In Summary

Composable solutions represent a fundamental shift in how manufacturing operations are structured and executed. By embracing the principles of Bottom-Up, Agility, Democratization, Human-Centricity, and Compliance, organizations can achieve faster time-to-value, greater productivity, and enhanced operational flexibility. The future of manufacturing lies in building systems that are as dynamic and adaptable as the challenges they address.

Composability as defined here and if applied correctly can give your manufacturing operations a massive jump on your digital transformation. Interestingly it can also serve to sift through the hype and ambiguity in the different so called "digital" technologies. By simply asking the technology vendors how the implement and satisfy the 5 pillars you can effectively qualify any technology as being in or our of the new paradigm. Remember clear objectives and strategy are still the most crucial part of your digital strategy. These objectives have to clearly define how productivity is increased in your operation and clarity around the composability drivers is an excellent strategy.

The Power of Teams

I have always inherently felt that there is immense power in teamwork with well-defined team roles. Done well, ie well functioning roles within teams, enhances collaboration and increases productivity. We have to recognize that complex projects and innovative solutions often require the collective effort of diverse skill sets and perspectives. However, the effectiveness of a team is not merely a function of bringing people together; it hinges on how well the team is organized and how clearly the roles within the team are defined. Well-defined roles enhance collaboration and increase productivity by providing clarity, fostering accountability, leveraging individual strengths, and streamlining communication.

I know this topic is a bit of departure from my normal themes around digital transformation and intelligence in manufacturing. I see many companies struggle with how to organize their digital initiatives and sometimes the essence of a good team that can help move the needle get's lost between all the technology and change management topics. 

What Constitutes a Well-Defined Team

A well-defined team is one where each member has a clear, specific role that complements the roles of others. These roles are carefully crafted based on the individual strengths, skills, and expertise of team members. In an engineering team, differentiating roles is crucial because it ensures that all necessary functions and tasks are covered without redundancy. For example, the team might include a project manager to oversee timelines and resources, a technical lead to guide the technical direction and resolve complex issues, and engineers to handle specific aspects of the design and implementation process. Each role is distinct yet interconnected, allowing the team to work efficiently and cohesively. The differentiation of roles prevents confusion and overlap, ensuring that each team member can focus on their specialized tasks and contribute uniquely to the team’s objectives.

Clarity and Direction

One of the foremost advantages of well-defined roles in an engineering team is the clarity it brings to the group. When each member understands their specific responsibilities, the overall direction of the project becomes clearer. The project manager ensures that timelines and resources are managed effectively, the technical lead provides technical guidance and oversight, and the engineers focus on their specific tasks, such as technical build, demoing, configurations, testing, and system integration. This clarity prevents overlap and redundancy in tasks, ensuring that team members are not duplicating efforts or working at cross-purposes. With clear roles, everyone knows what is expected of them, which reduces confusion and allows the team to focus on their collective goal. This focus enhances the team's ability to meet deadlines and maintain high standards of work.

Accountability and Ownership

Clearly defined roles foster a sense of accountability and ownership among team members. When individuals know their specific responsibilities, they are more likely to take ownership of their tasks. The project manager is accountable for project deliverables and timelines, the technical lead is responsible for the technical integrity of the project, and engineers are accountable for their respective contributions. This ownership translates into higher levels of commitment and motivation, as team members feel personally responsible for their contributions. Moreover, well-defined roles make it easier to track progress and identify any issues that arise. Accountability mechanisms can be put in place, ensuring that each member delivers on their commitments. This accountability not only boosts individual performance but also enhances the overall productivity of the team.

Leveraging Individual Strengths

Every team member brings unique skills, experiences, and perspectives to the table. Well-defined roles allow engineering teams to leverage these individual strengths effectively. By assigning roles based on each member’s expertise and strengths, teams can optimize their performance. For instance, the project manager might excel in coordination and resource management, the technical lead might have deep technical knowledge and problem-solving skills, and engineers might have specific technical expertise in areas like integration, production control, data analysis, or quality assurance. This alignment of roles with individual strengths ensures that tasks are performed efficiently and to a high standard. When team members are engaged in work that plays to their strengths, they are more likely to be productive and satisfied with their work.

Streamlining Communication

Effective communication is the backbone of successful teamwork. Well-defined roles help streamline communication within an engineering team by establishing clear lines of responsibility and reporting. Team members know who to approach for specific issues or information: engineers can turn to the technical lead for technical guidance, and the project manager can address scheduling and resource allocation concerns. This streamlined communication is particularly important in large teams or complex projects where numerous tasks and sub-tasks must be coordinated. With clear roles, communication becomes more targeted and efficient, facilitating quicker decision-making and problem-solving.

Enhancing Collaboration

Collaboration is the lifeblood of any high-performing team. Well-defined roles create a structured environment where collaboration can flourish. When team members understand their roles and the roles of their colleagues, they can better appreciate how each contribution fits into the larger picture. This understanding fosters a cooperative spirit, as individuals are more likely to support one another and work together towards a common goal.

In a collaborative environment, team members are encouraged to share ideas, provide feedback, and build on each other's strengths. This dynamic exchange of ideas leads to more creative solutions and innovative approaches to problems. When roles are clear, team members can engage in more meaningful collaboration without the fear of stepping on each other's toes. They can confidently contribute their unique perspectives, knowing that their input is valuable and will be integrated into the team's efforts.

Moreover, collaboration enhances performance by creating a sense of shared responsibility. When team members collaborate effectively, they develop a collective ownership of the project. This collective ownership motivates everyone to put in their best effort, as the success of the project is seen as a shared achievement. As a result, the team becomes more cohesive and resilient, capable of overcoming challenges and achieving higher levels of performance.

The Power of Network Dynamics and Teams of Teams

The last perspective I wanted to bring comes when organizing multiple teams with well-defined roles into a larger, interconnected network can amplify these advantages. This concept is explored in depth in the book "Teams of Teams" by General Stanley McChrystal. McChrystal argues that in complex environments, traditional hierarchical structures are often insufficient. Instead, he advocates for a networked approach, where teams operate with a high degree of autonomy but are also closely connected and aligned with other teams through shared goals and transparent communication.

In an engineering context, this means that multiple teams – each with clear roles for project managers, technical leads, and engineers – can collaborate more effectively across organizational boundaries. For instance, a software development team can work in tandem with a quality assurance team and a user experience design team, with each team bringing its specialized expertise to the table. This networked approach enables rapid problem-solving and innovation, as information flows freely and decisions can be made quickly.

By embracing the dynamics of a "teams of teams" structure, organizations can respond more agilely to changes and challenges. The interconnectedness fosters a culture of continuous learning and adaptation, where best practices are shared, and collective intelligence is leveraged. This approach not only enhances the performance of individual teams but also drives the overall success of the organization, leading to groundbreaking innovations and sustained competitive advantage.

Bringing this All Together 

Working in teams with well-defined roles is essential for enhancing collaboration and increasing productivity especially with the increased complexity that comes with digital transformation. The clarity provided by distinct roles helps align the team towards common goals, while accountability mechanisms ensure that tasks are completed efficiently. Leveraging individual strengths maximizes the team’s potential, and streamlined communication fosters quick and effective problem-solving. Ultimately, well-defined roles create a collaborative environment where team members feel respected and valued, leading to higher levels of productivity and success. This collaboration not only drives individual performance but also elevates the entire team's performance, leading to innovative solutions and outstanding results. In a world where teamwork is increasingly important, the organization of these teams is paramount to achieving exceptional outcomes. By embracing the power of network dynamics and the "teams of teams" approach, organizations can further enhance their agility and effectiveness, paving the way for sustained success in an ever-evolving landscape.