Policy implementation and change management
Writing the policy is only part of the process.
We bridge the gap between a policy being published and a policy being used, through implementation planning, communication, training and reinforcement that address both the structural and the human side of change.
The problem
The harder half is getting people to understand it, believe it, and change how they operate because of it.
Implementation fails when it is treated as an afterthought: the policy is signed, an email goes out, and everyone returns to doing the work the way they did it last month. Six months later the office is running two processes at once, the old one informally and the new one on paper, and nobody can say which governs.
We treat implementation as the mission rather than the last slide.
The work itself.
Stakeholder readiness assessment
Who is affected, what it changes for them, where resistance will come from, and what has to be true before rollout is realistic.
Implementation planning
Sequencing, ownership and milestones, built so the change lands in an order that makes sense to the people absorbing it.
Communication and engagement
The plan for how the change is explained, to whom, and by whom. Delivered, not just recommended.
Training and reinforcement
The sessions that introduce the change and the follow-through that keeps it in place after attention moves on.
What is changing right now
A class deviation is not the finish line.
Adopting FAR Council model text through a class deviation changes what the rules say. It does not change what your workforce does, which templates they reach for, or which steps they still perform out of habit.
The FAR Council itself frames the period between deviation adoption and formal rulemaking as a testing period, with feedback expected. That only works if the change is genuinely operating on the ground, which is an implementation problem rather than a drafting one.
That is what the work on this page is for: closing the distance between a rule that has changed and a workforce that has actually changed with it.
What working together looks like.
Assess readiness
We establish what the change actually asks of each group, and what is standing in the way. Often the honest answer is that the policy needs adjusting before the rollout does.
Plan and communicate
Sequencing, communications and the conversations that have to happen before go-live. We run these rather than writing a plan for someone else to run.
Reinforce and hand over
Follow-up after the attention has moved on, which is where most implementations quietly fail, then a handover your team can sustain.
organizations launching new policies, undergoing regulatory changes, or managing transitions that require sustained behavioral and operational shifts across teams.
What usually comes with it.
Policy & Process Development
The policy, procedures and templates being implemented. Frequently the same engagement.
Read more →Training & Organizational Development
Sustained behavioral change needs capability, not just communication.
Read more →Need a change that actually holds?
Tell us what you are dealing with and we will tell you how we would approach it.
Start a conversation ↗