← Back to Playbooks

Playbook 5 — Reinforcement

Why adoption regresses within 90 days without a deliberate hold

Old habits are the default gravity. Reinforcement is the only phase that fights it, and it is the phase almost every rollout skips.

The pattern is predictable enough to plan around. Weeks one to four, novelty and attention carry usage. Weeks five to twelve, the tool meets a busy period, a bad output, a deadline that makes the old way faster for a day. The old way still works; that is the problem. Nothing forces the switch to stick, so it quietly un-switches.

ADKAR ends on reinforcement because without it the sequence does not hold. In practice, reinforcement is not a motivational exercise. It is a set of small structural things that make the new way marginally easier to keep than to abandon.

Make the tool the default path, not an alternative. If the workflow still starts in the old system and the AI step is optional, most people will skip the optional step under pressure. Where the template, the first draft, or the first-pass reply lives inside the tool, the habit has something to attach to.

Keep the wins visible. Not celebration — evidence. A short, recurring note of what the tool actually did this month, with a real number attached, does more than any launch banner. It answers the silent question of whether this is still worth the effort.

Watch the reversion, not the logins. A team can log in daily and still be doing the work the old way alongside it. The signal that matters is whether anyone, under time pressure, went back to the manual route. Those moments are the real data, and they are easy to miss because they look like normal work.

Then check, on a schedule:

The reason reinforcement gets skipped is that it produces no visible milestone. There is no demo, no launch, no approval. It is just the difference between a change that lasted and a change that looked like it did.

Next: Playbook 6 gives you the four numbers that tell you it worked.