Communicating when there is a major technology change
For those of you who are ASAE members, you may be aware that ASAE recently when through a major technology infrastructure change, which had a direct impact on the member experience online. For example, because of these changes, anyone with a previous login had to update their password (a common requirement when changing systems).
And of course, as with any significant technology changes, there have been bumps along the way. To ASAE's credit, they have a web page dedicated to reporting issues directly related to these system changes. (Click here to view that page.)
The page highlights where issues have been identified, as well as when issues have been corrected (or are still in process). It even has helpful color coding!
This is a really smart thing for ASAE to do. No system change goes perfectly, but being completely transparent with your members and customers about what is happening is the best way to communicate that you're paying attention and working on those issues!
Is this necessary for every project? No. But if you're doing something that has a significant impact on the member experience online, communicating those changes and communicating how you're addressing problems, as you go, is transparency at its best.
![]()
Wes's Wednesday Wisdom Archives
It is never done – so celebrate!
It is never done – so celebrate! A client of mine recently had their official […]
MDR (Minimum Data Required)
MDR (Minimum Data Required) I’ve written about minimum viable product (MVP) in software development in the […]
Simpler and Faster is Better
Simple and Faster is Better Earlier this week I was fortunate enough to attend a […]
Patience and grace
Patience and grace A past client of mine recently told me: “You inspire confidence and […]
Sometimes you just have to try it and see what happens
Sometimes you just have to try it and see what happens The single greatest key […]
Training and testing
Training and testing I’ve written before that the best form of training follows this process: […]
How to save a “failing” project
How to save a “failing” project It is not unusual for me to receive a […]
How to avoid the “IT black hole”
How to avoid the “IT black hole” Going all the way back to my days […]
The “People” are important!
The “People” are important! I’ve written a lot about people, process, and technology over the […]
Always look for the MVP
Always look for the MVP I first wrote about minimum viable product (MVP) just three […]
