Why heatmaps alone are insufficient

The appeal of the change heatmap is its simplicity. A colour scale from green to red, a grid of business units against a timeline, and suddenly the entire portfolio is visible on a single page. For organisations just beginning to manage change at a portfolio level, that visibility is a genuine step forward. The problem is not the heatmap itself – it is the assumption that presence equals impact. A heatmap shows that a change is happening to a particular group of people in a particular period. It does not show how much adaptation that change requires, how quickly the group can absorb it, or whether the accumulated load is approaching the point of failure.

Research from McKinsey has consistently found that large-scale transformation programmes fail at a high rate, with organisational fatigue and change overload among the most commonly cited root causes (McKinsey, “Losing from Day One”). A heatmap can show you that a transformation is in flight; it cannot show you whether the people carrying it are already running at capacity from the five other initiatives that appear alongside it on the same grid. That distinction matters enormously for sequencing, resourcing, and governance decisions. The five ways below are designed to close that gap.

Way 1 – Weight impacts by intensity, not just presence

The most immediate limitation of a standard heatmap is that it treats all changes as equal. A global enterprise resource planning migration sits in the same coloured cell as a minor update to an approval form. Both show up as a mark in the grid, but the adaptation burden they place on employees is orders of magnitude apart. The first requires people to learn new systems, change long-established workflows, and often restructure how entire functions operate. The second takes an afternoon to understand. Treating them identically in your measurement framework produces a picture that is technically accurate but practically misleading.

The solution is to introduce impact weighting – scoring each change not simply on whether it touches a group, but on how deeply it requires that group to change their knowledge, capability, and behaviour. The Prosci ADKAR model offers a practical framework for this: changes that require significant shifts in Awareness, Desire, Knowledge, Ability, and Reinforcement carry a substantially higher adaptation burden than those requiring only one or two of those dimensions. A system migration typically demands all five. A process clarification might only require updated Knowledge. When you weight your heatmap data by ADKAR-dimension intensity, the saturation picture that emerges is dramatically more accurate. High-intensity changes show up with proportionally greater weight, allowing you to identify genuine saturation risk even in periods when the raw count of initiatives looks manageable.

Way 2 – Measure the pace of change, not just volume

Volume measurement captures how many changes are in flight at any point in time. Pace measurement captures something different and arguably more important: the interval between significant changes, and whether employees have enough time to stabilise before the next major disruption arrives. A heatmap that shows three major initiatives across a twelve-month period might look manageable – until you realise that all three land in the same six-week window, followed by six months of relative quiet. The volume is moderate, but the pace is brutal.

Human beings need time to consolidate change. Neurologically and psychologically, the process of embedding new behaviours and workflows requires a period of reduced pressure during which the new way of working becomes habitual rather than effortful. When the next significant change arrives before that consolidation has occurred, people are being asked to adapt from a position of instability rather than a position of readiness. Harvard Business Review research on change fatigue identifies precisely this dynamic – it is not just the number of changes that exhausts people, but the relentlessness of the pace. Measuring recovery windows between significant change events, and building those windows explicitly into your portfolio calendar, is one of the highest-leverage actions a change practitioner can take. The heatmap shows presence; pace measurement shows whether anyone has time to breathe.

Way 3 – Build capacity baselines for employee groups

Not all employee groups are equally capable of absorbing change at any given moment. A frontline team that has just completed a major system rollout has depleted change capacity. A corporate function that has been stable for two years has a full reservoir. A heatmap treats every cell in the grid as if the people behind it have identical absorptive capacity, which they manifestly do not. The third way to graduate beyond the heatmap is to establish capacity baselines for each major employee group, and then compare actual change load against those baselines rather than against an undifferentiated average.

Gartner research on change fatigue suggests that employees can effectively absorb approximately three concurrent major changes before performance and engagement begin to deteriorate materially. That figure is not universal – it varies by the nature of the work, the maturity of the organisation’s change capability, and the level of leadership support available – but it provides a useful starting point for establishing thresholds. The Change Compass platform enables organisations to set group-specific capacity thresholds and track actual change load against them in real time, generating alerts when a particular employee group is approaching or exceeding their capacity limit. This transforms the heatmap from a passive record of what is happening into an active management tool that flags risk before it becomes failure.

Way 4 – Integrate change data with operational performance metrics

Change measurement that lives only inside the change management function is change measurement that struggles to influence business decisions. Leaders who control the sequencing and resourcing of initiatives are, understandably, more responsive to data expressed in the language of business outcomes than data expressed in the language of change methodology. The fourth way to graduate from heatmaps is to connect your change load data with the operational performance metrics that your organisation already tracks and cares about: productivity indices, customer satisfaction scores, employee engagement survey results, voluntary attrition rates, and error or rework rates.

