Linear vs Non-Linear Work in VUCA Environments

A Systems Dynamics Perspective

Executive Summary

Linear and non-linear work approaches serve different organizational purposes. However, in VUCA (volatile, uncertain, complex, ambiguous) environments, linear methods have critical limitations. This document examines the fundamental differences between linear and non-linear work. It analyzes when each approach is appropriate. The document explores practical failure patterns of linear methods in VUCA contexts. It presents agile alternatives through the lens of Agile Systems Dynamics. Organizations operating in VUCA environments must consciously design their work systems as portfolios. They should maintain linear processes where stability exists. Additionally, they need to build non-linear, adaptive capabilities where complexity and uncertainty dominate.

Introduction

The distinction between linear and non-linear work is not merely methodological. It reflects fundamentally different assumptions about how the world behaves. It also affects how organizations should respond[1][2]. Business environments are becoming more volatile and complex. This makes the choice of work approach a strategic question rather than a tactical one.

This document synthesizes research on VUCA management, agile methodologies, systems dynamics, and organizational learning. It offers practitioners a comprehensive framework for choosing and designing appropriate work approaches. We examine both the theoretical foundations and practical implications through real-world examples and an Agile Systems Dynamics lens.

Definitions: Linear vs Non-Linear Work

Linear Work

Linear work operates on several core assumptions[3][4][5]:

Sequential phases with clear start and end points (A → B → C)
Predictable cause-and-effect relationships that remain stable during execution
Proportionality: inputs produce proportional outputs with minimal variation
Context stability: the environment changes slowly relative to execution cycles
Decomposability: complex problems can be broken into independent sub-tasks

Linear work thrives on optimization, efficiency, and variance reduction. It assumes that if you execute each step correctly according to plan, the cumulative result will match expectations.

Example: Building a standard highway bridge follows linear work patterns. Requirements are known. Engineering principles are established. Regulations are stable. The sequence of foundation → structure → surface → handover is predictable.

Non-Linear Work

Non-linear work recognizes different system characteristics[3][6][7][8]:

Progress occurs through feedback loops, iteration, and branching paths
Small changes can produce disproportionate effects (non-proportionality)
Outcomes emerge from interactions among many autonomous agents
Context co-evolves: the environment and the work influence each other continuously
Systems cannot be meaningfully decomposed without losing essential dynamics

Non-linear work optimizes for learning speed, resilience, and adaptability. It assumes that uncertainty and emergence are inherent, requiring continuous sensing and adjustment.

Example: Building a digital platform ecosystem involves understanding evolving customer behavior. Emerging technologies and shifting competitive dynamics must also be considered. This requires non-linear work. You release, observe, learn, adapt, pivot, and co-evolve with users and the market.

Where Each Approach Excels

When Linear Work is Appropriate

Linear work remains superior in specific contexts[3][4][5]:

Complicated but Stable Domains

Problems with many interdependent parts, but predictable behavior
Examples: standard ERP implementations, regulatory compliance reporting, established manufacturing processes
Expertise and best practices provide reliable guidance

Repeatable Operations

Low variance in inputs and environment
Focus on throughput optimization, cost reduction, and quality consistency
Value comes from execution excellence, not discovery

Slow-Changing Environments

Environmental change occurs more slowly than delivery cycles
Long-term infrastructure programs, routine operations, safety-critical systems
Deviation carries higher risk than delay

Benefits of Linear Work:

High resource utilization and efficiency
Accurate forecasting of time, cost, and capacity needs
Clear accountability through defined handoffs
Lower coordination overhead for routine tasks

When Non-Linear Work is Superior

Non-linear work becomes essential in different conditions[6][7][8][9]:

VUCA Environments

Volatility: rapid, unpredictable changes in key variables
Uncertainty: limited predictability of events and outcomes
Complexity: many interconnected, interacting factors
Ambiguity: unclear cause-effect relationships, multiple interpretations

Complex Adaptive Systems

Multiple autonomous agents with local goals and decision rules
Emergent patterns arise from agent interactions
Examples: markets, ecosystems, organizational cultures, innovation

High Novelty and Learning Requirements

