June 7, 2026
By Vanguard Enterprise Intelligence Unit with the work of Lynda Gratton, Amy Edmondson, Ravin Jesuthasan, Peter Cappelli, and Willy Shih.

The New Talent Constraint in Operations

Operations has always depended on people, but the nature of that dependency is changing. For decades, many companies treated operational talent primarily through roles: plant manager, planner, buyer, quality engineer, warehouse supervisor, maintenance technician, logistics coordinator, production associate, process engineer, and team lead. The organization defined the role, hired against the role, trained for the role, and measured performance inside the role.

That model is becoming insufficient.

Operations now sits at the intersection of supply-chain volatility, automation, AI, geopolitical risk, energy constraints, labor shortages, customer expectations, and continuous process redesign. Teams must do more than execute stable routines. They must diagnose problems, adapt workflows, interpret data, collaborate across functions, manage partners, and learn new tools while still maintaining cost, quality, safety, and service discipline.

This is why operational talent is becoming a strategic constraint. A company may have strong assets, advanced systems, and well-designed processes, but if its teams cannot absorb change, interpret signals, and coordinate under pressure, performance will deteriorate. In modern operations, capability is no longer a support function. It is part of the operating model.

The most advanced organizations are therefore shifting from role-based workforce planning to capability-based workforce design. They still need roles, but they no longer assume that a role description captures what the business truly needs. They ask a deeper question: what capabilities must the operating system possess, and how do we build teams that can deploy those capabilities as conditions change?

Why Role-Based Structures Are Under Strain

Role-based structures work best when work is stable, repeatable, and clearly bounded. In many operations environments, that stability is declining. A planner may need to understand AI-assisted forecasting, supplier disruption scenarios, and commercial demand signals. A procurement manager may need to evaluate geopolitical exposure, supplier resilience, and sustainability requirements, not only unit cost. A warehouse leader may need to manage automation, labor variability, real-time inventory visibility, and safety. A plant manager may need to integrate energy resilience, workforce development, digital systems, and customer-specific flexibility.

The work is becoming more fluid than the job titles.

This does not mean roles are irrelevant. Roles create accountability. They clarify ownership. They support compensation, reporting, and career progression. But role-based thinking becomes limiting when it treats the current job structure as the future capability model.

A capability-based approach begins with the work the organization must be able to perform. It identifies capabilities such as demand sensing, rapid problem-solving, digital fluency, supplier-risk interpretation, quality discipline, automation oversight, cross-functional coordination, frontline coaching, scenario planning, continuous improvement, and partner management. It then asks how those capabilities should be distributed across teams, not merely assigned to fixed roles.

This shift matters because uncertainty rewards versatility. A team with narrow role clarity but weak learning capacity may perform well under stable conditions and struggle when conditions change. A team with broader capabilities can reconfigure work more effectively.

Deloitte’s 2026 Global Human Capital Trends research found that seven in ten business leaders identify speed and nimbleness as their primary competitive strategy over the next three years, with leaders emphasizing faster orchestration of people and resources and greater workforce adaptability as key drivers of success. That is an operations issue as much as a human-resources issue.

Skills Gaps as Operating Risk

Skills gaps are often discussed as hiring challenges. In operations, they should be understood as operating risk. When teams lack the capabilities required to run modern operations, the consequences appear in service failures, quality problems, safety incidents, slow adoption of technology, weak supplier management, inefficient changeovers, poor forecasting, and employee burnout.

Manufacturing is one of the clearest examples. Deloitte’s 2026 manufacturing outlook notes that talent remains a major strategic issue and that adaptive workforce planning can help address uncertainty and increasing skill requirements. Recent reporting on manufacturing labor shortages similarly describes the talent problem as structural rather than cyclical, with companies increasingly turning toward automation and workforce orchestration rather than conventional hiring alone.

The implication is that organizations cannot hire their way out of the problem. Hiring remains necessary, but the external labor market may not supply enough experienced people with the right technical, digital, and adaptive capabilities. Operations leaders must therefore build, borrow, redesign, and augment talent simultaneously.

