A project's alignment with the espoused values of an organization is a significant predictor of its acceptance among employees and its long-term sustainability. In change management practice, explicitly articulating how a change initiative reflects and reinforces organizational values is a strategic communication and engagement tool that builds legitimacy and reduces resistance.
Definition and Distinction
Organizational values are the stated principles and beliefs that an organization publicly endorses as guides to its behavior, decision-making, and culture (Schein, 2010). Common examples include values such as integrity, innovation, customer-centricity, collaboration, and sustainability. Values alignment, in the change management context, refers to the degree to which a project's purpose, methods, and outcomes are consistent with—and can be credibly shown to embody—these stated principles.
This concept is distinct from strategic alignment (the relationship between the project and the organization's strategic objectives) and cultural fit (the compatibility of the change with the organization's actual, lived culture, as opposed to its espoused values). Practitioners should recognize that espoused values and enacted values do not always coincide, and that change plans must address both.
Why Values Alignment Matters
Employees who perceive a change as inconsistent with their organization's values are significantly more likely to resist it. Conversely, when a change can be authentically framed as an expression of shared values, it generates a sense of shared purpose and moral legitimacy that supports adoption (Kotter & Cohen, 2002). Leaders and change sponsors who communicate values alignment persuasively reduce the psychological cost of change for affected individuals.
For change managers, documenting values alignment also provides a narrative framework for all communications. When stakeholders ask 'why are we doing this?', the values alignment statement offers an answer grounded in the organization's own declared identity.
Assessing and Documenting Values Alignment
To assess values alignment, change managers should: obtain the organization's current set of stated values (typically from the corporate website, annual report, or internal culture framework); review each project objective against each value to identify connections; and consult with the project sponsor to confirm that the identified connections are authentic and endorsed.
Avoid constructing artificial connections. If a project does not genuinely align with a particular value, do not claim it does. Stakeholders, particularly those who are sceptical of change, will identify such inconsistencies and use them to undermine the change narrative.
Example of a well-written values alignment statement: This project aligns with our Integrity value by replacing manual, error-prone processes with an auditable digital workflow, ensuring accurate financial reporting. It supports our Innovation value by introducing automation that frees our teams to focus on higher-value analytical work.'
Common Pitfalls and How to Avoid Them
Claiming alignment with all values indiscriminately: Asserting that a project aligns with every organizational value is rarely credible and suggests superficial analysis. Focus on two to four values that have genuine, demonstrable connections to the project.
Focusing on espoused values rather than enacted culture: If the organization's actual culture does not reflect its stated values, aligning the change to espoused values without acknowledging cultural realities may ring hollow. Supplement values alignment with a cultural readiness assessment.
Using values as marketing language rather than substantive analysis: Statements such as 'this project aligns with our people-first value because it's good for employees' are not substantive. Articulate specifically how the project embodies the value in its design, implementation, or outcomes.
Neglecting to update the values alignment narrative during project delivery: If the project scope or approach changes, the values alignment rationale may need to be revised. Keep this field current throughout the project lifecycle.
References
Kotter, J. P., & Cohen, D. S. (2002). The Heart of Change. Harvard Business Review Press. https://hbr.org/books/kotter
Schein, E. H. (2010). Organizational Culture and Leadership (4th ed.). Jossey-Bass. https://www.wiley.com/en-us/Organizational+Culture+and+Leadership
Cameron, K. S., & Quinn, R. E. (2011). Diagnosing and Changing Organizational Culture. Jossey-Bass. https://www.wiley.com/en-us/Diagnosing+and+Changing+Organizational+Culture