It's not the mistakes, but how you respond
Recently a client was complaining about a bug that had been introduced in the latest release of their software. She was very upset that the bug hadn't been caught before the release.
While I understand her frustration, bugs are a reality of software. The real test here is how the software company responds to notification of this bug. Will they acknowledge the problem? Will they fix it right away? Will they offer a workaround?
Software bugs are inevitable. Human error is inevitable. How the vendor responds to those errors is what really matters.
When my clients are selecting a new software system, part of the process is reference checks. One question I always recommend is something along the lines of "Tell me when there was a problem with your vendor. What happened and how did they resolve it?" How the vendor responded to any significant challenges will say a lot about the vendor.
The reality is there will always be errors, there will always be bugs, there will always be challenges with any software. What matters most is how the vendor responds to those issues.
(And by the way, this applies to all of us. We all make mistakes. It's how we respond to those mistakes that really counts.)
Wes's Wednesday Wisdom Archives
If it’s not in your AMS, why not?
If it’s not in your AMS, why not? I like to tell my clients they’ll […]
Why checkboxes and tags are awesome and dangerous
Why checkboxes and tags are awesome and dangerous One of the most common functions in […]
Don’t miss obvious engagement data
Don’t miss obvious engagement data What I’ve experienced with my clients over the years is […]
All data requires active management
All data requires active management It’s a simple fact of data management that is often […]
Documentation is critical for consistency
Documentation is critical for consistency There are so many reasons why documenting your data management […]
Consumer demands change and technology changes
Consumer demands change and technology changes When I work with clients on the selection of […]
Why I write
Why I write Thirty years ago, I started a new job as director of membership […]
DAN – The Data Analytics Network
DAN – The Data Analytics Network I’m a huge fan of users groups (both internal […]
Process before technology
Process before technology In a conversation with a client recently, I was reminded (yet again) […]
Opting out and communication preferences
Opting out and communication preferences Last week’s newsletter discussed the need for associations to collect mobile […]