This requires a different level of discipline. Leaders need to know which capabilities are scarce, which are mission-critical, which can be developed internally, which can be supported through technology, which can be accessed through partners, and which require redesign of the work itself. A skills gap is not only a people shortage. It may be a sign that the operating model is too dependent on scarce expertise.

Hybrid Work and the New Operating Reality

Hybrid work is often associated with corporate offices, but operations leaders face their own version of hybrid complexity. Some work must happen on-site: production, maintenance, warehousing, quality inspection, field service, logistics execution, and safety-critical supervision. Other work can be distributed: planning, procurement, analytics, engineering support, customer coordination, supplier management, scheduling, and some forms of training or technical assistance.

This creates a more complex operating model. Teams may be split between physical and digital environments. Frontline employees may feel that flexibility is unevenly distributed. Remote experts may support multiple facilities. Managers may need to coordinate across shifts, regions, and platforms. Knowledge transfer may become harder when people are not consistently co-located.

The challenge is not simply whether hybrid work is allowed. The challenge is designing hybrid operations deliberately. Leaders must determine which decisions require physical presence, which forms of expertise can be virtualized, which routines preserve connection, and how information flows between on-site and distributed teams.

Hybrid operations can strengthen capability when designed well. Remote engineering support can help plants solve problems faster. Digital training can expand access to learning. Centralized analytics teams can support local decision-making. Virtual supplier reviews can increase cadence. But hybrid models can also create distance, miscommunication, and resentment if they are treated as policy rather than operating design.

The standard should be operational coherence. Flexibility must support performance, not merely preference.

Retention in High-Pressure Environments

Operations environments are often high-pressure by design. They involve deadlines, safety requirements, customer commitments, physical constraints, cost targets, disruption response, and continuous improvement expectations. In recent years, that pressure has intensified. Teams are asked to absorb new technology, manage supply volatility, respond to demand swings, improve productivity, reduce cost, and maintain service quality despite uncertainty.

Retention becomes difficult when pressure is high and meaning, support, autonomy, development, and fairness are low. Employees may tolerate demanding work when they see progress, receive support, trust their managers, and understand why the work matters. They are less likely to stay when the work feels endless, poorly prioritized, under-resourced, or disconnected from growth.

This is why retention in operations cannot be solved only through compensation. Pay matters, especially in competitive labor markets. But high-performance teams stay when the operating system gives them a reason to believe their effort builds capability rather than merely absorbs stress.

Managers play a central role. They translate strategy into daily priorities, coach problem-solving, protect teams from avoidable confusion, and create the conditions for learning. HBR’s 2026 work on transformation failure emphasizes that the human element, especially leaders’ people skills, is often the root cause when change efforts fail. In operations, this is particularly important because transformation is not occasional. It is increasingly continuous.

From Training to Capability Development

Many organizations respond to skills gaps with training programs. Training is necessary, but it is not sufficient. A training program may teach a skill without changing the work system that determines whether the skill is used. Employees may complete courses in lean methods, data analytics, safety, automation, or leadership, but return to environments where managers lack time to coach, incentives reward short-term output, or systems prevent experimentation.

Capability development is broader. It connects learning to work. It gives teams opportunities to apply new skills, receive feedback, solve real problems, and build confidence through repetition. It also creates visible pathways for advancement, which improves retention.

A serious capability system includes structured onboarding, skills matrices, rotational assignments, cross-training, coaching routines, simulation, digital learning, apprenticeship models, peer learning, and after-action reviews. It identifies the capabilities required for current performance and future strategy. It measures skill depth across teams, not merely training completion.

Academic work on reskilling and upskilling for the future-ready workforce emphasizes that Industry 4.0 and related technological shifts require ongoing learning systems rather than one-time skill acquisition. That principle is highly relevant to operations, where technology, process, and workforce design are now evolving together.

