January 28, 2026
By Vanguard Enterprise Intelligence Unit with the work of Rita McGrath, Amy Edmondson, Roger Martin, Gary Hamel, and Lynda Gratton.

The End of Stable Operating Assumptions

For much of modern management, uncertainty was treated as an interruption. Leaders built annual plans, designed operating rhythms, allocated budgets, and established reporting systems around the assumption that disruption would be occasional. A supply shock, demand slowdown, policy shift, labor issue, or technology change might force adjustment, but the underlying management architecture remained stable. The organization would absorb the event, revise the forecast, and return to normal.

That assumption has become increasingly difficult to defend.

The operating environment facing managers in 2026 is not defined by a single disruption. It is defined by overlapping volatility. Economic fragility compresses demand visibility. Geopolitical shocks reshape supply chains and regional exposure. Tariffs alter cost structures. Technology cycles accelerate faster than organizations can absorb them. Cyber risk, talent instability, customer uncertainty, regulatory shifts, and capital discipline now converge inside the same managerial system. The problem is no longer that managers must respond to disruption. The problem is that disruption has become part of the normal operating condition.

This requires a different managerial philosophy. Resilience can no longer be treated as emergency preparedness or crisis response. It must become a repeatable operating capability. The strongest managers are not those who avoid uncertainty. They are those who build units, processes, and teams that can sense change early, interpret it accurately, respond quickly, and preserve discipline while adapting.

Management in perpetual uncertainty is not improvisation. It is the design of disciplined adaptability.

Why Traditional Management Systems Struggle

Traditional management systems are often built around hierarchy, stability, and control. Decisions move upward. Information moves through formal reporting channels. Budgets are set according to annual assumptions. Performance reviews lag reality. Risk is managed separately from execution. When the environment is stable, this architecture can produce consistency. When the environment is unstable, it can produce delay.

The problem is not hierarchy itself. Hierarchy can clarify accountability. The problem is rigidity. A rigid hierarchy filters weak signals too slowly. Frontline teams may see changes in customer behavior, supplier reliability, pricing pressure, or execution risk before senior leadership does. But if the organization lacks a mechanism for translating those signals into action, information becomes trapped at the edges.

Rigid management also encourages false precision. Teams may continue executing against a plan because the plan has institutional authority, even after its assumptions have weakened. Managers may protect targets instead of revising them. Departments may optimize their own metrics while the broader system becomes more fragile. The organization appears disciplined, but its discipline is attached to outdated conditions.

In uncertainty, management must distinguish between discipline and rigidity. Discipline means preserving standards, accountability, and decision quality. Rigidity means refusing to adapt when conditions change. The resilient manager protects the first and eliminates the second.

From Command-and-Control to Sense-and-Respond

The central managerial shift is from command-and-control to sense-and-respond. Command-and-control asks whether the organization is following the plan. Sense-and-respond asks whether the plan still matches reality.

This does not mean managers should abandon planning. Planning remains essential. But the purpose of planning changes. In stable environments, a plan can function as a route. In unstable environments, a plan must function as a reference point. It helps managers understand what changed, why it matters, and whether the response should be minor adjustment or strategic reset.

A sense-and-respond system has three core functions. First, it creates visibility. Managers must be able to see changes in demand, cost, capacity, quality, delivery, customer sentiment, working capital, supplier reliability, and team strain before those changes become crises. Second, it creates interpretation. Data alone is not enough. Managers need forums and routines that help teams distinguish noise from meaningful change. Third, it creates action. Once a signal is understood, the organization must know who has authority to respond and how quickly.

This is the foundation of operational resilience. A resilient unit does not wait passively for senior leadership to diagnose every disruption. It has enough local intelligence, decision rights, and operating discipline to respond within defined boundaries.

The Unit-Level Resilience Framework

Operational resilience must be built at the unit level. Enterprise strategy matters, but volatility is often experienced locally. A sales team sees demand hesitation before the financial forecast reflects it. A warehouse sees fulfillment pressure before customer churn appears. A customer support team hears frustration before the brand dashboard registers decline. A plant manager sees supplier inconsistency before the executive risk committee reviews exposure.

The unit-level resilience framework begins with exposure mapping. Every manager should identify the specific dependencies that could weaken performance. These may include suppliers, systems, talent roles, customer segments, logistics routes, software platforms, regulatory assumptions, pricing models, or specialized knowledge held by only one person. The purpose is not to create a theoretical risk document. It is to make vulnerability visible.

The second step is signal definition. Managers must decide which indicators reveal stress early. These may include longer cycle times, rising defect rates, late supplier responses, quote delays, customer cancellation language, employee overtime spikes, inventory imbalances, lower close rates, slower receivables, or increased exception handling. A resilient unit does not rely only on lagging financial indicators. It tracks the operational signals that precede financial damage.