Past solutions are weak predictors of future success
Problem definition itself evolves through exploration
New business models, transformations, breakthrough innovations

Benefits of Non-Linear Work:

Higher adaptability and resilience to unexpected change
Better fit to emergent opportunities and threats
Continuous learning and course correction
Encourages experimentation and diversity of approaches
Enables distributed decision-making closer to information sources

Comparative Overview

Aspect	Linear Work	Non-Linear Work
World assumption	Mostly stable, predictable	Volatile, emergent, interconnected
Planning style	Upfront, detailed, phase-gated	Rolling, adaptive, scenario-based
Control logic	Command-control, variance reduction	Distributed control, feedback loops
Optimization focus	Efficiency, cost, utilization	Learning speed, resilience, adaptability
Typical methods	Waterfall, stage-gate, linear KPIs	Agile/lean, experiments, probe-sense-respond
Best domain	Complicated, repeatable work	Complex, novel, strategic work
Feedback timing	Late, end-loaded	Early, frequent, structured
Scope management	Fixed upfront scope	Evolving scope via backlog

Table 1: Comparison of linear and non-linear work characteristics

Can We Use Linear Work in a VUCA World?

The answer is nuanced: yes, but within boundaries and as part of a conscious portfolio design[7][9][10][11].

The Dual Reality

Research on VUCA management emphasizes that the overall environment may be increasingly complex and volatile. However, not every organizational subsystem operates in that regime. The overall environment may be more complex and volatile, but individual subsystems may not necessarily follow that pattern[9][10][11]. Organizations that thrive in VUCA view themselves as complex adaptive systems. Some components remain highly standardized. Others are deliberately exploratory.

Appropriate Use of Linear Work in VUCA

Linear work remains valid for:

Core regulated processes: Finance closing, payroll, compliance, safety-critical operations where deviation is risky and learning cycles are long
Validated implementations: Once a new process has been validated through experiments and pilots, its broader rollout may follow a linear playbook
Infrastructure and support: Stable technology infrastructure, routine maintenance, established service delivery

When Linear Planning Becomes Dangerous

Linear approaches create risk when applied to[7][9][11][12]:

High-uncertainty strategic domains (new product strategy, digital ecosystem plays, major organizational redesign)
Contexts where problem definition itself is evolving
Initiatives spanning multiple years in rapidly changing markets
Cross-functional transformations involving cultural and power dynamics

The Ambidextrous Organization Pattern

A pragmatic organizational design is the dual-system or ambidextrous approach[1][7][9][11]:

One subsystem optimized for efficiency and execution (linear processes)
Another subsystem optimized for exploration and adaptation (non-linear processes)
Explicit interfaces, governance, and resource allocation between the two
Dynamic rebalancing based on environmental scanning

Research on strategic agility and VUCA management consistently supports this ambidexterity. Organizations maintain “structural separation with senior team integration.” This approach balances exploitation and exploration[1][9][11].

Agile Systems Dynamics Lens

Agile Systems Dynamics (ASD) explicitly models organizations as non-linear social systems. In these systems, “agile” emerges as a pattern of evolving behavior. It is not a fixed framework or methodology[13][14].

Core ASD Perspectives on Linear vs Non-Linear Work

1. Agents and Objectives vs Tasks and Phases

Traditional linear work assumes agents (teams, leaders, departments) will execute a predefined chain of tasks. ASD recognizes that:

Agents have partially aligned or conflicting objectives[13][14]
Their interactions, power relations, and local decisions alter the trajectory
Work design must account for agent autonomy and goal diversity

Non-linear work explicitly acknowledges agent dynamics. It builds coordination mechanisms that allow local adaptation within boundaries. These mechanisms avoid enforcing rigid task sequences.

2. Feedback Loops as the Real Engine

Agile practices (sprints, reviews, retrospectives, continuous discovery) are mechanisms to generate and process feedback faster than the environment changes[13][14].

From an ASD perspective:

Non-linear work is designed around fast learning loops that update local rules, structures, and strategies continuously
Linear work tends to suppress or delay feedback through long phases and late integration, which increases risk in complex domains

