The implementation gap opens up in four predictable places.
The first is manager capability. A policy may say that staff can raise concerns informally with their line manager. But line managers are rarely trained to receive concerns well. They often don’t know what to do with what they hear. They minimise, they deflect, they escalate prematurely, or they promise action they’re not empowered to take. A policy that depends on managers being good at something they’ve never been trained in is not an implementable policy.
The second is process visibility. A concern is raised, a process is triggered, and then the whole thing disappears behind a wall of confidentiality. The person who raised the concern has no idea what’s happening. The rest of the team has no idea either. Months later, nothing visible has changed, and the organisation has quietly taught everyone that raising concerns leads nowhere.
The third is decision consistency. A policy may say that certain behaviours have consequences, but in practice the consequences are applied unevenly. A junior staff member gets performance-managed out for the same behaviour that a senior person is informally coached about. A well-networked person gets a quiet warning. Someone without internal allies gets a formal letter. Staff see this. It teaches them something about the gap between stated policy and actual governance.
The fourth is follow-through. A training programme is delivered, an action plan is written, a set of commitments is made. Six months later, there is no one tracking whether the commitments were kept. The accountability lives in a document, not in a person’s job description, not in a KPI, not in a review conversation. Policies without follow-through quietly become performative.