When you can demonstrate a correlation between periods of high change intensity for a particular group and subsequent dips in that group’s productivity or engagement scores, you are no longer making a theoretical argument about change capacity. You are showing the business cost of change saturation in terms that finance leaders, operations directors, and executive sponsors can immediately understand and act upon. McKinsey’s research on people and organisational performance consistently shows that organisations that treat change capacity as a measurable business variable – rather than a soft concern – achieve significantly better transformation outcomes. Integrating your change data with operational metrics is the step that makes that connection tangible and defensible.

Way 5 – Connect measurement to portfolio governance

Measurement without governance action is, ultimately, just reporting. The fifth and most consequential way to graduate from heatmaps is to connect your change saturation data directly to the portfolio governance processes where sequencing, prioritisation, deferral, and resourcing decisions are actually made. This means ensuring that change capacity data is a standing input to your portfolio review forums, that there are clear thresholds that trigger mandatory review of an initiative’s timing when capacity limits are breached, and that change practitioners have a formal voice at the table when those conversations occur.

In practice, this looks like presenting change load data alongside financial and risk data in portfolio dashboards, using saturation thresholds to inform go/no-go recommendations for new initiative launches, and having the evidence base to argue for deferral of a lower-priority initiative when a critical employee group is already operating at capacity. The Change Compass platform is specifically designed to support this governance integration – providing the portfolio-level visualisation, group-specific capacity tracking, and reporting outputs that change leaders need to participate credibly in executive governance forums. Measurement at this level shifts the change management function from a delivery support role into a genuine strategic capability, one that actively shapes the conditions in which transformation succeeds.

Building a change measurement maturity journey

These five ways are not a single leap – they are a maturity journey that organisations can progress through at a pace that reflects their current capability and the urgency of their change portfolio challenges. Most organisations begin with the heatmap because it is accessible and requires only basic data collection. Adding impact weighting is typically the logical next step, because it requires only a scoring framework applied to data you already have. Pace measurement comes next, as it requires a more disciplined approach to recording change timelines and recovery periods. Capacity baselining requires a modest investment in establishing thresholds and tracking systems. Operational integration requires collaboration across functions. Governance integration requires organisational authority and sustained commitment from executive sponsors.

Organisations that have completed this journey report qualitatively different conversations in their portfolio forums. Instead of debating whether a particular team is “too busy” based on subjective assessments, they are working from data that shows exactly how much change load that team is carrying, how that load compares to their established capacity threshold, what the pace of upcoming changes looks like, and what the likely operational impact of proceeding with the current schedule will be. That is the difference between change management as an art and change management as a discipline. The five ways above are the pathway from one to the other.

Frequently asked questions

How do I start weighting change impacts when we have never scored initiatives that way before?

The most practical starting point is to apply a simple three-tier classification – low, medium, and high intensity – based on the number of ADKAR dimensions a change requires employees to shift. Low-intensity changes require knowledge updates only. Medium-intensity changes require new knowledge and some adjustment to established behaviours. High-intensity changes require significant shifts across all five ADKAR dimensions. Even this rough classification will produce a materially more accurate picture of saturation than an unweighted count, and you can refine the scoring framework as your data matures.

What is a realistic capacity threshold for frontline employee groups?

The Gartner benchmark of approximately three concurrent major changes provides a useful starting point, but it should be calibrated to your specific context. Frontline roles with high operational pressure and limited discretionary time tend to have lower thresholds than knowledge worker roles with more flexible schedules. It is also worth distinguishing between the number of changes and the cumulative intensity of those changes – a frontline team might manage three low-intensity changes comfortably while struggling with even one high-intensity transformation on top of normal operational demands.

How do we get access to operational performance data to connect with our change load data?

This is primarily an organisational relationship challenge rather than a technical one. The change management function typically needs to establish working relationships with HR analytics, operations reporting, and finance teams to access relevant data sets. The most effective approach is to identify one or two high-visibility pilot cases where change saturation is a plausible contributing factor to an observable performance issue, and use those cases to build the business case for ongoing data integration. Once you can demonstrate the value of the connection, access tends to become much easier to negotiate.

How do we ensure change capacity data actually influences governance decisions rather than just being noted and ignored?

The single most important factor is executive sponsorship for the principle that change capacity is a legitimate portfolio constraint – equivalent in status to financial capacity or resourcing capacity. Without that sponsorship, change data tends to be noted and set aside when it conflicts with delivery timelines. With it, there is a formal basis for the change function to request that initiatives be deferred, sequenced differently, or resourced more heavily when capacity thresholds are breached. Building that sponsorship typically requires the kind of operational integration described in Way 4 – showing the business cost of ignoring capacity data is the most powerful lever for establishing governance authority.