Values to Behaviours Translation: Why It Is Harder Than It Looks and Why It Matters

Most values work stops at articulation. The organisation convenes a workshop, or a senior leadership team, or in some cases a broader consultative process involving a cross-section of the organisation, and it arrives at a set of words. Integrity. Courage. Customer obsession. Collaboration. The words are genuine; they reflect something the organisation actually believes about itself or wants to believe about itself. They are presented at the all-hands. They appear on the website. They are inscribed on the lobby wall. And they remain, in the majority of cases, precisely where they are: as words, describing aspiration, with limited operational existence in the day-to-day experience of the people who are supposed to be living them.

The failure is not in the values themselves, and it is rarely in the intent behind the values exercise. The failure is in the gap between values articulation and values translation, the step of converting an aspirational word or phrase into a set of specific, observable, context-relevant behaviours that people can perform, assess, develop, and hold to account. THIS TRANSLATION STEP IS HARDER THAN IT LOOKS, and it is almost universally underinvested in relative to the resources that go into the values articulation process itself. The result is a values architecture that describes what the organisation aspires to be without creating the conditions under which people can actually behave that way.

I want to be precise about the nature of the difficulty, because “values to behaviours translation is hard” is not, by itself, useful. The difficulty operates at three levels, each of which has a different structural character and requires a different design response. The first level is conceptual: the translation from a value to a behaviour requires the organisation to make specific and sometimes uncomfortable choices about what the value actually means in this context, which means deciding what it does not mean as well as what it does. The second level is contextual: behaviours that embody “integrity” in a customer-facing service role look meaningfully different from behaviours that embody “integrity” in a financial control function or a product development team. Universal behavioural anchors are a compromise that frequently serves no context particularly well. The third level is accountability: behaviours only become real when they are observed, discussed, assessed, and held to account through the recurring processes of the organisation. Values translation without accountability architecture produces a slightly more specific aspiration, not a behavioural reality.

The first challenge in values translation is getting the organisation to be specific and honest about what a value actually means in its context. This is more difficult than it appears, because the process of values articulation typically moves toward words that are broadly agreeable rather than toward words that are precisely defined, and broad agreement and precise definition are in tension with each other. “Integrity” is agreeable to almost everyone in an organisation because almost everyone believes they have it and believes it is important. The moment you ask what integrity specifically means here, what it looks like on a Tuesday morning in a pressured business context, you move from broad agreement to specific commitment, and some of what emerges is more contested than the original word suggested.

I have facilitated values translation workshops where the process of getting specific about what a value means revealed significant disagreements that the values articulation process had papered over. Not dishonest disagreements; the leaders in the room genuinely believed in the value. But disagreements about what it meant in practice, about which of the behaviours it implied were actually expected and which were aspirational, about whether the organisation’s current systems and leadership behaviours were consistent with the value or in tension with it. SURFACING THESE DISAGREEMENTS IS NOT A FAILURE of the values process. It is precisely what the values process should do, because a value that means different things to different leaders in the same organisation is not an operational value; it is a word that provides the cover of shared aspiration without the substance of shared commitment.

The discipline of values translation requires the organisation to do the specific definitional work that the values articulation process typically avoids. For each value, the translation process should produce: a clear statement of what the value means in the specific context of this organisation and its strategic priorities; a clear statement of what the value does not mean, which boundary-drawing is often more useful than the positive definition; and a set of two or three specific behaviours that directly embody the value in the contexts where it is most relevant, expressed in the language that the organisation’s leaders and managers actually use rather than in the elevated register of organisational aspiration.

The second level of difficulty in values translation is contextual, and it is one that HR professionals who design values programmes frequently underestimate. Behaviours that embody a given value look meaningfully different across functions, levels, and business contexts, and a behavioural anchor designed to be universally applicable is almost always a behavioural anchor that is insufficiently specific to be useful in any particular context.