The quality and speed of feedback loops determine system agility more than any particular methodology or tool.

3. Structural Coupling with Environment

A system demonstrates agility in ASD when its internal structures co-evolve with environmental signals. These structures include roles, policies, cadences, and decision rights. This evolution occurs rather than resisting these signals[13][14].

Linear work assumes weak coupling: the environment can be treated as constant during execution
Non-linear work assumes strong coupling and builds mechanisms to adapt structure as the system learns

Agile transformations that succeed change not just process but also governance, incentives, and power distribution to enable structural adaptation.

4. Portfolio of Dynamics, Not One Best Practice

ASD reframes the linear vs non-linear question as a dynamics design question:

Where do we want stabilizing dynamics? (standardization, low variance, linear throughput)
Where do we want exploratory dynamics? (experiments, branching paths, non-linear scaling effects)
How do we design coherent interaction rules between these dynamics?

The art of organizational design in VUCA involves creating systems. These systems do not oscillate between chaos and rigidity. Instead, they maintain dynamic balance.

ASD-Style Diagnostic Questions

For any work stream, ASD would guide leaders to ask:

Information decay rate: How quickly does external information (customers, regulators, competitors, technology) invalidate our current plan?
Agent coordination complexity: How many autonomous agents must coordinate, and how aligned are their objectives?
Cost asymmetry: What is the cost of being wrong vs the cost of being slow?
Feedback availability: How quickly can we generate reliable feedback about our decisions?

Decision heuristic:

Plans invalidate slowly + few agents + aligned objectives + high cost of delay → Bias toward linear work with light feedback
Plans invalidate quickly + many agents + conflicting objectives + high cost of error → Design non-linear work with explicit agile feedback loops and adaptive structures

Practical Examples of Linear Work Failing in VUCA

Understanding failure patterns helps organizations recognize when they are applying linear methods inappropriately[12][15][16][17].

Typical Failure Patterns

Plans Become Obsolete on Contact with Reality

Traditional strategy and annual planning often assume environmental stability. In VUCA contexts, markets, technologies, or regulations shift before execution completes, rendering detailed plans irrelevant[12][18][19].

Strategy research shows that rigid plan-and-execute approaches lead to “implementation crises.” In these situations, employees no longer see connections between daily decisions and the original strategy[12][18]. Organizations experience:

95% of employees not understanding how to act on strategy[12]
Repeated re-planning while competitors adapt faster[12][18]
Strategy documents becoming “implementation theater” rather than decision guides[12]

Rigid Phase-Gates Delay Feedback

Waterfall and heavy linear methods lock requirements and design early, with testing and user feedback only at the end. In unstable contexts, this means validating solutions only after environments and needs have changed[15][16][20].

Empirical research on projects in adverse (VUCA) environments shows method misfit to the level of change. This misfit significantly increases failure rates in time. It also affects budget and goal achievement[15].

Example 1: Public-Sector IT (Waterfall Failure)

Context: A large police IT system in Scotland (i6) ran as a classic waterfall project. It assumed an existing solution could be linearly adapted. This adaptation aimed to replace approximately 130 processes and systems[16].

What happened:

As complexity and interdependencies emerged (bespoke needs, cross-system standards, data integration issues), the original linear plan could not absorb the learning
Rework exploded, delays accumulated, coding flaws multiplied
The contract was eventually terminated despite stakeholders “doing everything by the book”[16]

Why this is a VUCA/linear mismatch:

High uncertainty about integration with many legacy systems
Multiple stakeholders with evolving requirements
Governance optimized for documentation and pre-contract certainty instead of iterative discovery and incremental integration[16][20]

Example 2: Strategy Implementation Crisis

Context: In volatile markets, traditional multi-year top-down strategy rollouts frequently fail because plans cannot guide decisions once conditions change[12][18][19].

Failure mechanisms:

Strategy documents define targets and initiatives but lack simple decision rules for teams facing local surprises (e.g., sudden competitor entry, supply disruption)[12][18]
Linear cascades through annual cycles prevent rapid adjustment
By the time budgets and objectives are updated, markets have moved again[12][18][19]

