Change Saturation and Change Capacity: A Guide to Change Planning
Change saturation and change capacity show how much change an organization can absorb, helping you diagnose readiness and plan sustainable initiatives.
Can an organisation fail at change while every individual project reports green? Change Saturation and Change Capacity explain how that happens: the failure sits in the sum of what lands on people, a sum that no project owns. Leaders who misread it tend to spend the very capacity they need on fixing the wrong thing.
What Change Saturation Is: When Change Disruption Exceeds Change Capacity
Change saturation is the state that the Prosci Change Saturation Model, published by Prosci, defines as change disruption greater than change capacity, so saturation describes a relationship between two variables: the demand change places on a group and that group’s power to absorb it. The definition sounds obvious, yet most organisations track only one of the two variables, and usually only in part: they know which projects have been approved and hold no figure at all for what their people can take. Change saturation and change capacity therefore have to be read as a pair, starting with the demand side, then the supply side, then what happens when one change load meets groups of different size.
Change Disruption: The Demand Side
Change disruption is the collective impact of multiple simultaneous changes on a group, from minor procedural updates to major strategic shifts, each one demanding resources and attention. Prosci sets out that scope in Prosci Change Saturation Model, and the word that does the work is collective.
Collective is where the tally leaks. Each sponsor sees only their own slice of the demand. A payroll process update, a new CRM and a reporting-line restructure might each be assessed by its own project team as moderate impact, and each assessment is accurate on its own terms. To the accounts team that receives all three in the same quarter, they arrive as one load: three sets of training, three revised checklists, three new approval paths, and three periods in which output drops while people relearn routine work.
Minor procedural updates matter here more than their size suggests. They rarely reach a steering committee, they carry no change budget, and they seldom appear on any roadmap, yet each one consumes attention in the form of a changed form, a new system field or a revised sign-off. A group can absorb two large programmes and still be tipped over by the dozen small changes that arrive alongside them without anyone counting.
Disruption therefore accumulates at the receiver, and the source never sees it. A disruption figure assembled from project charters will undercount every time, because a charter lists what the project intends to deliver while the receiving group carries what the project costs in attention.
Change Capacity: The Supply Side
Change capacity is how much change a group or organisation can absorb at a given time, and Prosci treats it as the receiving side of saturation, a quantity that varies from one organisation to the next.
Capacity is invisible until it runs out. It has no budget line, no headcount code and no dashboard tile, so people keep absorbing change past the point where absorption is still working. Absorbing a change means learning a new tool while still running the day job, unlearning routines that took years to build, and tolerating a period of slower, more error-prone work before the new way settles. Every one of those activities draws on the same hours and the same attention as the operational work the group is paid to do.
Capacity also recovers slowly after each change lands. A team that has just settled one system migration has not yet rebuilt the speed and confidence it had before, and the next change starts drawing on a reserve that is only partly refilled. What sets the size of that reserve for a particular group is a separate question, governed by conditions that can be inspected one by one.
Because capacity keeps no ledger, the first hard evidence most leaders receive of its limit is a missed date or a resignation, by which point the shortfall has already been paid for.
Tim Creasey’s Bucket in the Prosci Change Saturation Model
Tim Creasey frames saturation as a matter of supply and demand in Prosci’s Enough is Enough: Tips for Avoiding Change Saturation, and illustrates it with a bucket of water. The size of the bucket represents change capacity, while the water already in the bucket, and still being added to it, represents change disruption. The Prosci Change Saturation Model then breaks both quantities into their components, so that the bucket and the water can each be examined on their own terms.
The phrase “still being added” is the part of the image leaders tend to miss. Water arrives over time, so the level at any moment includes changes approved months ago that are still landing. A group can overflow without a single new approval, simply because earlier changes are still pouring in: a go-live that slipped by a quarter now lands on top of the next wave, and the bucket was sized for neither arriving together.
Same Change Load, Different Saturation Points
Two organisations carrying an identical change load can reach saturation at different points, because saturation depends on the size of capacity as much as on the volume of disruption.
That relational property is what defeats every attempt to publish a universal limit. A rule such as “no group should run more than four concurrent changes” assumes groups are interchangeable, and they are not. Picture two business units in the same company, each receiving the same new finance system and the same revised expense policy in the same month. One is a stable team with a few spare hours in its week and managers who have time to coach. The other is a contact centre running at full utilisation through its peak season, where every hour spent in training is an hour of queue time.
The first unit absorbs the load with a short dip in output. The second hits saturation within weeks: adoption stalls, workarounds spread, and the system that worked well elsewhere gets a reputation for being broken. Only the receivers differed between the two units.
The same reasoning applies across organisations of similar size and sector, and it explains why peer benchmarks on change volume reassure leaders more than they inform them. A threshold has to be located group by group. A single enterprise-wide limit will be too tight for some teams and too loose for others, and the loose side is where the damage shows up first.
Change Saturation vs Change Fatigue: Portfolio Condition Versus Individual Response
Separating change saturation from change fatigue comes down to four questions about where each one sits, who experiences it, what it costs, and whether the two always move together, and the answers determine whether leaders act on their people or on the change portfolio. The distinction sounds academic until a leadership team has to choose between a wellbeing programme and a portfolio review that compete for the same sponsor time and the same budget. The evidence for each answer comes from a different place, from The Change Compass’s portfolio framing to Prosci’s survey data on turnover and trust.
Saturation as the Structural Cause
The Change Compass’s guide Change Saturation: How to Detect It Early and Protect Your Portfolio places saturation at portfolio level and calls it the structural cause, produced by how many initiatives an organisation approves, launches and runs at once.
Structural means the condition is manufactured by decisions: approvals, go-live dates, resource assignments and funding releases, most of them made in portfolio forums by people who never feel the cumulative load themselves. Each decision is defensible when taken alone. The overload comes from their sum, and no forum is usually responsible for the sum.
That placement has a practical consequence for who can fix it. No individual employee can resolve saturation by becoming more resilient, because the inflow keeps coming regardless of how well any one person copes. No single project manager can resolve it by communicating better, because their project is only a fraction of the load landing on the group. Only the forum that controls the inflow can change it.
The Change Compass adds an observation that explains why saturation is so damaging once it sets in: when a business unit is saturated, even well-designed initiatives stall, because the people receiving them no longer have the bandwidth or the psychological readiness to engage. A strong business case, good training material and a committed sponsor cannot compensate for receivers with no room left.
The cause, in other words, lives in a room where the people affected by it are rarely present, and the evidence of it surfaces somewhere else entirely.
Fatigue as the Individual Response
Change fatigue, in The Change Compass’s terms, is the psychological response of the individuals living inside a saturated organisation: the exhaustion, cynicism and withdrawal people feel when change keeps arriving faster than they can settle it.
Because fatigue belongs to individuals, it varies from person to person under the same load, depending on how many of the changes touch a person’s own role, how much discretion they have over their work, and what they are carrying outside work. Two colleagues on the same team can report very different levels of fatigue in the same month.
Fatigue also lags behind the decisions that cause it, building across waves of change and becoming visible months after the approvals that produced it. It shows up as reactions more than as refusals: the shrug at the next town-hall announcement, the assumption that this initiative will be dropped like the last one, the slide into doing the minimum the new process requires and keeping the old spreadsheet alive just in case.
Fatigue carries forward from one change to the next. People judge each new change by their experience of the previous one, so a fatigued workforce discounts a well-run programme before it starts, and the programme pays for problems it did not cause.
Because fatigue is felt, it gets surveyed, reported and discussed in leadership meetings. The portfolio condition underneath it rarely receives the same treatment, so the visible measure tends to attract the fix.
What Fatigue Costs: Turnover, Stress and Trust
Prosci puts numbers on fatigue in Prosci Change Saturation Model: of employees feeling change fatigue, 54% look for a new role, 48% feel more tired and stressed at work, and 37% trust their employer less.
Each figure maps to a different cost, and the costs land in different budgets:
- Employee turnover. People searching for a new role take process knowledge with them, often in the middle of a change. The colleagues who understood the old system well enough to translate it into the new one are frequently the ones who leave, and their replacements inherit both the change and a learning curve.
- Stress and tiredness. Tired people revert to familiar workarounds because learning takes energy they no longer have. The new process exists on paper while the old one keeps running underneath it, and the organisation pays for both.
- Trust. Lower trust means the next announcement is discounted before it is read, so every subsequent change needs more sponsorship effort to reach the same level of adoption.
The figures describe employees who already report fatigue, so they show what fatigue does once present, not how many people have it. They are best read as consequences that compound over time.
Trust loss compounds most of all: the sponsor of the next initiative inherits a deficit they did not create and cannot see on any project report.
When Saturation and Fatigue Diverge
Saturation and fatigue can come apart in both directions: a saturated portfolio lands unevenly on the workforce, and an individual can be fatigued even when the wider portfolio does not look saturated.
Uneven exposure is the more common case. An ERP rollout, a process redesign and a new compliance regime might all land on finance operations, while sales receives a single new dashboard over the same period. Enterprise-wide pulse surveys average the two and report moderate strain, while finance operations is past its limit. Leaders reading the average conclude there is no saturation problem, and the group that is drowning stays invisible inside a reassuring number.
The opposite case occurs as well, and it is easy to miss. A team lead who acts as change champion on four separate initiatives, each modest in its own right, can be exhausted while the portfolio overall looks manageable. Personal circumstances, a role sitting at the junction of several workflows, or a recent promotion can produce genuine fatigue with no portfolio-level overload behind it. In that case, role design, workload support and individual wellbeing measures are the right response.
Diagnosis matters because the remedies differ. Treating fatigue alone, through resilience workshops or wellbeing days, leaves the portfolio-level cause untouched, and the next wave of change lands on people who were coached to cope with a load nobody reduced.
The question for any leadership team looking at exhausted people is which of the two cases it is facing, and whether anyone holds the data that would tell them.
Why Change Saturation Is Rising: Ten Planned Change Programmes a Year
The evidence on why change saturation is rising comes from three directions, McKinsey’s count of change programmes per employee, survey data on how many organisations already sit near their limit, and research on the stress people carry before workplace change arrives, and together it suggests that managing capacity has become a permanent leadership task. Each figure has limits worth knowing before it goes into a board paper, and those limits change how the numbers should be used.
Ten Programmes a Year: McKinsey’s Volume Finding
McKinsey & Company reports in Change is changing: How to meet the challenge of radical reinvention that the average employee now experiences ten planned change programmes a year, a fivefold increase from a decade ago.
Ten programmes a year means nearly one a month, and each one brings its own training, its own revised process and its own reporting. The recovery time that once separated major changes has disappeared. An employee absorbing a new programme roughly every five weeks rarely reaches full competence on the previous one before the next arrives, so they spend most of the year operating on the lower, slower part of the learning curve.
The word planned narrows the count in a way that matters. The figure counts deliberate programmes, so unplanned shocks such as a supplier failure, a regulatory surprise or a reorganisation after a leadership change sit on top of it. The figure is also an average, which hides how unevenly the load is distributed between groups.
Change Volume Against Falling Engagement and Health
Over the same decade in which change volume rose fivefold, McKinsey finds that engagement and health measures have fallen, support for change programmes has dropped, and the disconnect between employees and leaders has grown. Volume and the conditions needed to absorb it moved in opposite directions at the same time, which is the pattern the saturation equation would predict.
The fall in employee engagement and support is itself a capacity loss, since willing participation is one of the resources a change draws on. A sponsor who once filled a pilot group with volunteers now has to assign people to it, and assigned participants need more coaching, more follow-up and more time before the new way of working holds.
How Many Organisations Are Near Saturation
The Change Compass, citing Prosci, reports in Change Saturation: How to Detect It Early and Protect Your Portfolio that 73% of organisations are near, at or beyond their saturation point.
The phrase covers three distinct states, and the difference between them matters more than the headline. Near saturation is where action is cheap: a resequenced go-live or a deferred initiative can still prevent overload. Beyond saturation is where the costs described in the fatigue data are already being paid, and recovery takes longer than prevention would have.
The figure comes from respondents’ own judgement of their organisations, which makes it a measure of perceived strain, and perceptions can differ between the executives who answer surveys and the groups who absorb the change. Even so, perceived saturation shapes behaviour: people who believe there is too much change act on that belief by withdrawing effort, whatever the formal portfolio data says.
The figure also says nothing about where inside an organisation the strain sits. An organisation reported as near saturation may have most of its groups comfortable and two or three far beyond their limit, and an executive answering the survey may know about only one of them.
If roughly three in four organisations sit at or near the line, being a typical organisation offers no protection. The useful question shifts from whether saturation exists to which specific groups sit beyond their point, and how anyone would know.
External Stress Already in the System
David Michels of Bain & Company cites the American Psychological Association Stress in America survey, in which 80% or more of respondents named inflation, supply chain issues, global uncertainty and the war in Ukraine as significant stressors.
Michels uses that finding in his article for Bain, A Flood Of Change: Leading Through Times Of Overload (Bain & Company), to make a point about capacity: people have a limited capacity to absorb change, and each person has a different level of resilience. Workplace change lands on people whose attention is already drawn down by prices, family pressures and uncertainty about the economy.
The external load also varies by group in ways a change plan rarely records. A frontline workforce on hourly pay feels inflation differently from a head-office team, and a function with suppliers in disrupted regions carries the supply chain stress into its working day.
That matters for capacity planning because the attention people use to absorb a new system is the same attention they use to manage stress outside work. A change plan sized on the assumption of a calm, focused workforce will overestimate how quickly adoption can happen when the workforce is already carrying external load.
McKinsey adds the forward view: it expects the pace of change to accelerate, driven by geopolitical, societal, technological and financial shifts. Waiting for change volume to fall back to a manageable level is a plan the forecasts give little reason to trust.
What Determines Change Capacity: Culture, History, Structure and Change Competency
Change capacity is determined by a set of conditions that can each be inspected, namely Prosci’s capacity factors, the operational constraints that limit a group from week to week, and the construct management researchers call organizational change capacity, which together turn capacity from a vague property into something a practitioner can locate. The difficulty is that these conditions interact: a strong culture can mask thin managerial bandwidth until a second large programme lands and the gap opens all at once.
Prosci’s Capacity Factors
Prosci names five factors that set change capacity: culture, history, structure, perceived need for change, and change management competency, as Tim Creasey lists them in Enough is Enough: Tips for Avoiding Change Saturation.
These factors are slow variables that shift over years, so they set a group’s baseline capacity before any particular programme is planned. They also explain why capacity cannot be read from headcount: two departments of the same size, with the same skills mix, can absorb very different amounts of change because they differ on these factors. Reading them for a specific group gives a practitioner a starting estimate of how large that group’s reserve is likely to be.
Culture and Structure
Organizational culture sets how a change is received: whether people expect to be consulted before a decision, whether trying something new and getting it wrong is safe, and whether managers are rewarded for running today’s operation or for adopting tomorrow’s. Structure sets the paths along which change travels, including how many layers a decision crosses, how many approvals a new process needs, and how many separate functions can send change to the same person.
A matrix structure multiplies the points at which change enters a role. A regional sales lead might receive a CRM change from the commercial function and a pricing process change from finance in the same month, with neither sender aware of the other. Culture then determines whether that sales lead raises the collision early or quietly absorbs both until something gives.
History With Past Change
Prosci notes that an organisation’s history with past change shapes how much new change its people can absorb, so capacity carries the memory of earlier initiatives. People predict the next change from their experience of the last one, and those predictions change how much effort they invest at the start.
An organisation that launched three transformation programmes in five years and quietly dropped two of them teaches its people to hedge: they keep the old spreadsheet running alongside the new system until they are sure the change will stick. That hedging doubles the workload of the transition and slows adoption. A history of changes that were finished, measured and reinforced builds the opposite habit, and new programmes start with credit.
Perceived Need and Change Management Competency
Perceived need is the degree to which people see why a change is necessary. When the reason is clear and believed, absorbing the change costs less effort, because people are not also arguing with it in their heads. Change management competency is the skill held by leaders and practitioners in sponsoring, sequencing, coaching and reinforcing change, and it determines how much of a group’s capacity each initiative wastes through poor execution.
These two factors respond faster than culture or history, which makes them the most practical places to start. A regulatory change with an explained and accepted rationale tends to be absorbed more readily than a discretionary one with a vague case, even when the regulatory change is larger. Strong change management competency means the same capacity goes further, because less of it is consumed by confusion and rework.
Operational Constraints: Attention, Bandwidth, Slack and Coordination Load
Operational constraints are the week-to-week limits on capacity: specific resources a group draws on when it absorbs a change, any one of which can run out while the others still have room.
Where the slow factors set a baseline, these constraints decide whether a particular group can take a particular change this quarter. They are the conditions a practitioner can inspect directly:
| Constraint | What runs out | Where to look |
|---|---|---|
| Leadership attention | Senior time to sponsor, decide and unblock | Steering committee agendas, sponsor calendars |
| Managerial bandwidth | Line managers’ time to coach and reinforce | Span of control, manager hours spent on escalations |
| Operational slack | Spare hours after the day job is done | Utilisation, overtime, backlog trends |
| Structural flexibility | Room to adjust roles, rotas and approvals | How long a role change or rota change takes to agree |
| Dependency and coordination load | Effort spent aligning with other teams | Number of hand-offs and joint sign-offs per change |
| Learning capability | Ability to acquire new skills quickly | Time to proficiency on recent changes |
| Adoption load | Number of changes already mid-adoption | Changes live but not yet embedded in the group |
| Trust and coherence | Belief that changes fit together and will last | Pulse comments, informal feedback, rumour volume |
The constraint that binds first differs by group. An operations centre on full rosters usually lacks operational slack long before anything else. A product team may have hours to spare but be tangled in dependency and coordination load, so every change waits on three other teams. A newly reorganised function may have slack and skills while trust and coherence have collapsed.
Adding capacity on the wrong constraint achieves nothing: extra training budget does not help a team whose real limit is that its managers have no hours left to reinforce what the training taught.
Organizational Change Capacity in Management Research
Management research treats organizational change capacity (OCC) as a measurable construct, which gives practitioners vocabulary and evidence beyond consultancy frameworks.
Three recent journal articles show the range of the research stream. In the Asia-Pacific Journal of Business Administration, Organisational change capacity and performance: the moderating effect of coercive pressure (2021) examines three sequential dimensions of OCC, in which capacity for change shapes process capacity and then context capacity. In Management Decision, The relationship between extreme contexts, organizational change capacity, and firm product and process innovation (2023) tests OCC as the mediator between perceived extreme contexts and firm innovation. In the Journal of Strategy and Management, Dynamic managerial capabilities and organizational change capacity as precursors of organizational dynamic capabilities in SMEs (2025) positions OCC as a meta-capability alongside managers’ own capabilities, feeding the dynamic capabilities a firm uses to adapt.
Read together, the studies place capacity between conditions and outcomes: it is shaped by what an organisation has experienced and it shapes what the organisation can achieve, including innovation under pressure. That position makes OCC something to manage actively, since a variable that mediates performance is worth measuring. The research also depends on asking managers and staff about their own organisations, which means the people inside the system are treated as the most reliable informants on how much change it can take.
Change Capacity Pays: Bain’s Change Power Research
Bain & Company’s change power research tests whether change capacity is worth funding and answers in three parts: the nine factors that make up an organisation’s power to change, the financial and employee results that travel with those factors, and what capacity’s place among them implies for sponsors. The research comes from a consultancy that sells change work, a point worth holding next to every figure it produces.
Nine Factors Across Leading, Teaming and Organizing
David Michels and colleagues at Bain & Company surveyed 1,885 employees at about 40 companies and identified nine factors that determine an organisation’s “change power”.
Michels reports the study in Bain’s Measuring Your Organization’s Ability to Change (Bain & Company), and groups the nine factors into three skill sets: leading change, teaming for change and organizing for change. The grouping is useful for anyone trying to locate a weakness. Leading concerns what sponsors and senior teams do: setting purpose and direction and making the change matter. Teaming concerns how groups work together through the change, across functions and levels. Organizing concerns the structures, resources and routines that let the change be absorbed.
The three skill sets distribute responsibility. A saturation problem in one business unit might trace to leading, where sponsors keep approving new work, or to organizing, where nobody holds the resources to backfill people seconded to projects. Knowing which skill set is weak points to a different owner and a different fix.
The design of the research also matters for practice. Because the factors are scored in a survey of employees, change power becomes something that can be compared across units and tracked over time. Capacity stops being a matter of opinion in a steering committee and becomes a measured attribute with a trend line. The survey also asks employees, so the judgement of capacity comes from the people who carry the change.
Margins, Growth and Inspired Employees
Bain reports that companies with strong change power have margins twice those of companies with weaker change power and grow revenue up to three times faster.
The people results point the same way. Twice as many employees at high change-power companies report being very inspired by their jobs, and their CEOs and senior management teams earn higher approval ratings. For a sponsor deciding whether capacity work is worth the money, these are the figures most likely to move the conversation away from treating it as overhead.
Those figures deserve careful reading before they go into a business case. The research is a survey-based correlation published by a firm that sells change consulting, so it shows that change power and performance travel together without proving which drives which. Profitable companies may simply have more slack, better-paid managers and more freedom to invest in how they change, which would raise their change power as a result of their margins.
Even with a generous discount for that reverse effect, the gap Bain reports is large. A doubling of margins does not disappear because part of it runs in the other direction, and it is difficult to describe an attribute associated with differences of that size as soft. The reasonable conclusion is that change power is worth measuring in one’s own organisation, where the relationship can be tested against local data.
Capacity as a Capability, Not a Ceiling
Bain counts capacity as one of the nine change power factors, which positions it as a capability an organisation can build instead of a fixed ceiling to stay under.
Michels makes the point directly in A Flood Of Change: Leading Through Times Of Overload (Bain & Company), where capacity sits among the factors that determine an organisation’s power to change. Most writing on saturation treats capacity as a limit to respect: find the threshold and keep the load under it.
Treating it as an improvable capability with a financial return changes who should care about it and how it gets funded. The audience widens from the change team to the CFO and the executive sponsors, because capacity now connects to margin and growth. The funding route moves from overhead, which is cut first in a tight year, to investment, which is judged against an expected return.
The question a leadership team asks changes as well. Under the ceiling view, the question is how much less change the organisation can do. Under the capability view, the question becomes how much more change it could carry if it built capacity deliberately.
An organisation that treats today’s capacity as fixed caps its ambition at that level, and gives up the growth that a larger capacity would allow.
Signs of Change Saturation: Why It Gets Misdiagnosed as a Communication Problem
The signs of change saturation appear at two levels, portfolio symptoms visible in adoption and attrition data and delivery signals visible in a programme’s calendar, and both resemble problems of discipline or messaging, which shapes the response leaders reach for. The misreading is understandable, because each signal on its own has a cheaper explanation than an overloaded portfolio, and the cheaper explanation is usually the one a busy steering committee accepts.
Portfolio Symptoms: Adoption, Go-Lives and Attrition
The Change Compass lists four portfolio symptoms of saturation in Change Saturation: How to Detect It Early and Protect Your Portfolio: declining adoption rates, missed go-live milestones, rising attrition, and visible disengagement on initiatives that previously ran cleanly.
Each symptom has an innocent explanation available. A falling adoption rate can be blamed on a clumsy user interface. A missed go-live can be blamed on a vendor. Rising attrition can be blamed on the job market. Leaders who take each signal separately will usually find a local cause, fix it, and move on.
The fourth symptom is the one that resists a local explanation. When an initiative that had been running cleanly starts to show disengagement, with the same team, the same sponsor and the same plan, the initiative itself has not changed, while its surroundings have. Something else is now drawing on the attention of the people it depends on, and that something is usually another change.
The symptoms are most informative in combination and by group. Adoption slipping on two unrelated initiatives that share the same receiving team, plus a missed milestone from a third, points to the team, whatever the individual project reports say. Read one at a time, they look like three separate problems with three separate owners.
All four symptoms lag, which is their main weakness. By the time attrition rises, the employee turnover costs in the fatigue data are already being incurred and the capacity that would have prevented them is spent.
Delivery Signals From an S/4HANA Transformation
A CIO account of an SAP S/4HANA transformation, published as Change saturation is not a communication problem in CIO, shows saturation reaching delivery mechanics well before it reached any engagement survey.
The people behind the signals were functional resources supporting the implementation while still doing their day jobs. At the same time the organisation was adopting Agile ways of working, so they were also learning new project roles, Agile ceremonies, Jira, new testing expectations and new processes. Many held real authority in their day jobs that did not carry over into their transformation roles, so they were learning to operate without the standing they normally relied on. The account’s conclusion is that saturation rarely announces itself in an engagement survey, so leaders should watch delivery signals first.
Attendance Erosion Before Pushback
The first signal in the account was erosion in attendance, before any pushback appeared. Stand-ups were missed, ceremonies got shorter, and the same names dropped off invitations. People raised no objection to the transformation while they triaged their calendars, choosing the meeting they could least afford to miss and quietly letting the others go.
Leaders tend to watch for resistance, so silence reads as consent, and attendance erosion passes unnoticed because nobody complains. Yet attendance data is available in calendars and meeting tools in close to real time, long before any survey cycle. The names that drop off first form a map of where capacity has already run out, and the pattern tends to repeat: the same functional leads appear on the competing-priorities list again and again.
Status Work Crowding Out Delivery
The second signal was status work crowding out delivery. A growing share of the team’s week went to preparing updates, attending check-ins and answering follow-ups, so the programme started paying for visibility with the time it needed for the work itself. Deliverables slipped and readiness checkpoints came back with gaps.
Status work looks like control, which is why it grows without challenge. A functional lead who spends Monday morning preparing three slightly different status decks for three forums has lost half a day of delivery, and the decks will report the slip that the lost half-day helped cause. When reporting hours rise while throughput stays flat or falls, the ratio between them is itself a saturation signal worth tracking.
Why More Communication Deepens Saturation
Leaders who read saturation as a communication or discipline gap add meetings, follow-ups and status updates, and that treatment consumes the capacity the team needs to recover.
The CIO account describes the leadership response as reasonable on its face: more meetings, more follow-ups and more frequent status updates, all intended to get the programme back on track. What happened instead was that the same people responsible for completing the work spent more of their week explaining why the work was behind. The account names this as the pattern most organisations miss: saturation gets diagnosed as a communication gap, and the remedy drains what is left.
The mechanism works as a self-reinforcing loop. Each slip prompts a request for more oversight. More oversight removes delivery hours from the people who are already short of them. Fewer delivery hours produce the next slip, which prompts yet more oversight. Every step is locally rational, and the loop tightens with each turn.
Breaking it starts with a different diagnostic question. Instead of asking why the team is not communicating, leaders can ask what else is landing on the specific named people who keep dropping off invitations, and how much of their week the transformation actually has. That question points at the portfolio, where the cause sits, instead of at the team’s discipline.
Left unexamined, the steering committee’s rescue plan becomes the next increment of change disruption on the very group it was meant to rescue.
How to Measure Change Saturation and Change Capacity Across the Portfolio
Measuring change saturation and change capacity involves four pieces of work, which are accepting that no single figure exists, building the portfolio view that project tracking misses, reading demand against capacity, and converting the result into decisions executives will act on. Each piece is harder than it looks on a slide, and none of them produces a score that settles the question by itself.
Why Saturation Has No Single Measure
The Change Compass describes saturation as an emergent condition arising from three interacting variables, none of which is directly observable.
In How to measure change saturation: a practical methodology for enterprise change functions, The Change Compass names the three: the volume of concurrent changes landing on a group, the intensity of each change, and the group’s capacity to absorb them.
Emergent means the condition cannot be read off any one input. A group can carry many low-intensity changes without strain, or a single high-intensity one that exhausts it. Capacity varies between groups and over time. Saturation only appears when the three are combined, and each of the three has to be estimated through a proxy.
Volume is estimated from an inventory of initiatives and their timelines. Intensity is estimated from change impact assessments, which rate how much of a role each change alters. Capacity is estimated from a model of what a group can absorb. Every proxy carries error, and the errors combine when the proxies are put together.
That is why any dashboard showing a single saturation number for an organisation deserves a follow-up question about what sits behind it. The number may still be useful, but only if the people reading it know which assumptions produced it and how sensitive it is to them.
The practical consequence is that change saturation measurement is a structured judgement built from estimates, and its credibility depends on how openly those estimates are shown.
Building the Portfolio View the PMO Lacks
Tim Creasey of Prosci observes that the Project Management Office (PMO) typically inventories projects and their technical details but does not build a view of the cumulative impact of all changes on the people affected.
Creasey makes the point in Enough is Enough: Tips for Avoiding Change Saturation (Prosci), where he notes that saturation typically arises because nobody keeps a portfolio view of all the change efforts underway. Each project team focuses on its own business opportunity and does not see how its change collides with the others.
The fix is a change of axis. A PMO register is organised by project: one row per initiative, with scope, budget, milestones and risks. A saturation view is organised by affected group: one row per group, with columns for weeks or months, and cells holding the impact each initiative places on that group in that period. The same underlying data supports both, but only the second shows the payroll team receiving four changes in the month of year-end close.
Organising measurement by affected group turns it into a change portfolio management task. Saturation is the sum of impacts on one group from many initiatives, and project tracking, however thorough, adds up the wrong things for that purpose.
The harder question is who owns the group-level view. If no function is responsible for the group-level view, then no function can say that a group is full, and every new approval proceeds on the assumption that someone else is watching.
Reading Demand and Capacity Together
The Change Compass separates saturation measurement, which captures the demand placed on people, from capacity modelling, which captures what people can absorb, and treats the two as different kinds of work.
Its guide How to Build a Change Capacity Model for Your Organisation (The Change Compass) treats the change capacity model as a separate artefact from the demand view. Read alone, either side misleads: demand without capacity cannot say whether a load is too much, and capacity without demand cannot say whether it is being exceeded.
| Side | Question it answers | Main inputs | Typical owner | What goes wrong if read alone |
|---|---|---|---|---|
| Demand | How much change is landing on this group, and when? | Initiative inventory, impact assessments, timelines | Change function or portfolio office | High load is assumed to be overload, even for groups with room |
| Supply | How much change can this group absorb in this period? | Capacity constraints, workload data, recent adoption history | Business unit leaders with HR and the change function | Spare capacity is assumed to exist without checking what is already landing |
Demand: Concurrent Volume and Change Intensity per Group
Demand measurement counts the changes landing on each affected group in each period and rates the intensity of each one. Intensity reflects change impact: how much of the role a change alters, whether it touches processes, tools, behaviours, reporting lines or all of them. The ratings come from each initiative’s impact assessment, normalised so that different project teams use the same scale.
Volume alone misleads because a dozen small procedural tweaks and a single role redesign can count the same on a simple tally while placing very different demands on people. Weighting each change by its intensity separates the two cases. A customer service team facing one new knowledge base and one changed script carries far less than one whose entire workflow moves to a new platform in the same quarter, even though each faces two changes.
Supply: Capacity Modelling and the Overload Threshold
Capacity modelling estimates, for each group, how much absorption time exists in a period, using the operational constraints on capacity as its inputs. A practical way to frame it asks how much free time a person has to absorb change impacts before reaching an overload threshold, and then sums that across the group.
The weakness of the approach is that the threshold is hard to generalise in white-collar and knowledge work, where tasks expand to fill the time available and nobody’s week has a clear boundary. A workable response is to treat each group’s threshold as a hypothesis and test it against the delivery signals of attendance erosion and status work: a group whose modelled capacity looks ample while its people drop off stand-ups has a model that needs correcting.
Turning Measurement Into Executive Decisions
The Change Compass argues that measurement turns a felt problem into evidence that secures executive attention and supports a credible case for resequencing programmes.
The distinction it draws is between feeling saturation and proving it. Leaders sense that people are struggling and change managers notice adoption slipping, but a sense of strain does not move a portfolio decision. Evidence does, especially when it is comparative and specific: this group carries five concurrent high-intensity changes in the third quarter against a modelled capacity for two, and these are the initiatives responsible.
The comparison works best when it sets a group’s measured demand against its own modelled capacity, since an executive can argue with an abstract index but has a harder time dismissing a named team with a named set of initiatives landing in a named month.
The most effective format is usually a view by group and by period that executives can read in seconds, showing where demand exceeds modelled capacity and which initiatives drive the excess. Every hot spot on that view should come with a decision request attached: move this go-live, defer that initiative, add backfill to this team.
Measurement that ends in a report without a sequencing request tends to become one more document that consumes attention without changing what lands on people. The test of a saturation measure is whether it changed a date, a scope or an allocation in the next portfolio review.
How to Reduce Change Saturation: Sequence, Stop and Expand Capacity
Reducing change saturation works through two levers that follow from Prosci’s equation, reducing disruption or raising capacity, and an effective response works on both instead of pushing the current initiatives harder. Pushing harder is the default because it asks nobody to give anything up, while both levers require someone to concede a date, a project or a resource. The order that tends to work runs from sequencing and stopping on the demand side, through Bain’s foundational steps on the supply side, to prioritisation as the discipline that governs both.
Reducing Disruption
Reducing disruption means changing what lands on a group and when it lands, through sequencing the changes already approved and stopping or deferring some of them altogether.
Both moves act on the portfolio itself, a level the status-meeting trap never reaches. Sequencing keeps every initiative alive and changes only its timing, so it is the easier conversation. Stopping removes work, so it is the harder one, and it is the move most leadership teams avoid until the evidence forces it. The two work best together, because sequencing alone eventually runs out of calendar.
Sequencing Changes With a Risk Matrix
Prosci recommends organising the sequence of current changes with a risk matrix in Prosci Change Saturation Model, so that potential overload points are identified early and addressed before they occur. In practice, each change is placed by its impact on a group and its timing; where several high-impact changes stack on the same group in the same window, the matrix shows an overload point.
Change sequencing is the cheapest move available because nothing is cancelled. Moving a reporting-tool rollout for the finance team from the fourth quarter, when year-end close consumes every spare hour, to the first quarter costs a few weeks of benefit and can prevent a failed adoption. The matrix is only as good as the impact data behind it, which is why sequencing depends on the group-level portfolio view being in place first.
Sacrificing Good Ideas: Stopping and Deferring Work
David Michels of Bain & Company sets out, in A Flood Of Change: Leading Through Times Of Overload, a first step of sacrificing good ideas so that great ones have the space to flourish. In portfolio terms, that means stopping or deferring initiatives instead of adding to them, even when each initiative has merit on its own.
The difficulty of stopping work is mostly political. Good ideas have sponsors, stopping one can look like an admission of failure, and the benefits of a stopped project are easy to quantify while the benefits of a less saturated workforce are diffuse. A deferral list with named restart conditions helps: an initiative paused until the ERP stabilisation is complete is easier for its sponsor to accept than one cancelled without a path back.
Expanding Capacity
Expanding capacity uses Michels’ remaining four steps, each of which acts on a different constraint on how much change a group can absorb.
Bain’s change power evidence is the case for spending on these steps; the steps themselves are how the spending turns into capacity. They work over different time horizons. Removing bottlenecks and reallocating resources can show results within a quarter, while front-line ownership and personal resilience build over longer periods. A leadership team can therefore start with the fast steps while the slower ones take hold.
Removing Bottlenecks and Working in Smaller Increments
Michels’ second step is to accelerate speed by systematically removing bottlenecks and working in smaller increments. Smaller increments let people absorb one piece of a change and stabilise before the next piece arrives, which reduces the depth of the performance dip and shortens the time spent operating at reduced competence. Removing bottlenecks frees the waiting time that otherwise sits inside every change, such as approvals that take weeks or environments that are not ready.
A new procurement process rolled out category by category gives each buying team a few weeks to settle before its scope widens, where a single big-bang launch would put the whole function on the learning curve at once. The same logic underpins Agile ways of working, which is why organisations adopting them often find that delivery in increments raises capacity even before anything else changes.
Front-Line Ownership and Personal Resilience
The third and fourth steps are to give the front line more ownership and control, and to invest in building personal resilience. Ownership reduces the effort a change costs, because people who adapt a change to their own work spend less energy than people who receive instructions they had no part in shaping. Personal resilience is the set of skills and conditions individuals use to recover from strain, and Michels notes that each person’s level of resilience differs.
The two steps reinforce each other. A front-line team allowed to decide how a new scheduling tool fits its shift patterns will usually adopt it faster and with fewer workarounds than one handed a fixed configuration. Resilience investment pays off in this context because it sits alongside the demand cuts and the ownership changes, so the support goes to people whose load is also being managed.
Reallocating Resources as Conditions Change
The fifth step is to dynamically reallocate resources as circumstances change. Resource reallocation means moving people, budget and backfill toward the groups where the portfolio view shows overload points, and away from groups with spare capacity, as conditions change during the year.
A contact-centre team going through a telephony migration might receive temporary staff for six weeks so that agents can train without lengthening queue times, with the temporary budget drawn from an initiative that has been deferred. Annual allocation cycles cannot do this, because overload points move faster than budgets are set, so reallocation depends on a standing forum with the authority to move resources mid-year.
Limiting Change to What Can Be Accomplished
Michels treats prioritisation as the governing discipline: in A Flood Of Change: Leading Through Times Of Overload (Bain & Company), effective managers rigorously set priorities and limit change to what the organisation can accomplish.
Prioritisation in this sense means an explicit ranked list of initiatives, maintained against capacity, with new work admitted only when capacity is freed. It operates as an intake rule. No new initiative is approved for a group already past its modelled capacity unless the sponsor names what moves to make room, whether that is a deferral, a resequencing or added resources.
The rule changes the conversation in governance forums. Under the usual approach, each proposal is judged on its own business case, and the question is whether it is worth doing. Under a capacity limit, the question becomes whether it is worth more than what it would displace, which is the question that saturation makes unavoidable whether anyone asks it or not.
The difficulty is that the rule binds senior leaders as much as anyone else, including the ones who set it. An executive team that applies a capacity limit to business units while exempting its own strategic initiatives will find the limit ignored within a quarter.
The open question for each leadership team is who holds the authority to say that a group is full, and whether that authority would survive a request from the chief executive.
How to Start Applying Change Saturation and Change Capacity
Starting to apply change saturation and change capacity takes one bounded experiment: choose a single group that sits at the crossroads of several initiatives, list every change due to land on it over the next two quarters, and test that list with the group’s own managers before any enterprise-wide model is attempted.
The people inside the group will usually spot what the list misses within minutes: the system patch nobody logged, the policy revision arriving from another function, the audit that falls in the same month as a go-live. Their corrections are the first real data on the demand side, and their reactions to the finished list (“we cannot take the third one before March”) are the first real data on capacity. Choosing a group that already shows delivery signals makes the experiment easier to justify and the result easier to read.
Timing changes the cost of acting on the result. The experiment is worth running a few weeks before the annual planning cycle, when approvals are still open and a resequencing request costs a slide, compared with mid-year, when the same request means unpicking committed plans and contracts.
A boundary case is worth anticipating. If the list turns out to be short while people are plainly exhausted, the problem may sit outside the change portfolio, in workload, staffing or management practice, and the experiment has still done its job by ruling the portfolio out.
The failure mode to avoid is the opposite of starting small: commissioning an enterprise-wide capacity model first, spending two quarters building it, and making no portfolio decision in the meantime. The decision the experiment should force is concrete. Which single change, landing on that group, would you move first, and who has to agree?
Anonymous. Counted, not tracked.
Where is your organisation with this right now?
What is the hardest part where you are?
In a sentence: what are you trying to work out right now?
No names, no company. Anonymous. Counted, not tracked.