Consider “collaboration” as an example. In a product development team, collaboration might be embodied most specifically by the behaviour of sharing work-in-progress early enough for feedback to change the outcome, and by actively seeking input from engineering before design is finalised. In a client-facing sales team, collaboration might be most specifically embodied by the behaviour of proactively connecting the client to internal expertise that was not part of the original brief, at the cost of some deal velocity. In a senior leadership team, collaboration might be most specifically embodied by the behaviour of raising a concern about another function’s decision in the room where the decision-maker is present, rather than allowing the concern to circulate informally outside the room. These are the same value; they are substantively different behaviours. A UNIVERSAL ANCHOR THAT ATTEMPTS TO DESCRIBE ALL THREE will describe none of them with the specificity that makes them discussable in a performance conversation or observable in a daily working context.

The design implication is that values translation requires a contextualisation step that most values programmes do not include. After the universal behavioural anchors have been established, the organisation needs to invest in a function-level and level-specific translation process, working with the leaders and managers in specific contexts to identify the two or three behaviours that most specifically embody each value in their working reality. This process takes more time and more design resource than producing a single universal behavioural anchor for each value. It also produces a values architecture that people in specific contexts can actually use, which is the only outcome that matters.

The third and most operationally consequential level of the values translation challenge is accountability. Even when the organisation has done the conceptual work well, has produced specific and contextually relevant behavioural anchors, and has communicated them clearly and credibly through leadership modelling, those behaviours will not become the actual operating norms of the organisation unless they are embedded in the accountability systems through which the organisation manages performance and makes decisions about people.

What does embedding values in accountability systems actually require? It requires that the values-behaviours connection appears explicitly in the performance conversation structure: not as a separate values assessment section at the end of the performance review, but as an integrated dimension of how performance is assessed throughout the year. It requires that the behaviours are observed and discussed in ongoing developmental conversations rather than only at annual review moments. It requires that they appear in promotion and succession decisions as explicit criteria, not merely as implicit considerations. AND IT REQUIRES THAT LEADERSHIP BEHAVIOUR THAT IS INCONSISTENT WITH THE VALUES IS NAMED AND ADDRESSED, even when the leader in question is performing strongly on business metrics.

The last point is the most difficult and the most important. In my experience facilitating values work, the single most reliable predictor of whether a values architecture will be operational or aspirational is whether the organisation is willing to hold high-performing leaders to account for values-inconsistent behaviour. Every organisation has examples of leaders whose business results are strong but whose behaviour is visibly inconsistent with the stated values. How the organisation responds to those examples is the most powerful culture message it sends. The response that says “this is our values standard and it applies to everyone” creates conditions in which the values become real. The response that implicitly or explicitly prioritises business results over values consistency teaches the organisation, with complete clarity, that the values are aspirational rather than operational.

An effective values-to-behaviours translation process has four stages, each of which builds on the previous and each of which requires a different kind of design investment. The first stage is the definitional work: for each value, establishing what it means in this organisation’s specific context, and being explicit about the boundaries. The second stage is the contextualisation work: working with specific functions and leadership levels to identify the behaviours that most specifically embody each value in their working reality. The third stage is the integration work: embedding the values-behaviours connection into the performance conversation structure, the promotion and succession criteria, and the leadership development programme content. The fourth stage is the accountability architecture: establishing the observation and feedback mechanisms that enable values-consistent behaviour to be recognised and valued, and values-inconsistent behaviour to be named and addressed.

THE MOST IMPORTANT DECISION in the entire process is the choice of what to cut. Organisations that try to translate five values, each with four behavioural anchors at three proficiency levels, produce a values architecture that is too complex to be operational. The design discipline is to identify the two or three behaviours per value that are most critical in the specific context of this organisation’s current strategic priorities, to express them with the specificity and the language that people in the organisation will recognise as their own, and to protect the resulting framework from the inevitable pressure to add more, to be more comprehensive, to make sure nothing important is left out. Completeness is the enemy of operationality in values work, as it is in competency frameworks.

Finally, the most visible and most powerful mechanism of values translation is leadership modelling. The most carefully designed behavioural anchors and the most rigorously built accountability architecture are secondary to the daily experience that people have of watching their leaders. When leaders make values-consistent choices in difficult moments, when they choose the right action over the expedient one, when they hold to account a peer who is performing well but behaving poorly, they translate the values more effectively than any workshop or communication campaign. THIS IS THE WORK THAT CANNOT BE OUTSOURCED to HR, and it is the work that the translation process ultimately must engage senior leaders in, not just as endorsers of the framework but as active practitioners of the behaviours it describes.