Impact: Research and practice reports show that strategies framed as fixed plans become disconnected from daily operations. Executives endlessly re-plan while implementation stalls[12][18].

Example 3: COVID-19 and Just-In-Time Supply Chains

Context: Global supply chains were optimized linearly for cost and efficiency—just-in-time inventory, minimal buffers, long single-source chains—assuming smooth, predictable flows[21][22][23].

What failed:

When borders closed or suppliers stopped during COVID-19, companies had little visibility beyond tier-1 suppliers and almost no slack
Cascading shortages and long recovery times resulted
Planning models treated demand and supply as stable and independent, not as coupled non-linear systems with correlated shocks[21][22][23]

Linear work vulnerability:

Response plans were not designed for rapid scenario updates and local decision-making
Companies that stuck to original sourcing and inventory assumptions suffered deeper and longer disruptions than those that adjusted quickly[21][22][23]

Example 4: Digital Transformation as Linear Rollout

Context: Many digital transformations are organized as linear programs. They begin by defining the target state. Next, they involve selecting technology and implementing in phases. Finally, these programs roll out to all units[17][20].

Failure statistics: Studies show 70-90% of such initiatives fail or stall[17].

Key patterns:

Inflexible culture and process suffocate experimentation, so pilots do not reveal real adoption dynamics and scaling issues until too late[17]
Bureaucratic waterfall phases (heavy documentation, long approvals) slow learning and prevent teams from adapting when they discover new needs or constraints[17][20]
Rigid, top-down approaches collide with evolving technologies, unclear use cases, and changing organizational power dynamics[17]

Systemic Structure of These Failures (ASD Interpretation)

From an Agile Systems Dynamics perspective, each failure shares the same underlying structure. There is strong non-linearity in the environment and organization. However, work is designed as if the system were linear.

Hidden feedback loops and delays:

In IT and transformation cases, feedback (real user needs, integration issues, cultural blockers) appears late and is filtered through governance layers
Corrective action arrives when the cost of change is maximal[16][17][20]

Misaligned agent goals:

In strategy and transformation, executives optimize for plan certainty and budget approval while local teams need decision flexibility
Linear design amplifies goal conflicts instead of exposing and renegotiating them early[12][17][18]

Over-optimization for single objectives:

Just-in-time supply chains optimized for efficiency at the expense of resilience, ignoring non-linear risk amplification when shocks hit tightly coupled networks[21][22][23]

ASD would model these as systems where reinforcing loops (commitment to original plan, sunk-cost bias, local optimization) overpower balancing loops. These balancing loops include experimentation, early feedback, and design for resilience. This leads to brittle behavior when VUCA factors spike.

Agile Alternatives That Succeed in VUCA

Agile alternatives succeed where linear methods fail. They treat work as iterative and feedback-driven. The process is emergent rather than as fixed linear plans. They optimize for learning speed, resilience, and adaptability instead of upfront certainty[1][18][24][25][26][27].

Core Agile Patterns for VUCA

Short Feedback Cycles and Incremental Delivery

Frameworks like Scrum, Kanban, and related agile practices rely on small batches. They emphasize frequent inspection and adaptation through sprints, reviews, and retrospectives. This approach allows teams to update plans as volatility unfolds[24][25][26].

Contrast with linear delivery:

Linear “big-bang” delivery delays learning until the end
In high uncertainty, shorter cycles significantly improve fit to changing customer and stakeholder needs[24][25]

Emergent and Adaptive Strategy

Emergent strategy approaches deliberately treat complex contexts as spaces. In these spaces, problem definition and solution co-evolve. They use principles and decision rules instead of detailed long-range plans[18][28][29].

Strategy work in VUCA:

Uses iterative scenario planning, continuous sensing, and “act-sense-respond” logics
Aligned with Cynefin’s complex/chaotic domains
Replaces linear “analyze-plan-execute” with adaptive frameworks[18][28]

Concrete Agile Alternatives by Domain

Product Development and Transformation

Scrum, Kanban, and Hybrid Agile

Systematic reviews illustrate that customizing agile frameworks to context increases responsiveness. Such customization also reduces time-to-market and improves customer satisfaction in volatile environments[24][25][26].

Why they succeed:

Replace fixed scope and long upfront design with prioritized backlogs
Enable incremental releases and continuous refinement
Succeed where waterfall frequently fails in digital and transformation initiatives[17][24][25]

Continuous Discovery and Dual-Track Agile

Successful organizations separate discovery from delivery. Discovery means learning what to build. Delivery is the process of building it. They run experiments, prototypes, and user tests in parallel with incremental implementation[25][26].

Advantage:

Avoids the linear trap of freezing requirements too early
Tests assumptions quickly, reducing risk of late, expensive surprises[17][25]

Strategy and Portfolio in VUCA

Agile and Emergent Strategy Frameworks

Emergent strategy methods explicitly framed for VUCA treat strategy as a living framework. This framework consists of constraints, options, and hypotheses. It is refined through iterative tests and feedback[1][18][28][29].

Characteristics:

Use design principles, option portfolios, and regular strategy reviews
Replace infrequent rigid planning cycles
Enable faster strategic pivots when conditions shift[1][18][28][29]

Agile Portfolio Management

Agile portfolio approaches use shorter funding cycles. They rely on lean business cases and frequent reprioritization. These methods help to shift investment across initiatives as new information emerges[25][26].

Benefit: Overcomes the linear “lock-in” of multi-year fixed business cases that become misaligned in volatile markets.

Supply Chains and Operations

Agile and Resilient Supply Chains

Post-COVID-19 analyses show that companies with more agile supply chains recovered faster. These agile supply chains include multi-sourcing, regionalization, flexible capacity, and digital control towers. They captured market share compared with linear just-in-time models optimized only for cost[21][22][23][27][30].

Key features:

Continuous monitoring and scenario planning
Cross-functional collaboration
Near real-time reconfiguration of flows and suppliers[22][27][30]

Network Agility and Modular Operations

Leaders build modular operations and flexible supplier networks. They segment supply chains to enable different responses for different product segments. This approach is preferred over one monolithic plan[21][22][27][30].

Leadership, Learning, and Organization Design

Agile Leadership Practices

Agile leadership in VUCA emphasizes clear intent with flexible paths, frequent delivery, open communication, experimentation, and empowerment over command-and-control[26][31][32].

Focus areas:

Framing problems and setting boundaries
Enabling local decisions
Makes organizations more responsive than purely top-down linear decision chains[26][31][32]

Agile Learning and Continuous Improvement

Agile learning focuses on rapid learning loops, cross-functional collaboration, and application of new knowledge to new situations. This approach is strongly associated with higher agility and better outcomes in VUCA contexts[1][25][26].

Systematic reviews of agile transformations highlight adaptive leadership, continuous improvement, and contextual tailoring of methods as key success drivers[1][25].

Comparison: Linear vs Agile in VUCA

Dimension	Linear Method in VUCA	Agile Alternative That Succeeds
Planning horizon	Long, fixed plans	Short cycles, rolling planning
Scope	Fixed upfront scope	Evolving scope via backlog
Feedback	Late, end-loaded	Early, frequent, structured
Strategy	Plan-then-execute	Emergent, iterative strategy
Supply chain	Cost-optimized just-in-time	Resilient, multi-sourced, digital
Leadership	Command-control, predict-control	Empowering, adaptive leadership
Learning	End-of-phase reviews	Continuous improvement loops
Risk management	Upfront risk assessment	Iterative risk discovery
Decision-making	Centralized, hierarchical	Distributed, context-driven

Table 2: Linear methods vs agile alternatives in VUCA contexts

Practical Implications and Recommendations

For Leaders and Practitioners

Conduct honest context assessment: Use ASD diagnostic questions to determine where linear vs non-linear work is appropriate in your organization
Design dual systems explicitly: Do not treat the entire organization as either linear or agile—consciously architect ambidextrous portfolios
Invest in feedback infrastructure: The quality of your feedback loops determines agility more than any methodology label
Build adaptive capacity: Train leaders and teams in sensing, interpreting, and responding to weak signals rather than just executing plans
Challenge linear defaults: Question assumptions of stability, predictability, and proportionality in strategy, transformation, and innovation work
Create safe-to-fail experiments: In uncertain domains, design small, reversible experiments rather than betting everything on a single linear plan