The goal is not to make everyone capable of everything. The goal is to build enough versatility that the team can adapt without breaking.

The Capability-Based Team Model

A capability-based team model begins by identifying the work the operating system must perform under different conditions. It then builds teams around complementary capabilities rather than narrow job descriptions alone.

For example, a high-performing plant team may need technical maintenance capability, quality judgment, data interpretation, frontline coaching, safety discipline, scheduling flexibility, continuous improvement skill, and escalation judgment. A supply-chain planning team may need forecasting, scenario planning, supplier-risk analysis, commercial awareness, inventory strategy, and systems fluency. A logistics team may need network optimization, disruption response, partner management, customer communication, and cost discipline.

The model asks where each capability resides. Is it concentrated in one expert? Distributed across several people? Supported by technology? Dependent on an external partner? Missing entirely? This creates a more accurate view of operational strength.

A capability-based model also supports internal mobility. Employees can move across roles because their capabilities are visible. A warehouse supervisor with strong data fluency and coaching ability may become a planning leader. A maintenance technician with automation expertise may become a reliability engineer. A procurement analyst with supplier-risk skill may move into category management.

This strengthens retention because employees see a future inside the organization. It also strengthens resilience because the organization is less dependent on rigid role boundaries.

Human-AI Teams in Operations

AI and automation are changing operational talent requirements. They do not simply replace work. They change what human excellence looks like.

As AI systems become more common in forecasting, scheduling, quality detection, maintenance, procurement analytics, warehouse optimization, and customer-service operations, employees must learn how to interpret recommendations, challenge outputs, and intervene when systems are wrong. Automation shifts human work toward supervision, exception management, diagnosis, improvement, and coordination.

This requires new capabilities. Workers need digital fluency, but they also need judgment. Managers need to know how to redesign workflows around AI rather than add tools on top of old processes. Teams need to understand when to trust a model, when to question it, and how to learn from outcomes.

Recent AI-readiness research argues that AI success is fundamentally an organizational learning problem rather than a technology purchase. It notes that large investments often fail to deliver meaningful earnings impact when leadership alignment, culture, governance, human capital, operations, data architecture, and systems infrastructure are not developed together.

That insight applies directly to operations. AI tools will not create high-performance teams if teams do not learn how to use them. The future of operational talent is not human versus machine. It is human capability amplified by well-designed technology.

Case Pattern: The Adaptive Manufacturing Team

Consider a manufacturer facing demand swings, automation upgrades, and skilled-labor shortages. Its legacy workforce model assigns employees to specialized roles with limited cross-training. When demand shifts, the company relies on overtime, supervisors, and temporary labor. When equipment changes, only a few technicians understand the new systems. When quality problems arise, problem-solving depends on a small group of experienced employees.

A capability-based redesign would begin by mapping the critical capabilities required for the plant: equipment operation, changeover skill, maintenance diagnosis, digital-interface fluency, quality problem-solving, safety leadership, and team coaching. The plant would then create cross-training pathways, pair experienced technicians with newer employees, use simulation or digital tools for equipment training, and create a skills matrix visible to supervisors.

The result would not be instant flexibility. But over time, the plant would become less dependent on a few experts and more capable of adapting labor to changing demand and technology. Capability depth would become part of operational resilience.

Case Pattern: The Supply-Chain Planning Team

Consider a supply-chain planning team managing volatile demand, supplier constraints, and tariff uncertainty. Historically, planners were evaluated on forecast accuracy, inventory targets, and service levels. The work was technical but relatively stable. Now planners must interpret weak demand signals, evaluate supplier risk, coordinate with sales, model scenarios, and decide when to escalate.

A role-based model may continue treating planners as forecast managers. A capability-based model would define a broader set of requirements: demand sensing, scenario modeling, commercial interpretation, supplier-risk awareness, communication, and decision judgment. The team would build routines that connect planners with sales, procurement, finance, and operations. It would use AI tools for signal detection while training planners to challenge and contextualize outputs.

