Be careful about getting tangled
“We had done a lot to tangle ourselves up.” - Bridget Walsh, Chief Operating Officer at Emergency Nurses Association
In a discussion at AMS Fest this week, this is how Bridget Walsh characterized what their AMS of 17+ years looked like as they worked to move from their legacy system to a new one.
I love this quote for two reasons:
- The use of the word "tangle." It's very descriptive of what many AMSes look like after years of use.
- The ownership of the entanglement ("We had done a lot..."). Data management systems don't just tangle themselves. They become tangled for many reasons including neglect, staff turnover, outdated/ineffective business rules, and lack of documentation.
Seventeen years in one system is a very good run, so ENA should be proud of that. But I appreciated Bridget's acknowledgment of ENA's need to "untangle" where they were as they moved to a new system.
So what are you doing to make sure your AMS doesn't get too tangled up?
Wes's Wednesday Wisdom Archives
When’s the “least bad” time?
When’s the “least bad” time? When working with clients on a new project, especially a […]
A poor launch can set the stage for YEARS
A poor launch can set the stage for YEARS It is not uncommon for me […]
Have the courage of your convictions
Have the courage of your convictions Having the courage of your convictions means you’re willing […]
Even your online directory is out of date!
Even your online directory is out of date! Back in the day of printed directories, […]
Start small
Start small When I work with my clients on projects that involve measuring member engagement, […]
Some context, please
Some context, please A pet peeve of mine: A report about associations (e.g., marketing benchmarks report) where […]
Eventually automated emails get ignored
Eventually automated emails get ignored During the discovery and development phase of implementing a new […]
The challenge the AMS providers see
The challenge the AMS providers see Over the years I’ve asked AMS providers what they […]
Be careful about “solutioning” too quickly
Be careful about “solutioning” too quickly One of the great things about software developers is […]
What’s our next action?
What’s our next action? As you can imagine, I spend a lot of time in […]