The perceived need for change—the degree to which individuals who are impacted by a change believe that change is necessary—is a fundamental determinant of adoption success. When employees do not understand or accept the rationale for change, even technically well-designed solutions will fail to achieve the behavioural adoption required to realise intended benefits.
Definition and Distinction
Perceived need for change is a subjective measure: it reflects what impacted individuals believe about the necessity of change, not what objectively may be required. It is the foundation of the 'Awareness' and 'Desire' stages of Prosci's ADKAR model (Hiatt, 2006)—without an understanding of why the change is needed and a personal belief that the change is necessary, individuals will not take the steps required to adopt new ways of working.
This concept is distinct from the objective case for change (the factual, evidence-based rationale for the initiative, typically documented in the business case), and from organisational readiness (the degree to which the organisation's systems, processes, and structures are prepared for change). Perceived need is entirely about the subjective beliefs of the people who will be most affected.
Why the Perceived Need for Change Matters
Change management research consistently demonstrates that insufficient awareness of the need for change and insufficient desire to support and participate in the change are the two most common reasons why change management efforts fail to achieve adoption objectives (Prosci, 2023). Before individuals invest effort in learning new skills or adjusting their behaviour, they must first understand and accept why the change is happening and why it is happening now.
Assessing perceived need early in the project lifecycle allows change managers to design targeted interventions. If perceived need is high, the change management strategy can focus relatively more effort on knowledge and ability development. If perceived need is low, the strategy must invest heavily in awareness and desire-building before moving to training and skill development.
Assessing and Documenting Perceived Need
Perceived need should be assessed through qualitative and quantitative research with the impacted population. Methods include structured interviews with representative employees and managers; focus groups segmented by impacted group; pulse surveys measuring awareness and desire; and analysis of informal feedback channels such as change champion reports and team meeting minutes.
Example of a well-documented perceived need assessment:
'Stakeholder interviews with 30 representatives from the Finance and Procurement functions indicate a low-to-moderate perceived need for change. While 65% of respondents agree that the current system has significant limitations, only 40% believe a system replacement is the appropriate solution, and 55% are concerned about the disruption of a major system change currently. The change communications strategy will prioritise building the case for change at the individual level, with particular focus on demonstrating the specific pain points that the new system resolves.
Common Pitfalls and How to Avoid Them
Assuming that the business case, once communicated, will generate perceived need: Employees process information about change differently from executives. A rationale that is compelling at the board level may not resonate with frontline employees unless it is translated into personally relevant, concrete terms.
Assessing perceived need only once at the beginning of the project: Perceived need can fluctuate over time, particularly if the project encounters delays, scope changes, or negative communications. Monitor perceived need throughout the change journey.
Conflating passive awareness with genuine perceived need: Knowing that a change is happening is not the same as believing it is necessary. Assessment tools should distinguish between awareness and acceptance.
Ignoring low perceived need as a risk: When perceived need is low, adoption risk is high. This should be treated as a formal project risk, with specific mitigation activities included in the change management plan.
References
Hiatt, J. M. (2006). ADKAR: A Model for Change. Prosci. https://www.prosci.com/resources/articles/adkar-model
Prosci. (2023). Best Practices in Change Management. https://www.prosci.com/resources/articles/change-management-best-practices
Kotter, J. P. (1996). Leading Change. Harvard Business Review Press. https://hbr.org/books/kotter