Three Approaches to Deriving a Single View of Change
Ask any senior change practitioner what they wish they had, and a single view of change sits near the top of the list. Not another dashboard, not another status report, but a genuine, consolidated picture of every change impacting a given group of people at any point in time. The ability to see cumulative change load, identify collision points, and make resourcing decisions based on evidence rather than instinct is, as many practitioners describe it, the “nirvana” of the profession. And yet, despite widespread agreement on its value, most organisations are nowhere near achieving it.
The gap between aspiration and reality is significant. Research from Prosci’s change management maturity model consistently shows that the majority of organisations operate at the lower end of the maturity spectrum, managing change reactively and in silos rather than as a coordinated, enterprise-wide capability. Individual project teams may run their own impact assessments, but those assessments rarely speak to each other. The result is a fragmented picture of change where no single person or team has a reliable view of what employees are actually absorbing.
What makes this problem particularly stubborn is that it is not primarily a technology problem. It is a practice problem. Organisations know they should consolidate their change data, but the question of how to do it, and at what level of rigour, is rarely answered clearly. This article defines three distinct approaches to building a single view of change, examines what each delivers and where each falls short, and makes the case for why the most sophisticated approach is not a luxury reserved for large enterprises with mature change functions. It is the standard every organisation should be working toward.
You can download a copy of the infographic summarising these three approaches at https://thechangecompass.com/wp-content/uploads/2021/06/Approaches-in-single-view-of-change.png.

