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
Honoring an industry legend
Honoring an industry legend I’m taking a break from my usual data management tips to […]
Never burn a bridge
Never burn a bridge My children have reached the age where they have, or are, […]
You CAN compete with the big guys…
You CAN compete with the big guys… In my experience, associations often undersell their actual […]
Join (or start) your users group!
Join (or start) your users group! Today’s message is simple: If the AMS you’re using […]
They don’t care, until they care.
They don’t care, until they care. One of the more common questions I get from […]
Longfellow and data management
Longfellow and data management “We judge ourselves by what we feel capable of doing while […]
Do you really need all that historical data?
Do you really need all that historical data? A question I’ll often get from my […]
AI actually requires thinking
AI actually requires thinking “I don’t think AI introduces a new kind of thinking. It […]
It’s not the mistakes, but how you respond
It’s not the mistakes, but how you respond Recently a client was complaining about a bug that […]
The hidden costs of bad data
The hidden costs of bad data Nobody likes bad data, and presumably we’re all working […]