When to Keep Linear Approaches

Linear work remains valuable when:

Operating in Cynefin’s “obvious” or “complicated” domains
Executing validated solutions at scale
Managing regulated, safety-critical, or compliance-driven processes
Optimizing stable, repeatable operations

When to Shift to Non-Linear Approaches

Non-linear work becomes essential when:

Operating in Cynefin’s “complex” or “chaotic” domains
Facing high uncertainty about problem definition or solution
Navigating rapid environmental change
Managing multi-stakeholder systems with emergent dynamics
Leading innovation, transformation, or strategic change

Conclusion

The choice between linear and non-linear work is not ideological but contextual and strategic. In a VUCA world, organizations must develop the capability to consciously design portfolios of work dynamics. They should maintain efficiency where stability exists. They must also build adaptability where complexity and uncertainty dominate.

Agile Systems Dynamics provides a powerful lens for understanding this design challenge. It emphasizes that agility emerges from the interplay of agents, feedback loops, and structural coupling with the environment. Agility stems from conscious dynamics design rather than from adopting any single methodology.

The evidence is clear. Linear methods optimized for predictability and efficiency fail systematically in VUCA contexts. These contexts are characterized by volatility, uncertainty, complexity, and ambiguity. Thriving organizations do not abandon structure. They build adaptive structures using short feedback cycles and emergent strategy. They employ modular operations and empowering leadership. This helps them sense and respond faster than their environments change.

The imperative for leaders is not to choose between linear and non-linear work universally. Instead, they must develop the sophistication to diagnose context. They need to design appropriate dynamics and build organizational capabilities for both exploitation and exploration. This ambidexterity—maintaining stability where needed while fostering agility where required—represents the essence of organizational fitness in VUCA environments.

References

[1] ScienceDirect. (2024). Managing the VUCA environment: The dynamic role of organizational learning and strategic agility. https://www.sciencedirect.com/science/article/pii/S0019850124002062

[2] World Scientific. (2025). From VUCA and BANI to a PUMO World: Why Agile Innovation Is Not Enough. https://www.worldscientific.com/doi/10.1142/S0219877025500129

[3] Neis, P. E. (2025, October 16). Linear vs. Non-Linear Systems. LinkedIn. https://www.linkedin.com/pulse/linear-vs-non-linear-systems-pierre-e-neis-0mt2e

[4] Lepaya. (2021, March 10). Linear vs Non-linear Learning and the Future of Work. https://www.lepaya.com/blog/linear-and-non-linear-learning

[5] Pinckley, C. (2020, May 4). What’s Working and What’s Not Right Now? Linear Vs. Nonlinear Thinking. LinkedIn. https://www.linkedin.com/pulse/whats-working-right-now-linear-vs-nonlinear-thinking-chris-pinckley

[6] Chuck’s LAMP. (2009, April 10). What kind of thinker am I? Linear vs. Non-linear thinking. https://chuckslamp.com/index.php/2009/04/11/non-linearthinking/

[7] Digital Leadership. (2024, April 23). VUCA World – Meaning, Examples And Management Steps. https://digitalleadership.com/blog/vuca-world/

[8] Agile Organization. (2026, January 14). The Dynamics of Agile Systems: Key Insights. https://agile-organization.com/2026/01/15/the-dynamics-of-agile-systems-key-insights/

[9] University of Western Ontario. (2021, August 1). Initiating Leadership Development In a VUCA Environment. https://ir.lib.uwo.ca/cgi/viewcontent.cgi?article=1233&context=oip

[10] Cadmus Journal. (2024, July 30). A Scale Development for VUCA World Management. https://www.cadmusjournal.org/article/volume-5-issue-3-p2/vuca-world-management

[11] Arkaro. (2025, August 3). Strategy Implementation Crisis: When Plans Fail in VUCA. https://arkaro.com/strategy-implementation-crisis/

[12] Neis, P. (2026, February 17). Agile Systems Dynamics: A New Approach to Organizational Behavior. LinkedIn. https://www.linkedin.com/posts/pierreneis_agile-systems-dynamics-field-guide-activity-7429837448886530049-aX23

