Manufacturing Doesn’t Adopt Fusion Teams. It Runs on Them
The next generation of plant performance will come from workflow-centric teams, not more disconnected tools.
Over the past few weeks, I’ve met with several manufacturing leaders across our community who are looking to scale their AI strategy – but they’re all facing a common challenge: finding the right balance between focusing on new capabilities and continuing to produce at a high standard.
The tech is there, but the process, governance, and organization haven’t caught up. As we zoomed out, it became clear that an operating model built on stability and siloed process expertise is not what’s required to drive end-to-end transformation across modern manufacturing networks. Instead, leaders are turning to a fusion team model that encompasses digital-enabled operators, tech Wizards, and Translators that connect digital strategy to on-the-floor execution.
Why Manufacturing Is Different
The traditional hierarchical model in manufacturing was built for stability and control. Operations, engineering, quality, maintenance, and planning each owned their domain, escalated issues through their chain, and coordinated through scheduled meetings or formal handoffs. That structure worked when production environments were predictable, changes happened slowly, and most decisions could wait for the next shift meeting.
That world is gone. Manufacturing environments today are challenged by compressed cycle times, tighter regulatory requirements, more frequent changeovers, growing SKU complexity, and rising expectations for sustainability and traceability. Plants are generating exponentially more data from sensors, MES, quality instruments, and supply chain signals. The gap between what silos can handle and what the business demands is widening fast.
How Fusion Teams Solve Silos
Functional silos in manufacturing operations create three specific problems:
- They slow down problem resolution. When a quality issue surfaces, operations flags it, quality investigates it, engineering evaluates the root cause, maintenance checks equipment, and planning adjusts the schedule. Each handoff adds delay while production continues at risk.
- They fragment accountability. Operations is measured on throughput, quality on defect rates, maintenance on uptime, and planning on schedule attainment. When those metrics conflict, the plant optimizes locally instead of systemically.
- They make it nearly impossible to operationalize new capabilities. A data scientist can build a predictive maintenance model, but if there is no clear owner to interpret alerts, coordinate with maintenance, and adjust schedules, the tool sits unused.
Fusion teams on the shop floor address all three. They collapse the handoff structure by putting the right expertise in the same operating unit. They create shared accountability by aligning the team around a production outcome, not a functional metric. And they provide the translation layer needed to turn technical capability into operational value by translating technical improvements into functional KPIs (think MES upgrades driving increased throughput).
What Does This Look Like in Practice?
Fusion teams in manufacturing look a little different from those in planning or procurement. On the shop floor, successful teams bring together site operations, engineering, maintenance, quality, and site production planning – along with end-to-end network planners and master data owners. In some cases, the team also includes specialists in standard work, visual management, capacity planning, and continuous improvement.
Given the critical nature of production deadlines, as well as safety and risk constraints, these teams need to be organized around a live production process with shared accountability for performance, escalation, and continuous improvement. Instead of handing issues across functions, teams work them in place, combining operational knowledge, technical expertise, and data stewardship in a single operating unit.
Because work flows continuously in production, many manufacturing fusion teams do not disband when a problem is solved. They own the workflow continuously, which allows them to build deep contextual knowledge, refine standard work, and drive sustained performance improvement over time.
Schneider Electric offers an example of this model in practice. Across its Smart Factory and Global Lighthouse sites, the company has brought together plant operators, industrial engineers, maintenance teams, supply chain planners, and digital specialists around shared performance challenges such as energy use, equipment reliability, throughput, and quality.
Rather than leaving digital tools with a central IT or transformation team, Schneider embeds these capabilities into frontline operations, so plant teams can act on real-time data and improve workflows continuously. These are fusion teams that combine operational knowledge with technical expertise to solve problems faster and improve plant performance over time.
The Rise of Cross-Functional Collaboration
Especially noteworthy is the importance of the Translator – the person who can convert process pain points into technical requirements, then help the frontline trust and use what gets built. Despite their critical role, our data shows that on average, just 5% of manufacturing job posts feature key Translator skills. (Our suggested target percentage is 15%.)
Plant environments do not tolerate fuzzy handoffs between domain experts and technical teams. Someone has to connect machine behavior, process design, data products, workflow logic, and operator reality in ways that hold up under live operating pressure.
Leadership must also evolve with this operating system. The old command-and-control model is poorly suited to teams that cut across engineering, operations, quality, data, and systems ownership. Leaders must shift from directing functional activity to orchestrating cross-functional outcomes. That means clarifying shared KPIs, aligning incentives, creating clean escalation paths, and protecting teams long enough for new ways of working to stick.
Zero100’s research finds that hiring for cross-functional collaboration for plant leadership increased 326% in the last two years, while standard skills like balancing a budget remained flat, indicating that the skills that earned you plant leadership in the past are not the same ones required to usher in a new way of operating.
How Fusion Teams Become an Operating System
The next generation of plant performance will not come from layering more disconnected tools onto factories. It will come from building workflow-centric teams that combine frontline expertise, Translator capacity, shared data products, and decision rights fast enough to matter in live operations. Planning and sourcing may have pioneered the fusion team concept, but manufacturing is where the model becomes a true operating system.
To get started in a plant, pick one live workflow where handoffs are hurting performance — quality response, downtime, changeovers, or scheduling, for example. Then stand up a small pilot team (not a full org redesign), and align that team to one shared metric. Give the team clear escalation and decision rights so issues can be worked in place, not handed off. Run in short sprints, learn on the floor, then scale the model to adjacent lines or sites.