It’s hard to get UNangry
I often emphasize to my clients the importance of testing and training. When a new system (or new functionality) is rolled out, you have to be sure things have been tested properly (so that it actually works) and you need to be sure staff is trained on how to use it.
The alternative is a system that is not working correctly, or staff does not know how to use, either of which will make staff users angry. And once they’re angry, it’s hard to make them UNangry.
In psychology, it’s called the anchoring effect. This is the “human tendency to rely too heavily on the first piece of information offered.” Or put another way, if I’m given a new system that doesn’t work right (or is too confusing to use), then I’ll always and forever believe “the system is broken.” And once they believe that, it’s exceedingly difficult to change their minds.
So if you’re launching a new system, or even new functionality within an existing system, make sure you’ve tested it thoroughly and make sure staff is well trained before you ask them to start using it. You’ll be glad you did.
![]()
Wes's Wednesday Wisdom Archives
Two tips for data conversion
Two Tips for Data Conversion I’ve written a lot about data conversion over the years […]
Who should “own” the database?
Who should “own” the database? One of the most common questions I get from my […]
What makes you weird?
What makes you weird? When I work with clients on selecting a new association management system, one […]
Why “AMS Consortiums” Don’t Work
Why “AMS Consortiums” Don’t Work About once a year I will get a call from […]
Your vendor will disappoint you
Your vendor will disappoint you I follow politics as a hobby. A past publisher from […]
Learn how to lose
Learn how to lose “Winning is great, sure, but if you are really going to […]
Ownership is Required
Ownership is required When asked for the most common reason AMS implementations fail, I typically respond […]
It’s all relative…
It’s all relative… Over the course of my 22 years of consulting, I’ve consulted with […]
Eliminate to optimize
Eliminate to optimize So much of data management is habit (both good and bad) which is […]
For data governance, ask “Why?”
For data governance, ask “Why?” Recently I’ve had the opportunity to work on several data […]