[13] Agile Organization. (2026, January 14). The Dynamics of Agile Systems: Key Insights. https://agile-organization.com/2026/01/15/the-dynamics-of-agile-systems-key-insights/

[14] Neis, P. (2026, February 17). Agile Systems Dynamics: A New Approach to Organizational Behavior. LinkedIn. https://www.linkedin.com/posts/pierreneis_agile-systems-dynamics-field-guide-activity-7429837448886530049-aX23

[15] SciELO. (2023, June 4). VUCA environment on project success: The effect of agility and resilience. https://www.scielo.br/j/bbr/a/mK4tMzsYMRhKLJbxPCL4c7w/

[16] UK Campaign for Change. (2017, March 8). A classic “waterfall” IT project disaster – yet officials went by the book. https://ukcampaign4change.com/2017/03/09/a-classic-waterfall-it-project-disaster-yet-officials-went-by-the-book/

[17] Veremark. (2025, May 2). Why Digital Transformations Fail and What Lessons Can Be Learned. https://www.veremark.com/blog/why-digital-transformations-fail-and-what-lessons-can-be-learned

[18] Arkaro. (2025, July 19). Strategy in a VUCA World: Emergent Approach Guide. https://arkaro.com/strategy-in-a-vuca-world/

[19] IMD. (2015, March 17). Is VUCA the end of strategy and leadership? https://www.imd.org/research-knowledge/leadership/articles/is-vuca-the-end-of-strategy-and-leadership/

[20] SCIRP. (2025, April 24). A Case Study on Adaptation of Waterfall Methodology. https://www.scirp.org/journal/paperinformation?paperid=142222

[21] McKinsey. (2020, October 8). COVID-19 and supply-chain recovery: Planning for the future. https://www.mckinsey.com/capabilities/operations/our-insights/covid-19-and-supply-chain-recovery-planning-for-the-future

[22] Bain & Company. (2020, April 9). Covid-19: Protect, Recover and Retool. https://www.bain.com/insights/covid-19-protect-recover-and-retool/

[23] PMC. (2021, May 19). Bend or break? Small business survival and strategies during COVID. https://pmc.ncbi.nlm.nih.gov/articles/PMC9764849/

[24] Adesso. (2023, February 22). Using agile working methods to navigate the VUCA world. https://www.adesso.de/en/news/blog/10-agile-software-development-using-agile-working-methods-to-navigate-the-vuca-world-2.jsp

[25] IntechOpen. (2024, November 6). Business Strategies and Best Practices for VUCA and BANI World. https://www.intechopen.com/chapters/1205762

[26] Gemrain. (2024, July 22). Thriving in Uncertainty: Agile Leadership for the VUCA Environment. https://www.gemrain.net/post/thriving-in-uncertainty-agile-leadership-for-the-vuca-environment

[27] Bain & Company. (2020, April 26). Supply Chain Lessons from Covid-19: Time to Refocus. https://www.bain.com/insights/supply-chain-lessons-from-covid-19/

[28] Hult. (2018, March 11). Managing strategy in a VUCA world. https://www.hult.edu/blog/managing-strategy-in-a-a-vuca-world/

[29] Haas Consulting. (2024, March 14). Agile strategy development in the VUCA world. https://haas-consulting.tech/en/neuer-ansatz-agile-strategie-entwicklung-in-der-vuca-welt/

[30] Knowledge Ridge. (2025, October 21). 3 COVID-19 Lessons for Agile Supply Chain Software. https://www.knowledgeridge.com/expert-views/3-covid-19-lessons-for-agile-supply-chain-software/

[31] Kaizenko. (2023, December 11). Leadership Agility in a VUCA World: Strategies for Success. https://www.kaizenko.com/leadership-agility-in-a-vuca-world/

[32] Harvard Business. (2025, February 10). Thriving in the Most VUCA of VUCA Environments. https://www.harvardbusiness.org/insight/february-2025-the-leaders-agenda-navigating-uncertainty-thriving-in-the-most-vuca-of-vuca-environments/