Making the Intentional Journey From Policy to Practice to Culture

Credit: Jason Leung

Most organisations have policies. Far fewer have made them work.

Not because the policies were badly written, but because writing policy is only the beginning of a much longer process. The document on the intranet is not the destination. It is a starting point — the organisation's first attempt to make its expectations legible. Whether those expectations translate into consistent behaviour, and whether that behaviour eventually becomes the unremarkable, self-sustaining way things are done here, depends on a series of deliberate choices that most organisations under-invest in, or skip altogether.

This piece is about those choices. About what good policy actually looks like, how it becomes practice, and how practice (when conditions are right) eventually becomes culture.

Where Policy Came From

Policy didn't emerge from a desire to create bureaucracy, although we've all experienced organisations that certainly feel that way. It emerged from a specific problem: scale.

In small organisations, expectations travel by proximity. The founder is in the room. Standards are set through direct observation, conversation, and imitation, and feedback loops are tight enough to enable quick course correction. As organisations grow, direct management becomes impossible. Policy steps into this gap as a mechanism for transmitting intent without requiring the person who holds that intent to be physically present.

It also carries compliance obligations. Regulatory requirements, legal risk, governance frameworks — these hardened what might otherwise have remained informal norms into documented commitments.

Both of these are legitimate reasons for policy to exist. But they are also, on their own, insufficient design briefs. A policy written primarily to satisfy a regulator or protect the organisation in a dispute will reflect exactly that purpose — in its structure, its language, and what it chooses to emphasise. A policy written to help an employee understand how to act well in a complicated situation will reflect that purpose instead. These are not the same document, and they do not produce the same outcomes. The choice between them, or how an organisation holds both aims simultaneously, is a strategic one that most policy frameworks never consciously make.

Policy as a Design Choice

Every policy embeds assumptions about what the organisation values, who its people are, and what kind of judgement they are trusted to exercise. These assumptions show up not just in content but in form: in how prescriptive or principle-based the language is, in whether the document addresses the reader as a thinking adult or a compliance risk to be managed, in whether intent is explained or simply mandated.

This is why policy is never culturally neutral. It either reflects and reinforces the organisation's strategic priorities and values, or it contradicts them. An organisation that says it values autonomy and trust but writes policies that are exhaustively prescriptive and assume bad faith, is not just producing bad policy. It is producing a cultural signal, consistently and at scale, every time an employee encounters those documents.

At its best, policy is an act of intention. It gives people a framework for navigating their roles with confidence, makes expectations explicit rather than leaving them to be inferred from whoever happens to be in charge locally, and connects day-to-day behaviour to the values and priorities the organisation has said matter. It is scaffolding and not a cage, a structure within which judgement can be exercised rather than replaced.

At its worst, it substitutes for judgement and people learn to cite rather than think. The policy says becomes a way to discharge accountability without actually taking it. But the failure here is not really about compliance culture versus something better. It is about policies that were never designed to cultivate judgement in the first place, treating the reader as someone to be controlled rather than someone to be equipped.

Why Policy Goes Wrong

When policy fails to translate into behaviour, the causes usually follow recognisable patterns.

The most damaging is misalignment: when what the policy says doesn't reflect what the organisation actually values, or contradicts what leadership demonstrably does. Employees notice this quickly. The lesson they draw is not that the policy is wrong, it's that the policy is not real. Once that inference is made, the entire policy landscape’s credibility becomes questionable.

Related is the problem of language and framing. Policies written in dense, legalistic prose signal that their primary audience is not the employee reading them. The form contradicts the function. If the organisation's stated priority is a culture of informed, confident decision-making, a policy framework that requires a legal degree to navigate works actively against that priority. The medium is part of the message.

