Most organizations treat friction is information as a communication task. It is usually an operating design task.
Resistance is often a signal, not a flaw in attitude. Treat friction as data so you can redesign workflow instead of blaming people.
The mistake I see most is treating this like a communication campaign. Teams announce, explain, and remind, then wonder why the old behavior survives. People are not ignoring the strategy. They are following the incentives and defaults in front of them.
A model you can use
- Put the step in the tool people already use.
- Reduce choices at decision points.
- Document decisions where everyone can find them.
- Teach the pattern through live examples, not theory.
These steps are not flashy. They work because they convert intent into repeatable behavior.
Example from the field
A knowledge management lead watched adoption stall despite strong training attendance. They shifted to apprenticeship-style reviews on live matters and published examples of good output each week. Confidence improved because people could see what good looked like.
Notice what changed: not motivation, not headcount, not a major reorg. The team changed ownership, defaults, and feedback loops. That is where operational leverage lives.
Practical takeaway
Start smaller than you think. One clear owner, one clear standard, one visible follow-up is usually enough to move a stuck system.
Where this breaks
The pattern usually breaks when teams skip reinforcement after launch. A good rule is to review one real output every week and ask what made it easy or hard to produce. Then update the checklist, template, or ownership map based on that evidence. This keeps the system grounded in real work instead of drifting into policy theater.
How to keep it alive
Treat this as a maintenance habit, not a one-time initiative. Put one owner on the process, schedule a monthly review, and retire steps that no longer help. Teams trust systems that stay current. They ignore systems that look frozen while work keeps changing.