Be aware of unintended consequences

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

Eventually automated emails get ignored

April 14, 2021

Eventually automated emails get ignored During the discovery and development phase of implementing a new …

Eventually automated emails get ignored Read More »

The challenge the AMS providers see

April 7, 2021

The challenge the AMS providers see Over the years I’ve asked AMS providers what they …

The challenge the AMS providers see Read More »

Be careful about “solutioning” too quickly

March 31, 2021

Be careful about “solutioning” too quickly One of the great things about software developers is …

Be careful about “solutioning” too quickly Read More »

What’s our next action?

March 24, 2021

What’s our next action? As you can imagine, I spend a lot of time in …

What’s our next action? Read More »

Don’t automate for the sake of automation

March 17, 2021

Don’t automate for the sake of automation I’m the laziest person in the world. I …

Don’t automate for the sake of automation Read More »

Don’t forget about what got better

March 10, 2021

Don’t forget about what got better Negativity bias is the tendency to focus on only …

Don’t forget about what got better Read More »

Give a little at a time rather than taking away

March 3, 2021

Give a little at a time rather than taking away I’m sure there’s research somewhere …

Give a little at a time rather than taking away Read More »

First, you gotta have the data

February 17, 2021

First, you gotta have the data When I work with clients on a new AMS …

First, you gotta have the data Read More »

Work on your relationship with your AMS vendor

February 10, 2021

Work on your relationship with your AMS vendor It is no coincidence that my most …

Work on your relationship with your AMS vendor Read More »

Dashboards for Data Integrity

February 3, 2021

Dashboards for Data Integrity I’ve written a bunch on data integrity reports. (Click here for …

Dashboards for Data Integrity Read More »

Scroll to Top