The third step is scenario planning. Each unit should prepare for a baseline scenario, a pressure scenario, and a rupture scenario. The baseline describes expected operating conditions. The pressure scenario describes moderate disruption, such as higher input costs, lower demand, staffing gaps, or slower suppliers. The rupture scenario describes a major break, such as a critical system failure, sudden regulatory constraint, customer loss, severe supply interruption, or rapid market shift.

The fourth step is response authority. A scenario is useful only if people know what they are allowed to do. Managers should define decision rights before disruption arrives. Which actions can frontline leaders take immediately? Which require department approval? Which require executive review? Without clear authority, uncertainty produces delay.

The fifth step is learning review. After each disruption, the unit should ask what was detected early, what was missed, what decision took too long, what process failed, and what should be changed. Resilience improves when each disruption becomes a management lesson rather than a temporary exception.

Scenario Planning as a Management Routine

Scenario planning is often treated as an executive strategy exercise. That is too narrow. In an environment of perpetual uncertainty, scenario planning must become a management routine embedded into operating units.

At the unit level, scenario planning should be practical rather than elaborate. A sales manager does not need a hundred-page forecast. He needs to know what happens if demand slows by ten percent, if customers delay purchasing decisions, if pricing pressure increases, or if a major account reduces volume. A supply chain manager needs to know what happens if a supplier misses two consecutive delivery windows, if freight costs rise, or if a tariff changes landed cost. A finance manager needs to know what happens if receivables slow, margin compresses, or inventory ties up more cash than expected.

The value of scenario planning is that it reduces emotional decision-making under pressure. When managers have already considered what may happen, they are less likely to freeze, overreact, or defend assumptions that no longer hold. They can respond according to prepared thresholds.

Effective scenario planning should define triggers. If margin falls below a set level, pricing review begins. If lead times exceed a certain threshold, alternative suppliers are contacted. If customer complaints rise beyond a defined point, service leadership intervenes. If overtime exceeds a sustainable level, staffing or workload allocation is reviewed. Triggers prevent managers from waiting until the problem becomes obvious to everyone.

The strongest organizations do not treat scenarios as predictions. They treat them as rehearsal.

Agility Without Indiscipline

One of the most common managerial errors in volatile environments is confusing agility with looseness. Leaders tell teams to move faster, be flexible, adapt, and respond to change. But if agility is not governed by standards, it becomes disorder. Teams begin improvising independently. Processes fragment. Quality varies. Decision-making becomes personality-driven. The organization becomes fast but unreliable.

True agility is disciplined adaptation. It allows movement within a clear operating frame. Managers should define what can change quickly and what must remain stable. Pricing tactics may change, but brand trust should not. Supplier choices may expand, but quality standards should not collapse. Workflows may be redesigned, but compliance cannot be ignored. Team roles may flex, but accountability must remain visible.

This is why resilient management requires operating guardrails. Guardrails give teams permission to adapt without losing coherence. They define boundaries around cost, quality, customer commitments, safety, compliance, authority, and escalation. Within those boundaries, teams can move quickly. Outside those boundaries, decisions must be reviewed.

Agility becomes powerful when people know the limits of their freedom.

Dynamic Sensing Systems

A resilient organization needs dynamic sensing systems. These are not merely dashboards. A dashboard can show information without changing behavior. A sensing system converts information into managerial attention and action.

A good sensing system combines quantitative and qualitative signals. Numbers matter: revenue, margin, churn, cycle time, defect rate, lead time, inventory, conversion, utilization, cash flow, and service levels. But qualitative signals matter as well. Customer hesitation, supplier tone, employee fatigue, recurring objections, frontline workarounds, and informal market feedback often reveal emerging stress before formal metrics do.

Managers should establish routines for gathering these signals. Weekly operating reviews should include not only performance metrics, but assumption checks. What has changed since the plan was made? Where are we seeing friction? Which customers are behaving differently? Which suppliers are becoming less reliable? Which process requires more exceptions than before? Which team members are carrying unsustainable load?

The critical managerial skill is pattern recognition. Not every signal deserves action. Volatile environments produce noise. The manager’s responsibility is to help the team distinguish temporary fluctuation from structural change. That requires judgment, context, and disciplined review.

Dynamic sensing turns management from periodic reporting into continuous awareness.

The Role of Middle Managers

Middle managers are often underestimated in resilience discussions. Senior executives set strategy, but middle managers translate strategy into execution under real constraints. They are close enough to operations to see problems early and senior enough to coordinate response. In uncertainty, their role becomes more important, not less.

A strong middle manager acts as a translator between strategic intent and operational reality. He explains why priorities are changing. He identifies where targets no longer match conditions. He protects teams from confusion while still holding them accountable. He escalates risk without dramatizing it. He adapts workflows without abandoning standards.

Organizations that weaken middle management in the name of speed may discover that they have removed the very layer needed to coordinate resilience. Flat structures can improve communication, but they can also create ambiguity if decision rights are unclear. The answer is not bureaucracy. The answer is capable management.

The best middle managers build local resilience. They know where the unit is fragile. They know which people hold critical knowledge. They know which processes break under pressure. They know which customers require special attention. They know when the team is adapting and when it is merely absorbing strain.