What a single view of change actually means
A single view of change is not a project list. It is not a programme register or a governance report showing which initiatives are on track. It is a structured representation of the change impacts landing on specific groups of people, at specific points in time, across all active programmes simultaneously. The emphasis is on people, not projects. The question it answers is not “what are we delivering?” but “what are our people being asked to absorb, and when?”
This distinction matters enormously in practice. A project-centric view tells you that three major technology implementations are running concurrently. A people-centric single view of change tells you that the customer service team in the eastern region is simultaneously absorbing a new CRM system, a restructure of their reporting lines, and a revised performance framework, all within the same eight-week window. Those are very different pieces of information, and only the second is useful for making decisions about change sequencing, communication timing, and adoption risk.
Building this kind of view requires agreement on a common data model: which change types you are tracking, how you classify impact severity, which employee groups or business units form the unit of analysis, and over what time horizon the view is maintained. Without that foundation, you end up with a patchwork of inconsistent assessments that cannot be meaningfully aggregated. The three approaches described below represent different levels of rigour in establishing and maintaining that foundation, and each reflects a different level of organisational commitment to change as a managed capability.
Approach 1 – Estimating the pulse: quick wins and limitations
The first approach is the most common starting point, and it is worth being clear that it is a starting point rather than a destination. In this approach, a change practitioner, portfolio office, or PMO collects high-level information about active and planned initiatives and produces a heatmap showing estimated change load across different employee groups over time. The word “estimated” is key. The impacts are not derived from rigorous assessment at the project level. They are approximated, often by a single analyst working from project plans and conversations with project managers.
The appeal of this approach is real. It is fast to stand up, requires no significant technology investment, and can be produced using a spreadsheet or a basic visualisation tool. For an organisation that has never had any consolidated view of change before, even an imperfect heatmap represents a step forward. It gives executive sponsors a rough sense of where the change load is heaviest, and it can prompt useful conversations about sequencing that would not otherwise happen.
The limitations, however, are substantial. Because the data is estimated rather than grounded in structured impact assessments, the view is only as reliable as the individual who produced it, and it degrades quickly as the change portfolio evolves. Projects accelerate, stall, or get descoped, and the heatmap becomes stale within weeks. There is also no systematic mechanism for keeping it current, which means it tends to be produced for a specific governance purpose, presented once, and then quietly retired until the next time someone asks for it. Decisions made on the basis of this view carry significant risk because the underlying data has not been verified at the project level and cannot be easily interrogated.
Approach 2 – Periodic pulse checking: building rhythm and structure
The second approach introduces a degree of structure and rhythm that the first lacks. Rather than producing an ad hoc heatmap when required, organisations operating at this level maintain a regular cadence, typically monthly, of collecting and updating change impact data from projects across the portfolio. Project teams are asked to document their impacts using a consistent template, and the outputs are consolidated into a single view that is reported to governance forums on a scheduled basis.
This approach represents a meaningful improvement. The data is more grounded because it comes directly from project teams rather than being estimated centrally. The regular cadence means the view is updated more frequently and is therefore more reliable. Governance bodies begin to develop a habit of reviewing the single view as part of their standard portfolio reporting, which normalises the conversation about change load and creates accountability for managing it.
In many organisations, this level of practice already represents a significant cultural shift. McKinsey research on large-scale transformations has consistently highlighted that poor coordination between concurrent change initiatives is one of the primary contributors to failed adoption and employee fatigue. A periodic pulse-checking approach at least surfaces these coordination risks in a structured way, even if it does not fully resolve them.
The limitations of this approach centre on its episodic nature. Monthly data collection means that the view is always somewhat out of date. More critically, the single view produced in this approach tends to inform reporting rather than drive decisions. It tells governance what is happening but does not integrate deeply enough into project planning, resourcing, or change sequencing decisions to actually change outcomes. There is also a data quality problem: when project teams are asked to self-report their impacts using a template, the quality of those assessments varies considerably depending on the maturity of the project’s change capability. Without a mechanism to validate or interrogate the data, the consolidated view can reflect widely different standards of rigour across the portfolio.
Approach 3 – Hand on the pulse: the embedded operating system
The third approach is qualitatively different from the first two, and it is the approach that every organisation should be working toward. Rather than treating the single view of change as a reporting artefact that is produced periodically and presented to governance, this approach embeds change data as a live, continuously maintained input into business operations and decision-making. The single view is not a report. It is an operating system.
In practical terms, this means that change impact data is maintained in real time, or close to it, and is structured in a way that allows it to be sliced, queried, and acted upon at multiple levels of the organisation. Business leaders can view the change load on their teams at any point. Change practitioners can identify emerging collision points and intervene before they become adoption failures. Portfolio offices can use the data to make evidence-based decisions about sequencing, resourcing, and prioritisation. And because the data is maintained continuously rather than refreshed monthly, it reflects the actual state of the change portfolio, not a snapshot from three weeks ago.
The defining characteristic of this approach is that change data is integral to governance rather than supplementary to it. Decisions about which projects get approved, which get deferred, and how implementation timelines are structured are made with explicit reference to the impact those decisions will have on the people being asked to absorb the change. Gartner’s research on change management effectiveness has found that organisations which integrate change capacity data into portfolio governance are significantly better positioned to sustain adoption and realise intended benefits from transformation programmes.
This approach also requires, and builds, a fundamentally different relationship between change practitioners and the business. Change is not something that happens to the organisation from the outside and is then managed reactively. It is a dimension of business performance that is actively monitored, managed, and optimised, in the same way that financial or operational performance is managed. That shift in mindset is as important as the tools and processes that support it.
Why organisations need to move toward approach 3
The case for moving beyond the first two approaches is not primarily about best practice compliance. It is about business outcomes. The accumulation of uncoordinated change is one of the most underappreciated risks in large organisations today. When too much change lands on the same people in the same window, adoption rates fall, productivity drops, and the benefits that justified the investment in each individual programme are not realised. This is not a theoretical risk. Harvard Business Review research on change fatigue has documented that employees experiencing high cumulative change load are significantly more likely to resist new initiatives, disengage from their roles, and leave the organisation.
The first two approaches provide some visibility into this risk, but they do not provide the granularity or timeliness needed to actively manage it. A heatmap produced six weeks ago, based on estimated impacts, does not give a business leader the confidence to make a high-stakes decision about whether to accelerate a technology rollout or defer it by a quarter. A live, data-driven single view of change does.
There is also a structural argument for approach 3 that relates to agility. Organisations that aspire to manage change as an agile capability, responding quickly to market shifts and internal priorities while maintaining employee wellbeing and productivity, cannot do so if their view of change is episodic and imprecise. Agility in change management requires the same real-time data foundations that agility in operations or product development does. Without a continuously maintained single view of change, decisions about sequencing and resourcing default to seniority and politics rather than evidence, and the organisation’s change capacity is chronically misallocated.
The maturity journey from approach 1 to approach 3
It would be unrealistic to suggest that every organisation can or should immediately adopt the hand-on-the-pulse approach. The journey from approach 1 to approach 3 is a genuine maturity progression, and it requires investment in data practices, governance structures, technology, and change practitioner capability. For most organisations, the progression is sequential, and each step builds the foundations that the next one requires.
Moving from approach 1 to approach 2 typically requires establishing a consistent impact assessment methodology that project teams can apply, creating a regular cadence for data collection and consolidation, and securing a governance forum that is willing to receive and act on the single view as part of its standard agenda. These are cultural as much as procedural changes. They require the PMO or change function to build credibility with the business by demonstrating that the data is reliable and the insights are actionable.
Moving from approach 2 to approach 3 is a more significant step. It requires a technology platform that can maintain and present change data in real time, a data governance model that ensures consistent quality across project submissions, and a set of business processes that use the single view as a live input rather than a periodic report. It also requires a change in how the organisation thinks about the role of the change function, from a support service that produces documentation to a strategic capability that manages change as a business resource.
The organisations that have successfully made this transition share a common pattern: they invested in the methodology before the technology. They established what data they needed, how it would be defined and collected, and how it would be used in decisions, before they invested in the platform to make it scalable. Organisations that invest in technology first, without a clear data model and governance framework behind it, typically find that the platform becomes another source of inconsistent data rather than a reliable operating system.
How The Change Compass enables the hand-on-the-pulse approach
The Change Compass is a digital change management platform purpose-built to support organisations in achieving and sustaining the third approach. Rather than requiring change practitioners to manually consolidate impact data from spreadsheets and project templates, the platform provides a structured environment where change data is captured, maintained, and visualised in real time across the full portfolio. Business leaders can see the change load on their teams at any point in time. Change practitioners can identify emerging pressure points and model the impact of sequencing decisions before they are made. Governance bodies receive a live, evidence-based picture of change capacity rather than a retrospective report.
Critically, the platform is designed to support the methodology as much as the technology, providing the data structures, impact assessment frameworks, and reporting templates that organisations need to build a consistent, high-quality single view of change. For organisations earlier in their maturity journey, it can also support the transition from approach 1 or 2, helping teams establish the data disciplines that make approach 3 achievable over time.
Frequently asked questions
What is a single view of change and why does it matter?
A single view of change is a consolidated, real-time representation of all the changes impacting a given group of employees at any point in time, across every active programme and initiative in the organisation. It matters because without it, organisations cannot reliably assess cumulative change load, identify collision points between concurrent initiatives, or make evidence-based decisions about sequencing and resourcing. Change practitioners who lack this view are managing complexity without the data they need to do so effectively.
How is a change heatmap different from a single view of change?
A change heatmap is typically a visual representation of change activity across the organisation, showing which groups are most heavily impacted during a given period. A single view of change is broader and more dynamic: it encompasses not just the visual output but the underlying data model, collection processes, governance structures, and decision-making integration that make the view reliable and actionable. A heatmap is often the product of approach 1, and while it is a useful starting point, it is not the same as the fully embedded single view that approach 3 delivers.
How long does it typically take to move from approach 1 to approach 3?
The timeline varies considerably depending on the size and complexity of the organisation, the maturity of the existing change function, and the level of executive sponsorship for the capability investment. In organisations that move deliberately and invest in methodology before technology, a transition from approach 1 to approach 2 might take six to twelve months, and from approach 2 to approach 3 a further twelve to twenty-four months. However, organisations that adopt a fit-for-purpose digital platform early in the journey can accelerate this considerably by building the right data disciplines from the outset.
Can smaller organisations achieve approach 3, or is it only realistic for large enterprises?
Approach 3 is achievable for organisations of all sizes, and in some respects it is easier for smaller organisations because the data volumes are more manageable and the governance structures simpler. The core requirements, a consistent impact assessment methodology, a live data environment, and governance integration, scale down as well as up. Smaller organisations that invest in the right platform and establish the right disciplines can often reach approach 3 faster than large enterprises, precisely because they do not carry the same legacy of siloed project governance and fragmented change data.
References
Prosci. Change Management Maturity Model. Prosci Research.
McKinsey & Company. The people power of transformations. McKinsey & Company.
Gartner. Organisational Change Management Insights. Gartner Human Resources Research.
Harvard Business Review. The Change Management Mistake Most Companies Make. Harvard Business Review, 2023.





