'Why should we change?' This is the most fundamental question in change management. It is the question that every impacted individual, consciously or not, asks when confronted with a change initiative. The quality and authenticity of the answer to this question determines whether individuals will develop the awareness and desire necessary to engage with and adopt the change.
Definition and Distinction
The case for change is the documented rationale that explains why the status quo is no longer acceptable or optimal, and why the specific change being proposed is the appropriate response. It is distinct from the business case (which is primarily a financial justification for investment), the project objectives (which describe what the project will deliver), and the change vision (which describes what the future will look like). The case for change focuses specifically on the human dimension: why do people—individually and collectively—need to change?
A compelling case for change operates at multiple levels. At the organisational level, it demonstrates alignment with strategy, regulatory requirements, or competitive necessity. At the team level, it explains how the change addresses current pain points and creates better working conditions. At the individual level, it articulates the personal benefits of embracing the change.
Why This Matters for Change Management
Prosci's ADKAR model places Awareness—understanding the need for change—as the first and essential stage of individual change (Hiatt, 2006). Without a clear, credible, and personally relevant answer to 'Why should we change?', individuals will not develop the desire to participate in the change or invest in acquiring the new knowledge and skills required.
The case for change must be both rationally compelling (grounded in evidence and logic) and emotionally resonant (connecting with the values, concerns, and aspirations of the audience). Communications research consistently shows that messages that combine rational evidence with emotional narrative are significantly more persuasive than those that rely on data alone (Heath & Heath, 2007).
Developing and Documenting the Case for Change
The case for change should be developed in close collaboration with the project sponsor and should be tested with representative members of the impacted population before broad distribution. It should address: the current state problems or opportunities that make change necessary; the consequences of not changing; the specific benefits of the proposed change; and the personal impact on the individual.
Example of a well-articulated case for change:
'Our current financial reporting process takes an average of 14 days to close each month, making it one of the slowest in our industry. This delays strategic decision-making and creates significant manual workload for our finance team—workload they consistently identify as a source of frustration and error. The new system will reduce month-end close to five days, eliminate the most time-consuming manual reconciliation tasks, and give our team more time for the analytical work they find most valuable. For our organisation, this is a necessary step in building the agility required to compete in an increasingly dynamic market.'
Common Pitfalls and How to Avoid Them
Building the case for change only at the organisational level: Organisational rationales (strategy, competitive positioning) do not resonate with frontline employees unless translated into personally relevant terms. Always develop a multi-level case for change.
Using only negative rationales (threat, risk of failure) without positive vision: A case for change built entirely on fear of consequences creates anxiety without hope. Balance the urgency of the current situation with an inspiring description of the future state.
Developing the case for change without involving employees: A case for change developed entirely by leadership and communicated downward may miss the specific concerns and pain points of the impacted population. Involve employee representatives in its development.
Communicating the case for change once and assuming it is understood: The case for change must be repeated, reinforced, and personalised across the change journey. A single communication event is rarely sufficient to build genuine awareness and desire.
References
Hiatt, J. M. (2006). ADKAR: A Model for Change. Prosci. https://www.prosci.com/resources/articles/adkar-model
Heath, C., & Heath, D. (2007). Made to Stick. Random House. https://www.randomhouse.com/books/124072/made-to-stick-by-chip-heath-and-dan-heath
Kotter, J. P. (1996). Leading Change. Harvard Business Review Press. https://hbr.org/books/kotter