Writing a Process Policy That Guides Behaviour

A process policy guides behaviour when it concisely establishes the process's purpose, scope, principles, authority, roles, controls and basis for measurement, rather than prescribing detailed procedure. A process becomes useful when people adopt it, leaders govern it and evidence drives improvement; documentation supports that but cannot substitute for ownership or behaviour.

• State purpose and scope clearly, testing them against representative cases including material exceptions.
• Define mandatory principles and avoid vague statements. In the article's example, a change policy defines when emergency authority applies without prescribing every screen or field practitioners use.
• Name accountable roles and set review and exception rules, then obtain governance approval before publishing.
• Use policy awareness as the starting signal, but compare it with compliance and approved exceptions before deciding whether the policy works. Agree a baseline, data source and owner for each measure.
• Avoid three pitfalls: writing a procedure instead of a policy, using vague statements, and publishing without governance approval. Use them as challenge questions in design and review sessions, and act on evidence of risk with an owner and a proportionate action.