A new tool may offer a clear improvement while still being difficult to adopt. People need to move information, learn a new starting point, and coordinate with others who may be using an earlier arrangement.
Observe the existing habit before proposing a replacement. Which parts are reliable, which are inconvenient, and which contain knowledge that is not written down? These details can explain resistance more accurately than a general claim that people dislike change.
Try a small transition with a path back. Preserve useful context and ask what became easier during ordinary work. An idea becomes practical when its benefit survives the effort of changing how the task begins.
- Observe the routine before changing it.
- Preserve knowledge held by the old process.
- Try a transition small enough to reverse.
An example to consider.
A new task application might fail because the existing handoff still happens in a conversation. Understanding that habit comes before designing another notification.
Put it in perspective.
Separate the possibility from the commitment. A small trial can answer a question while leaving room to change direction after you learn more.
Follow a related question
Distinguish local preferences from account data.
Where a cloud application livesWrite the assumptions beside the calculation.
An estimate with visible assumptionsKeep learning
Related background to continue exploring this subject.
Google: an introduction to language models NIST: AI risk management framework