There's always gonna be something
I've been consulting for 26 years now and I'm still sometimes surprised to learn that no matter how much due diligence you do, you'll still miss things.
Case in point: Working with a client recently on a system conversion, we discovered that the new system placed Puerto Rico, Guam, and the US Virgin Islands in a territories field rather than in the US State field. (This is how google's API manages this data.)
This was a problem for the association because their members in Puerto Rico, Guam, and the US Virgin Islands have made it very clear that they want to be listed in the state field, not somewhere else! This happened even though the association and I had specced out very precise functional requirements for the new system. We just happened to overlook this detail.
The client and vendor worked together to address the issue and all is fine. But it was yet another example of how it's possible to overlook important details, even if you've done extensive work to cover everything.
My point is this: Even though we missed this detail, ultimately we were able to address it. And it's important to keep in mind, our goal is success, not perfection. There's always gonna be something!
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 […]