In perpetual uncertainty, middle management is not administrative overhead. It is strategic infrastructure.

Process Redesign for Volatile Conditions

Processes designed for stable conditions often fail under volatility. They assume predictable inputs, consistent demand, available labor, reliable suppliers, and normal escalation patterns. When those assumptions break, the process becomes slow or brittle.

Managers should redesign processes around modularity, visibility, and escalation. Modularity means work can be adjusted without rebuilding the entire system. If one supplier fails, another can be activated. If one team is overloaded, work can be shifted. If one channel weakens, resources can move. Modularity creates flexibility without requiring constant reinvention.

Visibility means managers can see where work stands, where bottlenecks are forming, and where exceptions are increasing. Invisible processes become fragile because problems remain hidden until failure occurs. Visibility allows earlier intervention.

Escalation means teams know when a problem exceeds local authority. The purpose of escalation is not to centralize every decision. It is to move the right problems to the right level quickly. In resilient organizations, escalation is not treated as failure. It is treated as responsible management.

Process resilience does not mean adding complexity. It means designing work so that stress can be absorbed, redirected, or escalated before the system breaks.

Building Teams That Can Absorb Shock

Operational resilience depends on people. A process may be well designed, but if the team is exhausted, confused, undertrained, or overly dependent on a few key individuals, the system remains fragile.

Managers should identify critical knowledge concentration. Which tasks depend on one person? Which customer relationships are held by one account manager? Which systems only one employee understands? Which approval processes slow down when one leader is unavailable? These dependencies may appear efficient in normal times but become dangerous during disruption.

Cross-training is one answer, but cross-training must be targeted. Not everyone needs to know everything. The goal is to ensure that critical functions have backup capacity. Managers should create role redundancy for essential processes, document recurring decisions, and ensure that operational knowledge is not trapped inside individual memory.

Teams also need psychological readiness. Uncertainty creates fatigue. If every shift feels like an emergency, people eventually lose energy and judgment. Managers must communicate clearly about what is changing, what remains stable, and what the team is responsible for. Ambiguity cannot be eliminated, but it can be managed.

Resilient teams are not teams that never feel pressure. They are teams that understand the pressure, know how to respond, and trust that leadership is not asking them to carry uncertainty blindly.

Turning Volatility Into Management Advantage

Volatility can weaken an organization, but it can also reveal where advantage can be built. When competitors become slow, confused, or overextended, a resilient organization can gain share, deepen trust, improve operations, and strengthen its position.

A company that can adjust pricing transparently may retain customers while competitors surprise them with sudden increases. A company with better supplier visibility may fulfill orders while competitors miss deadlines. A company with trained middle managers may respond faster than a company waiting for executive direction. A company with scenario triggers may protect margin while others react too late. A company with dynamic sensing may detect demand shifts before competitors recognize them.

This is how volatility becomes a repeatable management advantage. Not because the organization enjoys disruption, but because it has built the routines to learn and respond faster.

The goal is not to become immune to uncertainty. No company is immune. The goal is to reduce the time between signal and action, while preserving the quality of judgment. The organization that does this consistently begins to compound resilience. Each shock makes the system smarter. Each review improves the process. Each response strengthens confidence.

The Manager’s Resilience Playbook

Managers should begin with a simple question: where would our unit break first? The answer may involve people, suppliers, systems, customers, cash, quality, or decision rights. Once the likely breakpoints are visible, the manager can design against them.

The next step is to define early warning signals. These should be specific, observable, and tied to action. A manager should know which signals indicate stress before financial results deteriorate. The earlier the signal, the more room the organization has to respond.

Managers should then build three scenarios for their unit: baseline, pressure, and rupture. Each scenario should include likely effects on customers, costs, people, processes, and cash. The purpose is not to forecast perfectly. It is to prepare the team to think and act under different conditions.

Decision rights must follow. Teams should know what they can change immediately, what they must escalate, and what standards cannot be compromised. This clarity allows speed without chaos.

Finally, managers should establish a learning review after disruptions. What did we see early? What did we miss? What slowed us down? What helped? What should change in the process? This turns uncertainty into institutional learning.

The Discipline of Resilient Management

Perpetual uncertainty does not eliminate the need for management. It makes management more important. In unstable conditions, charisma is not enough. Optimism is not enough. Speed is not enough. The organization needs managers who can preserve discipline while enabling adaptation.

The resilient manager does not cling to the original plan when reality changes. He also does not abandon standards in the name of flexibility. He builds systems that sense, interpret, decide, and learn. He gives teams enough structure to remain coherent and enough authority to respond. He prepares for disruption without becoming consumed by it.

This is the management challenge of 2026. The companies that perform best will not be those that predict every shock correctly. They will be those that build operating systems capable of absorbing shocks, learning from them, and responding faster than less prepared competitors.

Uncertainty is no longer an episode between periods of stability. It is the environment in which management now occurs.

The manager’s task is not to wait for normal conditions to return.

The task is to build a system that can operate well without them.