Be aware of unintended consequences
I've written before that every decision involves a trade-off. When considering the trade-offs that every decision requires, you should also keep in mind any unintended consequences that the decision may create. Consider the following example:
A client of mine recently changed AMSes. As part of that change, members have to log in to the website using a unique email address. (Previously members had used their last name and their member ID.) The challenge is that the association has thousands of member records without email addresses and as a result, a member without an email address cannot login to the website without contacting the association directly and speaking with a staff person (i.e., there is not automated way for the member to retrieve a username/password reset via email).
So the unintended consequence of this decision was that the staff now has to manage dozens of customer service calls to help members login for the first time, something they had not planned for.
Could this additional work been avoided via some other login method? Maybe. Or maybe not. But a discussion needed to happen, so that the association could make a fully-informed decision and understand the ramifications (i.e., the trade-offs and the potential unintended consequences) of their decisions.
So as you make any decision, ask yourself: "Could this decision create any unintended consequences?"
![]()
Wes's Wednesday Wisdom Archives
Perfection is expensive (in fact, it’s not possible!)
Perfection is expensive (in fact, it’s not possible!) “Perfection is expensive. The last 5 percent […]
AI is a journey, not a destination
AI is a journey, not a destination Lately I’ve noticed a lot of associations talking […]
Action produces information
Action produces information “Action produces information. If you’re unsure of what to do, just do […]
Why a single source of truth is so beneficial…
Why a single source of truth is so beneficial… The holy grail of data management is […]
Just because you can, doesn’t mean you should
Just because you can, doesn’t mean you should I’ve worked in and with associations for well […]
Data doesn’t need to be perfect to be useful
Data doesn’t need to be perfect to be useful “Your data doesn’t have to be […]
Don’t just clean data, clean reports and queries
Don’t just clean data, clean reports and queries One of the reasons I exhort my […]
Don’t forget, your staff have day jobs…
Don’t forget, your staff have day jobs… The vast majority of my work is finite […]
Beware the automated “How did we do?” trap!
Beware the automated “How did we do?” trap! One of the downsides of technology is […]
Hindsight is 20/20
Hindsight is 20/20 I’m currently working with a client that is moving from their legacy […]