The result is a planning team that does not merely maintain the forecast. It helps the organization make better decisions under uncertainty.

Case Pattern: The Field Service Organization

Consider a field service organization maintaining complex equipment across regions. Customer expectations are rising, skilled technicians are scarce, and equipment is increasingly digital. The company struggles with retention because technicians feel overworked and career paths are unclear.

A capability-based approach would identify the capabilities that drive service excellence: technical repair skill, diagnostic reasoning, customer communication, digital tool use, safety discipline, mentoring, and escalation judgment. The company could then create levels of capability rather than only titles, allowing technicians to progress through visible mastery paths. It could use remote expert support to help less-experienced technicians in the field. It could identify top technicians not only as individual performers, but as capability multipliers who train others.

Retention improves when employees see development, support, and respect for expertise. Performance improves when capability is deliberately multiplied rather than trapped in a few individuals.

Building the Operational Capability System

Leaders can build operational capability through a practical framework.

The first step is capability mapping. Identify the capabilities required to execute current operations and future strategy. This should include technical, digital, managerial, analytical, relational, and adaptive capabilities.

The second step is capability visibility. Build skills matrices and team capability maps that show where strengths, gaps, and single points of failure exist. This allows managers to make better staffing, training, and risk decisions.

The third step is work-integrated learning. Move beyond classroom training by embedding learning into real operational problems, improvement projects, rotations, simulations, and coaching routines.

The fourth step is manager enablement. Equip managers to coach, prioritize, give feedback, manage hybrid teams, and translate strategy into capability development. Managers are the link between talent strategy and operational reality.

The fifth step is career architecture. Create pathways that allow employees to grow through skills, mastery, and capability depth rather than only promotion into management.

The sixth step is technology augmentation. Use AI, automation, digital training, and knowledge systems to amplify human capability, reduce cognitive overload, and preserve institutional knowledge.

The seventh step is capability measurement. Track not only headcount and training completion, but proficiency, cross-coverage, internal mobility, time-to-competence, retention of critical roles, and operational outcomes linked to capability.

This framework treats talent as an operating system, not a staffing input.

Measuring Capability ROI

Capability investments must be measured if they are to compete for capital and executive attention. The challenge is that capability often produces value indirectly. It reduces downtime, improves quality, accelerates problem-solving, shortens onboarding, increases retention, improves safety, strengthens customer service, and reduces dependency on scarce experts.

Leaders should measure time-to-competence for critical roles, internal fill rates, cross-training coverage, turnover in key positions, safety performance, quality defects, service recovery time, equipment downtime, forecast response speed, and the number of process improvements generated by frontline teams. They should also measure manager effectiveness because managers determine whether capability development becomes daily practice.

The strongest case for capability investment connects talent metrics to operating outcomes. If cross-training reduces downtime, if digital fluency improves scheduling accuracy, if manager coaching reduces turnover, if simulation shortens onboarding, or if internal mobility reduces hiring dependency, the value becomes visible.

Capability development should not be defended only as good culture. It should be managed as performance infrastructure.

The Leadership Standard

Operations leaders must avoid two errors. The first is treating talent as a shortage to be filled. That mindset keeps the organization dependent on external labor markets that may not supply what the business needs. The second is treating capability as a training catalog. That mindset confuses activity with development.

The better approach is to design talent and capability as part of operations strategy. Leaders should ask what the operating system must be able to do, which capabilities are required, where those capabilities live, how they are developed, how they are retained, and how technology changes the work.

High-performance operations teams are not created by staffing alone. They are built through clarity, practice, coaching, systems, and meaningful work. They are sustained by managers who can develop people while delivering results. They are strengthened by technology that amplifies judgment rather than replacing responsibility. They are retained by career paths that make growth visible and work worth continuing.

In a changing world, operational advantage will belong to companies that can learn faster than their constraints. Talent is not only a resource for executing the operating model.

It is the capability that allows the operating model to evolve.