Layoffs in the tech sector are almost always explained through a macroeconomic lens: rising interest rates, tightening capital, corrections after a hiring boom. That explanation is accurate for large-scale reductions in force. It does not, however, account for a smaller and more frequent pattern that plays out inside individual teams and projects, one that has nothing to do with the market and everything to do with scope control.
A Project-Level Pattern, Not a Market-Level One
Set aside boardroom decisions for a moment and look at the team level. A project's requirements shift mid-execution. The team, unable to absorb the change within its existing plan, brings on contractors or new hires to cover the gap. Once the surge passes, those roles are cut. This cycle repeats across sprints and quarters, often without anyone naming it as a pattern.
This is a distinct phenomenon from a company-wide layoff, and the distinction matters. A market-driven reduction in force sits outside a project manager's control. This pattern sits squarely within it, functioning as a symptom of scope management rather than capital markets.
What the Research Shows
Requirements volatility (RV), defined as the tendency of project requirements to change over time, has a documented relationship with staffing instability. Thakurta (2013) applied system dynamics modeling to project data and found that specific patterns of requirement change produce disproportionate variation in manpower: a modest scope adjustment can trigger a staffing response well out of proportion to the change itself.
This finding aligns with earlier work. Khan et al. (2020) surveyed software practitioners and found scope creep to be a strong predictor of project failure, with a large share of failed projects showing poor scope management and budget overruns, conditions under which reactive staffing decisions are made under pressure rather than through planning.
Dasanayake and Markkula (2019) add a useful distinction here: not all requirement change carries the same weight. They separate market-driven change, which is largely unavoidable, from management-driven volatility, caused by factors like poor communication and unmanaged dependencies, which is preventable. The staffing instability described above tends to trace back to the second category, not the first.
Thakurta (2011) offers a governance-level explanation for why this goes unaddressed: most organizations acknowledge RV as a risk but lack any formal mechanism to measure it. Without measurement, volatility escalates unmanaged until it forces a reactive response.
The Underexplored Half of the Problem
Most of the existing literature on RV focuses on protecting the project: its architecture, its budget, its timeline. Comparatively little addresses how to protect the people delivering it.
Two areas of research point toward that gap:
- Workforce agility. Alviani et al. (2023) describe workforce agility as a deliberately cultivated organizational capability, built through flexible job design and genuine employee empowerment, that allows a team to absorb scope changes without resorting to headcount swings.
- Leadership agility. Saputra and Mulia (2025) identify rigid governance structures as a primary source of organizational fragility. They propose leadership agility, defined as adaptive decision-making that prioritizes team stability over strict plan adherence, as the more resilient alternative.
Mohammad and Kollamana (2024) ground this in practice: surveying and interviewing more than 120 agile practitioners, they found that just-in-time requirements refinement and shortened feedback loops measurably reduced the disruption caused by scope changes.
A Practical Starting Point
Of the mitigation strategies available, one is simple enough to implement immediately: require a trade-off conversation before approving any mid-cycle scope addition. The person requesting the change must identify what will be delayed, reduced, or deprioritized in return. This does not need to be a formal gate; a five-minute discussion is often enough to surface whether a request is genuinely urgent or simply convenient to approve.
This single habit addresses the root cause identified across the research: scope additions are rarely evaluated against their true cost to the team, which is what allows reactive staffing to feel like the path of least resistance.
Conclusion
Not every staffing fluctuation in tech traces back to the market. A meaningful share originates inside individual projects, where unmanaged requirements volatility forces reactive decisions that a stronger scope-management practice could prevent. This is a narrower claim than "the market causes layoffs," but it is a more useful one for practitioners: it points to a lever project managers can actually pull.