Embedding and Reinforcement
The phase everyone under-resources. The programme ends at go-live; the behaviour dies at week eight.
The blunt principle:
A behaviour lasts exactly as long as something in the system keeps asking for it. Motivation fades. Structure doesn’t.
So the job is to move the change out of the programme and into the organisation’s machinery.
The embedding checklist
Work through these in order of durability — the ones at the top survive without anyone’s attention.
🔒 Structural (most durable)
- The old route is switched off. Not deprecated. Off. With a date that passed.
- The new way is the system default, and the alternative requires an exception
- Required fields / gates make the behaviour necessary to complete the task
- Reporting only accepts the new format — no parallel spreadsheet accepted anywhere
- The behaviour is required by a control that someone audits
📋 Process
- It’s a standing item on the team meeting agenda
- It’s in the SOP / work instruction, and the SOP is the one people actually use
- It’s in onboarding — new joiners never learn the old way exists ⭐
- It’s in the checklist for the task
- There’s a named owner in the line, not in the programme
👤 People
- It’s in objectives for the roles that do it
- It’s in the management one-to-one template
- Managers are held to their own version of the behaviour
- Recognition for it happens in the normal rhythm, not as a programme event
- Someone senior asks about it regularly, in a standing forum
📊 Measurement
- The behaviour metric is in a BAU dashboard, not a programme report
- It has an owner who’d notice if it moved
- The counter-measures are still watched
- There is a defined trigger for re-intervention if it drops below
___%
The onboarding point deserves emphasis
New joiners are the cheapest and most permanent adoption you will ever get. They have no old habit to unlearn, no loss to grieve, and no memory of the previous way. Every month the new behaviour is not in onboarding is a month of people being taught the old way by well-meaning colleagues.
Check this personally. Induction material is famously out of date, and nobody owns it.
Reinforcement that works
| Works | Doesn’t |
|---|---|
| Same-day, specific, from their own manager | Quarterly awards |
| Small, frequent, certain | Large, rare, probable |
| Public recognition of the first person to do it well | Generic “great work team” |
| The system returning something useful within 24 hours | Benefits realised next financial year |
| Being asked about it by someone senior, routinely | A one-off leadership visit |
| Naming who caused a change | Anonymous “feedback has been noted” |
The mechanism: immediate, certain and small reliably beats delayed, uncertain and large for habit formation. This is exactly backwards from how most corporate recognition is designed.
Handover to the line
The moment the programme stands down is the moment of maximum risk. Do it deliberately:
Handover
Behaviour(s) handed over: _______________
Named owner in the line: _______________ (a person, with a job title)
What they’ve agreed to do: _______________
Metric they own: _______________
Where it’s reviewed, and how often: _______________
Trigger for escalation: if it falls below ___
Date of handover: _______________
30/60/90 checks in the diary: ☐ ☐ ☐
⚠️ “The line will pick it up” is not a handover. Name the person, get their agreement, put it in their objectives, and give them the metric. Anything less and the behaviour is orphaned the day you leave.
The week-8 re-intervention
Plan it now, while you still have resource.
Around weeks 6–10 the novelty is gone, supervision has stopped, and the true baseline emerges. Almost every programme has moved on by then — which is exactly why a small deliberate intervention at that point has outsized effect:
- Publish the trend and the best-performing team
- One visible sponsor act
- Fix the top three things champions have raised
- A short manager prompt: “ask about it in this week’s one-to-ones”
Half a day of effort, at the moment of maximum leverage.
→ Habit Loop and Behavioural Drift · Drift Check — 30 60 90 · Change Retrospective
← Back to the Behavioural Change Toolkit