Observing The Industry Traversing the Digital Divide — Its Finaly here!

Earlier this week at Nvidia’s GTC conference, I had a moment of reflection that, for me, brought a lot of threads together. The energy around AI was undeniable—but more importantly, it wasn’t just hype or futuristic vision. It was grounded in real capability, real deployment patterns, and a clear signal of where the industry is heading.

I shared some of my immediate thoughts in a LinkedIn post during the event, but stepping back, what stood out most was this: the conversation has fundamentally shifted. AI is no longer being discussed as an isolated capability or an experimental technology. It is being positioned as a core building block of how systems will be designed, how operations will run, and how value will be created.

For someone like me—who has been writing for years about composability, democratization, and the need for a new operational architecture—this felt less like a surprise and more like a confirmation. The pieces I’ve been describing are starting to come together in a very visible way.

And it reinforced something I’ve been saying for a long time: manufacturing is on the verge of a fundamental shift. Not another incremental improvement cycle, not another wave of disconnected digital initiatives, but a real transformation in how operations are run, improved, and scaled.

For years, that message felt like a warning. A call to prepare. Today, it feels more like an observation.

Because what I saw at GTC—and what I’ve continued to see in conversations across the industry—is that companies have reached the divide and looking at crossed it. The conversations have changed. The posture of leadership has changed. And most importantly, the level of commitment has changed.

I referred to this earlier in my 2025 trends webinar as a watershed moment, and what we are seeing now is exactly that playing out in real time. I would strongly encourage you to watch that discussion, as it frames much of what is now unfolding across the industry:

What’s important is not just that change is happening—but how it is happening!

Vibe Coding and the Realization of Democratization

One of the clearest signals of this shift is how solutions are now being created. I’ve spent a lot of time over the years writing about democratization in manufacturing—the idea that the people closest to the work should be empowered to improve it, and that technology should enable that rather than constrain it. What is emerging now with AI, and what some are starting to call “vibe coding,” is the most complete realization of that idea that I’ve seen in my career.

What makes this different from previous waves of low-code or no-code is not just accessibility, but the collapse of effort between intent and execution. The ability to describe a problem, iterate on a solution, and see something functional emerge in minutes fundamentally changes the dynamic of how operations evolve. It brings solution creation directly into the operational context, where engineers, operators, and subject matter experts can shape systems in a much more immediate and iterative way. We are now seeing a world where:

• A process engineer can describe a problem and generate a working application
• An operator can help shape a workflow in real time
• A team can iterate on solutions at a pace that was previously unimaginable

This is not incremental improvement. This is a step change in how value is created and something I have consistently pointed to in my writing on composability and frontline operations platforms.

The shift from centrally developed, rigid applications to adaptable, user-driven solutions that reflect the reality of the shop floor.

But what is becoming clear now is that AI is not just enabling this shift—it is accelerating it to a point where it is unavoidable and, I feel, it's removing the mindset barrier. The discussions about technical capabilities, or features and functions are quickly fading away, including the odd ask about monolithic systems and OOTB configurations. They are shifting to be about how quickly solutions it can be built and how effectively it can be applied. That changes expectations at every level of the organization, particularly at the executive level, where the potential for rapid productivity gains becomes much more tangible.

At the same time, this level of democratization introduces a new kind of responsibility. When the ability to create is broadly distributed, the risk of creating the wrong thing—or creating the right thing in the wrong way—also increases. This is where the narrative needs to mature beyond excitement about capability and into a deeper understanding of what it takes to operate in this new model.

Why Platforms Are Now Critical to Operational Integrity

As AI transforms the ability to create solutions, it is tempting to assume that bringing those solutions into operations will follow the same path. This is where manufacturing fundamentally pushes back. The same forces that make “vibe coding” so powerful—the speed, the accessibility, the freedom to create—also introduce a level of variability that operations simply cannot absorb without consequence. In a production environment, the introduction of new technology, solutions, logic, automation, or decision-making is not an isolated act. It becomes part of a tightly coupled system where even small inconsistencies can propagate quickly.

In these environments, the consequences of error are immediate and often irreversible. A mistake cannot be rolled back with a software update, and failures in safety, quality, or compliance can have serious and lasting impact. This reality fundamentally reshapes what trust means for AI. Trust is not about believing that a model is intelligent or statistically accurate, but about whether a system behaves predictably under changing conditions, supports human judgment, and fails safely when uncertainty arises. In operations, trust is earned through repeated, consistent performance in the flow of everyday work.