Then there's the design problem. Policy is typically created by functional subject matter experts who know their domain but may have limited visibility into how their requirements intersect with those of other parts of the organisation. The result is a policy landscape full of internal contradictions and uncovered ground, where employees are expected to navigate trade-offs that the framework itself never resolved. This too is a cultural signal, implying the organisation's systems are designed for it’s own convenience, rather than the employee's, when in fact these things should be mutually reinforcing.

Each of these failures produces the same outcome: a gap between the written expectation and the lived reality. It is in that gap, rather than through deliberate acts of defiance, that unintended culture forms — quietly, incrementally, and often invisibly until it's too late to course-correct without significant effort.

What Good Policy Actually Looks Like

Good policy is not long. It is not exhaustive and it does not try to anticipate every possible scenario. It is clear about what matters and why, with the why doing as much work as the what. When people understand the reasoning behind an expectation, they can apply it intelligently to situations the policy author didn't foresee. When they don't, they can only apply it mechanically to the situations explicitly addressed, and default to their own experience and risk appetite for the gaps.

Good policy is easy to find when you actually need it and easy to understand once found. It tells people where to go if they're unsure, points to supporting documents, and acknowledges that the person reading it is operating in real conditions: under time pressure, with incomplete information, and likely in circumstances the author didn't anticipate.

Most importantly, a well-designed policy suite should be coherent as a system. An employee moving across policies should encounter a consistent picture of the organisation's priorities and values, not a patchwork of conflicting obligations. That coherence acts as a reinforcement mechanism and is the foundation on which practice, and eventually culture, can be built. It becomes possible to internalise not just the individual rules but the underlying logic.

From Document to Practice

This is where most organisations lose the thread; publication is not implementation. A policy that exists but isn't known, understood, or applied is functionally inert and creates the illusion of a standard that is operating.

Translating policy into practice starts with raising awareness and removing barriers to adoption, including consideration of existing cognitive loads at work. Role modelling by leaders, managers, and experienced practitioners demonstrate what the policy looks like in action and creates feedback loops that it’s safe to adopt. Present leaders are able to explain the intent, answer questions, and connect the policy to the decisions and situations their teams actually face.

This is why policy roll-out is not a communications exercise and feedback loops matter enormously.

Noticing and Responding to Drift

People don't typically decide to ignore policy. They make small adjustments and those adjustments accumulate: a workaround becomes a habit, a habit becomes a norm. And then no one quite remembers that it once worked differently.

Catching this requires governance and assurance systems designed to detect it. Not surveillance, but systems that can identify deviations from expected practice, both isolated incidents and the cumulative patterns that indicate a broader shift. Where is the policy working as intended? Where is it creating friction that wasn't anticipated? Where is it producing outcomes that don't reflect the intent behind it? These signals need to reach the right people with enough time to course-correct before the deviation becomes the new baseline. Unwinding embedded habits is considerably harder than nudging practice back on track early.

When drift is detected, the response needs to be diagnostic before it is corrective. Is the gap a training issue? A process failure? A policy that doesn't actually work in the situations people face? Sometimes the practice is the problem. Sometimes the policy is. Getting that distinction right determines whether the intervention resolves the issue, or simply creates a different version of it, and sends a signal about whether the organisation is interested in understanding its systems or just enforcing them.

How Practice Becomes Culture

Organisational culture is a living system, and as such, it never stops interacting and evolving. This accumulates through the lived experience of what the organisation is actually like to work in: what gets recognised and what gets ignored, how leadership behaves under pressure, whether the way things are supposed to work and the way things actually work are close enough together that people stop experiencing the gap between them. Well-designed policy contributes to this, but it is not sufficient on its own. So while you can’t control it, you can create the conditions that reinforce the interactions you want and reduce the likelihood of cognitive dissonance that leads to unintended decisions and/or actions.

The organisations that succeed in this journey are not necessarily the ones with the most sophisticated policies. They are the ones where policy language, leadership behaviour, organisational systems, and day-to-day practice are aligned closely enough around shared priorities that the culture they intended is recognisably the culture that forms.