The tricky bit is that it's not just that the employees have been using their particular Day-Timers for years. It's that some of them, including some who are well-respected by their peers, have also been producing and selling accessories specific to that brand. A few on a large and profitable scale, many on a smaller and less-profitable scale. And the upcoming change threatens their economic ecosystem.
In that sort of situation, I wouldn't be surprised to see an unusual amount of effort being put into resistance to the change, and a high level of evangelism inherent in that resistance.
Have you run across this sort of situation in your professional experience? How did it work out?
Sort of, but not exactly. My field is called "software methodology" (literally, "the methods used to create software"). In some companies there are people who are responsible for defining the company's methods. Sometimes these people are called "architects" and sometimes they're part of a "project management office" (PMO). Although the software teams are the ones doing the work, the architects (or PMO) are "selling accessories"--they're taking established methods and customizing them to the company's needs. They do tend to resist a lot more.
Sometimes these folks are well respected, and sometimes they aren't. Regardless, I have to figure out who is well-respected, particularly the ones who also dislike the new system. People who are well-respected have disproportionate influence. If they accept the change (particularly if they really hated it to begin with), then it's easier for others to accept it, too.
Once I find these folks, I spend extra time helping them find that "transforming idea" in order for the larger change to be successful. So I talk with them and, without asking, try to get a sense of what they really care about. I don't look for details of how software is developed (analogy: HP & healing surges), but what they're truly passionate about. This often turns out to be rigor, reliability, quality, predictability, user satisfaction, sane work hours, career advancement, or something else (analogy: a realistic-seeming world).
Once I have this sense of understanding, I help those people discover how they can preserve those passions in the new system. I'll talk about how the system cares about rigor, or provides predictability, or can be adjusted on the fly to take advantage of user feedback. I'm not pushy about it, though, and I don't try to convince or persuade so much as to put myself in his (or her) shoes and show that I can see things from his perspective and that I value the same things he does. Then I use "did you know" to help him see that things aren't necessarily as bad as his preconceptions say. (Analogy: "suspension of disbelief is important to me too; I want the things that are happening to have some internal logic. It's hard for me to imagine what's happening otherwise. (pause) The way I deal with that in my game is to describe HP loss as 'getting winded' and taking shallow cuts. That way healing surges are cinematic surges of adrenaline rather than actual healing, except when magic is involved. What do you think of that approach?" ...If that quote sounds a bit forced, it is; it's easier in real conversation.)
This isn't as manipulative as it might sound. It's actually understanding his perspective and trying to show new possibilities. For this to work, I have to truly care about his success, and just show options rather than forcing. People can tell when you're being manipulative. It doesn't work if you are.
Anyway, these conversations don't really result in a "transforming idea," but they plant a seed. Usually that seed is enough to get people past the initial resistance and try the new system for a decent amount of time. At first it's chaos and disaster, but people work through it and eventually find that transforming idea that lets them make the new system work for them.
Umm... so, yeah.


Last edited: