In recent years, we've seen a similar pattern across companies in every industry. The pace of change is accelerating, the number of strategic initiatives is growing, and almost every one of them cuts across the organization. It's no longer about local tweaks to a product parameter or optimizing a single process. It's about interventions into systems, competencies, data architecture, customer journeys, and, increasingly, organizational roles themselves. Change is no longer an episode — it's becoming a permanent state whose intensity keeps growing.
Traditional approaches are starting to hit their limits
The traditional response from large organizations has been to increase project management capacity, or introduce agile management. With or without agile teams, though, companies keep bombarding the organization with more programs, more project structures, more coordination meetings, and more project managers. In an environment where there was spare personnel capacity and a relatively stable operational base, this approach worked. Organizations had enough internal slack to absorb parallel initiatives without seriously disrupting day-to-day operations.
We'd venture to say that era is coming to an end. Companies are simultaneously facing pressure on cost efficiency, headcount reduction, and rising productivity demands. AI will only accelerate this external pressure. The slack is disappearing. And it's precisely in this situation that a limit previously masked by that slack becomes fully visible: an organization's absorption capacity.
The ability to absorb change and generate results
Absorption capacity is an organization's ability to absorb change so that it genuinely shows up in people's behavior, processes, and results, without destabilizing operations in the process. It isn't an abstract theoretical concept. It's a very concrete sum of time, mental energy, skills, attention, and structural stability that people in individual roles have available to implement new requirements.
Once this limit is exceeded, change starts to be merely simulated. Projects keep running, governance structures keep functioning, reporting keeps getting filled in, but real implementation on the front line slows down or becomes distorted. It becomes harder and harder to trace the actual benefits of change initiatives. A typical symptom is the accumulation of technological and operational debt. New systems get rolled out without full stabilization. The term “MVP” has become a dignified name for unfinished work. Workarounds emerge and gradually become institutionalized, documentation goes stale, and process discipline weakens. People shift into survival mode instead of genuine integration.
Coordination capacity isn't absorption capacity
Increasing the number of project managers boosts coordination capacity at the level of managing initiatives, not absorption capacity at the level of actually implementing them. In other words, the organization becomes able to launch more changes, but not able to anchor them stably and extract results from them.
The key question, then, isn't how many projects we're able to manage, but how much change specific roles and specific touchpoints can carry at the same time. Every role has its own limit on parallel changes it can implement without a drop in quality and without a buildup of hidden debt. That limit is shaped by the complexity of the work, the degree of autonomy, the quality of supporting systems, and the overall stability of the environment.
The blind spot of the top-down approach
The strategic mistake in many transformation programs is that they're designed top-down, based on leadership's thematic priorities, rather than bottom-up, based on the absorption capacity of the final touchpoints. The executive team decides on a portfolio of initiatives, and only then deals with implementation. But the logic should run the other way: start at the specific point where the change needs to show up, analyze its real capacity, and only then structure the pace, scope, and sequence of changes accordingly.
That doesn't mean holding back ambition. It means managing it systemically. Absorption capacity isn't a fixed quantity. It can be increased — by simplifying processes, reducing legacy debt, clearer prioritization, investing in competencies, and creating a stable rhythm of change instead of permanent overload. An organization with higher structural quality and disciplined execution can absorb more parallel changes than one operating in permanent chaos.
Real agility
Real agility, then, doesn't lie in the number of projects running in parallel, but in the ability to stably integrate change into everyday reality without long-term damage to the system. Companies that understand this difference will, paradoxically, end up faster than those that keep expanding their transformation portfolios regardless of the limits of their people and structures.
At a time when layoffs driven by automation and AI are becoming a baseline expectation, and pressure for efficiency keeps rising, the question of absorption capacity is one of the key strategic topics. This isn't an operational detail of project management. It's the limit of an organization's actual capacity for change.