While AI can generate applications, workflows, and even autonomous behaviors with remarkable speed, manufacturing requires that every one of those elements operates within clearly understood and controlled boundaries. One misstep—whether it’s an incorrect parameter, an unexpected interaction, or an opaque decision—can create cascading effects. Quality can be compromised, performance can degrade, and most critically, safety can be put at risk. In my experience, nothing halts adoption faster in a manufacturing organization than a single visible failure that undermines confidence in the system.

You cannot afford uncontrolled experimentation in a live production environment. This is why I’ve consistently emphasized the importance of a platform-based approach—not as a technology preference, but as an operational necessity. A true operational platform provides:

• Governance over what is created and deployed
• Context so that solutions are aligned with real processes
• Control to ensure consistency, traceability, and compliance
• Resilience so that failures are contained and managed
• Connectivity so that decision and action are based on a holistic understanding
• Content that is industry specific and ready to increase quality and resilience

Accountability in this environment is unavoidable. When AI influences how equipment is configured, how deviations are handled, or whether a product is released, responsibility does not shift to the algorithm. Humans remain accountable for outcomes, which makes human-in-the-loop not just a design preference, but a requirement. If an AI system makes a mistake, and they certainly do, trust erodes quickly—and once that trust is lost, it is very difficult to regain. This is even more pronounced in regulated industries, where expectations around data integrity, traceability, and explainability are explicit, and systems must be understandable not only to technologists, but to operators, engineers, quality professionals, and regulators.

This is precisely why a platform approach is not optional—it is foundational. A manufacturing-focused platform creates the controlled, governed environment where AI can actually operate within the strict realities of production. It is what ensures that solutions are not only created quickly, but behave predictably, meet quality standards, respect safety constraints, and remain compliant over time. Without that structure, the same capabilities that make AI so powerful will introduce unacceptable risk. In manufacturing, you cannot compromise on errors, defects, or safety—and you don’t get multiple chances to get it right. A purpose-built platform is what makes it possible to harness the benefits of AI and “vibe coding” without violating the core requirements of the operation. With a platform, you enable what I often describe as controlled democratization—the ability to innovate broadly, but within a structure that protects the integrity of the operation. Without it, scale is not just difficult—it’s dangerous.

Why Domain Expertise Still Defines Success

The final and perhaps most critical element in all of this is the role of domain expertise—something that is increasingly being underestimated in the current enthusiasm around AI. There is a flawed narrative that AI can compensate for gaps in knowledge or experience, that it can generate solutions independent of deep understanding. But as I have explored in other posts, particularly when experimenting with AI as a creative partner, the technology is only as effective as the context and intent that guide it. In manufacturing, this distinction is not subtle—it is fundamental.

With the incredible democratization AI brings to creating solutions accelerates, this constraint does not disappear—it shifts. It becomes even more important and critical to define the right problem and to judge whether a solution will actually work within the realities of the operation. Manufacturing processes are complex, tightly interconnected, constraints by physical realities, driven by well defined methods, and governed regulatory requirements. Understanding how cause and effect play out in that environment is not something that can be inferred generically; it is built through experience, engineering discipline, and operational knowledge. AI can amplify that expertise, but it cannot replace it—and without it, the risk of creating solutions that fail in practice increases significantly.

In the hands of those with deep expertise, AI accelerates learning, experimentation, and scale. This becomes even more critical as we move toward more autonomous systems, where agents are expected to act within operations. Their effectiveness depends not just on data, but on the depth of understanding embedded in how they are designed—grounded in the experience of those who know how the system behaves, especially when things don’t go as planned.

The Take-Away

What we are seeing right now is the convergence of three defining forces: 

1. The democratization of solution creation through AI.
2. The need for structured platforms to govern and control that creation.
3. The enduring importance of domain expertise to ensure it all works in the reality of manufacturing operations. 

This convergence is not theoretical—it is actively reshaping how companies think about, design, and run their operations.

Crossing the digital divide was never just about connecting systems or digitizing processes. It was about enabling a fundamentally different way of operating—one where the creation, deployment, and continuous improvement of solutions are embedded directly into the fabric of the operation. What we are now beginning to see is what that actually looks like in practice, and it is both powerful and unforgiving.

As with any significant shift in manufacturing, success will not come from simply adopting the latest technology. It will come from understanding how to integrate these capabilities into the operational reality—balancing speed with control, innovation with discipline, and democratization with accountability. The companies that get this right will not just move faster—they will operate differently, and ultimately, outperform.

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.